Interview Process Steps Explained: All 9 Stages, Start to Offer

Last updated: August 2026

Quick Answer

A standard hiring process runs nine steps: application, resume screening, recruiter screen, assessment or take-home, hiring manager interview, team or panel interviews, final round, references and background checks, then offer and negotiation. Published recruiting benchmarks put the typical United States hire at roughly 44 days from opening to acceptance, with about 24 to 30 days from the first interview to a signed offer. Not every employer runs all nine, but they run them in this order. Rehearse each step separately in OphyAI Interview Practice and use OphyAI Interview Copilot to keep answers structured on live Zoom, Teams and Meet rounds.

#	Step	Who runs it	Typical length	What decides it
1	Application	Software plus a recruiter	Minutes to submit	Whether your resume matches the posting’s requirements
2	Resume screening	Recruiter or coordinator	2-9 days	Relevance, recency, and how easy your resume is to read
3	Recruiter screen	Recruiter	20-30 minutes	Motivation, level fit, compensation alignment, logistics
4	Assessment or take-home	Automated or async	45 minutes to a few hours	Whether your work meets the bar without an interviewer present
5	Hiring manager interview	The person you would report to	45-60 minutes	Whether you can do the job and they want to work with you
6	Team or panel interviews	Peers and cross-functional partners	2-4 hours total	Depth, collaboration, and specific skills
7	Final round	Senior leader or committee	30-60 minutes	Level calibration and any remaining doubt
8	References and background checks	HR or a vendor	3 days to 3 weeks	Verification, not persuasion
9	Offer and negotiation	Recruiter	1-7 days	Band, level, and what you asked for

This page is about the shape of the whole process. If your question is how many interviews you will sit rather than what happens between them, read how many rounds of interviews is normal instead.

How Long the Whole Process Takes

Published benchmarks for 2026 put the average United States hire at about 44 days from opening the requisition to an accepted offer, at an average cost to the employer of roughly $4,700, according to SHRM’s recruiting benchmarking work. Time to hire measured from the candidate’s first interview to acceptance is shorter, commonly reported at 24 to 30 days, while time to fill, which includes the sourcing and posting period before you appear, averages around 45 days.

Situation	Typical end-to-end length
Entry-level roles	30-45 days
Technology companies	35-50 days
Financial services	40-48 days
Healthcare organisations	42-49 days
Government and public sector	Often more than 55 days
Senior and leadership roles	Nearly 40 percent take more than 90 days

Two stages absorb most of the calendar: screening and interviewing each average around 8 to 9 days, largely because of scheduling rather than deliberation. That has a practical consequence. If you want to move faster, the highest-leverage things you control are giving wide availability, replying within the hour, and asking the recruiter at step 3 for the full list of remaining steps so nothing surprises you in week four.

Step 1: The Application

What happens: you submit a resume through an applicant tracking system, sometimes with screening questions about work authorisation, location, licences and salary expectations.

What decides it: the match between your resume and the posting’s stated requirements. Screening questions are often knockout questions, so answer them accurately rather than optimistically.

What to do: mirror the posting’s own vocabulary for the skills you genuinely have, put the most relevant experience in the top third of page one, and keep the formatting simple enough to parse. See our ATS-friendly resume guide for the specifics.

Step 2: Resume Screening

What happens: a recruiter or coordinator reviews the shortlist, usually for well under a minute per resume, against a small number of must-haves.

What decides it: relevance and recency. A screener is asking one question, which is whether you have done something close to this job recently enough to matter.

What to do: make the answer to that question visible without searching. If you are changing industries, put a two-line summary at the top that translates your experience into the language of the target role.

Step 3: The Recruiter Screen

What happens: a 20 to 30 minute call covering your background, why you are looking, why this company, your compensation expectations, location and notice period.

What decides it: whether you are motivated, correctly levelled, and inside the salary band. Very few candidates fail this on substance; many fail it on a vague “why this company” or an unresearched number.

What to do: prepare a 60-second background answer and a specific reason for this employer. Ask three questions of your own here: the full list of remaining steps, the level the requisition is written for, and the posted salary range. Rehearse the whole call in OphyAI Interview Practice and read the transcript back for filler.

Step 4: Assessments and Take-Homes

What happens: a coding assessment, a situational judgment test, a personality or work-style questionnaire, a recorded on-demand video interview, or a take-home project.

What decides it: for coding assessments, a score threshold, sometimes with hidden test cases. For situational judgment and work-style tests, consistency across items. For take-homes, whether the work runs, is tested, and is scoped sensibly. For recorded video rounds, whether your answer reaches its point quickly and includes a specific example.

What to do: read the instructions on your own invitation rather than a forum post about someone else’s, because time limits, attempt counts and deadlines vary. For a take-home, write the summary document last and make it say what you built, what you deliberately left out, and what you would do next.

