What this covers

The rounds that happen before anyone evaluates your work technically. In practice that means the recruiter screen, the human resources screen, and the first conversation with a hiring manager, founder, or principal investigator. The boundary is drawn by who is on the call, not by what they ask. A hiring manager who asks technical questions in an introductory call is still inside this volume; a scheduled technical evaluation is not.

The founder and principal investigator round is kept as a separate chapter, because the evidence shows it runs on different logic and is far less predictable than any other round.

Not covered: coding exercises, take home assignments, system design, and the research deep dive. Those belong to the technical volume.

Where this comes from

Roughly fifteen hundred firsthand accounts, collected specifically for this volume: recruiters and hiring managers describing their own practice, candidates describing what happened to them, principal investigators and founders describing how they decide, and vendor documentation where the mechanics of a system were the question.

Generic career advice sites were excluded by rule rather than by judgment. Almost everything a search engine returns on this topic is written to rank rather than to inform, and including it would have reproduced the same advice this volume exists to check.

Sources are not cited in the text. Every claim was verified at collection, and the underlying records with links, dates, and speaker identities are held locally. What appears here instead is a strength marker, which tells you how much weight a claim can carry.

The evidence markers

● Multiple independent firsthand sources agree. Act on it.

◆ One firsthand source, or a narrow set from a single place. Probably true, worth knowing, not worth restructuring around.

◇ Inference from adjacent evidence, not directly attested. Reasoning, clearly labeled as reasoning.

Apparent agreement is not always independent agreement. One account written in 2024 was found republished word for word under a different name in 2026. The markers reflect independent sources, not how often something was repeated.

The four lanes

The strongest single finding is that the first call is not one thing. Four distinct processes exist, and advice that helps in one hurts in another.

A. Small research organization. An AI for science startup, a small biotech, a nonprofit institute. Often no non technical layer at all; a scientist runs the first call and it goes technical within minutes.

B. Large pharmaceutical company. A remote, non technical talent advisor owns the entire gate. Behavioral competency scoring. Rigid salary bands. A clock measured in months.

C. Research institute, national laboratory, postdoc. No human resources before the science. The principal investigator runs it. You are expected to arrive with a direction.

D. Large technology company. The structured recruiter screen that all standard advice describes.

Where an answer differs by lane, the lane is marked. Where it does not, it is not.

What this volume will not do

It will not resolve contradictions by picking the more popular side. Where firsthand accounts genuinely disagree, both are given, with an attribution for the disagreement where one is supportable. That register is a chapter of its own, and it is the honest part of the book.

The rules

Two to five applications per company, not one. One per company is far more conservative than any recruiter in the evidence recommends. The red flag is incoherence, not count. One recruiter placed the real threshold at “well over 100 roles… zero business applying for”. Keep the set inside one job family and one seniority band, and submit them in the same short window. ●

Tell the first recruiter who contacts you about the others. This is one sentence and it removes the only failure mode recruiters actually name: with a different recruiter on each requisition, “one thinks the other is working with you and moves on, but then no one ends up moving forward.” ●

One email address, one phone number, one profile link, forever. Applicant tracking systems do not deduplicate on email. One matches on name, phone number and profile link together. Another matches on name, city and country, and does not look at email at all. A second identity therefore hides nothing, and it costs you control: profiles are merged later, and at one system the administrator doing the merge “won’t get to choose which one is retained”. ●

Vary bullet points freely. Never vary titles, employers, or dates. Old versions stay in the system: “our ATS does have a record of your old resumes.” Dates are the field that employment verification actually checks. There is a documented case where a candidate truthfully corrected a job title, an older version was still on file, and the process ended immediately. At one large system your most recent application also auto populates every later one, so the newest version silently becomes your identity there. ●

Apply early, and do not spend forty five minutes tailoring for a large employer. The advantage is real but concentrated in the first week or two, and strongest at small companies, where hiring managers describe freezing a shortlist of four or five people and never going back. At batch review employers arrival order is invisible by the time a person looks. Both camps in the evidence, the high volume camp and the high tailoring camp, agree that deep per application tailoring has poor returns at large employers. ●

Ask for referrals directly, and keep applying while you do. The measured effect from a study of one large employer is about seven percentage points added to the chance of an interview and about two added to the chance of an offer. It buys access, not endorsement. Applying first and getting a referral afterward is not wasted. Weak ties work. Name the shared connection and make the actual request; do not open with a request for an informational conversation. ●

Actively harmful

• A second email address or a second account. Detected on other fields, merged later, and you lose control of which version of you survives. ●
• Changing titles, employers, or dates between resume versions. Bullet points are free; these are not. ●
• Reapplying inside a company’s cooldown window. At least one major system ships a configurable rule that auto rejects and marks the application blocked, with no human ever seeing it. Assume roughly six months after a real interview loop. A paper rejection with no interview carries no such penalty. ●
• Applying to roles at one company that span different seniority levels or unrelated functions. ●
• Answering the sponsorship question inaccurately. It is a soft filter, not an automatic rejection: “it is not an immediate no… it does lower your chances”. It is also verified at offer stage, which is the worst possible moment to be caught. ●
• Cold messaging strangers with a vague request to chat. The version nobody in the evidence objects to is different: contact someone adjacent, ask who runs the process, then approach that person yourself. ●

One thing the evidence does not settle

Whether postings that are not real openings are common. One vendor puts it near twenty percent; a government research service states there are no official statistics and notes that the vendors publishing those figures sell hiring services; corporate recruiters deny doing it. What is verifiable is the evergreen requisition, which by its own vendor documentation has “no relationship to positions” and cannot hire you directly. There is no way to detect one before applying, so the practical move is to ask about the hiring timeline during the first call.

How to tell which lane you are in, before the call

Read the invitation, not the job title. Four things give it away.

Who sent it and what their title is. A talent partner, talent acquisition specialist, or people operations coordinator means a dedicated screening layer exists. A named scientist, a group leader, a head of research, or the founder means it does not. ●

How long the slot is. Twenty five to thirty minutes with a scheduling link is a structured screen. Forty five to sixty minutes booked directly by a scientist is a scientific conversation wearing a friendly name. ●

Whether the invitation names the next step. Structured processes describe the sequence up front. Small organizations and research groups usually do not, because it has not been decided. ◆

Where the posting lives. A posting on a large careers portal with a requisition number, an internal grade, and a wide published band is a banded organization. A posting on a small applicant tracking system with a narrow band, or no band, is not. ●

Lane A. Small research organization

This is an AI for science startup, a small biotech, or a nonprofit research institute. It is where most of your applications sit, and it is the lane where standard advice fails hardest.

There is often no non technical layer at all. At one institute the internal recruiter holds a biology doctorate. At another the hiring team runs the first conversation and human resources appears afterward. At national laboratory groups the hiring manager and group lead run the thirty minute screen themselves. There is no warm up round. ●

The first call tests research judgment, not logistics. A candidate described one company’s phone screen as “trying to assess my research ability, my critical thinking ability and my areas of expertise”, not a walk through the resume. ◆

An open, undefined problem arrives immediately, and speed is what is being measured. One twenty minute call ended with a written assignment to design a screen for a disease. An engineer who ran doctoral candidate interviews at a small company said he would rather hire “someone who comes up with a sub-par solution quickly and then iterates”. The instinct to go quiet and think is the wrong instinct here. Produce a rough answer out loud, then improve it in front of them. ●

The research talk comes early. At one company a twenty minute talk was the second round. Small organizations front load the seminar; large ones save it for the end. ◆

The band is either said out loud on the first call or does not exist. One institute’s human resources contact named a range on the first call. A four person company has no band at all, and the equity half cannot be priced, since “options are worthless until something happens later”. Compensation tracks the funding stage directly. ●

This call is your only chance to price the organization’s survival. Runway, whether the trials are actually registered, whether the founder can answer a hard question about the science. There is no equivalent signal available at a large employer. ●

Sponsorship is worse here, not better. Cap exempt status at nonprofit institutes is described as “almost impossible after research grant cuts”. Do not assume that nonprofit means visa friendly. ◆

Lane B. Big pharmaceutical

Compensation is a hard gate in the first minutes, not a closing negotiation. Bands are priced against an industry salary survey and enforced in both directions: “most, if not all, major biotech/pharma companies have a policy to not pay outside of brackets be it above or below”. One candidate was cut immediately after naming a number. The protective half of this is real: naming a low number does not push you below the band floor. The dangerous half is also real: naming a number above the band ends it. ●

The first round is behavioral competency scoring, not technical evaluation. One large company publishes its interview questions mapped to its stated values. Another instructs candidates in writing to answer in situation, task, action, result format. A candidate summarized it as “It’s every big pharma I’ve interviewed at.” There is no coding exercise and no take home at this stage. If you have prepared technical depth and not prepared structured behavioral answers, you have prepared for the wrong round. ●

The screener is remote, frequently in another country, non technical, and owns the entire gate. A hiring manager described it plainly: “a global remote team of HR recruiters do all the front end resume screening and phone screenings. Hiring managers may only ever see 10-15% of applicants resumes.” Nothing you say about method quality reaches a scientist unless this person passes you through. ●

The clock runs in months and silence is structural. Three weeks or more simply to schedule the first call. Ten to fourteen days from screen to manager. One aggregate figure for a computational biology hire at a large company was about one hundred and twenty days. A candidate who did both said “biotech companies tend to move faster than pharma… I onboarded at said biotech 5 weeks from the initial screening call.” Silence here is not evaluative. ●

Sponsorship is decided before any human speaks to you, and it can overrule the hiring manager. “We screen for visas via HR/ recruiter prior to me even seeing the resumes.” One manager stopped considering candidates who needed sponsorship at all, because human resources had repeatedly blocked people who had already passed his own interview. ●

A referral buys attention and nothing else. “all a referral really does is ensure a human looks at your resume”. “Referral increases your chances of being interviewed, not your chance of being hired.” Several insiders describe postings that exist to legitimize a person already chosen, often an internal candidate or a postdoc being converted. ●

Lane C. Research institute, national laboratory, postdoc

The science comes before human resources, if human resources appears at all. A candidate at a national laboratory wrote “I wasn’t first interviewed by an HR type person before being invited for an interview (I assumed this is standard practice).” At another the prescreen is run by “host PI and core project members”, with human resources appearing only at the offer to discuss salary. ●

Technical probing starts in the first minute, and the call can end there. A principal investigator who had just run thirty postdoc interviews: “I started asking these questions at the start of the interview. If during this technical portion of the interview it becomes apparent a candidate has lied about the expertise I end the interview early.” ◆

Homework is a gate, not a bonus. Multiple group leaders discard generic contact outright. A laboratory member who runs candidate conversations reported “half the time the interviewee has no clue what the lab is even doing and I relay that to my PI.” ●

You are expected to arrive with a direction, and choosing the wrong one is a documented reason for being cut. “A top candidate got dropped from second visits because all they talked about was how they wanted to develop their tool for a question that I didn’t think was exceptionally interesting and that didn’t fit into my program at all.” Competitive groups often ask for a one page written proposal after the call. ●

There is no process behind the decision. A full professor: “I will strategically neglect to request references as I won’t want to be talked-out of a candidate.” Many candidates never receive an answer at all. ●

On sponsorship, the single most useful fact is that most principal investigators do not know how any of it works. One account puts it directly: most group leaders are unaware of visa mechanics, so you have to be explicit early. Universities also tend to push the cheaper exchange visitor route rather than the working visa, because it is cheaper and covers the whole contract. ●

Lane D. Big technology company

This is the lane that all the standard advice was written for, and the smallest part of your applications.

The screen is structured, logistical, and owned by someone who cannot evaluate your work. Recruiters say so themselves, in both directions. One: “I mean you can’t for the most part. If you were qualified enough you’d be an engineer.” Another, immediately after: “Bingo! I’m not a mechanic… but I can still screen those candidates.” The reconciling version, from a third: “Recruiter screen: can the candidate talk the talk… Hiring Manager evaluation: can they walk the walk”. ●

The evaluation is noisy and the people doing it know it. A study of seventy six technical recruiters found a median resume read of thirty one seconds, accuracy around fifty five percent, and that two recruiters judging the same candidate disagreed about as much as if they had been judging two different people. The reasons given for cutting a candidate also diverge from the real ones. ◆

Bands are rigid, which protects you downward. One recruiter’s version: if the range is one hundred fifty to one hundred seventy five thousand and you say one hundred ten, the minimum offered is still one hundred fifty. A candidate independently reported being told his number was too low. This does not transfer to Lane A. ●

What this means for preparation

If you prepare one script, it will be tuned to Lane D and it will underperform in the three lanes where most of your applications actually are.

The practical version is that you need three openings, not one. In Lane A and Lane C, open with research substance, because the person on the call can evaluate it and expects it. In Lane B, open with a structured behavioral answer, because the person on the call is scoring you against a competency framework and cannot evaluate the science. In Lane D, open with a compact logistics friendly summary and save the substance for the next round. ◇

Q01. “Tell me about yourself.” / “Please walk me through your CV.”

Confidence: ●

Why they ask it: It is the default opener and the cheapest possible test of whether you can compress your own history into something a non-specialist can follow. One recruiter says plainly that what catches her eye is clarity: “If someone can explain what they did, why it mattered, and how it moved the needle for their team, that person immediately stands out.” Several recruiters also treat it as an icebreaker with no scoring attached.

What they are listening for: - Where you work now and what you actually do, briefly, then the previous experience relevant to this role. One recruiter states the wanted content exactly: “I just want to know 1) where you currently work and what it is you do (briefly!) and 2) any previous relevant & meaningful experience related to the job you are interviewing for.” - How you tell it more than what you tell. “I listen to them here but I’m more focused on HOW they tell me.” - Whether you map yourself onto the role rather than reciting a chronology.

How it fails: Rambling is the most cited failure. A candidate who posted a draft answer for recruiters to grade was told “90% of your answer did not answer the question…” and “I think that’s way too long, and it sounds like chat GPT wrote your response lol.” A recent graduate was rejected live on the call after she “couldn’t figure out what she wanted to hear” and was told she was unprepared. The opposite failure also appears: a candidate had “a list of potential answers ready to go but ended up stuttering through my educational and work background” on a four minute call. And one candidate who over-rehearsed found the interviewer went a different direction: “I prepared so hard that when it wasn’t the exact thing I expected I let my guard down.”

Contradiction in the evidence: length. Recruiters in the same thread say 30 seconds or less, 2 minutes, and “3-4 mins is good.” A research candidate reports preparing “a 30 second story about myself.” A separate group of recruiters rejects the question outright: “It’s a terrible question, honestly. I’ve been in talent acquisition for two decades and have never asked this question.” The split does not track lane or year; it tracks the individual recruiter. Treat it as unresolved and build a version you can deliver in 45 seconds and expand to two minutes if they stay quiet.

What to say: Three moves. Where you are now and what you build; one line of evidence with a number in it; why this role is the next step. Then stop and let them steer.

“I’m finishing a PhD in [your field], where I build [the kind of method you build] for [the kind of problem it is aimed at]. The work I’d point to first is [the project you would lead with], which [what it changed] by [the number that makes it concrete], and [who uses it now, or what it is used for]. I’m looking for a role where that kind of method work sits close to [the thing this employer has that your current setting does not], which is why this posting caught my attention.”

By lane: In a research organization or a lab, one candidate hired at a frontier lab reports the same slot arrives as “Please walk me through your CV” and adds a practical habit: check whether they have actually read it, because often they have not, and if they have not, walk the stations chronologically before adding the spin. In a lab or postdoc conversation the opener is frequently skipped entirely and the technical probing starts at once.

Q02. “What made you apply to our company?” / “What do you know about us?”

Confidence: ●

Why they ask it: To separate people who chose this company from people who applied to two hundred postings. It is one of the three questions that make up the canonical screen, along with why you are leaving and compensation. One candidate was asked “Why us?” four times in a single process: at the screening call, at the hiring manager interview, at the technical phone screen, and again in the onsite loop.

What they are listening for: - Evidence you did homework that the job description could not give you. One recruiter frames it kindly: “I don’t expect you to know anything, just be honest and I’ll give you a quick pitch. If you do know, how do you know about us.” - At small companies, whether you understand what the company actually does, in one sentence, correctly. - Whether the reason is specific to them rather than generic praise.

How it fails: At a startup, not knowing the product is fatal and instant. One candidate wrote after a founder call: “I definitely did not have a deep enough understanding of what exactly the start-up does (which he could tell right away).” A candidate who cleared one HR round out of many attributed it entirely to company research: say the things other candidates will not say, and show you actually know the company. In the postdoc lane, the failure is not having read anything: a PI reports interviewing “a bunch of people recently who had not bothered to read a single paper from our group or even knew what the current state of the art approaches were in our field.”

What to say: Name a specific thing they published, shipped, or announced; connect it to a specific thing you have done; state the open question you want to work on there. Two sentences is enough.

“I read [the specific paper, release, or announcement of theirs] [when you read it] and [what you actually did with it, for example reimplemented part of the evaluation for your own project], so I know where the failure cases are. The gap you flagged in the discussion, [name it in four or five words], is exactly what [the line of your own work that aims at it] has been aimed at, and I would rather work on it with [what they have and you do not, for example experimental feedback] than without.”

By lane: For a startup, the founder or hiring manager also wants signs you can name the market: one founder’s own screening question is “Who are our five biggest competitors?” For a lab or a national lab, the version asked is why this lab and which of the institution’s missions you see yourself affecting, and reading two or three of their papers is the stated minimum. For a big pharmaceutical company, the recruiter is checking the box, and a generic but coherent answer passes.

Q03. “Why are you leaving your current job?” / “What has you looking for a new opportunity?” / “What are you looking for in your next role?”

Confidence: ●

Why they ask it: It is a stability and attitude probe, and recruiters use it to route you. One recruiter: “I always ask them what about their current job is making them consider other options. It usually gives good insight on what is important to them career-wise and what work environment would be a better fit.” The same slot often becomes “what are your priorities in considering something new,” and one recruiter designs it so the candidate speaks 90 percent of the following minutes.

What they are listening for: - Motion toward something, not away from something. “Employers generally want the perception that you are running toward their job, not away from a different job.” - Professional restraint under an invitation to complain. “There’s a difference between talking shit about your company and telling the truth.” - A reason that is not only money, unless you are being grossly underpaid.

How it fails: Candour has documented costs. One candidate told a recruiter his employer had misrepresented the job, and only then learned “my current employer is a client of her company.” Another named the sentence he believes killed a call: he had “taken one for the team” on legacy stacks and concluded “it makes more sense to be selfish and protect yourself,” which he later described as good career advice but not what management wants to hear. A candidate on an intern HR round answered truthfully about why a prior internship lasted two months and was rejected by HR after the director round went well; her own post title was that she was cut for being too honest.

