HR Interview Screening Questions: 10 Proven Picks

A hiring manager has a strong résumé in front of them, a full interview calendar, and no reliable way to tell which candidates should move to the technical round. For a 15-minute screen, use ten questions that test motivation, communication, logistics, and role fit, then score each answer against criteria tied to the job. The questions below give Series A–C tech teams in the US and Europe a consistent starting point, with intent, red flags, and pass-through signals for phone and video screens.

Treat the screen as a decision, not a résumé recap. Ask the same core questions in the same order, record evidence rather than impressions, and move candidates forward only when their answers meet the requirements you set in advance. For SDR teams, a structured screen can also support better SDR hiring with hireSDR.

1. Walk me through your career, focusing on the roles most relevant to this position

Intent: Establish whether the candidate's experience matches the role's must-have requirements. Set a clear time limit and listen for scope, progression, and direct relevance, not a polished autobiography.

A broad opening can turn into a tour of every job the candidate has held. Keep the prompt focused. A strong answer connects past responsibilities to the role you're hiring for, distinguishes personal contributions from team outcomes, and gives you a concrete area to probe. For a remote engineering role, that might be ownership of a service, collaboration with a distributed team, or communicating technical trade-offs in English.

Scoring rule: Give the same prompt and time limit to every candidate. Rate the answer against three to five job-related criteria, then ask one follow-up about the most relevant role.

Red flags: The answer stays at the level of job titles, relies on vague claims, or doesn't clarify what the candidate personally owned. A candidate who gives a clear overview but no specific evidence may merit a follow-up, not an automatic pass.

Pass through: Advance when the candidate's experience covers the role's essential scope and they can explain their contribution with relevant detail. For a nearshore candidate, note practical remote collaboration experience, such as async work, time-zone overlap, or client communication. Use the same criteria whether a recruiter or hiring manager conducts the screen, as outlined in effective candidate screening steps.

2. Why are you looking to leave your current role?

Intent: Find out what the candidate wants next and whether the job can offer it. Ask the question neutrally. The point isn't to judge someone for leaving, but to test alignment between their motivation and the work, team, and growth path you can provide.

A strong response is specific and forward-looking. A candidate might want broader technical ownership, more exposure to product decisions, or a role with clearer customer impact. Ask, “What would an ideal next role include that your current one doesn't?” Then compare the answer with the actual job. If the candidate wants deep specialization but your startup needs someone to handle changing priorities, surface that mismatch now.

Red flags: The candidate offers only general complaints about managers, describes unexplained short tenures, or focuses exclusively on compensation. Those answers don't prove poor fit, but they leave important questions unanswered. Probe for context and what the candidate has learned about the conditions where they do their best work.

Pass through: Move forward when the candidate names a credible reason for exploring and that reason matches what the position can deliver. Record a concise summary so the panel can assess the same evidence later. Don't treat a request for better pay or a change in management as a character flaw; assess whether expectations and role conditions align.

3. What are your salary expectations?

Intent: Confirm whether the compensation conversation is viable before both sides invest more time. Ask for a range, share the approved band early, and make clear what the band covers, including any relevant bonus or equity components.

The answer only helps if your team has a current compensation range for the role, level, and location. A US-based company hiring in Europe or Latin America shouldn't rely on one broad regional estimate. Compare the candidate's expectations with the budget and the role's location-specific compensation approach, then clarify any differences in employment terms that could affect the offer.

Red flags: A candidate gives a number far outside the approved band and won't discuss the range, or the recruiter can't explain the company's compensation framework. The second problem is yours to fix before continuing the search.

Share your range before late-stage interviews. It's more useful to surface a genuine gap early than to discover it after the candidate has completed several rounds.

Pass through: Advance when expectations are compatible with the band or there's a clear, realistic path to alignment. Don't pressure candidates to disclose current pay; focus on expectations for this role and local requirements. For teams building cross-border compensation bands, salary benchmarking guidance can help frame the discussion.

4. Walk me through a project you shipped end to end

Intent: Test ownership, judgment, and delivery. Ask the candidate to describe the problem, constraints, decisions, trade-offs, and outcome. The project could be a service launch, a data pipeline, a product feature, or a process change, depending on the role.

