4.5 KiB
Interview Preparation Guide
STAR Format
Structure answers as: Situation (context), Task (your responsibility), Action (what you did), Result (outcome).
Keep answers to 1-2 minutes. Be specific. End with what you learned or would do differently.
Ready-Made STAR Examples
1. [PROJECT_NAME] ([SKILL_DEMONSTRATED])
S: [CONTEXT - what was happening, what was the problem] T: [YOUR RESPONSIBILITY - what you specifically needed to do] A: [WHAT YOU DID - specific actions, tools, methods] R: [OUTCOME - measurable results, adoption, impact] Use for: "[QUESTION_TYPE_1]", "[QUESTION_TYPE_2]"
2. [PROJECT_NAME] ([SKILL_DEMONSTRATED])
S: [CONTEXT] T: [YOUR RESPONSIBILITY] A: [WHAT YOU DID] R: [OUTCOME] Use for: "[QUESTION_TYPE_1]", "[QUESTION_TYPE_2]"
3. [PROJECT_NAME] ([SKILL_DEMONSTRATED])
S: [CONTEXT] T: [YOUR RESPONSIBILITY] A: [WHAT YOU DID] R: [OUTCOME] Use for: "[QUESTION_TYPE_1]", "[QUESTION_TYPE_2]"
Common Tough Questions
"Why did you leave [previous company]?"
[PREPARE YOUR ANSWER - be honest, forward-looking, no negativity about former employer]
"You don't have [specific skill/experience]."
[PREPARE YOUR ANSWER - acknowledge the gap, bridge to adjacent experience, show willingness to learn]
"Where do you see yourself in 5 years?"
[PREPARE YOUR ANSWER - show ambition aligned with the role's growth path]
"What's your biggest weakness?"
[PREPARE YOUR ANSWER - genuine weakness with concrete mitigation strategy]
"Why this company specifically?"
Customize per company. Must reference: specific projects, company values, market position, or team structure. Never give a generic answer.
Questions You Should Ask Interviewers
About the Role
- "What does a typical week look like in this role?"
- "What would success look like in the first 6 months?"
- "What's the biggest challenge the team is facing right now?"
About the Team
- "How big is the team, and how do you divide work?"
- "What does the development/project lifecycle look like, from idea to production?"
- "How do you onboard new team members?"
About Tech & Growth
- "What's your current tech stack for [relevant area]?"
- "Is there room to grow into more architectural or strategic decisions?"
- "How does the team stay current with new tools and methods?"
About Culture (use these to prevent disappointment)
- "How would you describe the team culture?"
- "What does professional development look like here?"
- "Is there flexibility for remote/hybrid work?"
- "What's the balance between development/new projects and maintenance work?"
- "How would you describe the leadership style in this team?"
- "What do people who thrive here have in common?"
Phone/Video Interview Tips
- Have STAR examples written out (use this file)
- Keep a glass of water nearby
- Smile when speaking (it changes your tone)
- Ask for clarification if a question is vague
- It's OK to take 5 seconds to think before answering
- End with: "Is there anything else you'd like to know about my background?"
After the Application (Best Practice)
Follow-Up Etiquette
- Don't call to "stand out" or to learn more about the role post-submission - this risks a negative impression
- If the employer specified a timeline, respect it and wait
- If no timeline was given and significant time has passed (2+ weeks), a brief call to ask about status is acceptable
- If you have genuinely new, relevant information to share, a short follow-up is fine
Thank-You Notes
- When you receive any update (interview invitation, rejection, or status update), send a brief thank-you message
- Express appreciation for their time and the process
- Keep it short (2-3 sentences)
Roleplay Guidelines
When the user asks for interview practice:
- Ask which role/company to simulate
- Start with easy warm-up questions ("Tell me about yourself")
- Progress to role-specific technical questions
- Include 1-2 behavioral questions using the competencies from the job posting
- End with a tough question or curveball
- After each answer, give brief feedback: what worked, what to sharpen
- Suggest which STAR example would work best for each question