Add Interview Questions and Structure #393
Conversation
module6/interviews/questions-4545.md
Outdated
| * Describe the 4 Pillars of OOP | ||
| * What is HTTP and give a brief definition? | ||
| * Explain Routing in .NET Core MVC? | ||
| * What happens if the inherited interfaces have conflicting method names? |
There was a problem hiding this comment.
The wording of this question feels a bit off to me. I have only used inherited for classes, and then use implemented for interfaces.
Maybe we reword to "What happens if a class implements two interfaces that have conflicting method names?"
There was a problem hiding this comment.
I updated the wording, and left it a bit confusing still. This is one that I think will be difficult for students and will require them to ask questions of the interviewer to understand what is being asked. 🤷♀️
| * Describe your strengths. How have you seen these in practice as a developer? | ||
| * Describe a time when you received feedback that you were surprised by. What did you do with that feedback? | ||
| * Tell me about a successful presentation you gave and why you think it was a hit. | ||
|
|
There was a problem hiding this comment.
Because of the week's focus, I suggest we add "What questions do you have for me?"
| You can ask these questions in any order. There are some questions each week that we know students will not be able to answer - this is by design to see how they exit a tough situation. Keep track on notes on [this tracker](https://docs.google.com/spreadsheets/d/1eMtwW-06Wv0YAdAnZVm5k8_VFNKEKzQeq24kGxMTHbQ/edit?usp=sharing), please! | ||
|
|
||
|
|
||
| ## Week 1 |
There was a problem hiding this comment.
I think we should probably set a passing bar for these. Maybe 6/10?
There was a problem hiding this comment.
Maybe there is also a half point structure or something for not knowing the answer, but gracefully exiting and sharing something related that you do know?
There was a problem hiding this comment.
I'm a little cautious of setting a minimum score - what if students give really thorough answers that take up more time? I don't want to penalize someone who doesn't get through all of the questions, if their given answers are good. Maybe we reduce the number of questions?
I do think there are points on the table for graceful exits. I think a good graceful exit might even earn full points - there are definitely questions included that I do not expect students will be able to answer.
There was a problem hiding this comment.
Hmmm, that's a good point. That is tricky, I agree with you that we want to make sure students have time to answer thoroughly.
I do think it's helpful to have a rubric before so students know they don't have to get every answer correct to pass, and that graceful exits get points.
But we could also say something along the lines of "You don't need to get all questions correct to pass and you can get credit for a graceful exit" then keep track of the scores and come up with a passing score after.
| * Tell me about a time you failed. How did you deal with the situation? | ||
|
|
||
|
|
||
| TODO: Update so that students can demonstrate Talking While Coding |
There was a problem hiding this comment.
I had originally thought that these interviews would be more leetcode style interviews vs questions. But in hindsight, I think it's good to have both. What do you think about maybe doing the first two weeks question style, and then the last 3 weeks more focused on Leetcode? And we can let folks know that as they are working on freethrows and pair interview practice in the early weeks.
We could even set up a structure where they ask each other these questions during weeks 3-5 in addition to doing a leetcode style interview with an instructor? I like these questions, but I think coding while someone is watching is also an area we could give a lot of helpful feedback in.
There was a problem hiding this comment.
Definitely - after I put all these questions together, I remembered that we wanted to focus Week 4 on talking while coding 🙃 So, that week I think will definitely be a code challenge.
Week 3, our focus was going to be 'using concrete examples', so I think that having questions will be give students more chance to show that skill.
What if we switch weeks 3/4 so that we do question, question, code, question, code? That breaks it up some, and let's us do a mix of both on either side of the holiday break?
There was a problem hiding this comment.
I like that plan! So switching talking while coding and using concrete examples.
I think with this we are pretty close (or there) on:
Weeks 3, 4 and 5 need some work so that we can tie them back to that week's PD focus.