Contradiction in the evidence: how honest to be. Multiple recruiters push honesty, especially about layoffs: “Being laid off is probably the most well-received reason for a employment gap,” and “if comes off better if someone just owns it and is honest. Otherwise it reads like you are trying to hide it.” Against that, one recruiter says “It doesn’t matter. You control the narrative… Just give them a plausible reason and move on. It’s not a lie detector test,” and a commenter on a founder round rejection advises “giving more cheesy answers next time because honesty is your enemy with HR style questions.” The split does not track lane. It tracks what you are being honest about: layoffs and restructuring get honesty credit, criticism of people and employers does not.

What to say: One neutral sentence about the current situation that includes something positive, then the forward reason, then the link to this role. Do not diagnose your employer.

“[One neutral and true sentence about where things stand now, including the part that is going well, for example that the last project is finished and this is a clean point to move]. What I want next is [the forward reason, stated as a property of the work rather than a complaint about anyone], and that is not something [your current setting] is set up to do. That is the part of your posting I want to talk about.”

Q04. “Why do you want to leave academia?” / “Why industry?” / “Are you sure you want this job?”

Confidence: ●

Why they ask it: They are testing commitment and whether you have understood what industry work is, not your motives as such. A hiring manager who has interviewed dozens of PhDs: “It’s not meant to be hard or a trap. It’s about getting a sense of where you’re at mentally. You’re fine as long as you don’t come across as only applying out of desperation because you didn’t get a tenure track position. Nobody wants to hire someone who doesn’t want to be there.” A candidate blog says flatly that you should “think clearly about why you wanna leave (every recruiter and hiring manager will ask you anyways).”

What they are listening for: - A plan, not an escape. A commenter with an industry PhD flair: “It is not a bad thing to come from Academia, they just want to see if you have a mid-term, long-term plan in mind for your career.” - Whether you are still on the academic market. One hiring manager: “We often directly ask if they are also applying to academic/post-doc jobs, and why/why not.” - Tone about industry. The most common self sabotage named by an interviewer is the candidate who is “high and mighty about their noble pursuits in academia” versus the supposedly money grabbing pursuits of industry.

How it fails: Two ways. First, the answer that is entirely about academia being broken. A candidate’s verbatim script, “Academia was something I was invested in pursuing, but due to how things are it’s simply not a viable career path for me anymore,” drew an immediate objection from another candidate: “instead of focusing on what OP wants to do and how they’d be able to contribute to the job they want, it’s more about how academia is all bad and OP just need a job.” Second, not having internalized the different working model. One commenter argues that if you have “not thought about what it means to live on administrative time instead of academic time” and have not prepared for questions probing the negative stereotypes of academics, that is why your commitment is still being questioned at the third round. Note that this doubt is re-asked at every round, not settled at the screen: a group of ex academics reports being asked at the final interview “So, you’ve got this PhD, you’ve spent some time teaching, are you sure you want this job?”

Contradiction in the evidence: whether money is sayable. One candidate answered in real biotech interviews, “I want to make more money than I’m making right now. And I also want my science to have a tangible product at the end of the day,” and that was the top voted answer in its thread. Against that, an advisor to a long time academic says the answer should be “a compelling scientific journey and impact you hope to make rather than just about money. One topic is viewed more positively than the other.” The safest reading of both: money can be present but must not be the load bearing reason.

What to say: State the scientific reason, name the concrete thing industry has that you need, and close the academic market question before they ask it.

“I want the work to end in something that gets used. In my field the bottleneck is not [the thing your field produces by default], it is [the missing ingredient that decides which method is actually right], and that loop exists here and not in [your current setting]. [Then close the academic market question in whatever form is true for you: which of faculty positions, postdocs, or neither you are still applying to, when you decided, and what you did differently because of it.]”

By lane: In the pharmaceutical lane this question is asked by a recruiter who will not evaluate the science, so translate first: “sit down and identify the skills you have acquired and translate them into industry terms/needs.” In the lab and postdoc lane the question inverts and becomes a career plan question; see Q07.

Q05. “Walk me through a project you’re proud of.” / “Tell me about your research.”

Confidence: ●

Why they ask it: This is where a research screen is actually decided, and the criterion is reasoning, not results. A scientist at a large pharmaceutical company who ran prescreens and onsites says it directly: “make sure to demonstrate at least one good example of problem solving or your thought process when talking about your research. I saw a lot of people just listing out results without discussing how they designed or iterated on their experiments. We can read your resume, it is really hard to evaluate someone when they don’t do this.”

What they are listening for: - Design and iteration: why this experiment, what you expected, what surprised you, what you changed. - Contribution disambiguation, which is an explicit criterion. The same interviewer: “clearly state what your contributions to research projects were and what was done by your coworkers. Sometimes we can make a good guess at it by inference but it will only help you to remove that guesswork from our evaluation. If you must be modest, the way to go is to clearly indicate everything that wasn’t your contribution so that by process of elimination we know what you did.” - Depth over breadth. A robotics PhD who ran a research search: “it is much stronger to present one thing well and have your interviewers come away with the belief that you really understand it.” - Whether you can talk about the papers you are an author of at all. One candidate’s summary of the recruiter screen at a large lab is that it is a chance to show “you actually know and can talk about the papers you are an author of.”

How it fails: Papers do not protect you. An interviewer: “Having a bunch of ICML/NeurIPS/ICLR papers is 99% due to your lab/advisor… I’ve interviewed people with very strong resumes on paper that were utterly clueless about fundamental concepts in ML and language modeling.” A candidate with offers from several top labs concluded that “technical skills and knowledge are evaluated much more than research experience, though the latter probably gets you the interview in the first place.” In the lab lane the failure is faster: one PI who had just interviewed thirty postdocs says that if a candidate has declared proficiency in the group’s core methods and cannot answer, “If during this technical portion of the interview it becomes apparent a candidate has lied about the expertise I end the interview early.”

What to say: Problem, why the obvious approach fails, what you did, what you personally did versus the collaborators, what it cost, what you would do differently. Volunteer the contribution split without being asked.

“[Who needed what, and the reason the standard approach could not deliver it]. The obvious fix, [the standard approach], was not affordable, so I tried [what you built instead]. My first version [the specific way it failed], which told me [what that failure implied about the setup], so I [the change you made in response]. To be clear about the split: [what a collaborator contributed] was theirs, [what came from someone else’s earlier work] came from a labmate, and [the parts that were yours] were mine. If I did it again I would have [the thing you would reorder, drop, or do first].”

By lane: Big tech and large labs ask this at the recruiter stage as a shallow verification; the deep version comes from the hiring manager. Small research organizations may run it as an entire round, and a research talk can arrive as early as round two. Big pharmaceutical screens frequently invert the ratio and ask scenarios instead; see Q08.

Q06. “You haven’t worked in this area before. Why are you applying here?”

Confidence: ●

Why they ask it: They want to know whether you are a scientist who can move or a specialist attached to one subject. This is the question that most worries candidates crossing from physics, chemistry, or structural biology into machine learning, and the evidence is more encouraging than the folklore.

What they are listening for: - Transferable technique, not your former subject. An industry interviewer names the rejection pattern: candidates who “talk about their pathway/protein of interest rather than the techniques they gained during their careers, and how these can be applied in the position.” - Present evidence in the new field. A candidate who pivoted into AI safety reports that his multilingual papers, including best paper awards, had no bearing on outcomes, and calls that “liberating, because that means that you can always pivot to a new field… if you demonstrate sufficient expertise in that field and the team wants you.” - Legible artifacts. A nuclear physics PhD: “A project using diffusion models can often get you noticed whereas a generic classification task may not.”

How it fails: Leading with the old domain, and applying where the background is unreadable. The same physics PhD found openness to physicists concentrated in three places: autonomous vehicles, machine learning for science, and language model startups. Elsewhere the pivot has to be argued from scratch.

What to say: Open by converting your background into capabilities the role needs, in one breath, before anyone asks. A candidate hired as a research engineer at a frontier lab used this almost verbatim:

“Hi, I’m [your name], a Machine Learning engineer. You’ve probably read my CV, so I will just briefly summarise what makes me uniquely qualified for this role. My background spans Physics, Sociology, and systems-level software engineering. As such, I can work with quantitative data at scale, have experience with messy human-produced data, and can build the software systems around that to train and serve large models.”

Your version: name three capabilities, each with a concrete anchor, and end on the one the role is actually about.

“I’ve spent [how long] doing [what your background actually is], which means three things for this role: I can [the first capability, stated as something you can do rather than something you studied], I’ve [the second capability, with the property of the data or the problem that made it hard], and I’ve [the third capability, the engineering one, with the number that shows its scale]. The last [span of time] of that has been [the capability closest to this job] specifically, which is the part of your posting I want to work on.”

Contradiction in the evidence: how much the pivot costs you. A candidate at a small research company found “most companies and teams did not care too much that I hadn’t previously worked directly on or published in their area of interest,” and a hiring side commenter goes further: “people with deep domain knowledge in something physical that has leveraged ML as a tool are way more interesting to hire than someone buried in code and gradients their entire career.” Against that, a widely read discussion among industry researchers holds that proper research roles expect state of the art results already delivered, and estimates three years of full time effort to pivot in. The split tracks the role: research engineering and applied science absorb pivots, named research scientist roles at frontier labs do not, at least not quickly.

Q07. “How does this job fit into your larger career goals?” / “Where do you want to be in five years?”

Confidence: ●

Why they ask it: In the academic lane this is the load bearing question of the whole conversation, and it is not asking for a document. A PI: “When I say 5 year plan, I don’t mean a form document. I mean that you, a mature, ambitious, and intelligent adult have a clear, and articulatable goals for your future and that you can convince me that spending 5-10 % of your working adult life in my group is going to benefit those goals.” Another PI states what the question tests: “What I want to know is people are going to take active control of their career path… I want people who aren’t passive about their futures.”

What they are listening for: - A direction you own, with a reason this position serves it. - Alignment with what they can actually offer. One recruiter’s note is simply that career goals “should match the role at least roughly.” - At a national lab, the specific values: “knowing your interests in starting projects, developing proposal writing skills, facilitating collaborations, all those speak towards the values of the lab and what they want in a new hire.”

How it fails: Having no answer, which reads much worse from a postdoc than from a student. The same PI: “a graduate student not having goals for grad school is a red flag, but a postdoc without them is a fire alarm.” The second failure is misreading who you are talking to: “Don’t tell me you want to work with a senior PI cause you did your PhD in the lab of assistant professor when i just started my lab.”

What to say: Name the capability you are trying to build, name what only this place can give you toward it, and be honest that the endpoint may move.

“In five years I want to be [the role you are actually aiming at, described as what you would own rather than as a title]. What I still lack is [the capability that is missing, named as a judgment rather than a skill], [the concrete decision that capability governs]. This group is one of the few places where I would sit close enough to that decision to learn it. Whether that ends in [one plausible endpoint] or [the other], I would rather decide after [the span of time] of doing it.”

By lane: This is a first call question in the lab, national lab, and postdoc lane, and it is often the question. In the big pharmaceutical and big tech lanes it appears as a shorter recruiter checkbox. In a startup founder round it usually does not appear at all, replaced by the risk and adaptability questions in Q15.

Q08. “Tell me about a time when…” (behavioral and competency questions)

Confidence: ●

Why they ask it: In the large pharmaceutical lane the first round is largely or entirely behavioral and it is scored against published corporate values. One large pharmaceutical company’s own careers page tells candidates in writing to answer using the Situation Task Action Result method. Another publishes its competency questions verbatim, including “Tell me about a time when you encouraged the sharing of different viewpoints and created a space for others to speak up. What actions did you take to encourage others to voice their disagreements?” and “Describe a time when you held others accountable for their commitments. How did you communicate and bring clarity to the team? What, if anything, would you do differently in the future?” It also states that its interviews are anchored to its values, with technical questions as the optional addition.

What they are listening for: - The team dimension above all in pharma. One employee names it: “How have you addressed problems? Have you blazed the trail completely on your own? Or have you sought perspective from key stakeholders and assembled a cross-functional team to establish a well-informed path forward? Big Pharma wants to hear you have done and are willing to do the latter.” - Reasoning, not the resume. An interviewer: “We can read your resume. We want to see how you think and reason. Always plan for situational. Things like: difficult decisions, delivering bad news, showing leadership, unexpected outcomes.” - Specificity under follow up. An interviewer at a large technology company who runs phone screens says the rejections she sees are mostly a STAR story that was not told well, or follow up answers that were not concrete enough; her example is a candidate who cited a number and could not say where the number came from.

How it fails: PhD candidates under-prepare this round because it looks easy. One candidate with offers from top labs: “I failed my first behavioral interview because I went into it thinking I’m obviously well-‘behaved,’ and came up blank on excruciatingly simple questions,” ending with the interviewer saying “You didn’t answer the question.” The second failure is having no story that fits the value being probed. A quality professional: “I got HR behavioral questions which were really tough to answer because I don’t generally show courage or heroism at work. I’m in quality… if I’m doing either of those things, the company is doing something wrong.”

What to say: Build six stories before the call, each usable for three prompts, each with a number and a “what I would do differently” ending, because the published probes ask for exactly that. Situation in one sentence, task in one, action in three or four with the decisions you personally made, result with a number, then the reflection.

“[The situation in one sentence, including what had gone wrong between the people involved]. [The first thing you did, and the fact that you did it before proposing anything]. What came out was [the real cause, which is usually not the technical one you assumed], so I [the change you made] and [what you did with it]. [The result, with a number on both sides of it]. What I would do differently is [the ordering mistake, stated as a sequence rather than as a character flaw].”

Contradiction in the evidence: whether the format selects for anything real. A candidate at big pharma: “STAR/situational interviews is how companies end up full of good talkers but not many great do-ers. If interviews favor bullshitters and eliminate people who are too truthful or stutter, then companies shouldn’t be pikachu surprised when the chain of command spins bad news as good all the way up.” Interviewers in the same threads insist the behavioral weighting is deliberate and correct. Both sides agree it is universal at big pharma, so the dispute does not change what you prepare.

By lane: Big pharma and big tech: expect it, prepare it, use STAR because at least one company asks for it in writing. Small research organizations: mostly absent, replaced by Q09. National labs: present but scoped narrowly, often as a panel with scripted questions about paper writing, technical conflicts, mentoring, and, at one lab, mostly about safety.

Q09. “Here’s a problem we’re working on. How would you approach it?”

Confidence: ●

Why they ask it: Small research organizations replace the behavioral round with an unspecified problem and watch you work. One research startup describes its loop as “giving them a real problem we’ve recently faced and seeing how they would reason through it.” A candidate at another was asked to prepare a 30 minute presentation “on a problem they had that I had no domain expertise in.” At an AI for science company, a 20 minute first call led straight to a written assignment: learn our platform and describe how you would use it for a drug screen in an immunological disease.

What they are listening for: - Speed of iteration, explicitly. An engineer who ran PhD interviews at a research startup: “I would rather hire someone who comes up with a sub-par solution quickly and then iterates on it, than someone who comes up with the perfect theoretical solution, but no code.” His single instruction to PhD candidates is “Just come up with something.” - Clarifying, which is permitted and wanted. The same interviewer: “It’s always important to have a discussion … to understand the problem.” Asking what the constraint is, what data exists, and what counts as success is part of the answer, not a delay before it. - Honesty at the edge of your knowledge. A research candidate: “Be honest about what you don’t know… this came across much better than trying to bluff through a topic I wasn’t confident about.”

How it fails: Silence while you look for the right answer. Also basic tooling: after interviewing dozens of PhDs, one interviewer reports that the most common disqualifier was that “Most PhDs we’ve encountered have very basic programming skills.”

Contradiction in the evidence: what the exercise measures. One reading is scientific judgment. Another, from a critic of the same account, is that “The startup risk tolerance is extremely high, thus it rewards quick and dirty over well thought out and solid,” and a third objects to the inference itself: “Notice the assumption here, that their 20-minute task is a perfectly reliable indicator of how the interviewee would behave in general.” A related commenter frames it as a structural mismatch: a PhD’s value proposition is a complex, well thought out thesis, and the exercise asks for the opposite. You cannot resolve this from the candidate seat. Play it their way and notice what it tells you about the work.

What to say: Out loud, in this order: restate the problem, ask two clarifying questions, state your assumptions, propose the crude version, name how you would know it is wrong, then name the better version you would build if the crude one survives.

“Let me make sure I have it: you want to prioritize compounds for a screen, and the constraint is assay throughput rather than compute. Two questions: how many can you actually run per week, and do you have any negatives, or only the hits? Assuming a few hundred per week and hits only, the crude version I would build this week is a similarity baseline over your existing hits, no learning at all, so we have a number to beat. The way I would know it is wrong is if it retrieves only analogs of what you already found. If it survives that, the version I’d actually want is a model trained on the assay readout directly, and the first thing I’d check is whether the readout is stable enough across plates to train on.”

Q10. “It doesn’t look like this is on your resume, but I want to be sure.” (the verification probe)

Confidence: ●

Why they ask it: A large part of this round exists to confirm that the resume is real. Recruiters say so repeatedly: “I can tell if their resume is inflated or accurate, if they can communicate clearly, if they can speak to their past projects.” A hiring manager arguing for taking the first call himself: “Cv is usually 90% buzzwords and things the person didn’t actually contribute to. Why not figure this out on the first call with him, asking a couple experience related questions instead of letting hr do this.”

What they are listening for: - Whether you can go one level deeper than the bullet. “Sometimes people claim to do things on their resume but when probed, they cannot really speak to them or give vague answers and cannot give me a specific example of when they actually did the thing.” - Quantified claims that survive a follow up: “if you’re telling me you did something ‘well’, I want to know what you specifically did and how you’re defining doing it ‘well’.” - Calibrated self assessment. A talent acquisition professional: “You’ll get much further being honest with experience level than when you tell me you’re experienced with a specific system, and your follow up statement demonstrates you have little to no familiarity.”

How it fails: One candidate described his successful screen as “very much an ‘are you BSing or is this experience actually genuine?’ round,” including an aggressive question about how he did a master’s degree while working full time. Another cleared the entire behavioral half of a screen and was rejected within the hour on a single tool claim: “my CV says intermediate Excel but, I am not and the role is looking for an intermediate user.” The rejection came with that stated reason.

What to say: Answer at the level of a specific instance, and mark the boundary of your experience without apologizing for it.

“I’ve used it in production on one project, [the project], where I [the specific parts you built with it] myself. I have not [the boundary of your experience with it, named plainly], so if that’s what the role needs on day one, I’d be learning that part.”

