The 4 Dimensions Every Recruiter Evaluates
No matter the role or company, interviewers assess four things: (1) Can you do the job? (2) Will you do the job? (3) Will you fit the team? (4) Are you worth the investment? Your preparation must address all four — technical skills alone are not enough.
- Technical competence — domain knowledge, problem-solving, tools
- Motivation & drive — why this role, why this company, career goals
- Cultural fit — communication style, collaboration, values alignment
- Self-awareness — understanding your strengths, weaknesses, and growth areas
Phase 1: Research (3–5 Days Before)
Most candidates skip research and wonder why they don't get offers. Serious candidates research the company, the role, and the interviewer before walking in.
- Read the company's About page, recent news, and LinkedIn posts
- Study the job description line by line — every bullet is a question signal
- Check Glassdoor and AmbitionBox for actual interview questions at that company
- Research your interviewer on LinkedIn — find common ground or shared experience
- Prepare company-specific answers: 'Why do you want to join us?'
Phase 2: Your Story (The 'Tell Me About Yourself' Framework)
This is the most asked question and the most wasted opportunity. Use the Present → Past → Future structure:
- Present: Your current role and key responsibilities (2 sentences)
- Past: 1–2 career highlights that are relevant to this role
- Future: Why you are excited about this specific opportunity
- Total length: 90 seconds. Practice until it sounds natural, not rehearsed.
Phase 3: Master the STAR Method
Every behavioral question ('Tell me about a time when…') should be answered using STAR: Situation, Task, Action, Result. Prepare 6–8 STAR stories that can flex to cover different question types.
- Situation: Set the context briefly (1–2 sentences)
- Task: What was your specific responsibility?
- Action: What did YOU do? (Use 'I', not 'we')
- Result: Quantify the outcome — numbers, percentages, time saved
Phase 4: Technical Preparation
For technical roles, preparation must be structured. Do not just skim topics — practice applying them under time pressure.
- Week 1: Core fundamentals (data structures, SQL, programming basics)
- Week 2: Problem solving on LeetCode (Easy + Medium)
- Week 3: System design concepts and case studies
- Week 4: Mock interviews — simulate real conditions with AI or a peer
- Day before: Light review only. No new topics.
On the Day: Confidence & Communication
The way you communicate matters as much as what you say. Recruiters make decisions in the first 2 minutes based on your confidence and presence.
- Speak at 120–150 words per minute — not too fast, not too slow
- Eliminate filler words: 'um', 'uh', 'basically', 'you know'
- Maintain eye contact 70% of the time
- Structure every answer: state your approach before diving in
- End each answer with a clear conclusion — do not trail off
Salary Negotiation (The Moment Most Candidates Give Up Money)
Never give a number first. When asked about salary expectations, use this framework:
- 'Based on my research and experience, I'm targeting X–Y range, but I'm flexible depending on the complete package.'
- Research market rates on Glassdoor and Levels.fyi first
- Always negotiate — 78% of employers expect candidates to negotiate
- Negotiate on base, bonus, stock, title, remote flexibility — not just one number
Common Interview Questions & Answers
Q1. Walk me through your resume.
I'm a [role] with [X] years of experience in [domain]. Most recently at [Company], I [key achievement with metric]. Before that, [brief previous highlight]. I'm excited about this role at [Company] because [specific reason].
Keep this to 90 seconds. Rehearse it until it sounds natural.
Q2. What is your greatest weakness?
I tend to over-prepare before delegating work to my team. I've been actively working on this by setting clear handoff criteria and check-in points, which has improved my team's velocity by 30%.
Choose a real weakness. Show self-awareness AND the steps you're taking to improve.
Q3. Why do you want to leave your current company?
I've had a great experience at [Company] and learned a lot, especially in [area]. I'm looking for an opportunity that offers [growth area / technology / leadership], which I see strongly in this role.
Never speak negatively about your current employer. Always frame it as seeking growth.
Q4. Where do you see yourself in 5 years?
I see myself as a strong technical leader with deep expertise in [domain]. In the next 5 years, I want to grow into [specific direction] and contribute meaningfully to the team's strategic goals.
Align your 5-year vision with what the company can offer.
Q5. Do you have any questions for us?
Yes — what does success look like for this role in the first 90 days? And what's the biggest challenge the team is working through right now?
Always have 2–3 prepared questions. Never say 'No, I think you've covered everything.'
Common Mistakes to Avoid
Not researching the company — sounds generic and unprepared
Memorising answers word-for-word — sounds robotic in delivery
Using 'we' instead of 'I' in achievement stories — hides your contribution
No quantified results — 'I improved sales' vs. 'I grew sales by 40% in Q3'
Talking too long — ideal answer length is 90–120 seconds per question
Not asking any questions at the end — signals low interest
Arriving unprepared for salary negotiation
Expert Tips
Prepare a 'brag file' — a running list of achievements, metrics, and wins you can draw from
Record yourself answering questions and watch it back — painful but transformative
Mock interview with an AI tool like SpeakWell AI to practice under pressure
Ask for feedback after every interview, even rejections
Send a thank-you email within 24 hours of the interview
Pre-Interview Checklist
10 itemsFrequently Asked Questions
How many days do I need to prepare for an interview?
For most roles: 2 weeks minimum. Entry-level roles: 1 week. Senior or technical roles: 3–4 weeks. Start preparation the moment you apply, not when you get the call.
Is it okay to refer to notes in an interview?
In virtual interviews: briefly noting key points is acceptable. In person: avoid it. Prepare enough that you don't need to.
How do I handle a question I don't know the answer to?
Say: 'I don't know the exact answer, but here's how I'd approach figuring it out…' Show your problem-solving process, not just your knowledge gaps.
Should I send a thank-you email after an interview?
Yes — always. Within 24 hours. Keep it brief: thank them, reference something specific from the conversation, and restate your interest.
Ready to ace your next interview?
Practice with SpeakWell AI. Upload your resume → get resume-based questions → practice with AI interviewers → improve communication → track progress → get instant AI feedback.