7 Interview Mistakes to Avoid in the US

Most interview advice in the US treats every candidate as if they were walking into the same room. They are not. A seed-stage startup hires by gut, a Fortune 500 runs you through six rounds and a scorecard, and a federal agency decides almost everything before a human ever speaks to you. The mistakes below are the ones that cost offers across all three — the ones we see on repeat in reader mail, LinkedIn threads, and hiring-manager blogs.

This is not a motivational list. Each mistake below comes with the specific thing to do instead, and where relevant, a source to verify the advice yourself. If you are interviewing in the next 30 days, read top to bottom. If you have one interview this week, skip to mistake 3 and mistake 6 — those are the ones most likely to move the needle in a single conversation.

Why the US interview market behaves differently

Two features set the US apart from almost every other market Arthlens covers. First, the gatekeeping layer is heavily automated: the U.S. Bureau of Labor Statistics documents that most mid-to-large employers now route applications through Applicant Tracking Systems (ATS) before any human sees them. Second, salary transparency rules vary by state — California, Colorado, New York, Washington, Hawaii, Illinois, and several others now require pay ranges in job postings, while most of the South and Midwest still do not. These two facts change how early you need to optimize for machines and how early you are allowed to talk about money.

Behavioral interviewing — the "tell me about a time…" style — also dominates more of the process than in many European or Asian markets. Amazon, Google, Meta, and most Fortune 500s publish hiring rubrics that explicitly grade STAR-method answers (Situation, Task, Action, Result). Treating the interview like an open chat, when the interviewer is quietly filling out a scorecard, is the single most common cause of "we went with another candidate" emails.

Mistake 1 — Submitting a résumé the ATS will never show a human

Before a recruiter reads your first bullet point, your PDF has already been parsed by software looking for keywords from the job description. A résumé with two columns, a graphical skills bar, a header in an image, or a font the parser cannot read often lands in the recruiter dashboard with half the text missing. That is not a ranking issue — it is a "the résumé arrived illegible" issue.

What to do instead: run your résumé through a single-column test. Copy the PDF into a plain text editor. If whole sections disappear or show up in random order, that is what the ATS saw. Then, for each role you apply to, tune a short "Core skills" line at the top using the exact phrasing from the job description — not synonyms. If the posting says "stakeholder management", do not write "cross-functional alignment". The parser is not a thesaurus.

Mistake 2 — Treating the recruiter screen as a warm-up

The 20-to-30-minute recruiter call at the start of most US processes is not an introduction. It is the first gate. Recruiters at large employers are measured on pass-through rate to the hiring manager, and they are looking for three specific things: a clean narrative for why you are leaving your current role, a plausible compensation range, and evidence you read the job description.

What to do instead: prepare a 45-second "why I'm here" story that names the company by name, references one specific thing about the role, and lands on what you want next — not what you are running from. Have a salary range ready that starts at or above the listed range if the state requires one. If the range is not listed, use Glassdoor, Levels.fyi, and the BLS Occupational Employment Statistics to anchor to real numbers in your metro area rather than a national average.

Mistake 3 — Answering behavioral questions with opinions instead of stories

"Tell me about a time you had a conflict with a coworker" is not an invitation to describe your philosophy of conflict. It is a request for a specific, dated incident with names (or redacted versions of them), numbers, and a result. US interviewers at structured-interview companies are explicitly trained — Google's public hiring materials and Amazon's Bar Raiser program both make this public — to discount answers that stay in the abstract.

What to do instead: build a bank of eight to ten STAR stories before the interview, each tagged to a competency (leadership, conflict, ambiguity, customer obsession, failure, influence without authority, data-driven decision, stretch goal). Write each as: 1 sentence situation, 1 sentence task, 3–4 sentences of action in first person, 1 sentence of measurable result. Rehearse out loud — the gap between a story on paper and a story under pressure is usually a full minute.

Mistake 4 — Bringing up compensation at the wrong moment