Before the call, go down your own resume line by line and, for anything you cannot expand into ninety seconds of specifics, either prepare it or remove it.

Q11. “When would you be able to start?” / “What’s your availability?”

Confidence: ●

Why they ask it: It is one of very few universal questions. A recruiter: “The only universal questions I ask all candidates are … what’s their availability timeline.” Another names availability as one of the two classic hard filters on an application form, alongside the right to work. Recruiter handover notes to the hiring manager include, at minimum, why the candidate is looking, a summary of their experience, and “any timeline constraints for the candidate to interview or start.”

What they are listening for: - A real date, and whether it fits the requisition’s urgency. - Notice period and anything that constrains scheduling for the rest of the loop.

How it fails: Vagueness costs you nothing directly but delays the loop, and the requisition has a clock. One hiring manager describes screening a hundred applicants in a week and says that once four or five good candidates are in the second round, “I’m not really revisiting the incoming resumes again.” In the postdoc and national lab lane, the mismatch runs the other way: a PI notes that interest and funding are separate events, and lab timelines run months, so a start date you name may be met with a long silence that is not a rejection.

What to say: Give a date and one constraint, then hand the timeline question back.

“I defend in [the month you defend] and could start any time from [the earliest date you would actually accept]. The only fixed constraint is [the one commitment already fixed in your calendar, with its dates]. What does your timeline look like on your side, and how many rounds are there after this one?”

By lane: Big pharma runs months and a slow calendar is normal; multiple candidates report ten to fourteen days just from HR screen to hiring manager. Startups can go from first call to offer in under a week. A national lab candidate went from interview to news in two months, and another got an offer in eleven days only because the section head knew of a competing deadline. Ask for the timeline, because the answer differs by an order of magnitude across lanes.

Q12. “Are you interviewing anywhere else? Where are you in those processes?”

Confidence: ●

Why they ask it: Recruiters give several distinct motives, and they are not the same motive. Pipeline management: “If you are in final stages with 3 other companies, I’ll never be able to move you through our process fast enough to compete.” Leverage on their own side: “if I like you, and you’re approaching finals somewhere, I’d like some leverage to use with my HMs to make sure they get you in ASAP.” And a candidate volume check: “1 or 2 other (early) processes are fine. But some people have 12 things going on for all kinds of places, which is a red flag.”

What they are listening for: - Whether you are a real prospect or a lottery ticket. - Whether their process is fast enough to win you. - Consistency, because it will be checked later. One candidate warns: “Treat recruiter calls as if you are talking to a permanent recording machine,” and reports recruiters cross checking earlier statements about competing offers.

How it fails: Naming an inflated number of processes, and naming companies to an agency recruiter.

Contradiction in the evidence: whether answering can hurt you. Internal recruiters say it cannot: “We always expect candidates to be interviewing other places. Answering that question shouldn’t deter your chances in any way.” An agency side recruiter says the opposite about the company names specifically: “most recruiters will then call A and B company and get those jobs on and put their candidates in… you are diluting your application everytime you tell someone where you are going to.” The split tracks who is asking. Internal recruiter, answer at the level of stage. Agency recruiter, answer at the level of stage and withhold the names.

What to say: Stage, not names, plus a live deadline if you have one, because a real deadline is the one thing that compresses these timelines.

“Yes, [how many other processes and what stage each is at], and [the nearest real decision date, if there is one]. That’s not pressure, it’s just the calendar I’m working with. If your process runs longer than that, it would help me to know now.”

By lane: In the postdoc lane the same question is asked and the advice from the academic side is stronger: “Make sure not to hide if you have applied elsewhere; scientific world is small, and people talk.” The PI version usually adds “what criteria would you use to decide between competing offers,” and the criteria are what is being scored.

Q13. “What’s your biggest weakness?” / “What’s the most recent piece of critical feedback you received?” / “How would your last boss rate you?”

Confidence: ●

Why they ask it: To see whether you have a working model of yourself and whether you can discuss criticism without either collapsing or deflecting. Recruiters keep a version of it in their standard set: “What are you not good at or not interested in doing professionally? (push for at least 2-3 examples and why).” One recruiter’s sharper variant: “Who were your last three bosses, and how will they each rate your performance on a 0-10 scale when we talk to them? … it’s not that you’ll actually ask, it’s that you get a sense of how the person responds to management.”

What they are listening for: - Specific, recent, and real. A founder: “Very specifically, what’s the most recent piece of critical feedback that you’ve gotten?… I’ve found that throwing in the ‘references’ comment is important because it tends to bring out more honest responses. I’m literally looking for them to get into the nitty-gritty of the when and the how, not fluffy or abstract responses.” - Whether you can hold other people’s negative view of you without contempt. One founder asks “If I were to go and speak to people who don’t think very highly of you, what would they say?” and watches for evasion, justification, or denial that anyone dislikes you. - In one large technology company’s intern HR round, the question arrives in a compressed form: summarize your shortcomings in two or three keywords, and give three keywords your collaborators would use about you.

How it fails: Abstraction, and the humblebrag. The founder quote above is aimed exactly at “fluffy or abstract responses,” and the reference framing exists because candidates otherwise supply a safe answer.

What to say: Name a real limitation, give the incident, give the mechanism you now use, and give the current status honestly.

“The most recent piece of critical feedback I got was from [who gave it] after [the occasion]: [the feedback in their words, not softened, and what it means in practice]. It cost me [the concrete consequence]. Since then [the mechanism you actually use now], and [the check you built in so it does not depend on your memory]. It is better, not fixed; [the condition under which you still fall back into it].”

Q14. “How do you work with AI?”

Confidence: ◆ (small number of sources, and both from one platform; the evidence is thin)

Why they ask it: A data scientist job hunting in North America reports that more and more recruiters now like to ask “How do you work with AI?”, as a routine recruiter question rather than a technical one. In one large technology company’s intern HR round, the question is a formal scored item: which agents and tools do you actually use, what AI information and models do you follow, and give concrete specifics.

What they are listening for: - Concrete tools and concrete use, not opinion. - Whether your practice matches the team’s. One candidate interviewing at a well funded AI startup asked how much the team writes its own code and was told that for the last three months they had been “almost exclusively using claude/codex on their research teams, as it’s allowed them to spend much more time experimenting and ideating, and leaving the execution to the bots.”

How it fails: Being caught unprepared. The same data scientist says the question caught her off guard the first few times, that she answered without structure, and that she was cut at the recruiter round more than once.

What to say: Two sentences of practice, one boundary.

“Day to day I use [the tools you actually use] for [the parts of your work where the specification is already clear, named concretely], and I keep [the parts you do not hand over] under my own hands, because that is where a wrong answer is expensive and silent. The habit I’ve built is [the one rule you actually follow, stated as an ordering].”

Q15. “Why do you want to work at a small company?” / “How do you feel about ambiguity?”

Confidence: ●

Why they ask it: Small companies are screening for flight risk and for whether you need structure they do not have. A candidate account of what a startup screen is really testing: “They are also vetting you to see if you’re just taking the job for a paycheck and will continue interviewing for bigger companies. Big company employees don’t work out as good hires at startups usually.” Founders state the adaptability criterion openly: “anyone you hire is likely to be doing a new job in three to six months. Smart and effective people are adaptable.” And: “The worst employees for a startup are those that come in and ask for the training manual. At a startup our job is to figure it out together, no one will spoon feed you a process.” A pre Series A founder asks it directly: “What is your appetite for risk? There is a high chance of failure.”

What they are listening for: - A reason to choose small that is not just availability of the job. One candidate reports being asked repeatedly why he wanted small companies after working at a large technology company, and noting that “saying better opportunity does not fit well.” - Evidence you have operated without a defined scope. At science startups this is the job description: “You often create your own job responsibilities as you go.” - Breadth. In biotech specifically, “startups want someone who is a generalist, not a specialist, with as much experience as possible in a broad number of areas.”

How it fails: One candidate recorded the whole exchange in two lines: asked whether he liked startups, he answered that he did not, and the process ended there. The other failure is inverse and worth knowing: candidates from large organizations are screened against at startups, with one commenter describing big company hires who “can’t stick to a small budget or expedite a timeline.”

What to say: Give the concrete reason, then the evidence, then the honest limit.

“I want to be close enough to the decision to change it. In my group I [the list of things you personally carried, from building the thing through to writing it up and dealing with whoever else was involved], and the part I liked was that nobody handed me the scope. What I’d want to know from you is how the first six months are defined, because I do better with a clear objective than with a clear process.”

By lane: This question belongs to the small research organization and startup lane, and a founder or CEO often asks it personally. Big tech and big pharma do not ask it. Note the inverse question exists too: in the pharmaceutical lane, moving from a startup back to a top tier company is described by an eighteen year veteran as difficult, so the direction of your move is itself read as a signal.

Q16. “What should we be doing differently?” / “I’m not sure you’re the perfect fit. Why do you think you’d be great?”

Confidence: ● for the practice, and the evidence directly contradicts itself on whether to volunteer critique

Why they ask it: In a founder round, this is a manufactured objection and the response is the data. A founder: “This is a great question because it’s an objection. I want to see how they handle objections like they would from a potential client or from a co-worker with a contrarian opinion.” Another investor and operator describes the leading indicator he hires on: “The candidate can see things you don’t see. Even within topics you’re fluent in, they’re able to convince you of new points of view or make you realize you’re missing something.” A sales leader’s version is “What should our team be doing differently that could yield 10x improvement?”

What they are listening for: - That you have an opinion at all. On the 10x question: “Can’t think of any suggestions. This one is a big red flag for me… They should be pretty well-versed in our company and product by then, so it’s often a sign that they haven’t done their homework.” - Ambition of the suggestion: “Oftentimes I hear ideas that are a 10% improvement, not 10X.” - Composure, not correctness, when the objection is aimed at you.

How it fails, and the contradiction: Volunteering critique unasked has documented costs. A candidate who passed the technical rounds shared an unsolicited view on the company’s product strategy with a co-founder and was rejected; commenters diagnosed it directly: “where you asked for an opinion in this one? Because if you shared that perspective without being asked to, I see why you were rejected.” The strongest version of the opposing rule: “Having been interviewed directly by the founders of the start-up means the company is a) still small enough and/or b) the founders still care very much personally whom they employ. If in such context you are applying as a rank and file software developer the interview is NEVER a good place and time to discuss your thoughts on their business if not being asked.” This contradicts the founders above who treat unprompted critique as the exact signal they are buying. The split tracks two things: whether you were invited, and whether the critique lands on a feature or on the business model itself. Rejecting the business model of the company you are interviewing at, at any seniority below the level that sets strategy, is the version that fails.

What to say: If invited, go one level deeper than a process tweak, and frame it as a question you would want to test rather than a verdict.

“One thing I’d want to test in the first month: [the public claim of theirs you actually read], but [the pattern you noticed that the claim does not account for]. If that holds, the ten percent version is [the incremental fix]. The ten times version is [the structural explanation, stated as a possibility rather than a diagnosis]. I don’t know which it is from the outside, and that’s the first thing I’d want to find out.”

If not invited, hold it, and use Q17 to ask the question instead of stating the conclusion.

Q17. “Do you have any questions for me?”

Confidence: ●

Why they ask it: Partly as a sell and partly as a signal check. One hiring manager describes his own first call as mostly orientation, saying “the goal with the first call is that they’ll ask the majority of the questions.” A recruiter is blunt that the content matters less than the fact: “recruiters often aren’t evaluating you too much based on the content of your questions, but they do notice the impression you give… Showing that you’ve prepared already puts you ahead of the curve.”

What they are listening for: - Preparation, and questions about team, culture, and longer term direction rather than only logistics. - At founder level, the questions are scored directly: “people who are very interested in joining a company have done their homework. They typically have several detailed questions, and those questions reveal a lot of things those people find important in their job.”

How it fails: Having none. Also asking a question the interviewer reads as out of scope: one candidate asked a second round interviewer what he thought needed improving in the team’s management and was told that is something to ask after you start, if you get selected. Commenters diagnosed the wording rather than the topic. Note also that the slot is not guaranteed: one candidate’s four minute screen ended without it, “They didn’t even ask me if I have any questions.”

Contradiction in the evidence: timing. One recruiter says nothing should be held back: “The best questions you should be asking in an interview don’t really change depending on the stage… Don’t hold anything back thinking you’ll save it for the next round, because the next round isn’t guaranteed.” A recruiter with thirty years in the field advises the opposite for anything touching flexibility or benefits: “I always coach that it’s best to wait till they want you. Then you’re in the driver seat.” The split tracks the type of question, not the stage: diligence about the role and the team early, conditions of employment later. A separate split runs on the closing question “do you have any concerns about my fit that I can address?” Two managers report it working well, one saying “I thought this was brilliant because I did circle back to some of her gaps.” One interviewer says the opposite: “NEVER ask that question during an interview. It directs the interviewer to deliberately think negative thoughts about you that they will not be able to forget.”

What to say: Two or three questions the person in front of you can actually answer, and one that tells you something real.

“Three things. Why is this role open, is it new headcount or a replacement? What does the rest of the process look like and how many rounds? And in the first sixty days, what is the problem you would want this person to have made progress on?”

Then, depending on lane, one substantive question: for a startup, how the research agenda is set and how much runway is behind it; for a lab, what happens to a project you start if you leave; for big pharma, what the hiring manager’s team is measured on.

By lane: A recruiter cannot answer research questions and should not be asked them; several recruiters say explicitly that they are not that level of expert and that technical questions belong to the hiring manager stage. Save those. In the small research organization lane the first call may be the founder, in which case the substantive questions are the only ones worth spending minutes on.

What the question is actually for

The recruiter is not evaluating your judgment when asking for a number. She is running a comparison against a band that already exists ●. A recruiter describing her own screen: “My primary focus is to make sure the candidate is ok with pay range, location, schedule.” A candidate who has been through many pharmaceutical screens describes the call as “3 minutes to discuss your background, 3 minutes to tell you about the job, and 3 minutes to talk about salary.” Another puts the mechanism plainly: “there’s a salary range for each position (it may be broad at your level, but the limits will be strict), and they want to make sure that your expectations are compatible with theirs.”

From the hiring side, the comparison is explicitly a cut ●. A hiring manager at a small biotechnology company: “if you aren’t pursued, they will typically screen you out based on compensation being too high or if the recruiter doesn’t believe the personality is a good fit.” A recruiter at a large technology company: “Recruiters have always rejected based on compensation expectations, even during better times. If you’re out of budget or at the max end of the budget and there are other candidates just as capable and happy with $10-15k less, it makes sense.” The same person adds the part candidates usually miss: “Comp expectations are considered the whole way thru all the way to offer. I’ve chopped candidates at offer stage due to bad faith or incredibly unreasonable aggression around compensation.”

One recruiter quantifies the tolerance: “If you’re in range but top of band most teams will still interview. If you’re +20-30% of band, it may not be worth wasting time” ◆.

There is also a version of the filter that has nothing to do with affordability. A C-level executive: “We coach all hiring managers to look for the signs that a person will be dissatisfied with their pay as it’s a big giveaway that they won’t stay long in the company. If your desired salary is above our target and especially if your level of experience falls below our target, we know from experience that you’ll be onto a new job within a year. It’s better for us to pass on you” ◆. A recruiter gives the same mechanism as a concrete case: a candidate asked 95 to 100 against an 80 to 90 budget while others asked 75 to 85, and “They didn’t get interviewed; the salary demand itself wasn’t the killer […] the problem was that they were simultaneously asking for more (could be done for a great candidate) while offering less than other candidates in the same pool. If you’re asking for more, you need to be demonstrably better” ◆.

The documented gap between public and anonymous. This is the sharpest split in the whole evidence set, and it tracks whether the recruiter is speaking under their own name ●.

Under their own name, on public professional platforms, recruiters say the question is benign. “When we ask about your expected salary, it’s not to undervalue you or judge your worth. It’s to ensure that both sides are aligned from the very beginning.” “So next time a recruiter asks about your salary expectations, see it not as a ‘trap,’ but as a step toward an honest and fair hiring journey.” A former recruiter at a large technology company, on her own channel: “when a recruiter asks you what are your salary expectations it’s not a trick question it’s actually them being genuine,” and, more strongly, “hiring managers if they really like you want to give you as much money as possible cuz they know you’re the perfect fit and they’ll put their neck on the line to um extend their budget.”

Anonymously, on the same subject, recruiters describe leverage and concealment ●. “Salary is also an instant rule in/rule out.” “Upper executives ask us not to disclose top range unless we need to.” On why the range is withheld from candidates: “People are greedy and the vast majority will just say they want the top of the range, which makes your job 10x more difficult because now they know the top end… You’re letting the candidate control the process instead of vice versa.” An agency recruiter describes actively pushing candidates down: “If I know the candidate is earning $90k and wants to jump at the $130k mark, it’s my job to hammer them down back to reality to the $110-115k mark.” And a candidate reports being told directly that a recruiter’s own pay depended on it: recruiters “know it’ll give them a leg up in negotiations, and some of them are even paid specifically to get that number (as one recruiter was brazen enough to reveal to me)” ◆.

The named public voice is not even internally consistent. The same recruiter who said publicly that the question is “genuine” advises elsewhere: “the reason why you want to redirect this question is because when you’re in a recruiter phone screen… you actually don’t have enough information to be able to tell the recruiter what your expectations are how would you know” ◆.

What to do with this: Treat the public framing as marketing and the anonymous framing as operations, but do not treat the anonymous framing as malice. Both describe the same act: your number is compared to a band, and a mismatch ends the call. Say to yourself before every screen: this is a comparison, not an evaluation.

The controlled test

One candidate ran the only controlled experiment in the evidence, and it is the single most useful item in this section ◆:

“I experimented with salary requirements! I applied for the same job under different names and with very similar resumes (keeping key words the same but making minor changes to the layout). Out of the 20 jobs that required my expected salary, I used the minimum, average, maximum, and above maximum. Most maximum or above-maximum salary applications received a rejection email within one or two days. The minimum salary always resulted in a first-round interview.”

Read what this does and does not establish. It establishes that at the application and filtering stage, the number is a monotone filter: lower gets you in, higher gets you rejected fast, and identical qualifications do not rescue a high number ◆. It does not establish anything about the offer that follows, because no offer stage was reached. It is a single person, on twenty postings, with self reported design and no reported effect sizes. Treat it as strong evidence about the filter and no evidence about the offer ◇.

Everything else in this section is downstream of that distinction.

Quoting the employer’s own published range was treated as too expensive

This is the pattern that most damages the standard advice, and it is attested repeatedly ●.

