Ftyjtk

I hold a PhD in computer science. I've been travelling to conferences presenting my papers and sometimes as part of my teaching assistance duty, I had to give some very simple lectures to students.

I found a position as professor and researcher in a university, and I've been asked to deliver a "test lecture" on a subject I don't know to students from a different background than mine. There will be a body of professors evaluating my teaching skills as well.

I am in the process of preparing the lecture, and realised I am preparing it as a presentation. I was wondering, what should I keep in mind when preparing the lecture? I am used to present in front of (a lot of) people, so that is not a problem. I am also used to prepare presentations for my work, so I was wondering if there is something I should keep in mind while preparing/delivering a lecture which is different from delivering a presentation.

Thank you!

Off the top of my head, things that are different about a lecture rather than a presentation:

• You're not simply relating stuff you did to your peers : You're teaching people who know less about the topic than you do (even if you only know what you got from the textbook when preparing!). So think carefully about the intended audience, and how to explain the concepts at the right level. This will take time. Fortunately...


• You have time. You have an hour or more rather than (say) 15 minutes. This means you need to convey less content per minute, and you can spend more time building understanding step by step. Try to think about helping your students to develop a mental model that they can fit the new concepts into, rather than just telling them facts.


• Because the students are having to assimilate completely new concepts, don't overcomplicate - keep the necessary cognitive load to a minimum by omitting unnecessary details. Don't lie to them, but it's OK to say, for example, "this is a simplification, but it's a useful way to think about it at this level. We'll come back to it in more detail later.".


• Because you have more time, you'll also need to think more about (and spend more time on) structure. Think about pacing - don't talk for an hour. Instead, especially if you have a relatively small class, try to get some discussion going, or set an exercise. This may not be applicable for a demo lecture during recruitment, though.

If you have a small group (<25 or so, as may happen for postgrad courses) then it's more like a lesson than a lecture and things can be far more interactive.

The more you know about your audience the better your presentation/lecture/class will be (not just on this occasion).

Will this be a regular class in a regular course, or a simulated class with some students and some volunteers or (I hope not) a group of professors pretending to be students?

Can you politely ask your prospective employer for information about your audience and the context? Is this a regular lecture? For what course, at what level? What have the students covered recently?

At the lecture, be sure to involve the students. Check that they understand the prerequisites for what you are covering. Ask if your notation matches what they are familiar with. This will take time. Don't worry about "covering all the material" - pay more attention to keeping the students engaged.

IMHO, Professors tend to teach into one ear, and most of it comes out the other ear. You'll be lucky if the brain in the middle processes the information.

I would focus on giving your class the opportunity to learn something they would never know on their own.

That being said, if you want the position, perhaps it might be better to find out what criteria you're being evaluated on, and what would be a 10/10 score for each category? In academia, positions are more about whether or not you satisfy some or other criteria than actual learning. I personally love the Stamford computer science teachers because of their focus on real-world problems and understanding their audience.

Is it true that you have been asked to deliver a "test lecture" on a subject you don't know?

I find it highly unusual that you would be asked to lecture on something which you do not know well.

Lecture does a pretty poor job of conveying information. You want to think about crafting an educational experience for your students. A good term to google is "active learning".

As a student one format that I really enjoyed was:

1. Overview and background on topic


2. Explanation of problem


3. Multiple examples


4. Let students try one problem, usually this was different to the other problems, like with an edge case.


5. Walk through problem with students.

For example:

1. Overview of Automata in CS (what are they and why are they useful?)


2. Explanation of Finite Automata


3. Examples


4. A slightly trickier one for students to try


5. Walk-through

Change depending on time and some topics take multiple lectures to cover. Hope this is helpful ^.^

I would like to stress Flyto's answer's last point — especially as OP stated "[I] realised I am preparing it as a presentation".

A lecture is (at least to me) not a keynote; you are not here to deliver knowledge (you then could just have them read a good book instead), but to make students gain knowledge/skills. There is a slight difference. This implies using educational techniques (pop-up quizz, Q&A, "off-line" exercises), and a lot of interactions.

It is then better (in an ideal world where you are not constrained by the limited number of lectures you can give to teach a subject) to teach well "5 points" only and students get 80% of it, rather than teaching "10 points" and students getting only 30% of it.
You should thus design your lecture keeping in mind: "Is this making my student get more knowledge out of my lecture?"

However, a test-lecture is not quite like a lecture neither. Your objective is not to make students get the most of your lecture, but to make attending professors think you are a good teacher. (The former is just one — among others — objective coming from the latter.) I would thus keep following points in mind:

• make sure you master the subject you're teaching. You don't want to be telling false things (unless if you explicitly state it's a simplification for the sake of the argument, as discussed by Flyto).


• 
  demonstrate a large range of education techniques… but avoid turning your lecture into a showcase neither.


• show that you care about students: interact with them, make them feel safe when they're asking questions, etc.


• 
  don't care about what students get from this lecture: I think it is more important that you don't "lose" any student (by, for example, teaching only "four points"), than wanting to make geniuses in one hour.


• HOWEVER, you also want to show attending professors that you are a smart person. So you might not want to only skim the surface, but get technical at some point.


• depending how you "feel" attending professors, either ignore them or involve them. I would rather advise the former. A good idea to know how you should involve them is to check where they are seating: in the back of the room (lecture is for students only — they are here only to observe) or at the front row (lecture is for them — students are just here to "fill the room").

I hope this helps. Here are some more concrete advice:

• During the first 3–5 minutes, create a connection with the students: tell them about who you are and what is going to happen during the lecture, that they can ask questions… but most importantly, make them speak: what's their background, what they've learned so far, etc.


• Dedicate a good 10–15 minutes to "funnel" into the lecture's subject: start with a very broad view of your discipline and zoom step by step into the subject of the lecture, so that it is linked to something and doesn't appear out of nowhere.


• 
  Pop-quizz at 2/3rd of the lecture.


• Make them learn a small but non-trivial technique (depending on the context), so that you can easily quantify your added value ("They didn't knew how to do this, now they know"). The idea is that it's non-trivial (thy couldn't have easily figured by themselves), but easy enough so that 85%+ of students get it within 10mins.


• Give examples. Tons of real-live examples, real case application of what you're teaching.


• Spare 5 minutes at the end to wrap up and answer potential questions.


• 
  Finish on time.