Step 5: The Hiring Manager Interview

What happens: 45 to 60 minutes with the person you would report to, mixing your background, two or three deep questions about your actual work, and their description of the role.

What decides it: whether they believe you can do the job, and whether they want to work with you. This is the single most predictive step in most processes.

What to do: prepare to talk for ten minutes about one project you owned, including the part you would change. Ask what the first 90 days look like and what would make this hire a success at six months. Drill it in behavioral format in OphyAI Interview Practice and cut each story to under two minutes.

Step 6: Team and Panel Interviews

What happens: two to four interviews with peers, cross-functional partners, and sometimes a skip-level manager. In technology this is where coding and system design rounds sit; in consulting, case interviews; in banking, technicals; in healthcare, clinical scenarios.

What decides it: depth in your specialism plus evidence you are straightforward to work with. Panels look for consistency across interviewers, so contradicting yourself between rounds is a real risk.

What to do: ask for the names and roles of your interviewers in advance and prepare a different question for each. Use one story per competency rather than the same story four times.

Step 7: The Final Round

What happens: a conversation with a senior leader, a bar-raiser style interviewer from outside the team, or a hiring committee review with no candidate present.

What decides it: level calibration and any doubt left from earlier rounds. Sometimes the decision has effectively been made and this step is about closing you.

What to do: treat it as substantive until proven otherwise. Have a view on the company’s direction and one thoughtful question about a challenge the business is facing.

Step 8: References and Background Checks

What happens: reference calls, employment and education verification, criminal background checks, and in regulated industries credit checks, fingerprinting and licence verification.

What decides it: nothing, if you have been accurate. This step verifies rather than persuades. It is also the step most likely to add unexpected weeks in banking, healthcare and government roles.

What to do: warn your referees before you list them and tell them what the role is. Make sure your resume’s dates and titles match what a verification vendor will find.

Step 9: Offer and Negotiation

What happens: a verbal offer, then written terms covering base, bonus, equity, start date and any conditions.

What decides it: the band for the level you were assessed at, and what you ask for. Most employers expect a counter on at least one dimension.

What to do: get the level in writing, ask for the posted band, and negotiate the whole package rather than only base salary. Our salary negotiation guide covers the scripts.

The Questions You Get at Each Step, With Sample Answers

1. “Walk me through your resume.” (Step 3)

Why they ask: to check the story hangs together and that you can be concise.

Sample answer: “I started in operations at a logistics company, which is where I learned to work with messy data. After two years I moved into analytics there, then joined my current company as a data analyst on the supply chain team. Over the last 18 months I have owned the forecasting model that the planning team uses weekly, which cut stockouts by 12 percent. I am looking now because I want to work on forecasting at a company where it is the core product rather than a support function, which is why this role interested me.”

Weak answers restate the resume chronologically with no through-line, or take four minutes to arrive at the present day.

2. “What are your salary expectations?” (Step 3)

Why they ask: to check you are inside the band before anyone invests interview time.

Sample answer: “Based on the market for this role and my level, I am targeting between $X and $Y in base salary, with flexibility depending on the rest of the package. I saw the posted range for the role is $A to $B, which lines up. Can you tell me where in that range this requisition is written for?”

Weak answers give a single number below your worth, or refuse to engage, which sometimes ends the process.

3. “Why are you leaving your current role?” (Step 3)

Why they ask: to find out whether you are running toward something or away from something.

Sample answer: “I have had a good run there and I am proud of the forecasting work. What I want next is scope I cannot get in my current team, because the analytics function reports into finance and the roadmap is set elsewhere. This role owns its own roadmap, which is the change I am looking for.”

Weak answers criticise a manager or a company at length. One factual sentence about a limitation is fine; three minutes of grievance is not.

4. “Talk me through your approach before you start coding.” (Step 4 or 6)

Why they ask: to see whether you plan or thrash.

Sample answer: “First I want to confirm the constraints: input size, whether the input is sorted, and what should happen with duplicates. Assuming up to a million elements and unsorted input, the brute force is quadratic which will not hold. I would use a hash map for lookups, which gets it to linear time and linear space. Before I write it I will name the edge cases: empty input, all duplicates, and integer overflow on the sum. Then I will code it and test with those three.”

Weak answers start typing immediately and discover the constraint problem eight minutes later.

5. “Tell me about a project you owned end to end.” (Step 5)

Why they ask: this is the load-bearing question of the hiring manager round.

Sample answer: “I owned the migration of our reporting pipeline from nightly batch to streaming. I scoped it after the sales team complained that dashboards were a day stale during quarter end. I ran the design review, wrote the ingestion layer myself, and coordinated with two other teams for the downstream changes. It shipped in nine weeks against a six-week estimate, because I underestimated the schema drift in one source. Freshness went from 24 hours to under five minutes. If I did it again I would spend the first week auditing source schemas rather than assuming the documentation was current.”