A good answer separates what the candidate did from what the team did. Ask, “What did you personally decide?” and “What would you change now?” For a DevOps candidate, probe the deployment or rollback choices. For a product manager, ask how customer needs shaped scope. For a BI developer, ask how they checked the output against the business question.

Red flags: The candidate can't explain their own contribution, lists tools without decisions, or describes success without saying how they knew the work was effective. Don't require confidential figures. An anonymized result or a clear explanation of the outcome is enough to test reasoning.

Pass through: Move forward when the candidate can walk through a relevant piece of work, explain at least one trade-off, and answer a specific follow-up about a decision they made. The result doesn't have to be perfect; their ownership and learning matter more than a rehearsed success story.

5. Describe a time you disagreed with a technical or product decision

Intent: Assess how the candidate raises concerns, listens, and works after a decision is made. Use a real example, not a hypothetical. Ask what evidence the candidate brought forward, how the other person responded, and what happened once the team chose a direction.

Strong answers show respectful disagreement grounded in user needs, operational risk, or technical evidence. The candidate may have changed the decision, or they may have accepted a different choice and helped execute it. Either outcome can signal sound judgment if they explain the reasoning and their contribution clearly.

Red flags: The candidate says they never disagree, describes “winning” without acknowledging the team's needs, or blames colleagues for a poor result. A story about conflict that ends before the decision is implemented is incomplete.

Pass through: Advance when the candidate gives a concrete example, explains their reasoning, and describes how they handled the outcome. Score evidence, listening, and follow-through separately. In a distributed team, pay attention to whether the candidate can explain how they handled disagreement through written communication as well as live discussion.

6. What is your availability, notice period, and overlap with our working hours?

Intent: Check the practical conditions for starting and collaborating. Ask about notice period, earliest start date, time zone, and the working-hour overlap the person can reliably maintain. Define the team's required collaboration window before interviews begin.

A candidate's stated availability needs to match how the team works. If the role requires live incident coordination or recurring planning meetings, explain those expectations and confirm the candidate can meet them. For remote teams, clarify whether overlap is a fixed schedule or changes with daylight-saving time.

Red flags: The candidate can't commit to an essential meeting window, or the team can't state which hours matter. Don't confuse a preference for async work with an inability to collaborate. Separate required live coverage from habits that can be handled asynchronously.

Pass through: Advance when the candidate's start timing and reliable overlap meet the role's documented requirements. Confirm time-zone assumptions during scheduling rather than relying on a vague statement that the candidate is “flexible.” LATAM can be a practical nearshore option for US teams that need working-hour overlap, as discussed in nearshore outsourcing advantages.

7. How do you communicate and collaborate when working remotely?

Intent: Find out whether the candidate has concrete habits for keeping work visible and teams aligned without constant meetings. Ask for an example of a handoff, a written update, or a time they unblocked themselves asynchronously.

Strong answers name behaviors, not just tools. A candidate might explain how they document a decision, flag a blocker, or summarize progress for teammates in different time zones. For a senior engineer, ask how they communicate technical risks to product or customer-facing teams.

Red flags: The candidate equates remote work with being available online, can't describe how they share progress, or relies on meetings to resolve every question. Don't score candidates on whether they use your exact preferred tool. Look for habits that transfer across Slack, Notion, Linear, Jira, or other team systems.

Pass through: Advance when the candidate offers a specific example of clear written communication or an effective handoff and can describe how they keep stakeholders informed. For roles where writing is central, ask the candidate to talk through a short status update or design note. Set expectations for the team's own practices using a guide to building remote work culture.

8. Walk me through how you would approach this problem at a high level

Intent: See how the candidate frames an unfamiliar problem before asking them to complete a test. Use a realistic, role-relevant scenario, such as a slow reporting query, a flaky deployment pipeline, or an onboarding flow with compliance steps. Remove confidential details.

A strong candidate clarifies the goal and constraints before proposing a solution. They identify trade-offs, explain how they'd validate the approach, and name a sensible first step. For an early screen led by HR or a nontechnical founder, score clarity and structure separately from technical depth. A brief video walkthrough can help the interviewer understand how to keep the discussion focused.