A candidate who named the posted range verbatim: “I was asked for my expected salary during an interview. I replied that the salary range in the job posting was exactly what I was looking for. I was rejected the next day by the recruiter because my salary expectations were too high. You cannot make that up. Obviously, they were looking to lowball and had no intention of ever paying the posted range.”

A candidate who met every listed and preferred requirement, including a rare language: “I state it would be on the higher end of the range provided due to meeting not only minimum requirements but also all preferred requirements too. After this the demeanor completely changed and I was essentially rushed off the call… I have just received my rejection email.”

A candidate who asked for the top of the recruiter’s own stated real budget, not the posted one: the posting said 76,000 to 116,000, “I ended up saying $95k which isn’t much more than my current salary. They told me that their budget was $90-95k and they were required to put that large range. Anyway, I was very disappointed when I ended up being rejected.”

A candidate who asked 110 against a recruiter stated 100 to 140: “I said 110k, and the next day I got an email saying the manager thought that was a bit too high, but maybe they could work something out. Then a couple days later, I got a rejection.” A second candidate confirms the same shape twice in one search: “Both said the interview went well, asked what i wanted / confirmed what i initially asked for, then rejected me. The amount is usually not crazy high either. It is actually less than what i make now.”

And two cases where the stated reason cannot be true ◆. One candidate answered at the top of the range, was ghosted, and then “I saw that they had reposted the position and this time the lower end was 10k higher than I asked for.” Another reports the same class of event from the other direction: an interview where “his mood shifted right after answering his question about my salary expectations which was $25 per hour,” followed by ghosting, followed by the same posting reappearing at 18 dollars per hour.

Recruiters confirm the underlying rule from their side. “you’re not getting the top of the band unless you’re practically overqualified for the role.” “If you go for the top of the range and you don’t have the experience for that, you’ll get a lower offer or won’t be considered because you’re too expensive in relation to your experience.” What annoys recruiters most, per the top voted answer on the question, is “when candidates flip the question and I give a range and they immediately tell me their expectation the top of the range” ●.

What to do with this: Do not name the top of any range, published or spoken, on a screening call. If you use the published range at all, use it as an alignment statement rather than a claim on its ceiling. A candidate’s working sentence, reported as never having raised a flag: “I’m comfortable with the salary range shown in the job ad, and if possible, I’d like to discuss my salary expectation further later in the process.”

What deflection actually costs

Deflection works often enough that people recommend it, and fails hard enough that the failures are unrecoverable. Both sides are firsthand.

Deflection failing. The clearest case is a call that ended in four minutes ◆. The candidate was asked for a number three minutes in, said he would need to know the benefits and equity situation first, and was told: “No, just forget about benefits and stock options for now, I just need to know what number you’d be ok with.” He held. The recruiter: “Woah woah man, you’re not even there yet. We can talk about that later but I NEED to know what is negotiable now.” The recruiter then said “Ok, have a good one,” and hung up before the candidate could say goodbye. Rejection followed a week later.

The same shape, without the anger ◆: a candidate turned the question around, “If you could tell me what the available budget is for this position, then I can confirm whether it’s suitable for me or not.” The interviewer laughed and said “Okay, we can skip this point for now.” The candidate’s own report: “After that, the whole vibe changed. And just as I expected, of course, no one contacted me again about the third round.”

Asking for the range before the call has its own failure mode ●. “Asked a couple of recruiters for salary bands before the call and got ghosted lol.” “I asked him the position, tasks and the pay range: He replied with everything, except the pay range. I asked again the pay range. Ghosted.” From the recruiter side, this is not accidental: “In my experience if you send an outreach message and what you get back is ‘what’s the comp’, 95% of the time they never meet about the role.”

Deflection also frequently simply does not survive contact ●. “I tried to dodge but recruiter said it was mandatory.” “during the onsite prep call with the recruiter he required me to give some sort of salary range… or I couldn’t go ahead with the onsite interviews.” “they asked me my salary expectation and I said ‘whatever is the industry standard’ and they kept persistently asking me for a number.” “Even though I tried to defer this, they got it out.” Recruiters name the exact phrases that fail: “Don’t tell the recruiter you’re looking for ‘market rate’ or ‘I’m sure you’ll make me a fair offer.’”

And recruiters describe the reputational cost of over deflecting ●. “If you dance around the question (‘I will wait to evaluate the total compensation’), you’re just gonna piss them off.” “Don’t play games. Tell me exactly the comp you are wanting and I will tell you exactly if it’s within range or not. It’s a stupid game candidates play and is an immediate turnoff.” A candidate states the norm the community converged on: “If you want to deflect the first time the question is asked, fine. But if you have to deflect more than once, you won’t come off like a professional.” A recruiter draws the same line more precisely: “Asking ‘what’s the budget?’ or ‘what’s the range?’ is completely fine. In fact, it’s a good question… But where people get it wrong is they rely on that as a rule. If you keep deflecting and refuse to give any indication, it can come across a bit evasive, especially later in the process.”

Deflection working. A candidate who compared his own two behaviors: “Some of the ones where I did not state my expectation mostly went silent; with the others the recruiter stated the company budget up front. The first group went nowhere, the second group basically all reached the interview stage.” ◆ Note that this is a report of deflection failing.

Against that: “I always respond with, ‘what is your expected range?’ That has always worked” ◆. A hard refusal against a stated company policy: “they said they must have my previous salary because it is their policy. So I responded that it was my policy not to disclose my salary. They couldn’t argue with that, and I got the offer I was looking for” ◆. “I declined to answer with the role I have now, and it worked out :shrug:. Not everyone is trying to screw you” ◆. And at one large technology company, “my recruiter asked before interview but did not press when I declined” ◆.

The split tracks two things ◇. First, seniority and scarcity: one candidate reports the deflection script works and adds, “you will see some companies pull out from it, you need to be prepared for that. It’s more acceptable the more senior the position is.” Second, whether the recruiter has already been told to collect a number before booking further time; where that is a hard requirement, no wording survives it.

What to do with this: Deflect exactly once, in the form of a question about their range, and then answer. Say it as one move, not two: “I don’t have a specific number in mind yet. Could you share the range that’s budgeted for this role, and I’ll tell you right away whether it works?” If they answer, respond to their number. If they push back and ask again for yours, give a range immediately and without apology. Do not deflect twice.

Does a low number cap your offer?

The evidence splits cleanly, and the split tracks organization type. This is not an averaging problem; both sides are right about their own lane.

Where a low number does not cap you. A recruiter at a large technology company: “Sharing comp expectations that are too low will NOT result in a lower offer. Why? Because HR wants to make sure internal equity is fair and the hiring manager doesn’t want you to leave the moment you get a better offer. If the range is 150k - 175k and you tell me your salary expectations are 110k, the MINIMUM I’m going to give you is 150k.” He adds the scope himself: “this is for large tech companies and FAANGs” ◆.

Corroborating from other recruiters ●: “If you’re too low and we move forward with an offer, most likely you will get more than your ask. Positions have to pay people in a similar ballpark for the same job.” “If they are looking for the low end of the range but have everything we want - we will pay them the high end.” And from candidates on the receiving end ◆: “The few times I gave a lower number the recruiter told me my number was too low and what the market rate is.” A candidate at a travel technology company who lowballed himself: the recruiter’s reaction was “Really?…” followed by an unprompted addition of five thousand dollars to the candidate’s own number.

In large pharmaceutical companies the band floor plays the same protective role ●: “most, if not all, major biotech/pharma companies have a policy to not pay outside of brackets be it above or below.” “if you low ball the range companies usually have a policy where they have to pay within a certain band even if your original salary request was lower for roles.”

Where a low number becomes the offer. “Well, made a mistake on telling the recruiter salary expectation prior to the offer stage. No surprise, recruiter came back with an offer exactly what I asked for and told me that you got what you wanted and pls sign. I didn’t know what happened on that day, the number i asked for was my current TC” ◆.

A candidate who named 65 to 70 against a stated 60 to 70 budget got an offer letter at 60, below the floor of his own stated range ◆. A candidate who named a number on a screen learned by accident, from a second recruiter working the same role, that it was “10-15K higher than what I quoted the screening lady” ◆. A candidate who let his salary history out: the recruiter “refused to put me through for that saying that it was not usual to get more than 10% more than what I am on. The company was willing to pay more” ◆. And the long tail of regret is real ●: “The first time I did not dare to ask; the person who got in was at least 5% above me”, and “I also asked too low when I joined last year, and I have regretted it all year”.

Two structural facts make the number durable ●. A recruiter: “recruiters keep very detailed notes so we know exactly what salary expectations you shared with us.” And a recruiter’s own handover sheet to the hiring manager begins with “comp expectations.”

What the split tracks: it tracks whether the employer runs a formal band with an internal equity policy, and whether anyone in the process is compensated for the spread ◇. Large technology companies and large pharmaceutical companies have formal bands and pay compression policies, and both sides of the evidence agree that a low number gets pulled up to the floor ●. Small companies, agency recruiters, and any process where one person both hears your number and writes the offer are exactly where the number becomes the offer ●.

What to do with this: Never state a number below what you would accept, in any lane, because the protection is a property of the employer and not of you. Where you are uncertain about the lane, treat the number as binding.

The stage distinction, which is the key to this entire section

Almost every apparent contradiction above dissolves once you separate two stages that use the same question for opposite purposes.

Stage one, filtering. The recruiter is checking a number against a band to decide whether to spend more time. Recruiters say this explicitly ●: “Recruiters are not negotiating when initially discussing salary expectations, we just wanna make sure we don’t waste time in case you are already way above the top range.” “It’s a negotiation tactic but you aren’t actually negotiating salary at this point (or any point) with the recruiter.” “A good recruiter aligns salary expectations on both sides before you ever reach interview. If the numbers don’t work, you shouldn’t be put forward.” One hiring manager’s own ledger: 51 of 81 first calls moved forward, with disengagement and “the candidate’s salary range expectations not matching what we can offer” as the leading cuts ◆.

Stage two, offer setting. A different mechanism, different people, different room. At a large pharmaceutical company, per its own published careers material, “The recruiter will calculate an offer in partnership with the hiring manager and deliver the offer” ◆. At a technology company that published its process, the offer goes into a private channel with named approvers, and offers outside guidelines “require approval from both the hiring manager’s manager and the Engineering executive” ◆. That approval friction is a structural reason a high number costs you at stage one and buys you very little at stage two ◇.

The consequences of confusing the stages are visible in the evidence. A candidate reports the specific error: “I brought up salary too early ; process slowed and eventually ended” ◆. And in the same ledger, of twelve processes, two died on the pay conversation ◆.

Where the evidence conflicts on this point, and it does: one experienced candidate insists “negotiations begin the moment you interact with a recruiter,” and a compensation service states “Negotiations can start in that first recruiter phone screen.” Against that, two recruiters say flatly that no negotiation is happening at the screen. The split tracks who is speaking ◇: candidates and negotiation coaches treat the screen as anchoring, recruiters treat it as filtering. Both can be true at once, because a number that anchors is also a number that filters. The practical resolution is that at stage one your number can only lose you the process or pass you through; it cannot win you money.

Note also what the offer stage actually yields, which is more than the screen implies ●: “I was negotiating an offer in the fall and was able to get the base 17% higher than their original offer, which was 20k over the range HR mentioned in the screening.” “I said a number and got an offer over it.” “my offers increased by 15% on average, the largest by 25%”. And a case where a first call floor became the offer: a candidate said he needed “minimum in the low-to-mid 300s in any combination of compensation components,” was told “Okay, our ranges overlap depending on what you can bring to the table, let me schedule your final round,” and closed at 306,000 ◆.

What to do with this: Write two numbers down before the call. A pass through number, which is the range you say out loud, chosen so that it is credibly inside their band and above your true floor. And a floor, which is the number you will not go below at offer stage and which you never say out loud on a first call. On the screen, your only job is to get past the comparison without capping yourself. Say to yourself: at this stage I can lose money but I cannot win it.

The published range is often not the real budget

Say the quiet part out loud, because a talent acquisition person did ◆:

“the range is usually meaningless anyway. ive had comp teams hand me ranges like $120-180k for a senior engineer. that range exists because HR needed to file it with the state. the actual budget the hiring manager has? $145-155k. nobody tells the candidate that part.”

Independently corroborated by a candidate who was told it directly: “They told me that their budget was $90-95k and they were required to put that large range” against a posted 76,000 to 116,000 ●. And by candidates who ran into the divergence live: “They asked about compensation expectations and then provided a salary range that was lower and different from the range advertised in the job posting.” “Especially annoying is when recruiters give you a range that could work, but realistically, the company will never give you top of range, and the real number is closer to the bottom.” “MANY times I’ve asked questions about the JD and they tell me ‘that shouldn’t be there’, ‘that’s a typo’… even ‘no we’re not actually remote’ ‘no that’s not the true salary range’.”

Recruiters describe deliberately quoting a narrowed range based on their read of you ◆: “If I have a role with a range of $100-130k, I gauge their experience and throw out a number that makes sense. If I feel there are not at the top end of I will say it is paying $100-115k and gauge their response.” Another names the width itself as the tell: a red flag is “The pay range is huge (more than $20,000 spread).”

The countervailing practice exists and is worth knowing ●. Some recruiters publish and hold the range: “been in TA for 20 years and i just tell them the range. every time. first call. the ‘candidates will anchor to the top’ argument is nonsense… when you play coy with salary, you’re selecting for desperate candidates who’ll tolerate that.” One company routes the entire alignment step through a published compensation calculator rather than extracting a number from you. One company commits in writing that “Expect the recruiter to discuss the compensation bands with you during your first screening call.”

What to do with this: Ask for the realistic midpoint, not the range. The sentence that gets a usable answer: “I’ve seen the posted range. Where in that range are people actually landing for this role right now?” A wide posted spread is a signal to ask this, not a signal about your value.

Working scripts

These are sentences taken from people who report using them and what happened. Treat each one as a shape rather than a script: the numbers, the levels, and the situations inside them belong to the people who used them, so put your own in before you borrow the sentence. What transfers is the structure, not the figures.

To defer once and hand the question back. The most endorsed wording in the evidence, reported working: “I don’t have a specific number in mind, what’s the range?” ◆ A longer version that also signals you understand package structure: “I’m open to the market range for this role. I understand there are a lot of different components within a salary such as base, equity, and bonus so I’m curious if there’s a specific range the team has in mind for this role.” ◆

To respond to a range they just gave you. A three case script that a candidate reports using dozens of times ●: - Higher than you expected: “That sounds like the right ballpark, we can work with that.” - In line with expectations: “Hmm, is there room for negotiation in there? That would be the lower end of my expectations.” - Below expectations: “Thank you for sharing this upfront, those numbers are well below my expectations and so I’d like to end the conversation here, thank you for your time. Feel free to reach out if you revise your numbers in the future.”

The same candidate reports the third variant surfacing hidden budget on the spot: “if they have the flex, this line brings it out right away. Just this week I used it and the recruiter on the other end said - ‘oh do you live close the greater NYC area? We can say that you’re in the New York zone and get you a higher TC’ If there is no flex, it saves you a ton of time” ◆.

A neutral alternative from another candidate, used identically in all three cases so that your reaction leaks nothing: “That range sounds like a good starting point,” or “I think that’s worth having a conversation.” And for a range that is far too low: “It looks like this may not be a good match, and I don’t want to waste your time, so please feel free to reach out if the company decides to extend the range.” ◆

To give a number when a number is required. A recruiter’s own fallback script: “Based on my research and the role’s requirements, I would expect a base salary in the range of $X to $Y. This range reflects my qualifications, experience, and typical market rate for this position.” ◆ A candidate’s version with a stated escape hatch: “Based on my research, the base for this position is $75k - $95k, and a number in that range would be acceptable as a starting point for negotiation, but contingent on the details of the position.” He notes he only uses it “as a last resort if I’m getting the feeling that there is little chance I’ll be able to proceed with the opportunity if I don’t answer” ◆.

A recruiter’s set of workable phrasings when no range has been disclosed ◆: “I’m interviewing for roles that are in the $150-200k range base plus bonus and equity.” Or: “I’m targeting a total rewards package over $250k with flexibility around the mix between base and bonus.” Or, for a candidate who exceeds the requirements: “I care a lot about internal equity so I’d like to understand your range better, but given that my experience exceeds what you’re looking for, I’d expect to be above the midpoint.”

To state a floor without naming a ceiling. The one fully traced success in the evidence, first call wording through to offer ◆: “I’m looking for a minimum in the low to mid 300s in any combination of compensation components to make a move.” The response was “Okay, our ranges overlap depending on what you can bring to the table, let me schedule your final round,” and the offer came in at 306,000. Note the structure: a floor, not a target; “any combination of components,” which refuses to be pinned to base alone.

To use a published range without claiming its ceiling. “I’m comfortable with the salary range shown in the job ad, and if possible I’d like to discuss my salary expectation further later in the process.” ◆ Or, where pay transparency law applies: “The listed salary range aligns with my expectations.” ◆ A sharper version that forces them to do the work: “Could you narrow the posted band to the part that applies to someone at my level?” ◆

To refuse salary history specifically. This is a separate question from expectations and deserves a separate answer ◆: “I’m not comfortable sharing proprietary information about how my current employer pays people.” And a documented case of holding against a stated policy: “It’s my policy not to disclose my salary.”

To recover after an over ask. One candidate re-anchored downward and the process resumed rather than ending ◆: he asked 85 against a stated 70, was told they would not go that high, then said he would be open at 75, and an interview was scheduled. The recoverable move is to name a lower number yourself, immediately, in the same conversation.

To read the requisition and price into it. A recruiter names the input ◆: “If the role has been open for quite some time the team will be more willing to move quickly for the right talent… If you have the niche experience they are looking for, raise your compensation target accordingly.” The question that gets you this on the screen: “How long has this role been open, and what has made it hard to fill?”

What not to say. “Market rate.” “I’m sure you’ll make me a fair offer.” “Whatever is the industry standard.” All three are named by recruiters or documented as failing ●. Also do not immediately claim the top of a range they just gave you; that is the single most cited irritant ●.

Decision table by lane

Where in the funnel this is decided, and by whom

Not by the hiring manager, and often not by a person at all ●.

The earliest layer is the application form itself. One company states in writing: “Due to a high volume of Candidates, [we use] automated decision-making to filter Candidates based on responses to our application questions. When certain criteria is met regarding visa sponsorship, work permits, hiring country, and other employment restrictions, our software will reject your application.” An employee at another company describes the same thing internally: “We have a question ‘are you currently authorized to work in the US’. ‘No’ answers are filtered out.” The sponsorship question sits inside the same auto filtered knockout block as referral and prior employment questions ◆.

