Full-stack engineer behavioural interview questions

As asked

Tell me about a feature you owned from problem framing through to production rollout. Walk through the technical and the non-technical decisions.

Sample answer outline

Pick a feature with measurable impact. Cover: how the problem was framed (and how you sharpened the brief), the technical decisions you made (database changes, API shape, UI architecture, rollout plan), the collaborations (design, product, data), and the rollout (canary, metrics watched, incidents during launch). Land on the outcome and what you would do differently. Strong full-stack candidates make non-glamorous decisions sound load-bearing: schema migration ordering, the cache invalidation that you almost missed.

Expect these follow-ups

• What is the part of the feature you are least proud of?
• How did you decide what to build vs what to defer?
• Did the metric actually move?

As asked

Tell me about a time you were responsible for a production incident. What failed, how did you diagnose it, what was the resolution, and what did you change afterward to prevent it from happening again?

Sample answer outline

A strong answer names a real failure (not vague), describes the diagnosis process with specific tools (APM, logs, queries), explains the immediate fix and the longer-term fix separately, and shows genuine ownership. The candidate should describe what they changed: monitoring, alerting, runbooks, or code changes. Look for them mentioning the blameless postmortem and what they personally learned.

Expect these follow-ups

• What monitoring or alerting would have caught this earlier? Did you implement that afterward?

As asked

Tell me about a time you disagreed with a teammate or tech lead about a technical approach. How did you handle the disagreement, and what was the outcome?

Sample answer outline

Look for the candidate to describe the actual technical substance of the disagreement, not just the interpersonal dynamic. A strong answer shows them presenting data or a proof of concept to support their position, being genuinely open to the other side's arguments, and committing to the decision once it was made. Avoid candidates who say they always defer to the senior engineer or who describe the other person as simply wrong.

Expect these follow-ups

• How did you decide to escalate vs. accept the other approach?

As asked

Tell me about a time when you realized mid-sprint that a feature would not be ready by the deadline. How did you handle it, who did you communicate with, and what was the outcome?

Sample answer outline

Look for proactive communication (they told stakeholders before the deadline, not the day before or after), a clear description of what was cut vs. kept, and evidence that the cut scope was handled afterward rather than just dropped. Strong candidates distinguish between cutting scope and cutting quality; they do not ship broken code to hit a date.

Expect these follow-ups

• What did you put in place so that the cut features did not get forgotten permanently?

As asked

Tell me about a time the requirements for a feature were vague or kept changing mid-development. How did you navigate that and still deliver?

Sample answer outline

Look for them driving a requirements clarification session rather than waiting, building incrementally with frequent demos, and making explicit technical decisions that were documented when product could not decide. Strong candidates show they can operate with ambiguity without getting blocked, but also know when to escalate.

Expect these follow-ups

• What would you do differently if you could redo that project?

As asked

Walk me through how you give code review feedback on a fullstack PR that touches a React component, an Express route, and a database migration. What do you look for at each layer, how do you prioritize comments, and how do you handle disagreements?

Sample answer outline

