Skip to content

Commit

Permalink
Update index.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@Tracey-M
Tracey-M authored Sep 5, 2023
1 parent 558c92e commit b7e198b
Showing 1 changed file with 1 addition and 133 deletions.
134 changes: 1 addition & 133 deletions professional_development/Mod3/index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,138 +6,6 @@ title: Module 3 Professional Development
* [Mod 3 PD Overview](./Pd_overview)
* [Resumes and Portfolios](./resume_and_portfolio)
* [Cover Letters Made Easy](./coverletters_made_easy)
* [Interview Preparation- Putting It All Together](
* [Interview Preparation- Putting It All Together](./Mod3/Interview_Preparation)

## Interview Preparation
Putting It All Together

### Overview
You've done the groundwork to prepare for your job search: refining your story, crafting your resume, and building your portfolio. Now is the time to put all of these things into motion and talk about why you're the right person for the job.

### Learning Goals
Identify how to prepare and research prior to an interview
* Ideate and try out solutions to improve your current interviewing strategy
* Understand how to answer interview questions through specific strategies

* [Slides for this lesson](https://docs.google.com/presentation/d/19v08-f77qv6HTMR3teiuv_SmXMHzpydHrdo144WYG_8/edit?usp=sharing)
* After you complete this lesson, you'll synthesize your learning in this [Exit Ticket](https://forms.gle/1WHVG6iiHX6bkfS97) by Thursday of Week 4.


#### Starting off Strong: Tell me about Yourself
This request for information is typically at the very beginning of an interview. It's an opportunity to provide the interviewer with insights into your qualifications and fit for the role.

<iframe width="560" height="315" src="https://www.youtube.com/embed/4TL2YnGS9AQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

### Preparation Strategies
There are many ways to prepare for interviews. The key to all interviews is **knowing who you are and how to talk about yourself.** Today, we'll go through 4 particular tips to help with this process:

1. Answer the whole question
2. Tell stories
3. Know how to talk about your experience
4. Research & prep


<iframe width="560" height="315" src="https://www.youtube.com/embed/w1ncXtkOqOo" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

#### Strategy #1: Answer the whole question
Pay attention to what the question is asking as well as any *subtext* inherent in the question. Let's look at an example:

<iframe width="560" height="315" src="https://www.youtube.com/embed/exQySTPJ490" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

* How do you deal with failure?

This question is asking you to:
* **Acknowledge that you fail.** You're not perfect, you have experienced failure. It's okay to be transparent about that
* **Describe what you do after you fail.** How do you pick yourself back up? What next steps do you take?
* **Give specifics.** Providing specifics and responding to questions in the form of a story can help them understand and remember your response better.


#### Strategy #2: Use the [STAR Method](https://www.indeed.com/career-advice/interviewing/how-to-use-the-star-interview-response-technique)
<iframe width="560" height="315" src="https://www.youtube.com/embed/6jfHij9Kj-4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
Use this as an opportunity to tell stories about your relevant experience. A great template to use to plan out your stories is the STAR method:

* **Situation:** The interviewer wants you to present a recent challenge and situation in which you found yourself.
* **Task:** What were you required to achieve? The interviewer will be looking to see what you were trying to achieve from the situation. Some performance development methods use “Target” rather than “Task”. Job interview candidates who describe a “Target” they set themselves instead of an externally imposed “Task” emphasize their own intrinsic motivation to perform and to develop their performance.
* **Action:** What did you do? The interviewer will be looking for information on what you did, why you did it, and what the alternatives were.
* **Results:** What was the outcome of your actions? What did you achieve through your actions and did you meet your objectives? What did you learn from this experience and have you used this learning since?

Example:
* Tell me about a successful project that you've worked on.

In this example, focus on establishing the situation or scenario for the project. Set the stage for the listener -- how many people were involved in this project? What was the timeline? What were the main technologies used?

Then move into the task/target and discuss the objective of the project. What was the purpose? Who was the user?

Then, walk through all of the actionable steps you/your team took to meet the objective of the project. What successes did you have? What challenges did you run into? What steps did you take to overcome those challenges?

And finally, what were the results of this project? What were you able to accomplish? What would you have done differently?


#### Strategy #3: Know how to talk about your experience
There are 2 elements to keep in mind here as you present your software and work experience:

* Discussing your Turing experience as professional experience
* Your previous work experiences

When talking about Turing:

* Do:
* Give a high-level description
* Talk about Turing as *professional experience*
* Highlight the differences between Turing and other code schools

* Don't assume your interviewer knows anything about Turing. That means not using Turing-specific jargon (module, inning, cohort, DTR, etc.)

Example:

Instead of saying “In Module 1, when I was working on my first paired project…” what could you say?

Consider how you would respond to this question:

"I’ve never heard of Turing. What did you focus on there? What’s the structure of the program? How did it prepare you for this career?"

For your previous professional experiences and background, unpack the transferable skills you have that apply to the job. Consider how your specific experiences make you uniquely qualified compared to other candidates. For example, have you worked with customers before in any capacity? Talk about it. Have you ever had to deliver on tight deadlines? Yes, you're a Turing student -- talk about that. Have you had to communicate with different teams? Talk about it.

#### Strategy #4: [Research and Prep](https://www.glassdoor.com/blog/7-research-job-interview/)
<iframe width="560" height="315" src="https://www.youtube.com/embed/Hfybq4a-2E8" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
1. Make sure to start by researching your company (you should do this before you submit your application anyway). Know what their tech stack is

2. Keep a running doc where you can keep track of common interview questions and specifics that you can draw from to answer these questions. Outline your stories here about projects, team situations, successes, and failures. Make sure to review these before each of your interviews.

### [Do you have any questions for me?](https://www.keyvalues.com/culture-queries)
<iframe width="560" height="315" src="https://www.youtube.com/embed/qP0Sl7qs6Jc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

At the end of almost every interview, you'll be given an opportunity to ask questions. Use this time to get a better understanding of the company, what it would be like to work there, and gauge whether this role is a good fit for you.

### Putting it into Practice
1. To continue preparing for interviews, create an interview prep document or story bank to write out answers by telling stories about various experiences.
2. Review this Story bank doc that includes templates, examples, and interview tips.
3. Use prompts below or from the story bank doc and write about one behavioral and one project question to start with and the STAR method:

* Pick a successful project and write about it with the STAR method (What was the situation/scenario of the project? What was the task/target of the project? What action
steps did you take? What were the results?):
* Write about a time you failed and what you learned from that experience:
* Write about how you've approached working with a team using a specific example:
* What other stories will you prepare to share?
* Do some research into your top companies' tech stacks; what do you already know? What can you compare to your own learning? What do you need to learn more about?
* Using this [interview prep resource guide](/resources/interview_prep_resources), pick out at least 3 resources you will use to prepare for interviews as well as 3
behavioral questions you could practice.

**Other Tips:**
* In your interview pre doc keep track of technical concepts you're practicing, behavioral answers, and feedback.
* Review:
* Your professional story
* Feedback you've received
* Your projects; Go through your projects to reflect on:
* One specific bug
* Something that was really hard
* Something that was rewarding
* Any interesting struggles/insights about the collaboration process
* Your Flower Exercise
* Your strengths
* Your areas of growth
* DTR Memos
* Retro notes
* Eval notes
## Check for Understanding
After you've completed this lesson, submit this [exit ticket](https://forms.gle/1WHVG6iiHX6bkfS97) by **EOD Thursday of Week 4.**

0 comments on commit b7e198b

Please sign in to comment.