The second layer is the recruiter, and this is where the decision is usually final ●. A hiring manager at a large pharmaceutical company: “We screen for visas via HR/ recruiter prior to me even seeing the resumes to think about which candidates to interview. So if youre getting to the hiring manager then its not the visa that is stopping you going further.” An employee at another: “Sponsorship is typically overseen by HR not hiring managers.” A recruiter names it as one of only three universal questions she asks every candidate regardless of role: “if they’ll ever need visa sponsorship, what’s their availability timeline, and what salary are they targeting.”

The hiring manager’s enthusiasm does not override this ●. “A few times, I called people who needed sponsorship and then asked HR to move forward with scheduling interviews. I always got pushback due to the visa issue. They really didn’t want to move forward even if the candidate had had a really positive phone screen with me. Eventually I learned my lesson and stopped doing phone screens for people who needed sponsorship unless we’d already failed to find someone who didn’t need it.” And at another company: “candidates with visa requirement (including transfer) may pass HR and HM screen for the right qualifications, but would not proceed past that right now.”

At large technology companies there is a third gate, legal ◆. “All the recruiter is willing to tell me that the legal team has recommended against moving forward with the application and that he can’t go against their assessment.” A candidate on the other side of the same mechanism describes the process working: “They all asked me to fill a small form so that their lawyers decide if my profile can pass it not.”

Timing within the funnel is not guaranteed to be early ◆. One candidate cleared the screen first: “Everything went well and was expecting a positive response. But after a couple of days the recruiter called and told they are not sponsoring and even though I cleared the interview, she has to reject my profile.” A commenter on the same thread states the norm: “If it’s during the first recruiter or HM call then yeah totally normal. Final loop, pretty weird and they should have figured this out by now.”

Note the recruiter’s own handover sheet, which carries the answer forward in writing ◆: it lists “citizenship/sponsorship (date if needed)” as a standing field alongside comp expectations.

What this means for you: the person who can be persuaded by your science is usually not the person deciding this, and by the time you reach them the decision has already been made ◇. Do not build a plan around impressing your way past it. Build a plan around reaching lanes where the answer is already yes.

The documented case where volunteering ended a process immediately

One case in the evidence is unambiguous, and it is the one to internalize ◆:

“My situation was a bit awkward. My OPT expires next February. I interviewed at a large search company and was told the interview results were fine, but when the recruiter asked whether I had any concerns, I stupidly said my OPT only had a few months left. The recruiter then went straight to the immigration team, who said they would not sponsor. They told me it was not moving forward, and my file was never even submitted to the hiring committee.”

The interview result was already positive. The question asked was “do you have any concerns,” which is not a question about immigration. The candidate answered a question that had not been asked, and the answer went to a team that had not been consulted. His own follow up: “it just got stuck in a dead loop on the visa question”.

A second case shows the pattern in a milder form ◆. A candidate answering a scheduling email volunteered the full immigration picture unprompted: “I said”Thursday I’m flexible all day, I need visa sponsorship, transferring the visa only takes 15 days," and then she disappeared without confirming an interview time“. But this one has an ending the first does not: the same candidate updated later that”the recruiter got back to me. The reason she had not replied was that she was discussing it with the hiring manager, and they decided to skip the phone screen and send me straight to the hiring manager interview". Silence after a disclosure is not proof of rejection ◆.

What to do with this: answer the question you were asked, and stop. “Do you have any concerns?” is not a visa question. Neither is “when could you start?” unless you have a date that makes the answer inaccurate, in which case you give the date and not the reason.

The documented cost on the other side

The evidence for answering inaccurately is equally firsthand, and the failures happen late, after you have spent everything.

The most concrete account ◆:

“Seven or eight years ago I concealed it. Two companies had already shipped the package to my home, including tax forms and company credit card applications. Then when I came clean about when the H-1B transfer would happen, both of them immediately sent me a UPS overnight label the next day and asked me to return the package.”

Another candidate, on the same question in a different year: “The other company that also gave me an offer destroyed the offer because of my”yes" answer." That one is the cost of accuracy, not inaccuracy, and it belongs in the record ◆.

The hiring side describes the same outcome as policy ●. “If someone responds ‘no’ to the question ‘will you require visa sponsorship now or in the future’ and it comes out during the offer process that they lied, that can be reputation ruining.” “If you lie and make it to the offer stage, they’ll find out then and pull your offer.” “Do you have them answer as part of the application? Record of their application and then if it gets further in the process and they reveal they need sponsorship, they’ve now lied on their application and that’s an integrity issue.” And from someone who runs screens: the failure mode of “Claiming no immigration sponsorship required when applying, then ‘clarifying’ your ‘mistake’ on the screener… I promise that does not work nor will it ever, so stop doing it.”

Recruiters also now expect it and screen for it directly ●. “Just had a call with a recruiter and he said first thing he needed to verify is that I’m a US citizen and don’t need sponsorship and that he’s met with lots of people the past week who said they were a citizen in their applications but once they meet they say they aren’t citizens and need sponsorship.” From the recruiter side: “lately candidates have been getting passed my screening question asking if they require sponsorship or will in the future. Most lie and say no, when they actually do.” And: “If I have a feeling they’ll need sponsorship it’s one of the first questions I ask on the screen and quickly end the call if they say yes.”

There is a separate, softer cost even to accurate answers given late ◆: “When candidates don’t tell us about sponsorship requirements, which is part of our application process, it’s an orange flag. We always try and sponsor where possible but withholding that information is never a good start to employment.”

What to do with this: you have one rule that settles this, and the evidence supports it on the merits rather than only on principle. An inaccurate answer does not buy you a job; it buys you a longer process that ends at the offer stage with the offer withdrawn ●. Answer accurately every time it is asked. The room you have is in what was asked, not in what is true.

How employers have closed the ambiguity

The gap that candidates try to use is the difference between “authorized now” and “will need sponsorship later.” Employers have closed it in writing, in three separate ways ●.

First, they ask two questions rather than one, and the second one is future tense. The verbatim pair that candidates report encountering everywhere: “1) ‘are you legally allowed to work in the United States’ 2) ‘Will you now or in the future ever need visa sponsorship’.” A recruiter separates the consequences: “If you answer No to question 1 you will be rejected. We cannot work with you. Legally… Question number 2. if you answer Yes, it is not an immediate rejection. This means you are on a work VISA and require extra steps before we can hire you. It does lower your chances as some companies will not sponsor you so your options are more limited, but it’s not an immediate no.” That distinction, hard filter versus soft filter, is the single most useful line in this section ◆.

Second, one large technology employer names the statuses explicitly on the form so the word game cannot be played ◆: “To stop candidates playing word games, after asking this question IBM adds a line saying that if you are on OPT, CPT, STEM OPT, or H-1B, you must answer”yes“.” Another writes the question so that the entire future is inside it ◆: “If hired, will you need immigration assistance or sponsorship from Facebook to begin or, at any time in the future, to continue to work lawfully for Facebook in the United States?”

Third, and most important for a PhD on OPT, the screen re-asks and reinterprets. A biotechnology hiring manager states the exact sequence ◆:

“As a heads up, if you answer no to that question, our next step is an HR screen where we will ask if you’re on OPT. To us that counts as sponsorship and if we’re unwilling to sponsor, we won’t hire anyone on OPT either.”

There is a live disagreement here. One candidate reports the community’s prevailing view as: “as long as you have current legal working authorization you are fine to put down that you don’t need it and discuss the issue at the interview” ◆. The hiring manager quoted above is the direct refutation of that view ◆. The split tracks who is speaking: candidates describe what gets them interviews, employers describe what happens at the screen. For you specifically, the disagreement is moot. With the future tense clause in the question and the named statuses on the form, there is no accurate “no” available to a person on OPT who will need sponsorship. So the question does not arise.

And there is no version of the application that avoids the question ●. An HR director: “you need to be consistent in asking it ie ask the same question to everyone. Ideally on your application form and again in your pre screen. Yes, you can ask candidates if they require sponsorship to work in the U.S., as long as the question is phrased appropriately and consistently asked to all candidates to avoid discrimination.” “This is usually a standard question on every application.”

What to do with this: stop treating the answer as a variable. It is fixed. Your leverage is entirely in which employers you apply to and how you frame what sponsorship means for them, which is the next two sections.

Cap-exempt status: what it does, what it does not, and the timing problem

What it is. A university global careers office states the categories ◆: “Employers that fall under the following categories are able to sponsor an H-1B visa without being subject to the annual cap: Higher education institutions; Nonprofit entities that are related to or affiliated with a higher education institution (such as hospitals); Some Nonprofit research organizations and Cap-subject organizations that require the H-1B employee to work exclusively with one of the above categories of cap-exempt employers.” The same source notes that it is not restricted to researchers: “You can receive an H-1B for many different types of specialty-occupation positions that support qualifying organizations, as long as the organization is willing to sponsor your visa.”

What it does. It removes the lottery. A candidate advising an international PhD choosing between a national lab and a semiconductor company ◆: “National labs don’t have h1b quotas so if you get an offer there, as long as you are eligible for an h1b, you get ypur visa in 2 weeks. Even if [the company] wants to hire you, they have to apply for the visa lottery if you will need h1b at some point.”

What it does not do, and this is the part that matters most. Cap-exempt status belongs to the employer, not to you ●. It is a property of who is filing, and it does not travel with you. “Academic H1Bs are cap-exempt as well, so if you want to transfer to a capped H1B at some point, you will still need to go through the H1B lottery.” “you can’t really move to cap subject later on and it’s really hard to jump to another cap exempt. No company will file lottery for you even if you get a job in January in case you are wondering. Ultimately i left US and moved to EU.” “They cannot move from a cap exempt h1B to cap H1B so easily.”

It also does not mean the employer will use it ●. “Many of these institutions have a lot of roles that ‘don’t qualify for (visa) sponsorship’. This means while they have jobs open, HR may block them from sponsoring H-1B (even cap exempt) by organization policy.” A candidate at a cap-exempt hospital system reports being asked to confirm status twice for a principal level position: “they made me confirm my legal status twice over because they weren’t doing anything for anyone anymore. Wouldn’t even do the non-lottery, non-$100K cap exempt COS H-1B for a PhD principal position. Immigration matters are just radioactive right now” ◆. And in the current funding environment: “getting cap exempt is very difficult or almost impossible after research grant cuts by the Government. You can try but don’t have much hope” ◆.

The timing arithmetic problem. This is the most important single piece of analysis in the whole gate, and it comes from an exchange between an employer and a candidate ◆.

The employer, at a cap-exempt nonprofit research organization, states their policy: “We never commit to sponsoring a green card in the hiring stage. When an employee is in year 2 of their SECOND H-1B, we will then look at sponsorship, many have already applied for EB2 NIW or EB1 OR. It also depends on funding. If a lab is going to lose funding, we take that into consideration too.”

The reply does the arithmetic: “they said they start looking at sponsoring GCs at year 2 of the second H-1B (i.e. ~5 years into the H-1B). The problem of course, is that even getting to filing PERM takes 1.5 years nowadays, and you can only extend H-1B if the PERM was filed at least 1 year before H-1B timeout. This is in fact a shining example of how large non-profits/research organizations don’t understand immigration timelines, are reticent to sponsor, and by the time the bureacratic organization is willing to sponsor, it is often too late.”

The rest of the case against ◆: cap-exempt employers “tend to pay a lot less than industry, up to 50-75% less,” and “often don’t sponsor green cards for many roles due to expense and bureaucracy. Once 6 years elapse, you may have to leave the US.”

The conditions under which it is still the right move, stated by the same commenter ◆: “(1) H-1B sponsorship is readily available, (2) there is a clear and viable path to a green card post H-1B, (3) your country of birth is not stratospherically backlogged (sorry, India and China).”

And the dissent, which is firsthand and should not be dropped ◆: “I work for a cap exempt employer; always have. Yes most cap exempt don’t pay as great as cap subject employers but that you get job stability, less visa issues and great work life balance… personally I feel that it’s kind of an advantage to someone like me with less competition!”

The split tracks the green card path, not the H-1B ◇. Everyone agrees cap-exempt makes the H-1B easy. The people who call it a trap are people whose permanent residence path stalled; the person who likes it is someone who is not racing a clock.

What to do with this: if a cap-exempt employer is in play, the question to ask before accepting is not “will you sponsor an H-1B.” It is: “What is the institution’s practice on permanent residence sponsorship, at what point in employment does it start, and has the office filed PERM for someone in a role like this in the last two years?” One candidate states the rule plainly: “if you are considering a cap exempt job you need to have a crystal clear understanding of their stances regarding immigration support… And because of the limiting nature of a cap-exempt H-1B, you need to know this ahead of time. With a regular H-1B you can always find another employer if your employer drags their feet on PERM.”

The disagreement over when to raise it

This is a genuine conflict with firsthand evidence on both sides, and it is not resolvable by picking a winner.

Raise it at the first call. The 2026 consensus in one thread ◆: “Should bring up in the phone screen before any interviews. You maybe wasting your time or their time if it already has been decided. If you think they will be blown away and say that they must have you and therefore will sponsor, dream on. That doesn’t happen in this current environment… If they don’t ask in the application, bring it up during the first recruiter/HR call. Be transparent early, but don’t make it the first thing they see.” Candidates in other threads say the same ●: “If I need visa support I obviously have to make it clear from the start. Otherwise I interview through a whole round and at the end they do not sponsor, which wastes both sides’ time.” And: “I try my luck and I usually bring it up in the first round of interviews to save us both some time.” Recruiters agree from their side: withholding it “is never a good start to employment.”

Wait. One candidate’s own tally is the strongest evidence for the other position ◆:

“i) I currently work at a F500, and the only reason I got in was because I didn’t specifically say I needed sponsorship during the recruiter screen. I went through the interview loop; the HM liked me a lot and he was okay with my visa status when I told him later. ii) I did a lot of recruiter screens last year and got rejected from most of them after I said I needed sponsorship. The week before Christmas I got instantly rejected from two recruiter screens in a row after I told them I needed sponsorship.”

Note carefully what he did and did not do. He did not say he needed no sponsorship. He did not volunteer that he did. He answered what was asked and disclosed at the hiring manager stage. That is the narrow path, and it is exactly the path your two rules describe.

What the split tracks ◇: it tracks whether the employer asks. Where the question is asked at the screen, and per the evidence it almost always is, the disagreement is empty; you answer accurately and the timing was decided for you. Where the employer does not ask, the split is real, and the cost of each choice is different in kind: raising it early costs you processes that were never going to convert, and waiting costs you goodwill and time in processes that were never going to convert. Neither converts a “no” employer.

A third position worth recording ◆: “You can include your visa status in the resume to avoid disappointments in the future.” This is the maximum disclosure end of the range. It is a legitimate choice for someone optimizing for time rather than for reaching the hiring manager.

What to do with this: do not volunteer, and do not evade. If the application asks, answer it accurately there, and consider that your disclosure for the whole process. If nothing asks and you reach a hiring manager who is enthusiastic, raise it yourself before an onsite or a panel is scheduled, because a scheduled panel is where the sunk cost starts to be theirs and the goodwill cost of a late disclosure becomes real ◇.

How this differs at each of the four lanes

Small research organization. The most hostile lane in the current evidence, for a reason that has nothing to do with you ●. A hiring manager: “We are told by HR to strongly prefer local and natives (anyone who would not need sponsorship).” Another: “visa hiring requires you show you did not have similarly skilled US applicants which is very hard to prove with current market conditions.” The economics are named concretely ◆: “The STEM OPT is not the issue, it’s what comes after. Unfortunately it’s an expensive process to sponsor somebody and not be guaranteed they get selected in the H-1B lottery. Last year an expedited H-1B transfer with lawyer fees cost around 9,000 at my org.”

But this lane also has the one mechanism where a scientific team can force the outcome ◆: “The hurdle has largely been that companies are on a hiring freeze and HR isn’t interested. But if the team says they need someone to do a specific role or need to hire they do still have the ability to bring about an o1.” The route through a small research organization runs through the scientists wanting you specifically, not through the recruiter.

Big pharma. Formally the same policy, with a stated threshold ●. “None of the big pharma/giant biotech companies even look at your resume if there’s a visa sponsorship criteria checked yes.” The reasoning from the hiring side: “Why would I go through the expensive and time consuming trouble to sponsor a visa holder when I can hire a citizen or permanent resident with the same qualifications? You will only see companies sponsoring for highly specialized skills and high levels (execs).” One hiring manager names the effective bar: “Wouldn’t do it for candidates below 95% percentile because immigration’s bureaucracy at the moment such a pain.” Another describes silent filtering with no statement in the posting: “My department is hiring right now and we outright reject anyone needed visa sponsorship… We still sponsor for higher level position but this is entry level PhD.”

The counterexamples are real and they are all the same shape ●: a niche, named, hard to replace skill. “I met a European postdoc who got H1b sponsorship from [a large pharmaceutical company’s] protein science division a few months ago, so opportunities are still out there if you have a very niche skillset that they desperately need.” “I know companies that are still sponsoring O-1s (think AIBio PhDs with citation counts in the thousands). H1-Bs not so much.” Two employees separately name the same company as an active sponsor.

Research institute, national lab, postdoc. Structurally the most available lane and the most likely to lock you in ●. The institution defaults matter more than your negotiation. Universities push J-1 for a stated economic reason ◆: “One reason universities won’t do H1Bs out of the gate is they have limits on postdoc length. Usually something like 4-6 years and the visa can be extended to 5. So why would they pay a ton more cash for an H1B when you can fulfill your entire contract on a J1?” Some have explicit policies ◆: “Some institutions will have policies (‘soft’ or ‘hard’) about favouring J1 sponsorship so won’t sponsor a H1B if a J1 is an alternative. J1 is a lot cheaper for the sponsor so they do tend to push it, especially in the first 1-2 years. Some PIs also know that postdocs that get a H1B, then EAD/Green Card won’t be as likely to stay around, so don’t want to speed up the process.”

The counterargument in the same thread ◆: “Academic H1Bs are NOT capped and never participate in lottery (as long as the position requires a master’s or higher, so all postdocs and faculty positions by definition), so, if an applicant manages to negotiate H1B, they’re better off going for it over J1 if they want to stay in the U.S. afterwards. J1 might require returning to your home country, and getting a waiver is never guaranteed.”

National labs are reported to do the same thing ◆: “Most national labs have become clever and simply utilize the F1 OPTs or J1 visas to hire ‘Postdoc students.’ Once you spend some time here, you essentially lose chances to partake in H1B visa lotteries.” The same commenter names which labs are easier for non citizen hiring and says to raise it with the hiring PI directly, “straight but subtle and politely.”