Strong candidates distinguish between blocking issues (correctness, security, performance), suggestions (style, alternative approaches marked as non-blocking), and questions (seeking to understand the author's intent). They give actionable, specific feedback rather than vague criticism. They are empathetic about the author's context and time. When receiving feedback they separate the code from themselves, ask for clarification before defending, and update or push back with a clear reason.

Expect these follow-ups

• How do you handle a PR that needs significant rework but the author is confident in their approach?

As asked

Adobe's values include 'create genuine impact.' Tell me about a time your engineering work directly changed the experience for a real user or customer. How did you measure that impact?

Sample answer outline

A strong answer uses the STAR format and connects the engineering decision to a measurable customer outcome, not just a technical metric. The candidate should name a specific metric (latency, error rate, conversion, NPS) that moved, explain how they knew the customer was affected, and show they cared about the outcome beyond shipping the feature. Adobe looks for engineers who think in terms of customer value, not just code output.

Expect these follow-ups

• How did you validate that the impact was actually caused by your change?
• What would you have done differently if the impact had been negative?

As asked

Adobe has dozens of products spanning Creative Cloud, Experience Cloud, and Document Cloud. Tell me about a time you had to get alignment from engineers or PMs outside your immediate team to ship something. What made it hard and how did you get everyone moving in the same direction?

Sample answer outline

Adobe values 'be genuine' and collective ownership. A strong answer shows the candidate actively sought out the other team's constraints rather than dictating requirements, used written async communication to build shared understanding, and resolved a real disagreement by finding the option that worked for both teams. Bonus points for showing awareness that cross-product dependencies at Adobe often span different release trains and require careful API versioning.

Expect these follow-ups

• How did you handle a situation where the other team's priority conflicted with yours?
• What artifacts did you produce to make the alignment durable past the initial conversation?

As asked

Adobe ships Creative Cloud updates on a regular cadence to tens of millions of users. Tell me about a time you had to ship something important but the requirements or priorities kept shifting mid-development. How did you handle it and what did you do to protect the quality of the final output?

Sample answer outline

A strong answer shows the candidate proactively narrowed scope to the highest-confidence requirements rather than waiting for perfect clarity, maintained a list of deferred decisions with explicit reversibility, and communicated change impact in cost terms to stakeholders so they could make informed calls. Adobe interviewers want to see resilience under ambiguity paired with disciplined execution, not just adaptability.

Expect these follow-ups

• What signals do you use to decide when to push back on a scope change versus absorb it?
• How did you keep the team morale intact while the target was moving?

As asked

Start us off: tell me about your background, and then tell me specifically why you want to work at Adobe versus another big tech company.

Sample answer outline

A strong answer delivers a 60-second arc: current role and key impact, what the candidate is optimizing for next, and a specific connection to Adobe's products or mission (not generic 'creative platform' fluff but something like 'I use Lightroom professionally and wanted to work on the rendering pipeline I depend on daily' or 'Adobe's Content Credentials initiative on AI provenance directly addresses something I have researched'). Adobe interviewers look for candidates who have a genuine relationship with the products, not those who applied to five big tech companies and Adobe happened to respond.

Expect these follow-ups

• Which Adobe product do you use most and what is one thing you would change about it?
• Where do you think Adobe is most vulnerable competitively and what would you do about it?

As asked

Airbnb's mission is to create a world where anyone can belong anywhere. Tell me about a specific time you created a sense of belonging or inclusion for someone, either a teammate, a user, or a customer.

Sample answer outline

A strong answer ties the candidate's specific action to an outcome the other person visibly experienced, not just to good intentions. It names the concrete thing the candidate changed, built, or said, and reflects on what belonging actually meant in that context. Bonus points for connecting it to product decisions that affected many people at once.

Expect these follow-ups

• How do you scale that kind of inclusion when you can't do it one-on-one?
• Have you ever failed to create belonging for someone and what did you learn?

As asked

At Airbnb, hosts and guests often have opposing needs. Give me an example from your own work where two stakeholder groups wanted opposite things. How did you decide what to build, and how did you communicate it to both sides?

Sample answer outline

Strong answers show the candidate explicitly mapped each group's underlying need (not just their stated want), found a solution that addressed the most critical need for each side, and communicated the tradeoff honestly rather than pretending both sides got everything. They should mention what signal they used to validate the decision afterward.

Expect these follow-ups

• What would you have done if the data pointed one way but your intuition pointed the other?
• How do you handle a stakeholder who keeps re-opening a decision you already made?

As asked

Describe a time you strongly believed in a technical approach that your team or manager pushed back on. How did you make your case, and what happened?

Sample answer outline

The best answers show the candidate prepared a concrete argument (data, prototype, spike) rather than just repeating the same opinion louder, adapted when they got new information, and either won the team over with evidence or accepted the final decision graciously. Airbnb values 'Champion the Mission' and 'Be a Host', so framing the disagreement as caring about the right outcome matters.