Red flags: The candidate jumps straight to a solution without checking assumptions, relies on memorized jargon, or can't explain why their approach fits the scenario. Don't turn a screening conversation into an unannounced technical exam.

Pass through: Advance when the candidate asks useful clarifying questions, lays out a coherent approach, and communicates trade-offs at a level appropriate to the role. If the screen identifies a promising approach but leaves technical depth uncertain, route that question to the engineering interview.

A short example can help interviewers calibrate how to frame a scenario-based prompt.

9. Tell me about a production incident you handled

Intent: Assess ownership, communication under pressure, and learning from operational problems. Ask the candidate to describe how the incident was detected, what they did to mitigate it, who they informed, and what changed afterward.

For SRE, DevOps, and backend roles, this question can separate hands-on incident experience from secondhand familiarity. A useful answer explains the candidate's role in the response and how the team reduced risk afterward, such as improving an alert, updating a runbook, or changing a deployment check.

Red flags: The candidate deflects responsibility, talks only about the technical fix, or can't explain how they communicated with affected stakeholders. Don't penalize someone for an incident with an imperfect outcome. Evaluate their decisions and learning, not whether every system behaved as intended.

Pass through: Advance when the candidate gives a clear timeline, identifies their own actions, and names a practical follow-up. If the role includes on-call work, ask directly about the candidate's operational responsibilities and whether they understand the schedule. For role-specific prompts, consult these DevOps interview questions.

10. What do you know about our company, and why do you want to work here?

Intent: Test preparation and whether the candidate understands the role, company stage, and working model. A useful answer connects something specific about the product or team to the candidate's experience and what they want to contribute.

Don't score enthusiasm, charisma, or memorized product descriptions. Ask what the candidate has learned about the position and what they'd want to understand early in the job. At a startup, make the trade-offs clear: scope may be broad, priorities can shift, and processes may still be developing.

Red flags: The answer could apply to any employer, or the candidate's expectations conflict with the role's actual scope. A candidate may have done limited research and still be a strong prospect, so give them room to explain how they evaluated the opportunity.

Pass through: Advance when the candidate can explain why this role makes sense for their experience and ask a relevant question about the team, product, or priorities. Be candid about the company's stage and work model, then score the fit based on the candidate's response to those realities.

10 HR Screening Questions Comparison Guide

Turn Good Screens Into Faster Hires

A useful screen produces comparable evidence, not a vague feeling about who seemed strongest. Structured interviews have been shown to predict job performance better than unstructured conversation. A major 2016 review reported an average operational validity of 0.58 for structured interviews and 0.38 for unstructured interviews under its preferred correction method. Validity describes how closely interview scores relate to later job performance, not a candidate's chance of succeeding. See the review of personnel-selection research.

Use this checklist to turn answers into consistent decisions:

Define the requirements: Select job-critical competencies from the role, not generic “fit.” Prepare a fixed question set tied to those competencies.

Set score anchors: Define what insufficient, acceptable, and strong evidence looks like before the first screen.

Record evidence: Write down the candidate's specific actions, examples, and explanations. Keep interpretation separate from what they said.

Check logistics consistently: Confirm the same job-related requirements for every candidate, including schedule, location, work authorization where relevant, and compensation expectations. Avoid questions about protected personal characteristics. The EEOC's guidance for employers explains which subjects to avoid in US hiring, and teams should also check applicable local laws.

Make a documented decision: Compare the evidence with the rubric. Move strong matches to the technical interview, identify what a “maybe” needs to prove next, and close out candidates who don&#39;t meet essential requirements.</li>

For teams hiring across regions, nearshore LATAM talent can offer practical time-zone alignment for US-based collaboration, but the same role criteria and scoring anchors should apply to every candidate. If your internal team needs help designing and running a consistent process, explore Recruitment Process Outsourcing or IT recruitment support. A broader hiring process guide can also help teams review how screening fits into the full candidate journey.

GENTY recruitment supports tech and sales hiring across Latin America with candidate screening, structured initial interviews, and curated shortlists. If you&#39;re building a repeatable screening process or need help finding nearshore candidates, visit GENTY recruitment to discuss your hiring needs.