Cost and timeline for a conversion, from someone who did it ◆: “I got a PI to sponsor me for a H1B after my J1 hit the limit and changed labs. The univeristy pushed back a little, but he argued the case. It costs about $5k, lawyers, and time. Takes about 2 months with fast tracking. So it is effort they would rather avoid if possible… Most PIs are clueless about international visas so you have to be explicit early on as not to supprise them.”

And a warning about cold approaches ◆: “if there are sponsorship requirements AND I am not familiar with your advisor or yourself, then there is no chance cold emailing works.”

Big tech. The most systematic and, in the evidence, the most open to specific routes ●. The filter is automated and precise, and it distinguishes transfer from new sponsorship ◆: “Google and all other big tech have a question on their online form… If you don’t have a visa and you don’t currently live in the US and you require sponsorship to get an H1B, that triggers a rejection… Big tech famously hires H1B transfers and other visas but not new H1Bs.”

O-1 is treated as a distinct and more welcome route by multiple accounts ◆: “last year when I was interviewing at big tech, they all agreed to sponsor an O-1. They all asked me to fill a small form so that their lawyers decide if my profile can pass it not… I haven’t yet met a recruiter who said no to O-1, they prefer it to H1B. The only thing is that you need to clear the bar.” Against that, a candidate at the same class of company reports the opposite outcome on O-1 specifically: “the recruiter asked if I needed visa sponsorship and said that they couldn’t provide it for an O-1 visa.” Both are firsthand; the split appears to track the individual candidate’s O-1 case strength as assessed by counsel ◇.

Outside the United States the same companies treat it as routine ◆: at a large research lab, “if your concern is about getting a visa, that’s relatively easy to do. [We] will provide assistance with the process. I went through it myself and it was relatively painless; it probably took 5-10 hours of my time total.” Another company’s recruiter attaches a price and a clawback to it: “it costs the company $10k for a visa sponsorship to the UK and if this role left before the 2 year mark, the employee has to pay some of the fees back” ◆.

Working language

These sentences are shapes, not scripts. They are written for a computational science PhD who is authorized now and will need sponsorship later, and none of them offers information that was not requested, but the status named in each one has to match your own facts before you say it. Check every bracketed part against your own situation first, because the whole value of this gate is that your answer is accurate.

When the application asks the two standard questions. Answer them as asked. “Are you legally authorized to work in the United States?” is Yes if you are currently on valid OPT. “Will you now or in the future require sponsorship for employment visa status?” is Yes. There is no accurate alternative, and the evidence shows that “no” does not survive the screen even when it gets you the screen ●.

When the recruiter asks on the call. The complete answer, and nothing after it:

“Yes. I’m authorized to work in the United States right now, and I will need sponsorship at some point in the future.”

If you want to add the one fact that changes the employer’s cost calculation, and only if you want to, add exactly this and stop:

“Yes. I’m authorized now, and I will need sponsorship later. Happy to walk through the specifics with whoever handles that on your side.”

That second sentence hands the detail to the right function rather than to a recruiter who cannot use it ◇, and it does not invite you to narrate your OPT clock.

When they ask a follow up you can answer favorably. Answer the follow up, not a broader version of it.

• If asked which status: “I’m on [the status you actually hold].”
• If asked whether you would need the H-1B lottery: answer with the fact, and note the exemption only if it applies. “For a cap-exempt employer, no lottery is involved. For a cap-subject employer, yes.”
• If asked about alternatives you actually qualify for: “I would also be a candidate for an O-1, and I’m happy to have your counsel assess the case.” This is the sentence the evidence shows opening a door at large technology companies ◆, and it is only usable if it is true of your record.
• If asked when you could start: give the date. Nothing about why.

When they ask a question that is not a visa question. “Do you have any concerns?” “Is there anything else we should know?” “What’s your timeline?” These are not immigration questions and the evidence contains the case of someone who answered them as if they were and lost a positive process before his file reached the committee ◆. Answer them on their own terms: “No concerns. I’m interested and available.”

When you are asked directly whether the company would need to file a new H-1B. If you are on OPT, the honest framing that costs you least is the one the evidence names as easier to sell ◆: employers find a transfer easier than a new sponsorship. If a transfer is what your case would be, say so plainly. If it is not, do not imply it is.

What to ask them, once, when the answer is still open. Put the question to the recruiter in the form that gets a policy answer rather than an opinion:

“What is the company’s current practice on sponsorship for this level of role?”

And at a cap-exempt employer, before any offer:

“Does the institution sponsor permanent residence, at what point in employment, and has that happened for someone in a role like this recently?”

What never to do. Do not answer “no” to the future sponsorship question. It is inaccurate for you, it is caught, and the evidence shows the catch happening at the offer stage, after everything is spent, with packages already shipped ●. Do not volunteer your OPT expiry date, your lottery history, your family’s status, or your long term plans in response to a question that did not ask for them ◆. And do not treat silence after an accurate disclosure as a rejection; in at least one documented case the silence was a recruiter arranging to skip the screen entirely ◆.

1. Why this round is different

The first non-technical round is usually a recruiter, and the recruiter is structurally unable to answer most of what you want to know. A recruiter states her own limit plainly: “I usually share that I’m not on the team so I can answer general organizational questions or logistical questions.” ● A hiring manager who has interviewed hundreds of candidates draws the same line from the other side: “ask your recruiter those questions, not the interviewer. I have interviewed 100s of candidates personally and you can only comment about your own working hours and the flexibility of your team, not the company… The questions about wfh policy and org structure are best left to the recruiter.” ● And an advisor writing to a biochemistry PhD interviewing for a senior scientist role: “Typically phone interviews are with HR people, so they won’t know much about technical details.” ◆

So there is a floor of what a competent recruiter can answer, and a recruiter states it: “Any decent recruiter can speak confidently at a high level about what you’ll do in the role, the team size, the cross-functional partners, and some sort of a growth trajectory. If they can’t give you those basic things, run. The company does not know what it wants.” ◆ That last clause is the operating instruction. When a recruiter cannot answer inside her own scope, the failure is the finding. One candidate asked what type of person would work well with the team and got back “someone who does it the [company] way,” which is a content free answer to a question the recruiter was supposed to own. ◆

The slot is also short. One recruiter describes a screen as roughly ten minutes of company overview, ten minutes of fit questions, two to three minutes of logistics, and whatever remains for you. Another puts the whole call at “10-15 min in my experience. Depends if you have questions for them.” ● A third routes candidate questions to the very start: “I let candidates ask their questions AT THE START OF THE INTERVIEW since that always ends up leading to the pitch anyway.” ◆ Assume you get three to five questions, not twelve, and assume they may arrive before you have heard anything.

Two things make the slot worth more than its minutes. First, questions the recruiter cannot answer still travel: “sometimes they answer and you can tell how connected they are to the job, other times they say ‘that will be a better question for the hiring manager’ If they like my question in either case, they may take special note and pass it along to the next person. I had an interview the other day where the hiring manager was following up on the recruiters notes from our conversation.” ◆ Second, the recruiter holds something nobody else will give you, which is the hiring manager’s intake brief. A candidate describes the real yield as “a ‘sneak peek’ of the key points the hiring manager noted, basic information on the team/structure, and typically important items that will be in the first few months.” ◆

One structural warning. A recruiter describes ending a call she has already decided against: “As soon as I realize that they’re not a fit, I stop asking questions and say, ‘that’s the last question I have. We’ve still got a minute. Do you have any questions for me?’” ◆ A very early, very abrupt handoff to your questions is a signal about where you stand, not an invitation. ◇

2. Questions that worked

Grouped by what they buy you. Each entry gives the sentence as it was actually spoken or written.

3. Questions that backfired

4. Stage gating

5. By counterpart

The same question lands differently depending on who is holding the phone. The closing concerns family is the clearest case in the corpus, and it is worth being precise about what the evidence actually shows.

Among recruiters commenting on that family, the negatives outnumber the positives and are the ones citing concrete harm: “comes across a little desperate. Don’t ask it”; “I hate all variations”; “they don’t show your understanding of the role or the business”; plus the annoyance list that includes “How’d I do?”. Two recruiters do like it, one of whom volunteers a softer rewording. Among hiring managers, the pattern is different in kind: the two who describe an actual instance of being asked both report it working. “One great question someone asked me was ‘do you have any concerns that I can address?’ I thought this was brilliant because I did circle back to some of her gaps. It gave her an opportunity to further address with me.” ◆ And “I always ask what they think a successful candidate will be expected to accomplish in the first 6-9m, what the profile of their ideal candidate looks like, and if they have any concerns or things I can clarify from my resume/the conversation.” ◆ The hiring manager objections in the corpus are stated as policy preferences about canned questions, not as reports of a candidate being harmed.

The practical rule that follows: with a recruiter, use the narrow retake wording or skip the family entirely; with a hiring manager, the concerns question is on the table. ◆

One source gives an explicit allocation by counterpart, and it is worth quoting whole because it is the only one of its kind here: “For potential colleagues in the same group, ask about the culture and what they like/dislike. For potential colleagues in a different group, ask about how the communication is between the different groups. For the hiring manager, ask what the expectations will be and what stresses them out the most. For upper management, ask them where they see the company a year from now. For HR, ask general questions about culture, company events, etc.” ◆

Two notes on the founder column. A founder confirms the questions are scored: “people who are very interested in joining a company have done their homework. They typically have several detailed questions, and those questions reveal a lot of things those people find important in their job.” ◆ And a founder tells you what he is scoring you on in return, which you should be ready to answer: “What is your appetite for risk? There is a high chance of failure.” ◆ One biotech source argues the opposite on money questions in the founder round: “Dont ask much about funding or investors or negative structural changes. They dont like that much from my previous talks.” ◆ That dispute is live; see section 7.

6. The one rule

Ask something. Asking nothing is the most frequently named red flag in this entire corpus. ●

It appears as a stated rejection reason in a verbatim rejection email: “You had very little questions about the company and the interviewers didn’t feel a lot of interest from your side.” ◆ It appears from a hiring manager as the top item: “The biggest red flag for me is when a candidate asks zero questions.” ◆ From a biotech interviewer: “It’s very much a red flag to not have any questions.” ◆ From another: “If you have nothing to ask, I will assume you are uninterested and didn’t research the company or role.” ◆ From a recruiter: “The questions you ask tell me how you think. They tell me whether you’re already picturing yourself in this role or just hoping to survive the conversation.” ◆ From a recruiter on the baseline effect: “The fact that you are asking any questions is a great sign… someone who acts like a dead fish” is the alternative. ◆ From an HR practitioner listing what a candidate must never say on a phone screen, alongside three others: “No questions to ask the company.” ◆ On how it reaches the debrief: “If you simply say you have nothing to ask, unless there are twenty or thirty minutes left and you have genuinely exhausted your list, it can become a yellow flag in the debrief.” ◆

I promised no counterexample and the corpus contains two, so here they are. One biotech interviewer dissents: “a person running out of questions to ask was never a big deal, and if anything just felt honest.” ◆ One interviewer says the slot is not scored at all: “When I interview someone, asking no questions or asking a silly one does not cost points, but asking a good one earns them.” ◆ Both are minority positions against roughly eight sources on the other side, and note that both concede the upside is real even where they deny the downside. There is also a reconciliation on record that both sides accept: “Running out of questions is not the same as not having any questions.” ◆ Exhausting your list mid loop is fine. Arriving empty is not.

The minimum viable pair, when the call has run long and you have thirty seconds. A recruiter states it as an explicit floor, and gives both sentences:

“Have at least two questions ready. Why is this position open is a good one. And it tells you if someone got promoted, quit, or was fired. And that’s useful information for you. What does success look like in the first 90 days? This question shows that you’re already thinking about how to deliver.” ●

Those two, in that order, are the whole fallback. They are answerable by a recruiter, they are both on multiple independent recommended lists, and together they cover the two things you most need before the next round.

7. Unresolved

These splits are real. I am recording them rather than picking a side.

Whether the questions slot is scored. A recruiter says largely not: “recruiters often aren’t evaluating you too much based on the content of your questions, but they do notice the impression you give.” ◆ Another says the decision is already made: “By the time we get to ‘Do you have any questions for me?’ I’ve already got a good sense of how I feel about the candidate.” ◆ Against that, a recruiter of ten years: “At the end of an interview, when I ask ‘What questions do you have for me?’ I have already decided how I feel about your skills. At this point, I want to understand how you think.” ◆ And a hiring manager whose top answer is that red flag hunting questions are what impress. ◆ The safe reading is that the downside is small and the upside is real, which is what both sides actually describe.

Question budget. A recruiter running an open question session takes the maximalist position: “The best questions you should be asking in an interview don’t really change depending on the stage… you should be asking strong questions the entire way through. Don’t hold anything back thinking you’ll save it for the next round, because the next round isn’t guaranteed.” ◆ Two candidates were rejected with “too many questions” as stated feedback. ◆ A third source recommends a fixed structure of three, one technical, one about team and management, and one relaxed backup dropped if time runs short. ◆ I cannot resolve this. The structured three, with the third one droppable, is the only proposal in the corpus that survives both sides. ◇

“based on this interview, do you think I’m a good fit for this role?” One firsthand offer follows it, at least one recruiter calls it desperate, one calls it acceptable but weak, one likes it. ●(that the split exists) Unresolved.

Benefits at the screen. Multiple engineers and one firsthand success say ask at the first call. A recruiter of thirty years says wait until they want you. ● Unresolved. Note the two positions are about different things: what you are entitled to see, versus when your leverage peaks.

Runway and funding in the founder round. Two comments in a single discussion take opposite sides, one saying “Dont ask much about funding or investors,” the other “Ask how much runway they have. Do they have series A or B funding?” ● A pre Series A founder calls the whole category near useless to a candidate: “Asking about growth plans, runways, product market fit, Founder experience, etc. is so hard to judge as to be hardly worth it… Just: do I want to work here and how big an issue is it if I lose my job in the next 3 to 18 months.” ◆ Another founder enjoys answering it. ◆ The only stable finding across all of them is that the reaction is more informative than the number.

Visa sponsorship timing. One firsthand tally shows disclosure at the recruiter screen producing instant rejections, and non disclosure until the hiring manager stage producing a job at a large company. ◆ A recruiter calls withholding an orange flag. ◆ The most recent consensus says raise it at the first call. ◆ Since recruiters ask about it universally anyway, the space between these positions is narrower than it looks, but I am not resolving which is better when you have the choice.

Compute allocation, publication and open sourcing policy, lab access. Nothing. This evidence base has no attested question and no attested outcome on any of them. If you want a wording for those, it will not come from here.

1. What this round is

The founder round is the conversation with the person who owns the outcome: a founder, a chief executive, a lab director, a principal investigator. At small organizations it is often not the last round but the first, and sometimes the only one. A startup founder describes running the initial screen himself: “as a first step do a quick 10-15 minute phone screen. If the candidate is a poor fit - you only spent 10 minutes on them.” ◆ A postdoc applicant reports the same absence of any intermediate layer: “I finally have gotten the opportunity to interview with a PI with no ‘pre HR interview’.” ● At a national lab, “the host PI and core project members joined the interview,” with no HR screen at all before it. ●

Two claims about this round circulate widely and are both contradicted inside the same discussions that produce them.

The first is that it is a culture chat. “Mostly CEO interviews are a vibe check,” says one commenter, and another agrees: “CEOs being the last round is fine and is usually just a culture fit / casual round.” ● That is sometimes accurate. One candidate reports that “the CEO interview round consisted of talking about which restaurants we’d been to in London” and still produced an offer. ◆

The second is that it is a formality. The top comment in one thread frames it that way: “They’re not sending everyone to the CEO so this is probably one of those deals where the CEO likes to talk to EVERYBODY before hiring and he’s not going to overrule the hiring manager unless you totally flub it.” Another puts it harder: “These CEO rounds are nigh on pointless but small companies are in love with them. They’re usually softballs and if you don’t make a fool of yourself they’re not going to block you.” Both items are flagged disputed, and the reason is in the same threads. One candidate: “Talked to literally 6 people and the CTO and CEO after a meeting where quite frankly nothing happened decided to override everyone and not hire me.” ● Another, after three rounds of “100% positive” feedback: “He vetoed my offer due to my experience not being deep enough.” ● A third was cut fifteen minutes into a system design discussion: “then he just abruptly ended it with a ‘have a nice day’ after 15 minutes. No feedback.” ● A fourth: “in founder round, I got rejected in between my intro within 3-4 mins as I don’t have B. Tech.” ◆

The accurate description is the one given by a commenter who works inside these loops: “Every place I’ve worked at everyone at the interview loop has what I call ‘veto power’, and that’s honestly a very reasonable thing, because nobody wants to hire anyone they don’t want to work with.” ● Treat the round as a live veto that is sometimes exercised on thin grounds. It is not decoration, and it is not a rubric either.

One structural note worth carrying: the founder round is usually reserved. “some small companies have this CTO/Founder round especially for senior roles since they want to chat with every person getting hired. Junior employees wont have this round.” ◆ Below roughly twenty people the founder is often still doing technical evaluation personally: “if it’s a very small startup like <20 people then these interviews can still be technical bc C-suite is still somewhat involved in R&D.” ◆

2. What actually decides it

3. The instinct problem

Founders say openly that this round runs on feel, and they say it in print, under their own names.

Altman: “There are a few things in the interviewing/negotiating process that you should watch out for because they usually mean that person will not be successful in a startup. A focus on title is an example; a focus on things like ‘how many reports will be in my organization’ is an even worse example. You’ll develop a feel for these sorts of issues very quickly; don’t brush them off. If you have a difficult-to-articulate desire to pass, pass.” ◆ (disputed) One founder is more explicit still: “When hiring for a startup, it’s often gut-feeling that dictates which of the similarly-qualified candidates is the best fit and I rely on this question to come to my conclusion,” where the question in play is a joke question. ◆ (disputed) The “Sunday test” is offered as a screen in the same register: “would you be likely to come into the office on a Sunday because you want to hang out with this person? … Treat your values as articles of faith. Screen candidates for these values and be willing to let an otherwise good candidate go if he is not a cultural fit.” ◆ (disputed) One founder reads drive off hobbies: “if a candidate tells me they run 10 miles a day as a hobby, that’s a signal of a strong internal drive.” ◆ (disputed) Another treats phone availability during work hours as decisive: “candidates who are unwilling to talk by phone during their current work day. This is a clear sign they are not really looking for their next gig.” ◆ (disputed)

The candidate accounts match what an uncalibrated instinct produces. Vetoes after unanimous panels ●. Cuts inside three or four minutes on a credential the earlier rounds had waived ◆. A fifteen minute termination with no feedback after a multi day take home ◆. And on the other side, offers from rounds that were nothing but restaurant talk ◆, and an instant offer “literally 5 minutes after leaving the office” that the candidate later read as the worst sign of all ◆.

