What Are Your Strengths?
The question: "What would you say are your strengths?"
Also asked as: "What's your greatest strength?" · "What would your peers say you're best at?" · "What would we notice about you in your first month?" · (Staff+) "What do you bring to a leadership team that others don't?"
Who's asking: an Engineering Director or Senior Engineering Manager, in a behavioral round.
Executive Summary: The director isn't collecting adjectives. They're checking whether you know what you're good at, can prove it with one story, and know what it costs you. The question is the same at every level. What changes is where the strength operates: in your code, your team's system, other teams' work, or how the organisation decides.
What the director is really asking
Underneath "what are your strengths?", a people manager is asking themselves three questions:
- "Where would I put this person first?" Your strength helps them decide what to hand you in your first month. One the role doesn't need ("greenfield prototypes", for a team running a ten-year-old platform) suggests you haven't thought about this role.
- "Is it real?" Anyone can say "I'm a strong communicator". The director believes it when a story shows you doing it, with a number and a moment where it didn't go to plan.
- "Do they know their own edges?" Every real strength has a shadow side. The engineer who digs deep also digs too long, and the one who aligns teams can slow a decision down. From Senior up, the cost is often the pull back to the strength that got you promoted. Naming that cost, and the habit that manages it, is the clearest self-awareness signal in the answer, and the part most candidates skip.
It doesn't map to one company value, although the cost beat is close to the "vocally self-critical" line in Amazon's Earn Trust principle (paraphrased). Two ladder dimensions do most of the work, scope (where the strength operates) and influence (whose work it changes), plus the self-awareness every director listens for. One answer gives the director a first read of where you operate; the final level comes from all the evidence in the round.
Level fit at a glance
| SDE | Senior SDE | Staff | Principal | |
|---|---|---|---|---|
| Asked at this level? | Core | Core | Core | Core |
| Story scope they expect | A bug or feature inside your team's system | A system your team owns, end to end | A problem across several teams that nobody owned | How the organisation makes a big technical bet |
| The bar in one line | One relevant strength, proven, with an honest cost | The strength improves a team outcome, and others can now do it too | The strength shows up in other teams' results | The strength changes how leaders decide, through a mechanism that outlasts you |
| Instant down-level | An adjective with no story | A strength about your own code | A strength shown only on your own team's project | A strength that's really about executing well |
It's foundational and often paired with weaknesses. It's Core at every level, though at Staff and Principal it often comes reworded ("what would your peers say you're best at?"), and the strength's altitude only confirms what your stories show. What it adds is the cost, a quick self-awareness read.
Every strong answer has the same shape, in about two minutes:
- Claim: one strength, in a sentence the director could repeat.
- Proof: one story that shows it, with a number and a moment where you changed course.
- Cost: the shadow side of that strength, a time it cost you, and the habit that manages it.
- At this level: how it shows up in your work now, and where you'd use it first here. From Senior up this carries the level beat: who else can do it now (Senior), which teams changed and what you stopped doing (Staff), or what runs without you (Principal).
Name one strength, not four. If asked for "strengths", plural, give one in full and a second in a sentence.
SDE: one strength, proven, with its cost
What meets the bar
- One specific strength a teammate could watch you use, not an adjective ("hard-working", "passionate").
- The proof is a task-level story you owned end to end, with a number.
- A course correction: something you got wrong, and who helped you see it.
- A real cost, managed by a habit that includes knowing when to ask for help.
Model answer
"I'd say my biggest strength is getting to the root of bugs that have gone quiet in the backlog because they don't reproduce. I'm patient with them, and methodical about narrowing them down.
The best example is from last year. I'm on the scheduling team at a company whose app restaurants and stores use to plan shifts for hourly staff. We had about forty support tickets a month saying a shift showed the wrong start time, and most were closed as 'can't reproduce'. I asked my lead if I could take it during a quiet sprint, and I lined the tickets up against our logs. The pattern was stores near a time-zone boundary, and shifts in the weeks around a daylight-saving change. We saved the start time with no zone attached, so the app read it in whatever zone the worker's phone was in, using today's offset instead of the one on the shift date.
My first fix only corrected how the time was displayed. In code review my lead asked what else read that field. The timesheet export did, so overnight shifts on the daylight-saving night would still have been logged an hour off. I reworked it to store each shift with the store's time zone and convert at display and export time, wrote a backfill for upcoming shifts, and added tests for the daylight-saving weeks. Wrong-time tickets went from about forty a month to two or three. Now, before I change a field, I trace everything that reads it.
Where it bites me is that I can go too deep. Early on I spent two full days on a bug in an internal report that hardly anyone used, and the feature I'd committed to that sprint slipped a week. Now I timebox: after half a day, I write up what I know and check with my lead whether it's worth more time. That's why I asked before taking those tickets.
On the team, I usually get the strange tickets, and I write up what I find so the next person doesn't start from zero. I'd want to bring that to your on-call rotation early."
Why this lands at SDE
- "Bugs that have gone quiet in the backlog because they don't reproduce": a specific, observable strength, and one an on-call team needs.
- "I asked my lead if I could take it": initiative inside the team's priorities, not around them.
- "My first fix only corrected how the time was displayed… Now, before I change a field, I trace everything that reads it": owns the miss, credits the reviewer, and names the habit it changed. That's coachability, a large part of what a director hires for at SDE.
- "The feature I'd committed to that sprint slipped a week": a cost with a real consequence, not a boast, and a timebox that answers "when do you ask for help?"
Follow-ups to expect
- "When did digging that deep cost you?": the most dangerous one, because it tests whether the cost is real → the two-day story and the slipped feature, plainly, then the timebox.
- "How did you take your lead's review comment?": tests coachability → what they said, and what you check now before asking for review.
- "What would your lead say your strength is?": tests self-awareness → if they'd name something different, say what and why.
- "How do you decide when to stop and ask for help?": tests escalation judgment → the timebox, and what you've ruled out when you ask.
Red flags
- ❌ "I'm a fast learner" or "I'm a team player", with no story behind it.
- ❌ A list of technologies ("I'm strong in Java and AWS"). That's a skill, not a strength.
- ❌ A story where the lead found the cause and you only implemented it.
Senior SDE: the strength makes the team better, not just you
What meets the bar
- The strength improves an outcome your team owns, measured at the system or product level.
- A trade-off you made with your PM or a partner team, and what it cost.
- Evidence that someone else on the team can now do it, because of you.
- A cost about how the strength affects the team, not just your own time.
Model answer
"My strength is making the systems I own calm to run, and these days, doing that through the team, not on my own.
For the last two years I've been tech lead of the identity team at a B2B software company: sign-in, single sign-on and sessions, with four other engineers. When I took it over, we had about twenty pages a month, and when I went through a quarter of them, roughly half needed no action at all. I deleted or retuned those alerts. Then I agreed a target with our PM: 99.9 percent of sign-in attempts succeed, not counting wrong passwords. The harder part was the trade-off. I proposed that if we burned through our error budget, the next sprint went to reliability instead of features. The PM agreed once I showed that sign-in failures were the top support complaint from our largest accounts. We used the rule twice in the first six months, and once it pushed a customer-requested admin feature back a month. I explained that to the account team myself.
I also got something wrong. For the first couple of months I fixed the worst problems myself, often in the evenings, because I knew the single sign-on code best. My manager pointed out that I'd become the only person who could debug it, which was the opposite of calm. So I stopped taking those fixes. I paired each on-call engineer through them instead, and we wrote the runbooks together.
A year on, pages are down to about six a month, and sign-in success went from about 99.5 to 99.9 percent. All four engineers have closed a single sign-on page without me, and the most junior one now runs our weekly on-call review.
The flip side is that when something's fragile, my instinct is still to fix it myself, tonight. I manage it with a simple rule: whoever is on call takes the fix, and I review it. Here, I'd start with a quarter of your on-call pages and see which ones need anyone at all."
Why this lands at Senior SDE
- "Making the systems I own calm to run… through the team, not on my own": a strength stated as a team outcome, not a personal skill. That's the Senior line.
- "The PM agreed once I showed that sign-in failures were the top support complaint": a trade-off won with evidence, with a real cost the candidate explained themselves.
- "My manager pointed out that I'd become the only person who could debug it": takes feedback about the pull back to the old strength, and changes how they work.
- "All four engineers have closed a single sign-on page without me": people growth you could check, next to a system result (pages, sign-in success).
Follow-ups to expect
- "How did your manager raise it when you'd become the bottleneck, and how did you take it?": the most dangerous one, because it tests coachability → what they said, and what you changed that week.
- "Who on the team is better at this than you now?": tests whether the growth is real → name the person and what they own.
- "What did those reliability sprints cost the PM, and how did you get them to agree?": tests trade-offs → the feature that slipped, and the data you showed.
Red flags
- ❌ "I write really clean code" or "I'm the best debugger on the team". Both are about you, not the team.
- ❌ Heroics as the proof: you fixed it on nights and weekends, alone.
- ❌ No trade-off, or no one else on the team got better.
Quick check before moving on:
Staff: the strength shows up in other teams' results
What meets the bar
- The strength operates across several teams, on a problem nobody owned.
- Other teams changed what they did, and the result is measured at the org level.
- You're clear about your part and credit the teams who built the fix.
- An honest cost about how you work at this altitude, often the pull back toward building it yourself.
Model answer
"My strength is making other teams faster: finding the problem underneath several teams' complaints, and framing it so the people who own the pieces can fix it.
The clearest example is our mobile release train. I'm a staff engineer in a consumer mobile org, with six feature teams shipping into one app and a small release team that owns the tooling. When I joined, about half the weekly releases slipped, and every team blamed a different cause. Nobody owned the process end to end.
I'll be honest about how I started. My instinct is still to build. Flaky UI tests were the loudest complaint, so I spent six weeks building a bot that quarantines them. It worked, and slips barely moved. When I went back through two quarters of slipped releases, about two thirds traced to unfinished features merged late without a flag. I had fixed the part I could fix with code.
So I changed approach. I wrote up the cost: each slip delayed everything on the train by about three days. I got the six tech leads to agree on the cause before anyone discussed fixes. The growth team pushed back hard, because creating a flag took a ticket and a day, and flags on everything would slow their experiments. That was a fair objection, so I changed the order. I made the case to the platform team's manager to make flags self-serve first, and their team built it. Once a flag took minutes, the growth team's manager signed up first. The feature teams moved unfinished work behind flags, and the release team took over my bot.
Over three quarters, on-time releases went from about half to around nine in ten, and the median time from merge to customers fell from roughly twelve days to six. I coached the release team's lead through running the cross-team review, and she now owns the process end to end. To make room, I stopped taking feature work.
My rule now: on a cross-team problem, I write the one-page cost and get agreement on the cause before I write any code. Here, the first thing I'd look for is the problem two or three of your teams describe differently."
Why this lands at Staff
- "Every team blamed a different cause. Nobody owned the process end to end": a cross-team problem the candidate found, not one they were handed.
- "I had fixed the part I could fix with code": the pull of the old strength, named precisely. Building got them promoted, and here it got in the way.
- "I made the case to the platform team's manager… and their team built it": influence without authority, credit to the builders, and an objection that changed the plan.
- "On-time releases went from about half to around nine in ten… she now owns the process end to end": an org-level result across six teams, and a leader grown to carry it.
Follow-ups to expect
- "Your instinct is to build. How would your manager know you're managing that?": the most dangerous one, because it tests whether the habit is real → a recent case where you agreed the cause first, and what you didn't build.
- "Why was this yours to take on, and what did you stop doing?": tests initiative and trade-offs → you saw the pattern across teams; name the work you dropped.
- "How does the growth team's manager talk about you now?": a people-manager probe → a working relationship, not a defeated opponent.
Red flags
- ❌ A strength shown by leading your own team's project, however big. That's Senior.
- ❌ Other teams adopted it because a director told them to.
- ❌ "I built the release system" when the teams did the work. Your part was the cause, the framing and the alignment.
Principal: the strength changes how the organisation decides
What meets the bar
- The strength is about how the organisation makes big technical bets, shown at CTO, VP or director level.
- The proof is a bet argued against a named alternative, in business terms (net revenue after build and running cost, what it ruled out).
- You own a wrong call inside the bet, and the mechanism you built because of it.
- The cost is the shadow side at org scale, and how you manage it.
Model answer
"My strength is helping a leadership team make big technical bets well: turning an argument about technology into a decision about risk and money, and then owning it.
I'm a principal engineer at a B2B software company of about three hundred engineers. About three years ago, European enterprise customers began requiring EU data residency, and roughly six million dollars a year of deals stalled. One camp wanted to re-architect the platform so every customer's data could be pinned to a region: about two years, with much of the roadmap frozen. I argued for a separate, self-contained copy of the stack in the EU, a cell, in about three quarters. The director leading the other camp and I wrote the comparison together, and I took it to the CTO and the head of sales as a business choice: the revenue each reached in year one, the roadmap each cost, and what each ruled out.
We chose the cell, knowing cross-region features would cost more later. The infrastructure and platform teams built it, about twenty engineers for three quarters, and it costs about a million a year to run. Against about four million a year of new contracts, that's roughly three million a year net, so it paid back in under two years. Some stalled deals had gone elsewhere by then.
I got part of it wrong. I underestimated the cost of operating two cells. For two quarters the EU cell lagged releases by weeks, and two EU customers raised it at renewal. That estimate was mine. I got engineering leadership to make 'shipped to every cell' our definition of released, and introduced a decision record for every bet that size: the alternative, the assumptions that would prove us wrong, and a six-month review. An architecture council I set up holds those reviews, and two staff engineers now chair it.
It has a downside: framing takes time. A director once told me I'd turned a two-week decision into a two-month one, and it had cost her team a planning cycle. Now teams make reversible decisions themselves, and only the hard-to-reverse few reach the council. Here, I'd start by learning which two or three decisions on your roadmap are hardest to reverse, and help frame those."
Why this lands at Principal
- "Turning an argument about technology into a decision about risk and money": a strength stated at the altitude where company decisions get made.
- "The director leading the other camp and I wrote the comparison together": a bet argued against a named alternative at exec level, bringing the other side along rather than beating it.
- "Roughly three million a year net, so it paid back in under two years": business terms net of build and running cost, plus what the bet gave up.
- "That estimate was mine… 'shipped to every cell' our definition of released": owns a direction-level miss with a customer cost, and turns it into a mechanism that two staff engineers now run.
Follow-ups to expect
- "When has your strength slowed the org down?": the most dangerous one, because it tests self-awareness at org scale → the two-month story, its cost, and how decisions are sorted now.
- "Who argued for the re-architecture, and what do they think now?": a people probe → their strongest argument, and what you took from it.
- "What does the council decide without you?": tests whether the mechanism is real → who runs it, and a recent call it made that you'd have made differently.
Red flags
- ❌ "I'm great at executing large migrations." That's a Staff strength.
- ❌ A revenue number with no cost behind it, or a bet with no alternative argued.
- ❌ No wrong call, or a strength that depends on you being in every room.
Quick check before moving on:
One story, four altitudes
| SDE | Senior SDE | Staff | Principal | |
|---|---|---|---|---|
| The strength | Root-causing bugs that don't reproduce | Making a system calm to run, through the team | Finding the shared cause across teams | Turning a technology fight into a business decision |
| Situation | About 40 wrong-shift-time tickets a month | About 20 pages a month, half not actionable | Half of weekly releases slipping, six teams | About $6M a year of EU deals stalled |
| Your role | Engineer on a shift-scheduling team | Tech lead of a five-person identity team | Staff engineer across six feature teams | Principal engineer, with the CTO and head of sales |
| The key move | Stored the shift's zone, not just a fixed display | Error budget agreed with the PM; paired on-call engineers through fixes | Got six tech leads to agree the cause; self-serve flags first | Argued a cell over a region-pinned re-architecture |
| Result | 40 → 2–3 tickets a month | Pages 20 → 6; sign-in success 99.5% → 99.9%; all four close SSO pages | On-time releases half → nine in ten; merge to customers 12 → 6 days | About $3M a year net; paid back in under two years |
| The cost, managed | Timebox half a day, then check with the lead | On-call takes the fix, I review | Agree the cause before writing code | Reversible decisions stay with the teams |
Read across a row: the strength moves from your code to how leaders decide, and the cost moves from your own time to the organisation's.
Draft your answer
Step 1: Pick the right strength and story
Start from the role: pick the strength this team needs most that you can prove. Unsure? List what people bring to you unasked, and what your last two reviews praised. The overlap with what this role needs is your answer. Then run your story through the test for your target level:
- SDE: Could a teammate name a time they watched you use this strength, and is there a number?
- Senior SDE: Did the strength improve something your team owns, and can someone else on the team now do it?
- Staff: Did at least two teams change what they did because of it?
- Principal: Did it change a decision at director or exec level, and does a mechanism apply it without you?
Then check that it passes all of these:
- It's relevant to this role, not just something you're proud of.
- The story is from the last 2–3 years, and you were central to it.
- It has a number you can defend three questions deep.
- You can name a real cost, a moment it bit you, and the habit you use now.
- Your manager would name the same strength, or you can explain why not.
If you're a new grad. Take the proof from somewhere another person watched you use the strength: a TA job, research lab, part-time job or internship counts if the story ends in a result you can point to. The director expects a smaller scope, not a thinner answer: one strength, one story and an honest cost with its habit. For example: "As a TA for intro systems, I was the one the other TAs sent their hardest segfaults to."
Aiming a level above your current title? Don't inflate the strength. Choose a story from the last 2–3 years where it already operated at the target level's scope (for Staff, a time two or more teams changed what they did). If you don't have one, name the strength at your real altitude and let your other stories carry the target level. That answer alone won't earn the level up, but a stretched one will cost you more under follow-ups.
Step 2: Fill the skeleton
CLAIM (10s) — One strength, in a sentence a director could repeat:
"My strength is ______, which means ______."
PROOF (60s) — One story: the scope → your moves ("I …, because …") →
the moment you changed course → the number.
COST (20s) — The shadow side of this strength, one time it cost you
or the team, and the habit you use now. At Senior and
up, your course correction and your cost can be the
same moment.
LEVEL BEAT (15s) — SDE: how teammates see it day to day (the tickets that
come to you, what you leave for the next person).
Senior: who else can do it now. Staff: which teams
changed, and what you stopped doing. Principal: the
mechanism that runs without you, and who leads it.
HERE (10s) — Where you'd use it first in this role. One concrete thing,
not "I'd hit the ground running".
Aim for about two minutes, and prepare a 30-second cut (claim, one sentence of proof with the number, cost) for "a quick one".
Keep it consistent with your weaknesses answer, but prepare that one separately: the cost beat isn't it.
Step 3: Calibrate it
| If your answer says… | It reads as… | Fix |
|---|---|---|
| "I'm a hard worker, a team player and a fast learner" | No evidence; below the bar at any level | One strength someone could watch you use, then one story |
| A Staff candidate: "I'm the strongest engineer on my team" | Senior | Show the strength working across teams, and the teams that changed |
| No cost, or "I just care too much" | Low self-awareness | The real shadow side, a time it cost you, and the habit you use now |
Step 4: Rehearse the follow-ups
Prepare these five, and say each answer out loud once:
- "When has that strength hurt you or your team?" The most dangerous one. A strong reply is a specific moment, what it cost, and the habit you use now.
- "What would your manager say your strength is?" A strong reply matches your claim, or explains the difference honestly.
- "Tell me more about your part in that." A strong reply goes one level deeper on your decision, and names who else did what.
- "Who on your team finds that strength hardest to work with?" A strong reply names a real person's view of it (by role), and what you adjusted for them.
- "How would we see that strength in your first ninety days?" A strong reply names one concrete thing in this team.
Common mistakes
- Claiming a strength your story doesn't show. If you say "leadership" and the story is about code you wrote, the director notices. Pick the strength the story proves.
- Naming the strength you wish you had. The director checks it against your other stories. Name the one people already bring you work for.
Key takeaways
- "What are your strengths?" tests self-awareness, evidence and relevance, not modesty or confidence.
- Same shape at every level: claim → proof → cost → at this level, in about two minutes.
- The level shows in where the strength operates: your code (SDE), your team's system (Senior), other teams' results (Staff), how the organisation decides (Principal).
- The cost beat is the clearest self-awareness signal: the shadow side, and the habit that manages it.
- The most common miss is a Staff candidate naming a Senior strength. Show it working across teams.
Test yourself on this question's key ideas: