Most candidates fail interviews not because they lack skill, but because they walk in unprepared for the shape of the process. The 2026 hiring landscape punishes improvisation. AI-assisted screening now sits between the recruiter and the hiring manager at roughly 60% of mid-to-large employers, so your first real evaluator is often a model scoring transcripts against a rubric. In-person final rounds have quietly returned at companies burned by remote-only hires who never gelled with the team. Loops are longer too — five and six-stage processes are the norm at well-funded employers, up from three or four in 2022.

The mental shift to make: interviewing is a skill, not a verdict on your existing competence. Two candidates with identical resumes get wildly different outcomes because one practiced the format and the other treated each round like a pop quiz. Strong engineers tank live coding rounds because they never rehearsed thinking out loud. Excellent operators flame out in panels because they kept reinventing their stories. Treat each stage as its own exam, and your hit rate goes up dramatically.

Stage 1 — The Recruiter Screen (20–30 minutes)

A recruiter is calling to verify three things: that you’re real, that your salary expectations match the budget, and that you can talk about your last job coherently. They aren’t evaluating depth — they’re filtering out chaos. The biggest mistake is treating the call casually and rambling for four minutes on “tell me about yourself.” The second is dodging the salary question, which reads as inexperience or fear.

Lead with a tight 90-second introduction: current role and scope, one signature accomplishment with a number, why you’re looking, what you want next. Name a salary range — don’t dodge — and ask one substantive question about the team.

Example question: “What’s the salary range budgeted for this role?”

Weak answer: “I’m flexible, whatever works.”

Strong answer: “Based on the scope you described and my last three years of comparable work, I’m looking in the 1.8 to 2.2 million KES range for base, and I’d like to understand the total comp picture before locking that in. What’s the band you’re working with?”

Other common questions: “Why are you leaving?” (frame it forward — what you’re moving toward) and “What attracted you to us?” (have one specific reason tied to a product decision). Prep: 60 minutes writing your 90-second pitch, then record yourself three times and trim every filler word. Do the same for the salary line until it sounds boring.

Stage 2 — The AI-Powered Pre-Screen

Increasingly common: a recorded interview answered into a webcam, scored by an AI on clarity, structure, keyword density, and sometimes sentiment. Some employers also use async coding platforms that watch your tab-switching. What the system is really evaluating is whether your answers contain the rubric’s expected signal — concrete actions, measurable outcomes, role-relevant vocabulary — in a coherent arc.

The most common mistake is treating it like a casual video chat — trailing off, restarting sentences, forgetting to name the result. The second is overcompensating by sounding robotic. The system isn’t fooled by jargon stuffing; it penalizes incoherence more than it rewards keywords.

Example question: “Tell us about a time you handled conflicting priorities.”

Strong STAR answer: “At my last role our team had committed to a Q3 platform migration and a new analytics dashboard for the CMO, both due in eight weeks. (Situation) I owned delivery for both. (Task) I ran a half-day prioritization session with stakeholders, mapped dependencies, and proposed shipping the dashboard at 70% scope to unblock the migration. (Action) We delivered the migration on time and the dashboard two weeks later at full scope. The CMO publicly thanked the team in the all-hands. (Result)”

Speak slowly, look at the lens, and hit Situation-Task-Action-Result audibly. Don’t try to game the model — clean structured answers win. Prep: two to three hours recording yourself answering the canonical behavioral questions until each lands in 90 to 120 seconds with a clean STAR arc.

Stage 3 — The Hiring-Manager Conversation

This is where most offers are won or lost. The hiring manager is asking “will I enjoy working with this person, and will they make my life easier?” under the guise of competence questions. They are projecting forward — imagining you in their Tuesday standup, in a tough Slack thread, on a deadline crunch. Likability and lower-case-r reliability do as much work here as skill.

The most common mistake is over-indexing on technical depth and forgetting to show ownership and judgment. The second is being too rehearsed — canned answers trigger distrust. Aim for prepared but conversational.

Have three prepared stories — a project you’re proud of, a conflict you navigated, a failure you learned from. Roughly 80% of behavioral questions are variants on those three.

Example question: “Tell me about a time you disagreed with a manager.”

Strong answer: “My manager wanted to ship a feature in a sprint I thought was two sprints of work. Rather than push back in the meeting, I built a one-page risk doc — three concrete failure modes, two with prior-incident evidence — and walked him through it 1:1. He agreed to a phased rollout. We shipped the safer version on time and the full feature three weeks later with zero rollbacks.”

Other questions to prepare: “What’s a decision you’d make differently?” and “How do you handle being wrong?” Prep: three to four hours writing your three core stories, then practice telling each to a friend until you can flex the framing on demand.

Stage 4 — The Technical / Functional Round

For engineering, expect a live coding session, a system-design conversation, or a take-home project. For non-engineering: a case study, a written exercise, a portfolio review, or an analytical problem worked out loud. What’s really evaluated is your reasoning process under mild pressure — not whether you arrive at the perfect answer.

The most common mistake is silent thinking — interviewers can’t score what they can’t hear. The second is treating every problem as adversarial. Ask clarifying questions, state assumptions, check in. The third is panicking when stuck.

Tip: Always think out loud. Interviewers are evaluating your reasoning, not just the final answer. When you get stuck, narrate the stuck-ness: “I’m second-guessing whether to optimize for read or write throughput here. Let me consider both.”