Say it plainly: this round is less predictable than any other stage in the process. The technical rounds have a rubric you can study for. This one has a person whose stated method is that if they cannot articulate why they want to pass, they should pass anyway.

The practical consequence is about allocation, not despair. The preparation that pays here is cheap and bounded: know what they do, know what you would work on, bring one thing they will learn from, bring two stories about working without structure. That is a few hours. Beyond that, additional preparation does not move a decision made on feel ◇. Do not treat a rejection at this stage as diagnostic information about your capability; three of the firsthand cuts in this corpus came after clean technical rounds ●. And run more processes in parallel than you would need if the last gate were rubric based ◇.

There is one structural filter that is worth knowing because it is not about you at all: a commenter’s rule of thumb is that founder run technical evaluation is legitimate when the company is tiny and the founder is technical, and is ego when the company is large enough to have a management layer. “if the place is tiny, and the CEO is technical, it can absolutely make sense. So if you have a large enough company to have a layer of senior managers/directors between the C-level and line managers, you probably don’t want the CTO or CEO interviewing regular IC hires directly.” ◆

4. Critique: invited but scoped

This section exists because a sharp technical reader will find the flaw in a research plan within twenty minutes of hearing it, and because the corpus shows that instinct is either the strongest asset in this round or the thing that ends it, depending entirely on form.

The worked sentences at the end of this section are shapes, not scripts. The details inside them are invented to show where the objection sits within the question, and the brackets mark what only you can supply. Fill each one with something true about your own work before you use it in a room.

5. The principal investigator variant

At a research group, institute, or national lab, the same round exists but the emphases shift.

Technical probing starts at minute one, and the call can end early. A principal investigator who had just run more than thirty postdoc interviews: “If you’ve declared proficiency in methods that are the bread and butter of my group you should be able to answer technical questions that only someone who has through deeply about the problems can answer. I started asking these questions at the start of the interview. If during this technical portion of the interview it becomes apparent a candidate has lied about the expertise I end the interview early.” ● Another describes the same probe: “Some postdocs come with oversold skills - e.g. they say they can do something, but it turns out they saw someone else do it, or someone else in the old lab contributed that part to the papers. I try and figure out true skills early as well.” ● A third: “I ask technical questions during interviews to evaluate if they understand the techniques and research objectives of my projects.” ●

The practical implication is about your own resume, not about study. Every method you claim is a live target from the first minutes, and the distinguishing question is whether you did it or watched it done.

Homework is a gate, not a bonus. One principal investigator’s minimum: “Read or at least skin some of my papers and talk about that here.” ● Another extends it to everyone on the schedule: “Familiarize yourself with the lab’s work and be ready to delve into discussions about your own research. … Typically, you will receive a list of individuals you will be meeting with well in advance. Take the time to research their work extensively.” ● A postdoc blogger states the strong version: “Make sure you’ve read all their recent papers and can discuss your opinions on their research. Come with questions and ideas.” ● The failure is named as a red flag directly: claiming interest in a listed research area when “it’s clear they don’t know anything about it.” ●

You are expected to arrive with a direction. “Have an idea what you would like to work on in this lab. Like if the PI asks you ok what would you work on in my lab you need to be able to make a simple proposal.” ● One principal investigator wants it in writing and quickly: “it’s ideal to have an idea of what you want to be doing (& be able to provide a 2-page research proposal quickly) but be flexible around this.” ● The proposal can be imposed as a gate after the first call: “the PI asked me to write a single-page proposal to decide if he would move forward with me.” ◆ Its stated purpose is not the document: “they wanted to assess my ability to conceive ideas and the extent to which I can think about science. In terms of format it’s really insignificant.” ◆ And the follow up matters as much as the draft: “If we are then discussing moving forward together I am looking for how you take feedback, make edits to your research proposal, etc.” ◆

Misjudging which direction interests them is a documented reason for being cut. This is the specific hazard for a candidate who arrives with strong ideas. “Be prepared to talk about how your skillset is going to help me push my research program forward. Don’t be the candidate that only talks about you and how you want to do X so you can do Y. Talk about how you want to do X, so you can do Y within the context of my research program. A top candidate got dropped from second visits because all they talked about was how they wanted to develop their tool for a question that I didn’t think was exceptionally interesting and that didn’t fit into my program at all.” ● Another names it as his standing complaint: “my pet peeve is the postdoc that takes up a position for a project but rather works on his interests or his career without regard for the project.” ● And bluntly: “Some postdocs come with preconceived notions that they will do studies they want to do in my lab, usually informed by the graduate mentor. That’s ‘okay,’ but in my lab, we need to do my work.” ●

The resolution is to bring a direction that is an extension of their program rather than an import into it, and to say which of their aims it attaches to ◇.

The career goals question is a test of independence, not of loyalty. “What I want to know is people are going to take active control of their career path.” ● “When I (we perhaps) say 5 year plan, I don’t mean a form document. I mean that you, a mature, ambitious, and intelligent adult have a clear, and articulatable goals for your future and that you can convince me that spending 5-10 % of your working adult life in my group is going to benefit those goals. … a graduate student not having goals for grad school is a red flag, but a postdoc without them is a fire alarm.” ● Vagueness here is listed among red flags directly: “a lack of motivation and vision. Vague answers to questions about goals, 5 year plans, and how my group fits into them.” ●

Two warnings attach. Stated goals are used as filters, sometimes against you: one principal investigator says of a candidate aiming at industry, “I’m not really qualified to advise them about industrial opportunities, so I would probably turn them away. That’s one filter.” ◆ And expectations about your exit vary enormously between groups: “my postdoc PI expects us to leave after 4 years to become group leaders. if that’s not our goal, we should do postdoc somewhere else. this is very different from my phd PI who let her postdocs stay for decades.” ◆ Ask what happens at the end before you volunteer an answer that may not match.

Fit can outrank the publication record. One principal investigator’s explicit ordering: “If they’re absolutely stellar and have the last 4 bullets of the Green list, then great. Otherwise, I will go for people with average CVs who are great to work with over stellar people with potential red flags.” ● Another: “This intellectual and interpersonal fit is waaaaay more important than simply attracting the most stellar candidates who graduate with 15 or 20 publications.” ●

The process has almost no external constraint. A full professor: “If these are met sufficiently, and I am confident in the ‘fit’ for a particular project, I will strategically neglect to request references as I won’t want to be talked-out of a candidate.” ◆ A single person’s judgment carries the decision and there is often no human resources counterweight, in either direction. That cuts both ways: a rejection may come as a personal call with real feedback, “they said the interview itself went well, but they went with the senior postdoc candidate who had more experience” ◆, or the decision may never be communicated at all: “A very common experience is that the PI never tells you anything, one way or the other. Many interviews end with ‘let’s stay in touch’ and then they never email you back.” ●

The informal framing does not make it informal. “Just to note you can’t get around rules on what you can and can’t ask in an interview just by calling it an informal chat. … Having an informal chat is great for screening and getting down to a shortlist, however it very much is part of the recruitment process and both sides need to treat it as such.” ● A neuroscientist documenting his own search calls the call exactly what it is: “You can think of this as an informal screening interview.” ●

Interest and funding are separate events. “Some principal investigators may express interest in hiring you upon application but may need time to secure funding for the position.” ◆ And a verbal offer is not an offer: one candidate was “given a verbal job offer and given a tour of the facilities,” then ghosted when the institute’s human resources process never converted it. ◆ Two practical items follow. Raise visa status early, because “Most PIs are clueless about international visas so you have to be explicit early on as not to supprise them” ◆, and the institutional default for international postdocs is often J-1 for reasons of cost rather than preference ◆. And expect the first call to be a stage, not the process: the common sequence is a thirty minute call, then a talk and a full day of one on ones ●.

6. What to ask a founder

Only questions with evidence behind them. Wording is given as it appears in the corpus.

On runway and survival. Ask, and ask simply. A founder, answering whether it is acceptable: “I like when people ask and I enjoy answering. If it’s important to you, you should ask. … Asking about financials shows that you’re aware there are risks working at a startup and you’re evaluating them, which is exactly what you should be doing and what they should want you to do. On how to ask? - You don’t need to be super analytical about it. Ex. ‘How many weeks of runway do you have in the bank?’” ◆

That founder’s caveat is the documented one: the over quantified framing is what grates, not the topic. A co founder draws the line by seniority: “Generally questions regarding stability phrased sensibly will be fine. Asking the exact burn rate is a little too probing if it’s a lower level position. Runway and funding details is fine though, in my opinion.” ◆ So: runway in weeks or months, yes. Burn rate, dilution, cap table detail, gross margin, from a junior or first industry hire, reads badly. Note that this is contested territory. One biotech commenter says “Dont ask much about funding or investors or negative structural changes. They dont like that much from my previous talks” ◆ (disputed), a pre Series A founder says the whole category is “so hard to judge as to be hardly worth it” ◆ (disputed), and another commenter claims “even asking these questions to a first time startup will probably prevent you from getting the job” ◆ (disputed). Against them: “You absolutely can, and should. Startup founders have to answer these questions every time they talk to investors; if they don’t have a well reasoned and rehearsed answer they probably aren’t talking to investors much, and that’s a huge red flag.” ◆

The reaction is data regardless of the answer. One candidate: “I asked this question to the founder, he got VERY defensive and borderline berated me for how dare you ask me these questions …. anyway, I rejected the offer.” ◆

On where the risk actually sits. From a widely shared candidate checklist: “What can we fuck up and this will still be a success” and “What can we absolutely not fuck up, because doing so would spell doom for the venture?” ◆ These do more work than runway, because they ask the founder to name the load bearing assumption out loud.

On the business model. “how does the business make money and who is the primary sales person? If the CEO is still the head of sales, it tells you the startup haven’t yet figured out it’s revenue model.” ◆

On the founders themselves. Track record first: “Ask if the founders have previous startups with successful exits.” ◆ The engineer who offers this has worked at three companies with first time founders and ranks it above runway. And the direct version, from the same candidate checklist: “What are aspects of your personalities as founder(s) that might make you difficult to work with on a company level? … what are your quirks that we should be prepared to face as an organization?” ◆

On equity, if it is on the table. “What % does your equity represent of the total company? If they don’t tell you this directly, then RUN AWAY.” ◆ And: “What kind of options does the founder/founders have? You want them to have the same class of options as employees; otherwise, incentives are misaligned from the get-go.” ◆

On what the organization actually values. A former recruiter, now a chief executive: asking what the top performers have in common “gives you insight to what the company values.” ● His stated purpose is dual, to signal seriousness and to screen them for yourself.

For a principal investigator, a different list. From a neuroscientist’s own documented postdoc search: “What is your philosophy for when a postdoc leaves to start a faculty position? What can I take with me (ideas, transgenic lines, newly developed tech, etc.)? Do you still write grants and publish on the same topics after I leave? … How are conversations surrounding authorship and credit had? … What’s the funding portfolio for the lab look like? … Do you have any plans of moving the lab or changing careers over the next 5 years?” ◆ At a national lab, add the two that a commenter says determine whether the position is worth anything: whether the host will absorb you or recommend you, and “Will you be able to publish, patent or get anything out that is tangible.” ◆ Raise work authorization “straight but subtle and politely with your hiring PI.” ◆

One framing note that makes all of these safe to ask: the same neuroscientist says he asked them “because I genuinely cared for the answers, but also because they served as a litmus indicator for me - to see whether the interviewer respects me enough to engage transparently rather than being offended by very fair (even if unusual) questions.” ●

7. What this round tells you about them

Candidates in this corpus consistently report that the founder round, not any other stage, is where they learned the organization’s real character. The tells are concrete.

How they treat information that is not theirs. One founder, on a candidate’s confidentiality obligations: “Those NDAs are of no importance to me. Give me the names.” When the candidate ended the interview, the founder’s closing words were “Eat shit and die.” ◆ The same founder had opened by accusing the candidate of lying based on numbers a third party recruiter had supplied: “what you just said is a lie, the numbers I have in front of me are saying otherwise.” ◆

What they say about hours, unprompted. “I was also thoroughly intimidated by the amount of times he re-iterated that the job will ruin work/life balance and how the ‘easier’ weeks will be 50 hour work weeks. I asked ‘how do breaks work there’ and he replied ‘breaks?’” ◆ Another: the chief executive “said that ‘science doesn’t wait for us, so you might have to come in during the weekends’.” ◆ A commenter’s read on the first of these is the correct one: “I would take those comments as a major red flag - the 50 hour, ‘less busy’ weeks and acting confused by breaks.” ●

How they behave about compensation. A demand to accept before disclosure: “they ask candidates to commit before sharing any details. I told him that didn’t seem like such a great idea, and he assured me that comp wouldn’t be an issue, and that they do this to avoid hiring mercenaries.” ◆ A late swap of equity for cash: “he lowballed massively and dangled stock options as an alternate to base pay.” ◆ Note also that in a founder round compensation may be negotiated in the room rather than by a recruiter afterwards ◆, and that a scientist chief executive sat in on a candidate’s salary conversation with human resources, which the candidate found unusual ◆.

Whether they can take a hard question about their own field. The clearest single red flag named in the corpus: “If they can’t answer tough questions on the science or the business model.” ◆ Its escalated form is a founder who defends his own research taste instead: insisting on one side of a literature with evidence both ways and dismissing “all of those papers are wrong,” then closing the visit by insulting the candidate’s postdoctoral advisor. ◆

Whether the room is a conversation or a broadcast. “Many CEOs are detached from reality, you’ll be listening to stories and anecdotal evidence for his favorite theory.” ◆ A related tell is the pitch aimed at the wrong audience: “it almost feels as though they are trying to convince me as an investor in the company rather than a worker,” which the candidate read as a possible sign of trouble ◆. The opposite failure exists too: “CEO was complete robot and didnt even try to sell me on the role.” ◆

Whether the founder can make decisions. Process disorder is attributed upward, correctly: “9 Zoom calls spread out over 3 months was ridiculous, showing a lack of organization and decision making from the company (and ultimately the CEO, who in this case was the hiring manager).” ◆ At the other extreme, an offer “literally 5 minutes after leaving the office” was itself the biggest warning in a round that had already gone strange ◆.

Whether authority is exercised by argument or by rank. “In a seed stage startup, the likelihood of a tyrannical CEO bossing everyone around and rejecting process is higher than larger companies. You want to try to catch that right away. A heavily involved CEO is likely, a technical CEO is fine, but a CEO who pulls ‘I’m the boss and I say work on this’ is a red flag.” ◆

Behavior outside the interview room. One candidate met a chief executive on a ski slope between interviews and watched him cut people off, stop without looking, cut lift lines and shout at people in his way: “It turned out to match his management style 1000%.” ◆ Another heard, in the interview itself, “but you don’t look autistic!” and reflects: “When people show you who they are, believe them and all that.” ◆

The synthesis offered by someone who has done this four times. “Runway is important, but just because they have two or 5 or 10 years of runway doesn’t mean they aren’t gonna lay your ass off in 2 months during a ‘pivot’. Every startup is draped in red flags. 9 out of 10 dont make it. … What you want to focus on is (a) ability to build transferrable skills. (b) integrity in the leadership/founders. Do they make outlandish promises (you will be the one burdened with fulfilling them!)? Do they have a track record? Do they have massive egos? Are they going to pressure you to cut corners on regulatory or quality or safety? These are the kind of things you can suss out with careful questioning in interviews.” ●

One item to interpret rather than fear: if the founder has recently moved out of the chief executive seat, a biotech commenter’s read is that “founder rarely resigned on their own when they were a CEO. They are almost always being told to ‘resign’ by the board of investors due to various reason (scientific, strategy, etc).” ◆

8. Disputed

Claims marked disputed in the evidence, left unresolved here, with the reason each is contested.

1. The founder round is a near formality at companies under roughly one hundred people (“he’s not going to overrule the hiring manager unless you totally flub it”). Disputed because a commenter two replies later in the same thread was vetoed at exactly that stage.
2. The founder round is theatre (“nigh on pointless … they’re not going to block you”). Disputed by the firsthand veto accounts in the same thread.
3. Founder run interviews are structurally worse because founders lack interviewing maturity (“the person interviewing me lacked the maturity, experience, or professionalism”). Disputed by founders who hold that their own judgment is the company’s best available signal.
4. You should never raise your view of their business unless asked (“the interview is NEVER a good place and time to discuss your thoughts on their business if not being asked”). Disputed because named founders treat unprompted insight as the exact signal they are hunting for.
5. Candour is punished, so give cheesier answers. Disputed for the same reason, and it is advice reconstructed after a rejection whose real cause was never disclosed.
6. Do not ask about funding, investors, or structural changes in a biotech founder round. Directly contradicted by other commenters in the same thread and by founders who say they welcome the question.
7. Runway, growth plans, and product market fit questions are nearly useless to a candidate (from a pre Series A founder: “so hard to judge as to be hardly worth it”). Other commenters in the same thread call them essential.
8. Asking diligence questions of a first time founder will probably cost you the job. This is the core unresolved dispute of the whole question topic; the evidence contains both a founder who welcomes the questions and a founder who berated a candidate for asking.
9. Make the founder pitch you, and if the pitch does not impress, “they are probably losers.” Disputed as a heuristic that rewards charisma over substance.
10. Founders should interview every candidate until the company reaches five hundred employees. The doctrine is real and attributed; the specific threshold is widely disputed as impractical.
11. If you have a difficult to articulate desire to pass, pass. Disputed by candidates as the mechanism through which unexamined bias enters small company hiring.
12. The Sunday test as a values screen. Disputed because it selects for social similarity to the founder.
13. Deciding between similarly qualified finalists on gut feeling, using a joke question. The clearest statement that the final round runs on instinct; disputed as unstructured.
14. Obsessive hobbies as a proxy for intrinsic drive (running ten miles a day as a hiring signal). Disputed as a proxy that penalizes people with caring responsibilities or health constraints.
15. Unwillingness to take a call during the current work day proves lack of interest. Disputed because it penalizes candidates whose current employers are strict.
16. Slightly below market salary plus a generous equity package is the right structure for early hires. The author himself predicted he would be “flamed” for it; candidates routinely dispute that startup equity compensates for the cash discount.
17. “Any time you have that ‘Wow!’ kind of feeling you need to just hire the person.” The accompanying test, whether a candidate can change your mind, is well supported; the hire on feeling rule attached to it is disputed as unstructured.

The call was short, so it went badly

False, and the evidence runs in both directions. A call scheduled for sixty minutes that ended at nineteen produced an invitation to a second interview. An eleven minute screen reached a final round. At one firm the longer of a candidate’s two screens was the one that ended in rejection. ●