Two errors sit on opposite ends here. The first is asking about salary in the first 10 minutes of a first-round interview with the hiring manager — a move that signals, fairly or not, that you are shopping rather than interviewing. The second is never bringing it up, discovering at the offer stage that the band is 25% below your market rate, and trying to renegotiate from a position of sunk cost.

What to do instead: if the state requires a posted range (California, Colorado, New York, Washington, and a growing list), trust it as a starting point and save the salary conversation for the recruiter or the offer call. If the range is not posted, ask the recruiter — not the hiring manager — in the first call: "What range is approved for this role?" When the offer arrives, move the negotiation to writing within 24 hours. Anchor on comparable roles in your metro area using BLS data or Levels.fyi for tech; do not anchor on your current salary, which is the weakest possible reference point.

Mistake 5 — Over-rehearsing technical and under-rehearsing the narrative

Engineers grind LeetCode. Product managers rehearse case frameworks. Analysts drill SQL. And then the interviewer opens with "walk me through your background" and gets a rambling three-minute tour that buries the best parts. In our reader mail from senior candidates in 2024 and 2025, this is the single most common post-rejection regret: technically strong, narratively vague.

What to do instead: write a 90-second version of your career story that follows the shape "where I started → the pivot → what I'm optimizing for next". Use the same structure every interview — only the emphasis shifts. Then rehearse the transitions, not just the content. "I moved from X to Y because…" is what interviewers remember. A list of job titles is not.

Mistake 6 — Treating "do you have questions for us?" as a formality

The closing question is a data point, not a courtesy. Interviewers are trained to read it: generic questions signal generic interest; specific questions signal that you have done the work. "What's the culture like?" is essentially a blank answer. "How does this team decide whether a project is finished?" is a question that only a serious candidate asks.

What to do instead: bring three questions tailored to the specific interviewer. For a hiring manager: "What does the first 90 days look like for whoever takes this role?" For a peer: "What is the thing about this team that surprised you most in your first three months?" For a director or VP: "Which bets is this team making that might not work out, and how would we know?" These signal that you understand that every job has risk, and that you want to know the shape of it.

Mistake 7 — Going silent after the offer, the rejection, or the ghosting

Three post-interview mistakes compound over years. First, not sending a thank-you note within 24 hours — still a baseline expectation at most US employers, even in 2026, and still a tiebreaker when two candidates are close. Second, not asking for written feedback after a rejection: in the US, there is no legal obligation to provide it, but about one in three recruiters will if asked politely and specifically. Third, letting a ghosted process die quietly when a two-line follow-up at the 10-day mark often restarts it.

What to do instead: send a short, specific thank-you note (three sentences, references one thing you actually discussed). After a rejection, reply within a week asking for "one concrete thing I could improve for a similar role next time" — the word "concrete" matters, and so does limiting to one. After silence, follow up once at 10 days with a clean question: "Is there an updated timeline for this role, or should I assume it has moved in a different direction?" You will lose nothing and sometimes gain everything.

Questions readers ask

How long should a US job interview answer be?

Behavioral answers using the STAR framework usually land between 90 seconds and 2 minutes. Anything under 45 seconds often skips the Result step; anything over 3 minutes starts to lose the interviewer. For technical or case questions, let the interviewer steer the length — they will interrupt when they have enough signal.

Is it true that US résumés should be kept to one page?

The one-page rule applies mostly to candidates with under 10 years of experience or to federal and consulting applications with strict page counts. For senior roles in tech, healthcare, or academia, two pages is standard and often expected. What matters more than length is that the first third of page one maps directly to the job description — that is where most ATS systems and recruiters decide whether to keep reading.

When should I bring up salary in a US hiring process?

Let the employer raise it first when you can. In states with salary transparency laws — California, Colorado, New York, Washington, and others — the listed range is a reliable starting point, so you do not need to ask. Once an offer arrives, negotiate in writing, not during the phone call, and anchor on the market data you collected from BLS, Glassdoor, and Levels.fyi rather than on your previous salary.