Expect these follow-ups

• At what point do you escalate versus accept the team's decision?
• Has there been a time you championed something and were wrong? What did you do?

As asked

Airbnb engineers work across host, guest, trust, and payments teams that each have their own roadmap. Tell me about a time you had to get engineers or teams you do not manage to prioritize work that was important to your project. What did you do, and what would you do differently?

Sample answer outline

Strong answers show the candidate mapped who had what incentive, found the overlap between their need and the other team's goals, and created a shared artifact (doc, prototype, metric) that made the case concrete. They should show they followed through rather than assuming alignment after the first conversation, and reflect honestly on what slipped.

Expect these follow-ups

• What do you do when the other team agrees in the room but then deprioritizes your ask a week later?
• How do you build the kind of credibility where teams trust your prioritization judgment?

As asked

Airbnb's reliability bar is high because a booking failure can ruin a trip for a guest and a host. Tell me about the most serious production incident you have been responsible for. Walk me through what happened, how you diagnosed it, how you communicated, and what you changed afterward.

Sample answer outline

Strong answers show calm diagnostic methodology (metrics first, logs second, recent deploys third), honest communication under pressure (stakeholders updated early even without answers), a clear fix vs. mitigation distinction, and a genuine postmortem with systemic changes rather than just blame. Candidates who have never had a serious incident should be able to describe a near-miss and what they did to prevent it.

Expect these follow-ups

• How did you communicate with non-technical stakeholders during the outage?
• What monitoring or alerting did you add afterward to catch this class of failure earlier?

As asked

Airbnb interviews heavily on self-awareness and growth mindset. Tell me about a significant piece of critical feedback you received from a manager or peer. What was the feedback, how did you react to it, and what specifically changed in how you work?

Sample answer outline

Strong answers name the specific feedback clearly (not vaguely), describe the initial emotional reaction honestly, show that the candidate investigated whether the feedback was accurate, and demonstrate a concrete behavioral change that stuck. Airbnb interviews heavily on growth mindset and self-awareness, so candidates who deflect blame or say the feedback was wrong without reflection score poorly.

Expect these follow-ups

• How do you actively seek out feedback rather than waiting for it?
• Have you ever received feedback you disagree with? How did you handle it?

As asked

Tell me about a time you went far beyond what was expected to deliver something for a customer or end user. What was the situation, what did you do, and how did it turn out?

Sample answer outline

A strong answer opens with a concrete situation where the customer need was clear but the path to meeting it was not obvious or easy. The candidate should show they took ownership without being asked, describe the specific actions they took that went beyond the standard scope, and close with a measurable or observable outcome. Bonus points for acknowledging friction or cost to themselves and choosing the customer anyway.

Expect these follow-ups

• How did you know what the customer actually needed versus what they asked for?
• What would you do differently now?

As asked

Describe a situation where you saw a problem that was outside your direct responsibility. What made you step in, what did you do, and what happened?

Sample answer outline

Strong answers show the candidate noticed a gap that others were ignoring or deferring, made a conscious decision to own it anyway, and drove it to resolution without waiting for permission. The best answers include why the problem mattered to the business or the customer, not just to the candidate personally. Interviewers look for evidence of follow-through, not just flagging the issue.

Expect these follow-ups

• Did anyone push back on you getting involved? How did you handle that?
• Would you do the same thing again, or would you escalate instead?

As asked

Tell me about a time you came up with a creative or simpler solution to a problem. Walk me through how you identified the problem, what you considered, and how you decided on your approach.

Sample answer outline

A strong answer shows the candidate did not just follow the existing playbook but actively challenged assumptions about how a problem should be solved. The solution should be noticeably simpler or more elegant than the obvious path, and the candidate should explain their reasoning, not just the outcome. Quantifying the impact (time saved, complexity removed, error rate reduced) makes the answer land better.