Length tracks the screener’s schedule and how quickly they got the answers they needed. It does not track their verdict.

They said they would pass my resume to the hiring manager

This is frequently a scripted exit, not a decision. Recruiters describe the tactic in their own words.

One: “My go-to tactic is the imaginary bad guy. Whenever my prescreens feel like they are obviously not the right candidate I will complete the prescreen as normal and wrap up by saying something about reviewing with the hiring managers.” ◆

Another: “I would tell them I’ll send their resume to the hiring manager and see what they say. Then reject the candidate a few days later.” ◆

The reason is not dishonesty so much as risk management. As one put it, “If you’re rejecting for personality issues, you can’t do that over the phone.” Deferring the rejection moves it into writing, where it can be phrased safely. ●

They asked if I had questions, so we were doing well

Sometimes the opposite. Two recruiters describe using the closing question as a way out of a call they have already decided against.

“As soon as I realize that they’re not a fit, I stop asking questions and say, ‘that’s the last question I have. We’ve still got a minute. Do you have any questions for me?’” ◆

And the reason it is invisible to you: “the candidate doesn’t really know what your pre screening questions are, so they aren’t gonna know the difference between you stopping at question 4/10 or question 10/10.” ◆

There is a countervailing account from a recruiter who says that by the time she reaches that question she already knows how she feels, which is compatible with both readings. Treat arriving at the closing question as neutral. ●

The conversation was warm and we had good rapport

Warmth is produced deliberately and is close to free. One recruiter’s description of the job: even when it is obvious within three minutes that the candidate is not a fit, the call gets stretched to its scheduled length. ◆

Rapport is also the part of the call that the screener is professionally practiced at and you are not. It is the least diagnostic thing in the room.

I have not heard back, so I am out

Silence is structural in at least three different ways, and only one of them means rejection.

It is often prohibited to say anything. “We’re not allowed to give feedback to anyone unless they’re in final rounds for legal protection.” And: “Most large companies literally forbid recruiters to give specific feedback.” ●

In some lanes the clock genuinely runs in months. Three weeks to schedule a first call and ten to fourteen days from screen to manager are normal at large pharmaceutical companies, and one aggregate figure for a computational hire was around one hundred and twenty days. ●

Sometimes the silence is the process working in your favor. In one documented case a candidate disclosed a sponsorship requirement, the recruiter went quiet, and the candidate concluded he had been rejected. The recruiter had in fact been negotiating with the hiring manager, and the outcome was that the phone screen was skipped and the candidate went straight to the manager round. ◆

They told me why I was rejected

The stated reason is usually not the operative one. A recruiter: “We all want to say it’s skillset, but the reality is it’s so often their presentation or conduct.” ◆

A study of technical recruiters found the same divergence at the resume stage: the reasons given for cutting a candidate differed from the factors that actually predicted the cut. ◆

Rejection reasons are written to be legally safe and non actionable. Do not redesign your preparation around one.

The screener seemed unimpressed by my technical work

In three of the four lanes this would matter. In the recruiter lane it does not, because the person cannot evaluate it. Recruiters say this openly. The useful reframing from one of them is that the screen asks whether the candidate can talk about the work coherently, and the hiring manager round asks whether the work is real. ●

An important corollary: technical depth deployed at the wrong round reads as poor judgment rather than as strength. One account, from the candidate side: “If you are going deep into system design, requirements gathering, and mentoring during a ten-minute recruiter call, you are likely over-talking the round.” ◆

What does carry signal

Much less than people want, and most of it is procedural rather than emotional.

A specific next step with a named date or a scheduling link sent during or immediately after the call. Being asked about your availability for particular slots rather than in general. The screener naming the specific people you would meet next. Being asked to send something concrete, a paper, a talk, a writing sample. Any of these represent work the organization has to do, and organizations do not do work for candidates they have already discarded. ◇

The honest summary is that a first call is close to a coin flip that you cannot read from inside, and that the correct response is to run the next application rather than to re examine this one.

The thirty minutes before

Six things, in this order.

Name the lane. Everything below depends on it. Who booked the call, what their title is, how long the slot is, and whether the invitation described the next step.

Have the lane appropriate opening ready. Research substance for a small organization or a research group, because the person can evaluate it and expects it. A structured behavioral answer for a large pharmaceutical company, because the person cannot evaluate the science and is scoring against a competency framework. A compact logistics friendly summary for a large technology company.

Have one number ready for compensation, and know which direction the risk runs in this lane. Above the band ends the call in a banded organization. Below the band costs you real money in an organization that has no band.

Have your sponsorship sentence written out and rehearsed. Not improvised. This is the single most expensive sentence in the call for you, and improvising it is how people either overshare or say something they cannot stand behind.

Have two questions you will ask even if there are four minutes left. Asking nothing is the most frequently named red flag in the entire corpus.

Have one page in front of you with your own numbers on it. Dataset sizes, runtimes, baselines beaten and by how much, what you personally built versus what the group built. Contribution disambiguation is an explicit scoring criterion in research hiring, and it is the thing candidates most often blur.

During

Write down the names of everyone mentioned, the described next step, and any date attached to it. These are the only reliable signals available to you, and they are easy to lose.

When an answer is abstract, ask for the most recent instance rather than for a general description. “Can you give me a recent example” and “how often does that happen” are the two highest yield follow ups, because a policy without an instance is not evidence.

Restate anything consequential before moving on. One sentence: “So if I am hearing you right, the band is X and the first round after this is Y. Is that right?” This costs nothing and converts vague statements into things you can rely on later.

If a question is deliberately vague, treat the vagueness as the exercise. Ask what they mean, then produce a rough answer out loud and improve it in front of them. In research organizations the speed of that loop is what is being measured, not the polish of the final answer.

After

The evidence here is weak, and it is more honest to say so than to hand you a template.

Follow up messages appear throughout the corpus, and almost none of the accounts report an effect. In the research group lane, non response is the norm rather than a verdict: “A very common experience is that the PI never tells you anything, one way or the other. Many interviews end with ‘let’s stay in touch’ and then they never email you back.” One large pharmaceutical employer explicitly asks candidates to stay in contact with their talent advisor, which is the closest thing to an invitation that appears anywhere. ◆

So: send a short note if you want to, because it costs nothing and one lane invites it. Do not read anything into the reply or the absence of one, and do not build a follow up strategy. ◇

The one action after the call that the evidence does support is procedural. If a specific next step and date were named and that date passes, ask about it once. If no next step was named at all, you learned something during the call, not after it.

The disposition that the evidence actually rewards

Two accounts, from opposite ends of the corpus, converge on the same unglamorous point.

From a candidate who passed a hiring manager screen in a bad market: “Smile and look at camera. Talk slower. Don’t over think.”

From a candidate who had spent months building the call up in advance: “honestly I was overthinking it… At the end of the day I had to realize that he’s human just like me and I was just being myself.”

Against the structural findings in the rest of this volume, that is not a contradiction. The parts of this round you can control are narrow, and the parts you cannot control are wide. Preparing the narrow parts thoroughly and then not performing is the whole technique.

The register

Does naming a high number get you filtered. Named recruiters say the compensation question is not a trap and exists so they can advocate for you. Anonymous recruiters say that a number above the range ends the conversation, and one controlled test in which a single person applied to the same job under several identities varying only the salary ask found that the maximum and above maximum versions were rejected within a day or two while the minimum version always produced an interview. Attribution: interest, plus a stage confusion. Both are true at different stages. Filtering and offer setting behave differently.

Does naming a low number cap your offer. A recruiter at a large technology company says no, the band floor still applies. Candidates at organizations without bands, and at agencies, report being given exactly what they asked for and nothing more. Attribution: lane, specifically whether formal bands and an internal equity policy exist. Rigid bands pull you up to the floor; their absence turns your number into the offer. Note also that no traced case in this corpus shows a screen number provably capping a final offer at a banded employer, so the protective claim is supported and the harm claim is not, inside that lane.

Should you refuse to give a number first. The standard advice says deflect and ask their range. One candidate executed it precisely, the recruiter escalated to “I NEED to know what is negotiable now”, then ended the call. Others report deflecting successfully. Several employers require a range before scheduling further rounds. Attribution: policy against execution, plus recruiter tolerance. The recurring stopping rule in the corpus is to deflect once and not twice.

How long the self introduction should be. Recruiters in the same forum, in the same year, say three to four minutes and say thirty seconds or less. Several say they never ask the question at all. Attribution: none available. There is no consensus among the people asking the question. Prepare a thirty second version that can expand on request.

Whether to ask what concerns they have about you. Recruiters lean hostile to the open version and describe it as lazy or desperate, though not uniformly. Hiring managers lean warm, also not uniformly. Attribution: what kind of statement each side is making. Every hiring manager who reports an actual instance says it worked and describes going back to a real gap because of it. The objections, on both sides, are policy preferences about canned questions rather than reports of it failing. Wording carries the rest: the narrow version that points at something already discussed outperforms the open request for a verdict, and the open version has a documented backfire.

When to disclose a sponsorship requirement. Candidates report instant rejection at the recruiter stage and report reaching an offer at a large employer only by holding the information until the hiring manager round. Recruiters call withholding an orange flag. Attribution: interest on the recruiter side, and real cost on the candidate side. Unresolved, and both costs are documented.

Whether cap exempt status is an advantage or a trap. Both positions appear, argued firsthand. Attribution: which visa you are talking about. For the working visa itself, cap exempt status is a genuine advantage, since it removes the lottery. For permanent residence it can be a trap, because the status belongs to the employer, it does not carry to an ordinary employer later, and the sponsorship timeline at these organizations frequently starts too late to finish. The two camps are describing different stages of the same path.

Exchange visitor status against the working visa for postdocs. Argued both ways inside a single discussion. Universities favor the cheaper exchange visitor route, which also covers the whole contract; candidates point at the return residence requirement that can attach to it. Unresolved. It depends on whether the requirement applies to your country and funding source, which is a question for an immigration attorney and not for a corpus of forum posts.

Whether the extraordinary ability visa is accepted at large technology companies. One account describes it as routinely accepted, another describes it being refused. Unresolved, and probably out of date either way. Treat as a question to ask directly.

When compensation and benefits may be raised by the candidate. One experienced community says the first call. A recruiter with thirty years and a former recruiter at a large technology company both say wait. Unresolved.

Whether postings that are not real openings are common. A vendor says roughly one in five. A government research service says there are no official statistics and notes that the vendors publishing the figures sell hiring services. Corporate recruiters deny doing it. Attribution: interest. The verifiable subset is the evergreen requisition, which cannot hire you directly by its own vendor documentation.

Volume against tailoring. A former recruiter at two large technology companies recommends high volume and applying early, and describes reading resumes in under thirty seconds and looking at roughly the first two hundred per posting. The opposing camp holds that applications outside a close match are wasted. Attribution: lane. Both camps agree that deep tailoring has poor returns at large employers.

Whether the founder round is a formality. Firsthand accounts inside the same discussions describe both a rubber stamp and a veto after a unanimous panel. Attribution: none. This round is genuinely uncalibrated, which is itself the finding.

Whether financial diligence questions help or hurt at a startup. Two comments in the same thread take opposite positions. A founder before their first major funding round calls the diligence questions hardly worth it; a fractional chief technology officer in the same thread calls the absence of a rehearsed answer a serious warning sign. Attribution: level. Precise burn rate questions from a junior candidate read differently than from a senior one.

How permissive national laboratories are about sponsorship. One account reports a visa in two weeks under cap exempt status. Another, from someone with direct experience at one of the laboratories, says they default to student and exchange visitor routes, and names three laboratories as more permissive than three others. Unresolved, and it varies by laboratory.

Whether an accent is a real obstacle. Within one community, the same thread contains an account of being cut after a director was dissatisfied with the candidate’s spoken English, and an account saying not to worry because people who have worked there for years also speak imperfectly. No consensus. Left open.

One conflict that is not a conflict

Advice from the Chinese language platforms and advice from the English language platforms diverge sharply on compensation, on honesty, and on where the human resources round sits in the sequence. In one market the round is a front loaded filter; in the other it comes last and often merely delivers a decision made elsewhere on headcount grounds. In one market negotiating is expected; in the other, asking above the budget gets the application discarded without discussion.

These are not competing claims about the same system. They are accurate descriptions of two different systems. The material from the Chinese platforms is retained in this volume only where it concerns immigration status, which transfers, and is otherwise marked as not transferable.

Where the evidence simply does not exist

Three questions that matter for research roles have no firsthand coverage at all in this corpus: how compute is allocated, what the publication and authorship policy is, and what gets open sourced. Not thin coverage. None.

This is worth stating rather than papering over, because the existing question bank already labeled that family as transferred from academic settings rather than attested in industry, and this collection confirms that label was correct. Ask those questions if you want the answers, which you should, but understand that nobody has written down evidence about how they land, and this volume is not pretending otherwise.

A note on counting

Apparent agreement across many posts is not always independent agreement. One account written in 2024 was found republished word for word by a different account in 2026 on the same platform. Popular explanations get copied, so a claim that appears many times may still rest on a single source. The evidence markers in this volume reflect independent sources, not occurrence counts.

Where your applications sit

Of the roles you have applied to, the distribution across the four lanes is roughly this. Small research organizations, meaning AI for science startups, small biotech, and nonprofit institutes, are the largest group. Large pharmaceutical companies are the second largest, and they are not a variant of large technology companies; they run a different process end to end. Research institutes, national laboratories, and postdoc positions are a smaller but real group. Large technology companies are the smallest group.

The practical consequence is that the standard first call advice, which describes a structured recruiter screen, applies to the smallest of your four groups. In your largest group the first call is frequently run by a scientist and goes technical immediately. Preparing one script for all of them means preparing for the lane you apply to least.

The pivot question, which you will be asked in every lane

You moved from engineering mechanics to computational biophysics to machine learning for molecular structure. That path is unusual enough that it will be asked about, and the evidence says the answer is scored on coherence rather than on the individual steps.

Two findings apply directly. First, publications get you the call and then stop counting; the depth is tested afterward, and candidates with strong publication records are routinely found to have gaps when probed. Second, in research hiring, contribution disambiguation is an explicit criterion. You are expected to state which parts of the work were yours and which were done by others, without being asked twice.

So the pivot answer should be one line of continuity followed by evidence, not a chronology. The continuity is real in your case: the mechanics background supplies the physics and the numerical methods, and the doctoral work applies them to molecules. Say that once, then move immediately to a specific thing you built and what it did. Do not narrate the sequence of degrees.

Sponsorship

You need it, and it is the most expensive single topic in a first call for you. Three findings shape the approach.

It is often decided before anyone speaks to you. At large pharmaceutical companies human resources screens for it before the hiring manager sees your file, and that decision can overrule the hiring manager.

Volunteering unrequested detail has ended processes. One candidate, asked an open question about concerns, mentioned the amount of time remaining on their work permit; the recruiter escalated it internally and the file was never passed on.

Answering inaccurately has also ended processes, later and more expensively, including after equipment had already been shipped to the candidate’s home.

Your two existing rules resolve this cleanly, and they were already the right rules. Never state anything untrue. Never volunteer a weakness that was not asked about. Applied here: answer the question that was asked, accurately, in one sentence, and stop. Do not append the timeline, the category, or the complications unless asked. Have that sentence written down before the call rather than improvising it.

One correction to a common assumption. Nonprofit research institutes are not automatically the safe option. Cap exempt status at nonprofits was described in the evidence as close to unavailable after research funding reductions, cap exempt status belongs to the employer rather than to you, and moving later to an ordinary employer puts you back in the lottery. Among national laboratories, the accounts describe some as considerably more willing than others.

The applications you have already sent

Two specific problems, both fixable going forward rather than retroactively.

Multiple email addresses. You have applied using more than one address. This does not do what it appears to do. Tracking systems deduplicate on name together with phone number and profile link, or on name together with city and country, and at least one does not look at email at all. So the second identity does not hide anything. What it does do is create records that get merged later by an administrator who cannot choose which version survives. Use one address, one phone number, and one profile link from here on.

The set at one large pharmaceutical company is incoherent. You applied to seven titles there, spanning postdoctoral scientist through director, and spanning RNA genomics, agent research, computational chemistry, human genomics, and software development. The evidence is consistent that the warning sign is incoherence rather than count, and that a set spanning seniority levels and unrelated functions is exactly the pattern recruiters name. Two to five roles inside one job family and one seniority band is the supported rule. A doctoral candidate applying to a director level posting is also a level mismatch on its own.

If a recruiter from that company contacts you, the single most useful sentence available is to tell them, unprompted, which other roles you applied to and which one you actually want. That converts a spray pattern into a stated preference, and it removes the coordination failure that recruiters specifically describe.

The one round where your strongest instinct is a liability

You identify weaknesses in a research plan quickly and precisely. In three of the four lanes that is an asset and it is being tested for. In the founder or principal investigator round it is conditionally an asset, and the condition is strict.

What the evidence actually supports is narrower than the usual advice, and the difference matters. Founders reward candidates who see something they do not, and they invite critique of your own past work, of a previous employer, and of objections they raise themselves. No founder in this corpus invites critique of their own current plan. Meanwhile candidates who volunteered a verdict on the business or the core approach were rejected for it. In a small research organization the core bet is the scientific approach itself, which is precisely the thing you are best at finding holes in.

The safe form is a question about method, not a verdict about the premise, and it is better delivered after being invited. Concretely, the difference is between saying that an approach will not work, and asking how they are handling the specific thing that would make it not work. The second sentence contains the same information, demonstrates the same judgment, and does not require the person opposite to defend their own decision to found the company.

Three sentences of that shape, in your own domain:

“Can I ask how you build the test split? I ask because the thing I would want to check first in my own work is whether close homologs end up on both sides, and I have been burned by that.”

“How long is the loop between a set of predictions going out and the experimental results coming back? I am trying to understand whether the model gets retrained inside a campaign or whether the design is effectively frozen between rounds.”

“When you quote that accuracy number, is it measured against your own assay data or against the public benchmark? Those two have come apart badly in the systems I have worked on, and it changes what I would prioritize in the first six months.”

Each one names a real failure mode, attaches it to your own experience rather than to their competence, and leaves them room to answer rather than to defend.

Earlier in your preparation you were advised to raise a structural objection to a company’s stated technical plan during an interview. That advice was right about the substance and wrong about the delivery. Raise it as a question, scoped to method, and preferably after being asked for your view.

Your one direct data point

You interviewed at a nonprofit research institute and were rejected afterward. That is the only account you own in the research institute lane, and it is worth more than any external report in this volume. If you still have notes from it, reread them against the research institute section: whether the first conversation went technical immediately, whether you were expected to arrive with a direction, and whether anyone from human resources appeared before the science.