Weak answers describe a team’s work without naming which part was yours.

6. “What would your first 90 days look like?” (Step 5)

Why they ask: to hear whether you have a method or just enthusiasm.

Sample answer: “First 30 days, learning: meet every partner team, read the last two quarters of postmortems, and ship one small change so I understand the deployment path. Days 30 to 60, contributing: take a real piece of the roadmap and deliver it end to end. Days 60 to 90, improving: by then I should have a view on the one process that slows the team down, and I would propose a change with evidence rather than opinion.”

Weak answers promise big changes before understanding the system.

7. “Tell me about a time you disagreed with a decision.” (Step 6)

Why they ask: to see whether you can hold a position and then commit.

Sample answer: “My manager wanted to launch a pricing change without an experiment because the quarter was closing. I disagreed and said so directly, with a note showing that a two-week holdout would cost roughly 1 percent of that quarter’s revenue and would tell us whether the change was working. He decided to ship anyway. I built the measurement in retrospectively so we could still learn from it, and the data showed the change was net negative for one segment, which we then fixed. I was right about the experiment and wrong about the urgency.”

Weak answers pick a disagreement where the candidate was obviously correct and the other person was foolish.

8. “How do you handle competing priorities?” (Step 6)

Why they ask: to test whether you have a rule or improvise.

Sample answer: “My rule is that anything with customer money or data at risk comes first, then anything blocking another person, then my own roadmap. Last quarter I had a launch deadline and a partner team blocked on a schema change I owned. I unblocked them first because their cost was three engineers idle, told my manager the launch would slip by two days, and it did. The important part is telling people early rather than quietly dropping something.”

Weak answers claim to do everything, which reads as an inability to prioritise.

9. “How would you design this system?” (Step 6, technical)

Why they ask: to see structured thinking under ambiguity.

Sample answer: “Let me start with requirements. Who are the users, what is the read to write ratio, and what is the acceptable staleness? Assuming a hundred thousand writes a day and reads that can tolerate a second of lag, I would start with a simple API in front of a relational store with an append-only event table, then add a read replica before caching. I would guard the write path with an idempotency key so retries cannot double-apply. The parts I would watch are the hot partition on the customer identifier and the reconciliation job.”

Weak answers name technologies before requirements.

10. “What questions do you have for us?” (Every step)

Why they ask: your questions reveal what you actually care about.

Sample answer: “Two. First, what does the first successful six months look like in this role, in the terms you would use in a review? Second, what is the thing about working on this team that people find hardest, that you would want a candidate to know before they accept?”

Weak answers say “no, everything has been covered”, which reads as low interest. For more, see our questions to ask the interviewer guide.

11. “Why do you want to work here?” (Steps 3, 5 and 7)

Why they ask: to filter out mass applicants.

Sample answer: “Two reasons. The problem: you are one of the few companies solving reconciliation for multi-entity businesses, and I have spent two years suffering that problem from the customer side. And the shape of the work: this role owns the pipeline end to end rather than handing off, which is how I want to work.”

Weak answers praise growth, funding or brand. Those are true of hundreds of employers.

12. “Where do you see yourself in five years?” (Step 7)

Why they ask: to check your goals and the role are compatible.

Sample answer: “I want to be the person a team relies on for the hardest technical calls in this domain, whether that is a staff title or a lead role. Concretely, in five years I would want to have owned a system from design to running it in production at scale, and to have brought two or three engineers up behind me. That is a path this team seems to have.”

Weak answers name a title with no substance behind it, or say something the interviewer can tell is designed to please.

13. “Is there anything else we should know?” (Step 7 or the end of any round)

Why they ask: to give you one last shot, and to see what you choose.

Sample answer: “One thing. We spent most of today on the technical side, and the part of my background I think is most relevant did not come up: I spent 18 months as the on-call lead for a payments system, which is where I learned most of what I know about failure modes. If reliability matters for this role, that is the experience I would point at.”

Weak answers use the slot to apologise for a bad answer earlier.

14. “Can you tell me about a gap in your employment?” (Step 3 or 8)

Why they ask: verification and context, rarely judgment.

Sample answer: “Yes. I took eight months off from March last year for caregiving reasons. I kept current by finishing a data engineering certification and doing two freelance projects, both of which are on my resume. I have been actively looking since April and I am ready to start immediately.”

Weak answers are evasive or over-explain. One clear sentence about the reason, one about how you stayed current, one about your availability. See our guide to explaining employment gaps.

How to Practice These

Practise by step, not by question list. The recruiter screen, the hiring manager round and the panel reward different things, and rehearsing them as one block is why candidates give a technical answer to a motivation question.

