Interview
Top HireVue Interview Questions in 2026: Questions, Answers & STAR Examples
50+ real HireVue interview questions with STAR-method answers. Behavioral, situational, and company-specific examples. Practice with AI mock interviews.
HireVue asks 5-8 questions in 20-30 minutes, and 60-70% of them are behavioral. That means the same core question types appear across JP Morgan, Goldman Sachs, Deloitte, Amazon, and hundreds of other companies — just with different angles.
This guide gives you the actual questions candidates report being asked, strong STAR-method answers for each, and the specific competency each question tests so you know exactly what the AI is scoring.
For format details and AI scoring mechanics, see our Complete HireVue Interview Preparation Guide. For company-specific variations, see Companies That Use HireVue.
How HireVue Categorizes Questions
Every HireVue question maps to a competency the company wants to evaluate. Understanding this helps you give the AI exactly what it's looking for:
| Competency | What the AI Scores | Frequency |
|---|---|---|
| Teamwork & Collaboration | Working with others, resolving disagreements | Very High — asked by every company |
| Problem-Solving | Analytical thinking, creative solutions | Very High |
| Leadership & Initiative | Taking charge, going beyond expectations | High |
| Adaptability & Learning | Handling change, learning from mistakes | High |
| Communication | Explaining complex ideas, influencing others | Medium-High |
| Motivation & Values | Cultural fit, purpose, drive | Medium |
| Situational Judgment | Hypothetical scenario reasoning | Medium (higher at consulting firms) |
Teamwork & Collaboration Questions
These appear in every HireVue interview regardless of company or role.
Q1: "Tell me about a time you worked on a team to achieve a goal."
What the AI evaluates: Collaboration, role clarity, shared success
Strong STAR Answer:
Situation: During my junior year, our capstone project team of 5 needed to build a full-stack inventory management system in 8 weeks. Two weeks in, we realized our database design couldn't handle the client's requirements.
Task: As the backend lead, I needed to get the team aligned on a database redesign without derailing our timeline.
Action: I called a team meeting and presented three redesign options with time estimates for each. Instead of pushing my preferred approach, I asked each team member to evaluate the options based on their component's needs. Our frontend developer pointed out that Option B would simplify their API integration. I facilitated a vote, and we went with Option B unanimously. I then created a shared Notion board to track migration tasks, assigned ownership for each table migration, and scheduled daily 15-minute standups for the next week to catch blockers early. When our testing lead fell behind, I paired with them for two evenings to write migration tests together.
Result: We completed the redesign in 5 days instead of the projected 8, and our final system handled 10x the data volume. The project received the highest grade in our cohort, and three team members specifically cited the collaborative process in their peer reviews.
Why this works: The Action is specific (three options, Notion board, daily standups, paired work), it shows facilitation vs. dictation, and the result is quantified.
Q2: "Describe a time you had a conflict or disagreement with a teammate."
What the AI evaluates: Conflict resolution, emotional intelligence, professionalism
Strong STAR Answer:
Situation: At my previous internship, a fellow intern and I disagreed on the architecture for a microservice we were building together. They wanted a monolithic approach for simplicity; I believed microservices were necessary given the scaling requirements.
Task: We needed to reach a decision within two days to stay on track for our sprint deadline.
Action: Instead of escalating to our manager, I suggested we each spend 30 minutes documenting the pros and cons of our approach, then compare notes objectively. When we reviewed each other's analysis, I realized their concern about operational complexity was valid — we didn't have the DevOps maturity for full microservices. I proposed a hybrid: a modular monolith with clear service boundaries that could be split later. I drew up a quick architecture diagram showing how this approach addressed both our concerns. They agreed it was a good compromise.
Result: We shipped the modular monolith on schedule. Six months later, when the team did move to microservices, the clean boundaries I'd built made the migration straightforward. My manager mentioned this collaboration in my internship evaluation as an example of mature conflict resolution.
Q3: "Tell me about a time you had to work with someone difficult."
What the AI evaluates: Interpersonal skills, patience, professionalism
Strong STAR Answer:
Situation: On a cross-functional project, I was paired with a senior data analyst who was dismissive of suggestions from junior team members and rarely responded to messages on time.
Task: I needed their dataset by Thursday to complete my analysis for a Friday stakeholder review.
Action: Rather than complaining to my manager, I adapted my communication style. I learned they preferred brief, structured emails over Slack messages, so I switched to email with clear subject lines like "Action needed by Thursday: dataset for stakeholder review." I also scheduled a 15-minute call to walk through my requirements in person, which turned out to be much more productive than async communication. During the call, I asked their opinion on how to structure the analysis — which showed respect for their expertise and made them more invested in the outcome.
Result: They delivered the dataset on Wednesday, a day early. We ended up collaborating effectively for the rest of the project, and they even recommended me for a follow-up initiative. I learned that adapting my communication style to others' preferences is more effective than expecting them to adapt to mine.
Problem-Solving Questions
Q4: "Tell me about a time you solved a challenging problem."
What the AI evaluates: Analytical thinking, creativity, systematic approach
Strong STAR Answer:
Situation: As a software engineer at a SaaS startup, our customer churn rate spiked from 5% to 12% over two months, and nobody could identify the cause. Marketing blamed the product, product blamed onboarding, and support was overwhelmed with tickets.
Task: My manager asked me to investigate the root cause using our analytics data.
Action: I started by segmenting churned customers by cohort, plan type, and feature usage. I wrote SQL queries to compare the behavior of churned users vs. retained users over their first 30 days. The data revealed something surprising: churn was concentrated among users who signed up through our new self-serve onboarding flow — they were 3x more likely to churn than users who went through the guided setup. I dug deeper and found that self-serve users were missing two critical setup steps: connecting their data source and inviting a team member. I presented these findings to the product team with a specific recommendation: add a progress tracker and email reminders for incomplete setups.
Result: The product team shipped the progress tracker in the next sprint. Within 6 weeks, the self-serve completion rate went from 40% to 78%, and churn dropped back to 6%. The CEO mentioned this analysis in the all-hands as an example of data-driven problem-solving.
Q5: "Describe a time you used data to make a decision."
What the AI evaluates: Data literacy, evidence-based reasoning (especially valued at Capital One, Amazon)
Strong STAR Answer:
Situation: As a product analyst intern, I was asked to recommend whether we should invest engineering resources in improving our mobile app or our desktop dashboard — both had feature requests from users.
Task: I needed to provide a data-backed recommendation within one week.
Action: I pulled usage data from Mixpanel for the past 6 months and analyzed daily active users, session duration, and feature adoption by platform. I also segmented by customer tier — enterprise vs. SMB. The data showed that while mobile had 60% of DAUs, desktop users had 3x longer sessions and 2x higher feature adoption. Critically, 85% of enterprise customers (our highest-value segment) used desktop exclusively. I built a cost-benefit analysis comparing the expected revenue impact of improving each platform, factoring in engineering cost estimates from the tech lead.
Result: I recommended desktop investment, projecting a 15% increase in enterprise retention. The VP of Product approved the recommendation, and Q3 enterprise retention improved by 18% — exceeding my projection.
Q6: "Tell me about a time you identified a problem before it became critical."
What the AI evaluates: Proactiveness, attention to detail, risk awareness
Strong STAR Answer:
Situation: While reviewing our API logs during a routine check, I noticed that response times for our payment endpoint had gradually increased from 200ms to 800ms over three weeks — still under the 2-second SLA but trending in the wrong direction.
Task: Nobody else had flagged this because it wasn't causing alerts yet. I decided to investigate before it became a production incident.
Action: I traced the slowdown to a database query that was doing a full table scan as our transaction table grew. The index that should have covered this query had been accidentally dropped during a recent migration. I verified this by running EXPLAIN ANALYZE on the query, then created a PR to restore the missing index with a migration script. I also added a monitoring alert to flag any endpoint that degraded by more than 50% from its baseline, so we'd catch similar issues earlier.
Result: After deploying the fix, response times dropped back to 180ms. My manager estimated that if the trend had continued, we would have hit the SLA breach within 10 days, potentially triggering penalty clauses with two enterprise clients worth $800K annually. The monitoring alert I added caught another degradation issue the following month before it impacted users.
Leadership & Initiative Questions
Q7: "Tell me about a time you demonstrated leadership."
What the AI evaluates: Influence, initiative, accountability
Strong STAR Answer:
Situation: During a hackathon at my company, I noticed that the three teams were all building similar internal tools, with no coordination between them.
Task: Without any formal authority — I was the most junior person there — I decided to try to align the teams.
Action: I created a shared document listing each team's project scope and shared it in the hackathon Slack channel, highlighting the overlap. I then proposed a 20-minute cross-team sync where each team pitched their approach. During the sync, I facilitated a discussion that revealed Team B's authentication module could serve all three projects. I suggested Team B build it as a shared library while Teams A and C focused on their unique features. I volunteered to be the integration point — reviewing PRs from all three teams to ensure compatibility.
Result: All three teams shipped by the deadline, and the shared auth library became an official internal package used by 4 other teams after the hackathon. I was nominated for the "hackathon MVP" award. More importantly, my manager started inviting me to architecture discussions based on the coordination skills I demonstrated.
Q8: "Give an example of when you went above and beyond."
What the AI evaluates: Drive, ownership, impact beyond requirements
Strong STAR Answer:
Situation: During my internship, I was assigned to fix a bug in the notification service — a simple null pointer exception that took about an hour to fix.
Task: My task was just the bug fix, but when I was in the code, I noticed the entire notification system had no retry logic. If a notification failed to send, it was silently dropped.
Action: After submitting the bug fix PR, I spent an additional evening designing a retry mechanism with exponential backoff. I wrote a short design doc explaining the problem — we were silently dropping about 3% of notifications — and the proposed solution. I presented it to my tech lead the next morning, and after they approved the approach, I implemented it over the next two days. I added dead-letter queue logging so we could track permanently failed notifications too.
Result: The retry mechanism recovered 95% of previously-dropped notifications. Customer support tickets about "missing notifications" dropped by 40% that month. My tech lead called it "the most impactful intern contribution this year," and I received a return offer.
Adaptability & Learning Questions
Q9: "Tell me about a time you failed and what you learned."
What the AI evaluates: Self-awareness, growth mindset, resilience (especially valued at Microsoft)
Strong STAR Answer:
Situation: In my first month as a junior developer, I was asked to optimize a slow database query. I was confident and went straight to rewriting it without fully understanding the existing query's purpose.
Task: I needed to improve query performance while maintaining the same results.
Action: I rewrote the query, tested it against a sample dataset, saw a 5x speed improvement, and pushed it to production. Within an hour, the finance team reported that their monthly reconciliation numbers were wrong. My "optimized" query had removed a LEFT JOIN that handled edge cases for refunded transactions — I'd changed the business logic, not just the performance. I immediately rolled back the change, then spent the rest of the day understanding every line of the original query. I documented what each join and filter did, then wrote an optimized version that preserved the exact business logic. I also added integration tests with edge case data to prevent this kind of regression.
Result: The corrected optimization still achieved a 4x speed improvement, and the regression tests I wrote caught two similar issues from other developers in the following months. Most importantly, I learned to never modify code I don't fully understand. I now always start by writing tests that capture current behavior before making performance changes — a practice I've carried through every role since.
Q10: "Describe a time you had to adapt to a significant change."
What the AI evaluates: Flexibility, composure, constructive response to change
Strong STAR Answer:
Situation: Midway through a 6-month project, our company was acquired, and the new parent company mandated we migrate from AWS to Azure within 90 days — while continuing to deliver feature milestones.
Task: As the infrastructure lead on a 4-person team, I needed to plan and execute the migration without slipping our product deadlines.
Action: Instead of panicking or pushing back, I spent the first two days mapping every AWS service we used to its Azure equivalent and identifying the gaps. I created a phased migration plan: Phase 1 (weeks 1-4) migrated stateless services, Phase 2 (weeks 5-8) migrated databases with zero-downtime cutover, Phase 3 (weeks 9-12) was testing and decommissioning. I negotiated with product management to shift two lower-priority features to the next quarter, which freed up 30% of our sprint capacity for migration work. I also set up parallel environments so we could test in Azure while serving production from AWS.
Result: We completed the migration in 85 days — 5 days early. We had zero customer-facing downtime and actually improved our P95 latency by 15% because Azure's region was closer to our user base. The CTO used our migration as the template for the remaining 6 teams.
Communication Questions
Q11: "Tell me about a time you explained something complex to a non-technical audience."
What the AI evaluates: Clarity, audience awareness, patience
Strong STAR Answer:
Situation: Our sales team was losing deals because they couldn't explain our API-first product to non-technical procurement teams at enterprise clients.
Task: My VP of Engineering asked me to create a presentation that the sales team could use to explain our platform without getting lost in technical jargon.
Action: I sat in on three sales calls to understand where confusion happened. I found that sales reps were using terms like "REST API," "webhook," and "microservices" — which meant nothing to procurement. I created a new deck that explained our product using analogies: APIs became "digital handshakes," webhooks became "automatic notifications — like getting a text when your package is delivered," and our architecture became "specialized teams working together vs. one person doing everything." I also created a one-page FAQ answering the top 10 questions procurement teams asked, and ran a 30-minute training for the sales team.
Result: The sales team's demo-to-close rate improved from 22% to 35% in the following quarter. Three sales reps specifically credited the new materials. The VP of Sales asked me to create similar materials for two other product lines.
Q12: "Describe a time you persuaded someone to change their mind."
What the AI evaluates: Influence, evidence-based argumentation, empathy
Strong STAR Answer:
Situation: Our team lead wanted to build a custom analytics dashboard from scratch — estimated at 8 weeks of development. I believed we should use an existing tool like Metabase and invest those 8 weeks in our core product instead.
Task: I needed to convince the team lead without undermining their authority or making them feel overruled.
Action: Instead of arguing in a meeting, I spent one evening setting up a Metabase proof of concept with our actual data. I replicated the three most-requested dashboard views and shared the result in a "just wanted to show you something interesting" email to the team lead. I framed it as "here's what I found while exploring options" rather than "here's why you're wrong." I included a comparison table: custom build (8 weeks, ongoing maintenance, limited charts) vs. Metabase (2 days setup, community-maintained, extensive visualization). I emphasized the upside for them: "This frees your team to work on the ML features you've been wanting to prioritize."
Result: The team lead reviewed the POC and immediately saw the value. They brought it to the next planning meeting as their own recommendation, which I supported without claiming credit. We saved 7.5 weeks of development time and redirected those resources to the ML pipeline, which became the company's main competitive differentiator that year.
Motivation & Values Questions
Q13: "Why do you want to work at [Company Name]?"
What the AI evaluates: Research depth, cultural alignment, genuine interest
Framework for a strong answer (adapt per company):
"I'm drawn to [Company] for three specific reasons. First, [specific product/initiative] aligns with my interest in [domain] — I've been following [specific recent news or project] and I find the approach to [specific challenge] compelling. Second, [Company]'s culture of [specific value from their values page] resonates with how I work — in my last role, I [brief example demonstrating that value]. Third, the [specific team or role] would let me build on my experience in [relevant skill] while growing in [area you want to develop]. I'm particularly excited about the opportunity to [specific contribution you'd make]."
Do NOT say: "I want to work here because it's a great company" / "The salary is competitive" / "I need a job." These score zero on cultural alignment.
Q14: "Where do you see yourself in 5 years?"
What the AI evaluates: Ambition, alignment with company growth paths
Strong Answer:
"In 5 years, I see myself as a senior engineer who has deep expertise in [relevant domain] and has grown into a technical leadership role. Specifically, I want to have designed and shipped systems that serve millions of users, mentored junior engineers, and contributed to the architectural direction of my team. I'm drawn to [Company] because the scale of problems here would accelerate that growth — I'd be working on systems that [specific impact]. I'm also interested in eventually bridging the gap between engineering and product strategy, so I'd seek opportunities to work closely with product and business teams as I grow."
Situational / Hypothetical Questions
These are more common at consulting firms (Deloitte, Bain, BCG) and Goldman Sachs.
Q15: "A client is unhappy with your team's deliverable. How would you handle it?"
What the AI evaluates: Client orientation, composure, problem-solving (Deloitte favorite)
Strong Answer:
"My first step would be to listen. I'd schedule a call with the client to understand specifically what fell short of their expectations — is it the scope, the quality, or the timeline? I'd resist the urge to be defensive and instead take detailed notes on their concerns. Next, I'd assess internally with my team: was this a miscommunication about requirements, or did we genuinely underdeliver? If we missed the mark, I'd own it transparently with the client: 'You're right, here's what happened, and here's our plan to fix it.' I'd present a concrete remediation plan with a timeline. If it was a misalignment in expectations, I'd work with the client to document revised requirements and set up more frequent check-ins to prevent drift. Either way, I'd follow up in writing to confirm alignment and add this as a retrospective topic so the team learns from it."
Q16: "You discover an error in a report that's already been sent to a client. What do you do?"
What the AI evaluates: Integrity, urgency, communication (finance/consulting favorite)
Strong Answer:
"I'd act immediately. First, I'd verify the error — confirm what's wrong, assess the impact, and determine if it changes any conclusions or recommendations. Then I'd escalate to my manager within the hour, presenting the error and my proposed correction. Transparency is non-negotiable: I'd recommend we notify the client proactively rather than hoping they don't notice. I'd draft a correction communication for my manager's review that explains the error, provides the corrected data, and states what we're doing to prevent it — like adding a peer review step. Speed and honesty build trust more than perfection does."
Q17: "How would you handle a situation where your manager gives you conflicting priorities?"
What the AI evaluates: Initiative, communication skills, prioritization
Strong Answer:
"I'd address it directly rather than guessing. I'd go to my manager with a clear summary: 'I have Task A due Thursday and Task B due Friday, but both require 3 days of work. Here's how I'm thinking about prioritization, based on business impact — does this align with your thinking?' If they can't decide, I'd ask: 'If I can only complete one by the deadline, which one would you choose?' I've found that managers appreciate when you surface conflicts early instead of silently missing a deadline. If the conflict happens repeatedly, I'd suggest a brief weekly priority-setting check-in to prevent it."
Company-Specific Question Variations
The same competency gets asked differently depending on the company:
| Competency | JP Morgan Version | Amazon Version | Goldman Sachs Version | Deloitte Version |
|---|---|---|---|---|
| Teamwork | "Tell me about a time you collaborated across teams" | "Tell me about a time you earned trust from a skeptical team" | "How do you build consensus in a group?" | "Describe working with a cross-functional client team" |
| Problem-Solving | "Tell me about a technical challenge" | "Tell me about a time you simplified a complex process" | "Walk me through how you'd analyze [problem]" | "A client presents you with incomplete data. How do you proceed?" |
| Leadership | "Describe a time you showed leadership" | "Tell me about a time you had to make a decision without your manager's input" | "How would you organize a sock drawer?" | "You're leading a team that's falling behind. What do you do?" |
| Failure | "Tell me about a time you made a mistake" | "Tell me about a time you failed to meet a customer expectation" | "What's the biggest risk you've ever taken that didn't pay off?" | "Describe a recommendation that was wrong" |
For detailed company breakdowns: Companies That Use HireVue →
Building Your STAR Story Bank
You don't need 50 stories. You need 8-10 versatile stories that can be adapted to different question angles.
Story Bank Template
For each story, prepare:
| Field | Example |
|---|---|
| One-line summary | "Redesigned the database during capstone project" |
| Competencies it covers | Teamwork, Problem-Solving, Leadership, Communication |
| Situation (2 sentences) | Capstone team, database couldn't handle requirements, 2 weeks in |
| Task (1 sentence) | Needed to align team on redesign without derailing timeline |
| 3-4 Action bullet points | Presented options, facilitated vote, created tracking board, paired with testing |
| Result (quantified) | Completed 3 days early, 10x data volume, highest grade |
Versatility Test
A good story can answer 3-4 different questions:
- "Tell me about teamwork" → Focus on facilitation and the vote
- "Tell me about problem-solving" → Focus on the three redesign options
- "Tell me about leadership" → Focus on taking initiative as the backend lead
- "Tell me about communication" → Focus on the daily standups and cross-team alignment
If a story only answers one type of question, replace it with a more versatile one.
Practice These Questions with AI
Reading questions and answers isn't the same as answering them out loud with a timer. The only way to prepare for HireVue's format is to practice it.
Thita.ai's AI Mock Interview simulates the one-way video interview format:
- Real behavioral questions from the same competency areas HireVue tests
- Timed responses to build your 3-minute pacing
- AI-powered feedback on your answer structure and content
- Practice as many times as you need before your real interview
For behavioral-specific practice: Practice Behavioral Questions →
Key Takeaways
- 60-70% of HireVue questions are behavioral — STAR method is essential for all of them
- The same 7 competencies (teamwork, problem-solving, leadership, adaptability, communication, motivation, situational judgment) cover 95% of questions
- Strong answers have specific details — names, numbers, dates, outcomes
- The Action section should be 50-60% of your total answer
- Build 8-10 versatile STAR stories that each cover 3-4 competencies
- Company context changes the angle, but the core questions are remarkably consistent
- Practice on camera — the format matters as much as the content
Start Preparing Now
Step 1: Read the Complete HireVue Interview Prep Guide for format and AI scoring details
Step 2: Find your company's specific question style
Step 3: Take a free AI mock interview to practice these questions in HireVue's timed format
Related Articles
- HireVue Interview Preparation: The Complete Guide 2026
- Companies That Use HireVue: Complete Prep Guide
- HireVue Coding Assessment Preparation Guide
- JP Morgan HireVue AI Interview Preparation
- Behavioral Interviews for Engineers: Real Questions and Strong Answers
- How to Explain Your Thought Process in Coding Interviews
- Best AI Interview Prep Tools in 2026