Example question (system design): “Design a URL shortener that handles 10K writes per second.”

Strong opener: “Before I sketch architecture, let me confirm three constraints — read-to-write ratio, acceptable latency at p99, and whether we need analytics on the redirect path. Assuming a 100:1 read-write ratio and 100ms p99, I’d start with a key-value store fronted by a CDN-cached read path, and reserve the relational store only for analytics aggregation.”

Prep: for technical roles, six to ten hours over two weeks on timed practice problems, plus one mock with a peer for live feedback. For non-engineering case rounds, three to four practice cases out loud.

Stage 5 — The Panel / Values Round

Multiple stakeholders join, sometimes over a half-day onsite. The same questions repeat. They’re checking consistency, and testing how you behave when tired. By interviewer four your guard is down — that’s the point.

The biggest mistake is reinventing your stories. If you told a different version of the conflict story in round two, the panel debrief catches it and reads it as embellishment. The second is treating the junior interviewer with less energy than the senior one. Panels share notes; the IC’s “off vibe” feedback is often the kill signal.

Repeat your prepared stories confidently. Vary framing to match the question, but keep the facts identical. Treat every interviewer as a decision-maker.

Example question: “What do you do when a teammate isn’t pulling their weight?”

Strong answer: “First I check whether I’m reading it right — workload, context, what they’re blocked on. Last year a teammate was missing standups and I assumed disengagement; turned out he was covering for a sick parent. We re-scoped his sprint, I picked up two tickets, and he was back at full capacity in three weeks. If after a real conversation someone isn’t delivering, I escalate to the manager with specifics — not a complaint, a pattern.”

Prep: schedule four 45-minute mock conversations back-to-back so the panel day feels familiar, not novel.

Stage 6 — Salary Negotiation

Negotiation isn’t a separate calendar stage, but it deserves the same prep as a technical round. Bring up money explicitly once during the recruiter screen as a range, then again only after the offer is verbal or written. Negotiating before leverage — before they’ve decided they want you — is how candidates get pre-screened out.

When asked “what’s your expected salary?” after the recruiter screen, deflect: “I’d like to understand the role fully before fixing a number. The recruiter and I are aligned on the band — happy to revisit at offer stage.”

The anchoring move: when the offer arrives, name a number 15 to 25% above what you’d actually accept, anchored in market data. “Based on comparable offers and the scope you’ve described, I was hoping to land closer to 2.4 million base.” Then go silent. Silence does enormous work here.

Negotiate total compensation, not just base. Equity (vesting cliff, refresh policy, strike price), signing bonus (often the most negotiable line — recruiters have discretionary budget), remote allowance, learning stipend, PTO, and start date are all on the table. Get every concession in writing before you sign.

When the offer is meaningfully below market: name the gap calmly, share evidence (Levels.fyi, Glassdoor, a competing offer), and ask what flexibility exists. About 70% of below-market offers move when you push back professionally. The other 30% don’t — and that tells you how they’ll value you for the next four years.

Interviewing Remotely or on Video

Most loops include at least two video rounds, and the medium silently penalizes candidates who don’t prepare. Get your camera at eye level — stack books under the laptop if needed — so you’re not filming up your nose. Light your face from the front; backlight turns you into a silhouette and tanks AI screening scores. Use a wired headset or quality earbuds; laptop mics pick up keystrokes and read as unprofessional.

Body language carries less signal on video, so compensate by nodding visibly, leaning forward, and pausing before answering rather than overlapping. Look at the camera lens, not the face on screen.

Have a contingency plan for technical issues. If video drops, switch to audio-only rather than fumbling to reconnect. Keep the recruiter’s phone number open. When something breaks, narrate calmly: “Looks like my video froze — happy to dial in by phone.” Grace under technical pressure is itself a signal.

The Questions You Should Ask the Interviewer

Every interview ends with “do you have questions for us?” and your answer is being scored. Zero questions reads as disinterest. Five strong ones reads as seriousness. Prepare across four categories.

Role clarity: “What does success look like at six months and eighteen months?” Listen for a concrete answer versus vague aspirations. Vague answers mean the role isn’t well-defined and you’ll be set up to fail.

Team and operating rhythm: “How does the team make decisions when there’s disagreement?” or “Walk me through last week.” Listen for whether the answer sounds like collaboration or chaos.

Growth and trajectory: “Who has been promoted in the last year, and what did that path look like?” Listen for concrete examples versus hand-waving about “lots of opportunity.”

Red-flag probes: “Why is the role open?” and “What’s the biggest challenge facing the team?” A manager who admits a real challenge is usually better than one who pretends everything is fine.

After the Interview

Send a same-day thank-you email — three sentences, referencing something specific the interviewer said. Recruiters tell us this still sways close decisions, and almost no one does it. Send one per interviewer.

Following up: one polite check-in after the recruiter’s timeline has passed, then silence. Two follow-ups in a week reads as anxious; one well-timed nudge reads as professional. If you have a competing offer, share it once, factually, with no theatrics.

Handling rejection productively: ask for feedback in writing. About 30% of recruiters will give you something useful — save those notes. The same gap will surface in your next interview, and next time you’ll be ready. Treat each loop as a data point, not a verdict on your worth.