Use OphyAI Interview Practice for voice or text mock interviews in behavioral, technical, system design and case formats. It asks follow-up questions the way a real interviewer does, and returns a transcript with per-answer feedback, which is the fastest way to find the 30 seconds of preamble you did not know you were adding. Run one mock per step in the week before your loop.

Use OphyAI Interview Copilot during live rounds on Zoom, Microsoft Teams and Google Meet, where it transcribes the conversation and shows answer suggestions on a private overlay. Rules on candidate use of AI assistants differ by employer, role and round, and some employers prohibit outside tools in live technical assessments, so ask your recruiter and follow their answer; use it for mock rounds where the rules are unclear.

Start practicing →

Frequently Asked Questions

What are the steps of the interview process in order?

Application, resume screening, recruiter screen, assessment or take-home, hiring manager interview, team or panel interviews, final round, references and background checks, then offer and negotiation. Smaller companies compress the middle: a startup may run only a recruiter screen, a hiring manager conversation and a team round. Large regulated employers add assessments and slower verification steps. The order rarely changes even when steps are skipped, so knowing the sequence tells you what is coming next.

How long does each step of the interview process take?

Screening and interviewing each average around 8 to 9 days, mostly because of scheduling rather than deliberation. The recruiter screen itself is 20 to 30 minutes, a hiring manager interview 45 to 60, a panel or onsite 2 to 4 hours, and background checks anywhere from 3 days to 3 weeks depending on the industry. End to end, published benchmarks put the average United States hire at roughly 44 days, with entry-level roles closer to 30 to 45 days and senior roles frequently past 90.

What is the difference between time to hire and time to fill?

Time to hire measures from the candidate’s first interview or first contact to an accepted offer, commonly reported at 24 to 30 days. Time to fill measures from the moment the employer opens the requisition, which includes the sourcing and posting period before you exist as a candidate, and averages around 45 days. Recruiters often quote the shorter number. When you ask “how long will this take”, ask specifically how long from this call to a decision.

Which step of the interview process matters most?

The hiring manager interview. It is the step where a single person decides whether you can do the job and whether they want to work with you, and their advocacy usually carries the final decision. Panel rounds add evidence, and the final round mostly calibrates level or resolves doubt. If you have limited preparation time, spend it on being able to talk for ten minutes about one project you owned, including what you would change.

Can I skip steps or speed up the hiring process?

You cannot skip employer-mandated assessments or background checks, but you can remove most of the delay you control. Give wide availability rather than two slots, reply within the hour, complete assessments the day you receive them, warn your referees in advance, and ask at the recruiter screen for the complete list of remaining steps. If you have a competing offer with a deadline, tell the recruiter as soon as you have it in writing rather than in the final week.

What happens after the final interview?

Usually a debrief where interviewers submit written feedback, then a decision meeting or committee review, then references and background checks, then a verbal offer followed by written terms. That sequence commonly takes one to two weeks, longer at large companies with hiring committees or level-calibration steps. If you have heard nothing a week after your final round, one polite follow-up to the recruiter is appropriate and does not count against you.

How many interviews are in a normal hiring process?

Three to four rounds is the common baseline, though the number of individual conversations is higher because a panel or onsite counts as one round but several interviews. Seniority pushes it up and small companies push it down. We cover the counts, the variation by company size and role, and what to do when a process runs long in how many rounds of interviews is normal.

Company processes vary in the details, and the guides below show how the nine steps look at specific employers:

Rippling interview guide: a four-stage process with a team-dependent take-home
Wells Fargo interview guide: assessments and a recorded video round before any live conversation
Amazon interview guide: an online assessment then a loop with an outside interviewer
Google interview guide: a hiring committee between the loop and the offer
JPMorgan interview guide: a superday of back-to-back interviews
Accenture interview guide: assessments plus multiple client-facing rounds

Sources and verification notes

Sources checked August 2026. Direct first-party fetches were blocked by the network policy where this post was written, so benchmark figures were consulted through search result summaries and are attributed to their publishers below. Hiring timelines vary widely by employer and role; the numbers here are published averages, not guarantees about your own process.

Management.org, time-to-hire statistics for 2026: the 24 to 30 day time-to-hire average, the roughly 45 day time-to-fill average, and the 8 to 9 day averages for the screening and interviewing stages. Checked August 2026.
ConsultAdd, average time to hire benchmarks 2026: the SHRM 2025 Recruiting Benchmarking Report figures of 44 days and roughly $4,700 per hire, and the seniority split showing nearly 40 percent of senior roles taking more than 90 days. Checked August 2026.
Treegarden, average time to hire benchmarks by industry 2026: the industry ranges for technology, healthcare, financial services and government. Checked August 2026.
Pin, the hiring process explained in 8 steps: the employer-side stage sequence used to structure the nine candidate-facing steps here. Checked August 2026.