Expect these follow-ups

• How did you convince others the simpler approach was safe?
• What risks did you accept by going with a non-standard solution?

As asked

Tell me about yourself and why you want to work at AMD specifically. What draws you to what we do here?

Sample answer outline

A strong answer ties the candidate's background to AMD's core business areas: CPUs (EPYC, Ryzen), GPUs (Radeon, Instinct), or the ROCm software stack. It names a specific AMD product line or technology the candidate has used or admired, shows awareness of AMD's competitive positioning against Intel and NVIDIA, and connects the candidate's skills to a real team need rather than offering a generic answer about 'innovation'.

Expect these follow-ups

• What AMD product have you used or worked with most recently?
• How do you stay current with developments in the semiconductor or GPU compute space?

As asked

Tell me about a time you had a serious disagreement with a colleague or cross-functional partner. What was the disagreement about, how did you handle it, and what was the outcome?

Sample answer outline

AMD values direct, fact-based communication. A strong answer names the specific technical or scope disagreement, explains the candidate's approach to separating the idea from the person, and shows they sought data or a third party to resolve it rather than escalating or avoiding. The outcome should include what changed and what they learned about working with that person.

Expect these follow-ups

• Would you handle that differently today?
• How do you disagree with someone who has more seniority than you?

As asked

Describe a project where the requirements were unclear or kept changing. How did you move forward and still deliver something useful?

Sample answer outline

A strong answer shows proactive clarification: the candidate identified the ambiguity early, went to the right stakeholders with specific questions (not an open-ended 'what do you want'), documented assumptions, and delivered an incremental result. AMD expects engineers to operate in hardware and software spaces where spec changes are common, so the answer should show comfort with iteration and versioning rather than blocking on a perfect spec.

Expect these follow-ups

• What assumptions did you explicitly document?
• How did you communicate scope changes to stakeholders who expected the original plan?

As asked

Tell me about a project or decision you made that did not turn out the way you intended. What went wrong, and what did you take away from it?

Sample answer outline

AMD interviewers look for genuine self-awareness, not polished spin. A strong answer names the real mistake (a wrong architecture call, a missed deadline, a misread dependency), explains what the candidate missed and why, and describes a concrete change they made afterward. The candidate should own the failure without blaming others, while still showing they can analyze what external factors were at play.

Expect these follow-ups

• How would you catch that class of problem earlier next time?
• Did you share what you learned with the broader team?

As asked

Anthropic's mission is the responsible development of AI for the long-term benefit of humanity. In practice, that means building increasingly capable systems while trying to make them safer. How do you personally think about that tension, and how would it shape your day-to-day engineering decisions here?

Sample answer outline

A strong answer shows genuine engagement with the tension rather than dismissing it. The candidate should acknowledge that safety and capability are not always orthogonal and give a concrete example of where they have chosen a slower or more conservative path because the risk profile demanded it. They should tie this to Anthropic's stated position as a safety-focused lab that still ships products, showing they can operate in that nuance.

Expect these follow-ups

• Can you give me a specific example from your past work where you slowed down to reduce risk?
• How would you push back on a product decision you thought introduced unacceptable safety risk?

As asked

Anthropic expects engineers to have strong opinions and raise them clearly, but also to commit fully once a decision is made. Tell me about a time you had a strong technical or product disagreement with your team or manager. How did you raise the concern, and how did you handle it once a decision went against your view?

Sample answer outline

A strong answer shows the candidate raised the concern clearly and with evidence, not just as a complaint, listened to the counter-arguments, and then committed fully once the decision was made rather than sulking or undermining it. Bonus points for an example where they turned out to be wrong, demonstrating genuine humility. The story should show they can separate their ego from being right.

Expect these follow-ups

• What would it have taken for you to escalate rather than commit?
• Have you ever been in a situation where you committed but the outcome proved you were right all along, and how did you handle that?