</> MAANG.io

Foundations

The behavioral questions new grads and SDE I candidates are asked, from tell me about yourself to your first mistakes and disagreements. Every lesson also shows how the expected answer grows from SDE to Principal.

0 of 36 solved 0%

Tell Me About Someone Whose Working Style Was Very Different From Yours

The question: "Describe a situation where you found it difficult to work with someone who had a very different working style or background. How did you handle this challenge and what was the outcome?"

Also asked as: "Tell me about a colleague you found hard to work with, even though you agreed on what needed doing." · "Who's the person at work you've found most unlike you?" · "Tell me about someone whose way of working drove you up the wall."

Who's asking: an Engineering Director or Senior Engineering Manager, in a behavioral round.

Executive Summary: The director is deciding whether you need people to work like you, and whether you'd make their team narrower or wider. The strongest signal is how you describe the other person: what you saw them do, never what kind of person they are. What changes with level is what the difference makes you change: one teammate, your team, several teams, then a very different executive and an org.

What the director is really asking

The director is answering three questions:

  • "Do they need people to be like them?" Everyone finds someone irritating. What do you do with it?
  • "Will they make my team narrower or wider?" Someone who only works well with people like them shapes a team into copies, through who gets heard and who gets hired. It matters most at Principal, where one person's way of working sets what an org rewards.
  • "Can they see their own style as a style?" If you come across as normal and the other person as different, the director has heard how you'd describe the next person.

This question is about how someone works: pace, writing or talking, planning or building. If the two of you fought over what to do, that's a conflict story, and the Conflict & Influence lessons cover it.

The word "background" needs care. Never generalise about anyone's culture, nationality, age, gender or neurotype. Say what you saw someone do, not what kind of person they are. "She came from a big enterprise, so she loved process" is a stereotype, even said kindly. "She wanted a written spec before any code, and she told me about the outage behind that" is an observation. Work history is fine as a fact ("he'd spent ten years on firmware"), but it doesn't explain him. If a practical gap really mattered, such as a twelve-hour time difference, name the gap and what you changed. Your own background is yours to mention or not, including when you were the one treated as different; the story still runs on what each of you did. If a colleague told you something private, describe what you changed, not why. If the story is an assumption you made and got wrong, tell it as your assumption, and what showed you.

It maps loosely to Amazon's "Earn Trust"; treat that as approximate. Three ladder dimensions do most of the work: how you treat people, conflict (the low-heat kind) and, from Senior up, people.

Level fit at a glance

SDE Senior SDE Staff Principal
Asked at this level? Core Common Common Rare
Story scope they expect One colleague, one piece of work Someone on your team or project, and how the team works A peer on another team, on work across teams A very different executive, on a multi-year bet across an org
The bar in one line Name both ways of working, say what it costs to them directly, and agree how you'll work with the difference still there On work you own, get the best from someone unlike you, often by changing how the team works, at a stated cost Keep your judgment with someone very unlike you, and leave several teams working differently, through managers you don't run Reach an executive unlike you, keep your technical calls, and price it in business terms
Instant down-level "They were difficult, so I worked around them", or any stereotype "I got him to work the way the team does" A clash inside your own team, or nothing changed beyond the two of you One colleague you learned to work with, and nothing that reached the org

At Senior and Staff, other questions carry more of the signal. At Principal, directors usually ask the executive version.

Quick test: would they read your description and say "yes, that's what I do"? Good. Would the same sentence fit anyone from the same group? That's a stereotype: cut it.

SDE: say it to them, then get the work done

What meets the bar

  • You describe the difference as what each of you did, yours included, with no label on them.
  • You dealt with them directly. If it took too long, you can say what the delay cost.
  • You found out why they work that way, from them or from what you saw.
  • You got the work done with the difference still there, and there's a number.

Model answer

"We were building self-scheduling at a recruiting software company, so candidates could pick their own interview slot. Two of us had the feature and six weeks. I plan, so I wrote eleven pages before I touched anything. The engineer I was paired with builds first. She'd have a rough prototype by lunch, and she changed the interface between her code and mine almost every morning.

We agreed on what to build. How she got there drove me up the wall, and I handled it badly. I told two teammates she didn't plan, then told our lead as a heads-up. Our lead asked if I'd told her, and I changed the subject. One of those teammates mentioned it to her, and she came over. 'You've told three people I don't plan. You haven't told me.'

I didn't defend it. I told her what I should have said two weeks earlier: every interface change meant redoing my side, about four days so far. She hadn't known. She told me that with calendars she can't tell what breaks until she clicks through it, and she'd shown a prototype to a customer's recruiter. Panel interviews, a footnote in my plan, were about four in ten of their bookings.

We split it. She kept prototyping on her branch and changed the shared interface only on Mondays and Thursdays. I cut my plan to one page of rules that had to hold, and she tested against it. That page caught a double-booking bug in her next prototype.

We shipped in seven weeks, one late, because our lead checked two more customers and agreed to add panels. In the first month, about 3,400 interviews were booked that way with two double bookings from calendar lag, and the median time from invite to booking, across all interviews, fell from 2.6 days to 14 hours.

If how someone works bothers me, they hear it first. Her half-broken links at five o'clock still grate. I open them anyway, because that's usually where I find out what my plan got wrong."

Why this lands at SDE

  • "I told her what I should have said two weeks earlier": the level beat. A peer tells a peer, on one feature, with a specific cost.
  • "I plan, so I wrote eleven pages": the candidate's own style, named as one.
  • "That page caught a double-booking bug" beside "a footnote in my plan": each way of working caught what the other missed, so nobody's vindicated.

Follow-ups to expect

  • "What would she say was hard about working with you?": the most dangerous one, because it catches any story where only the other person has a style → you complained first, and defended plans that had gone stale.
  • "How did you decide when to involve your lead?": tests judgment → "I went too early and for the wrong reason, to complain. I'd go if we'd talked and were still stuck."
  • "What do you mean by a different background?": tests for the stereotype → "I mean how she works. I know what she does and the reason she gave me." Then stop.
  • "What did you learn that you still use?": tests whether it stuck → a later example where nobody had to come to you.

Red flags

  • ❌ The stereotype. "People from that culture don't push back", "younger engineers just hack things together." You've told the director how you'd talk about their team. No-hire at any level.
  • ❌ "In the end she saw that planning matters." A conversion story, with you as the winner.

Senior SDE: a team with room for more than one way of working

What meets the bar

  • The person is on your team or a project you own, and you can say what the difference was costing the work, not only you.
  • You changed how you lead them, or a team practice (reviews, design docs, on-call), with the people it affects, and you can say what it cost.
  • Someone does better work because of it, and you can name what they did.

Model answer

"At a cloud-backup service, I led a six-person team rebuilding the restore path. I work out loud. A peer of mine, who owned the deduplication index, works in writing. His design comments were the team's best, and he turned down nearly every meeting. So I wrote a Tuesday decision review into our team agreement, attendance expected, and called it the process.

He came twice, then went back to the doc. In month three the room changed the chunk size. His comment from the night before showed why that would break the index, and nobody had read it. Three weeks of rework. I wrote in his peer feedback that he needed to be more present. Our manager sent it back and asked what his comment had said.

That week a junior engineer told me they'd barely spoken on Tuesdays in three months. I counted at the next review: three of us did nearly all the talking. I'd taken how I like to think and made it a rule for six people.

I told him that, and withdrew the rule. He drafted the replacement: proposals in writing 48 hours ahead, comments count as attending. The team agreed to a one-quarter trial, because it had an end date. Six weeks in, a retry question ran eleven days in comments and took ten minutes on a call, so I pushed for one addition: any thread stuck for two days gets a 15-minute call. He disliked that, and agreed because he'd sat through those eleven days.

Decisions got slower, from about two days to five, and they've stayed there. Our PM still dislikes it. Reopened decisions went from nine a quarter to two. I gave that junior engineer the resumable-restore design, their first, and reviewed it in the doc. The rebuild itself took failed restores from 2.3 percent to 0.6.

A rule that suits me is the one I check with whoever talks least. He won't take a meeting he can answer in a comment, and I talk things through. So I call someone for ten minutes, write it down, and he takes it apart in the doc."

Why this lands at Senior SDE

  • "I'd taken how I like to think and made it a rule for six people": the level beat. Only someone who sets how a team works can say this, inside one team.
  • "any thread stuck for two days gets a 15-minute call": the spine. Writing has a cost too, and the candidate shows it.
  • "Decisions got slower, from about two days to five, and they've stayed there": a cost still running, and someone still unhappy.

Follow-ups to expect

  • "Why do you think he works that way?": tests for guessing → "He told me reasoning gets lost in a room, and I saw that happen. Beyond that it's not mine to guess."
  • "Who did you grow on this?": don't claim him, because he's a peer → the junior engineer: what you handed them, how you reviewed it, and how their next design went.
  • "How did you get the team aligned?": two of the three talkers liked Tuesdays → the end date, the reopened count, and who misses the room.
  • "What did you trade off to hit the date?": tests judgment → the three weeks were rework, not a trade. The trade is slower decisions and a PM who objects.

Red flags

  • ❌ The stereotype, as a diagnosis. "I think he's probably on the spectrum." You don't know, and it isn't yours to say.
  • ❌ "I was the lead, so I made him come." Conflict resolved by authority.

Quick check before moving on:

Staff: work across the difference and keep your judgment

What meets the bar

  • The person is a peer on another team, on work across teams, and you manage none of them.
  • You changed how you worked with them and kept your judgment: you said what you saw, in a form they could use.
  • Managers you don't run agreed to something because of you, and you can say why each one moved.
  • You say "I" for the framing and alignment, credit the teams for building, and put a number and a running cost on the result.

Model answer

"Banned harassers kept coming back on our dating app, because four teams learned of a ban at different times. I pulled the data: 23 percent of harassment reports involved an account already actioned elsewhere. I showed each of four managers their own slice, and they committed people to one shared signal. I led it, managing none of them.

The staff engineer running enforcement wanted the same design. I decide on my feet. He writes forty pages and checks every failure, because a wrong suspension locks out a real person. In month two I settled a question in a hallway, and he found a case it broke. I overcorrected: I stopped calling him and put everything in comments.

In month five I worried one signal could let a group mass-report someone off the app. I had no data, so I left one comment on page 31. He replied asking what I'd seen. I had nothing to show and let it drop. I ran the review that cut the abuse section, alerting included, to hold the date. He argued against it, my date won, and I never raised my worry.

Five weeks after launch, a group did that: about 1,900 accounts wrongly suspended over nine days before anyone saw it. His rollback design, which I'd thought was overkill, had the signal off in 40 minutes. It stayed off seven weeks. He told me he was slow, not fragile, and I should have called.

I went to the four managers with him and proposed a split: his team signs off anything that can suspend an account, and I own the shared dates and a list of unproven worries. Of the first dozen, two were real, and the rest cost people days. The split adds two weeks to those launches. The messaging manager agreed last, because those seven weeks had put reports back on her team. Six months after the teams brought it back with safeguards, that 23 percent was 9, signal and safeguards together.

Speaking up might not have saved that section. I had a hunch and we had a date. Nobody got to weigh it, and those people spent up to two weeks locked out. When I've gone polite with someone, I phone that day with what I've got."

Why this lands at Staff

  • "I went to the four managers with him and proposed a split": the level beat. Authority over none, and both ways of working given a job.
  • "He argued against it, my date won, and I never raised my worry": the miss sits with the candidate, and his care stays intact.
  • "His rollback design, which I'd thought was overkill": his way of working limited the damage from the candidate's silence.
  • "Of the first dozen, two were real": most hunches come to nothing, so one that landed proves little.

Follow-ups to expect

  • "So you saw the risk and it happened. Why isn't this a story about you being right?": tests for hidden self-praise → "One hunch of mine landed, and I can't tell you in advance which ones will: most since have been nothing. The review might have cut it anyway, the nine days came from a cut I ran, and his design limited the damage."
  • "How did you get the other managers to agree?": tests influence → enforcement wanted it because appeals landed on that team. Photos and matching took the two weeks because seven weeks patching their surfaces had cost more.
  • "What did you do for the people you locked out?": tests how you treat people → reinstatement, the notice sent, how many came back. Don't guess who they were.
  • "Why was this your problem, and what would have happened without you?": tests ownership → you found the 23 percent; without it, teams keep fixing their own surface. Say what you stopped doing to take it on.

Red flags

  • ❌ "He was too slow, so I worked around him." Contempt, and his reason is missing.
  • ❌ "I learned to be patient." Nothing changed beyond the two of you.

Principal: bring along someone who will never work like you

What meets the bar

  • Why it's rare: directors with limited time usually get this signal from the executive version ("Tell me about a senior executive who worked very differently from you"), though it's asked plainly too, often word for word in values-based banks. They're probing whether your way of working makes an org narrower or wider.
  • Keep the scope honest: one executive and one bet is the right size.
  • You changed how you reach them and kept the technical calls that are yours.
  • The cost is in business terms, and something in the org works differently.

Model answer

"I set technical direction for an elevator maker's connected maintenance, a three-year, $40 million bet moving 90,000 elevators from fixed visits to sensor-driven ones. It pays only if the field operations VP changes how her mechanics are dispatched. She decides in short conversations and site visits. I write long analyses. I sent her 30 pages, then more, and read her not replying as not caring about evidence. Seven months went, with no pilot.

Her chief of staff said she'd stopped at page two, so I asked to join her visits. In the third machine room, a mechanic showed us door wear our model had scored healthy. Older controllers, about 35 percent of the fleet, sample too coarsely to see it, so I ruled that on them the model can add visits but never cancel one, at about $7 million a year in planned savings. That got us her first pilot region.

Two years in, three of nine regions are live, about a year behind plan, callbacks are down 17 percent, and my model teams spend two days a quarter with mechanics. She decides the next regions and when a mechanic overrules the model. Which controllers we trust is my call. When we disagree, we argue it in a machine room, and I've lost two of the last five. Those memos were for me. I ask people how they decide first."

Why this lands at Principal

  • "I ruled that on them the model can add visits but never cancel one": the level beat. An engineer's call inside a business bet, priced at $7 million a year, and it earned the pilot.
  • "read her not replying as not caring about evidence": the misreading, owned, with no label on her.
  • "I've lost two of the last five": she didn't convert, the candidate didn't fold, and each knows whose calls are whose.

Follow-ups to expect

  • "How did you bring her along?": the Principal probe → you went to how she decides. Say what she never agreed to.
  • "How did this change the org's roadmap, and what were the second-order effects?": tests business judgment → pilot order set by her, $7 million a year given up.
  • "What mechanism outlived your involvement?": the Principal probe → the days with mechanics: who protects them, and what they miss.

Red flags

  • ❌ The stereotype, by discipline. "Ops people don't care about data." A whole function dismissed by someone setting direction for it.
  • ❌ "She isn't data-driven." Her site visits were evidence.

Quick check before moving on:

One story, four altitudes

SDE Senior SDE Staff Principal
Situation One feature, two opposite paces My team's restore rebuild, and a peer who works in writing One signal across four teams, and a peer who checks everything A three-year bet, and a VP who decides on site
Your role Peer on the same feature Tech lead of a six-person team Staff engineer across four teams, managing none Set technical direction; her mechanics aren't mine
The key move Told her the cost; split how we worked Withdrew my rule; he drafted the replacement Four managers agreed a split giving both styles a job Joined her visits; ruled the model can't cancel on old controllers
Result Booking 2.6 days to 14 hours; a week late Reopened decisions nine to two; decisions slower for good 23% to 9%; 1,900 wrongly suspended; two weeks per launch Callbacks down 17%; $7M a year given up; a year behind
Reflection They hear it first Check rules that suit me with whoever talks least Gone polite? Phone them that day Ask how people decide first

Draft your answer

Step 1: Pick the right story

Test each story at your target level:

  • SDE: One colleague on one piece of work, dealt with directly (or you can own that you didn't), and the work got done?
  • Senior SDE: Someone on your team or project, a change in how the team works or how you led them, and you can name who did better and what it cost?
  • Staff: A peer on another team, at least two teams changed what they did because of you, and managers you don't run agreed to something?
  • Principal: A very different executive on an org-level bet, you changed how you reached them and kept your calls, and something in the org works differently?

Then check all of these:

  • It's from the last two or three years, and you were central to it.
  • You agreed on what to do. If you fought over the decision, use a conflict story instead.
  • Nothing depends on who they are. Take out any mention of their culture, nationality, age, gender or neurotype. The story still stands.
  • You can name your own style as a style, and say a number for the work.

If you're a new grad. A research lab, a club project or a course team counts if you agreed on the goal but worked in very different ways, and a real deadline made that matter. The director expects one colleague and one piece of work, but still wants your own style named, what you changed and what got done: "My lab partner planned every experiment on paper first; I'd usually written three scripts before she finished her first page."

Aiming a level above your current title? A Senior aiming at Staff can tell the cross-team version only if managers you don't run really changed something. If you have a practice on your own team, tell it at that altitude and show you see the next one: "If I did it now, I'd take it to the two neighbouring teams, because their reviews shut out whoever doesn't talk in the room." A Staff aiming at Principal should bring an executive story, not stretch this one.

Step 2: Fill the skeleton

SITUATION      (15s) — The work, your scope and what was at stake: ______
THE DIFFERENCE (15s) — What each of you did, yours included. No labels, and
                       nothing about who they are: ______
THEIR REASON   (10s) — What they told you, or what you saw: ______
YOUR MISTAKE   (15s) — What you got wrong, stated as a decision. Include one
                       thing you still held to: ______
ACTIONS        (35s) — 2–3 moves, each "I …, because …". What they did
                       themselves, and why they went along: ______
LEVEL BEAT (inside ACTIONS) — the line only your level could say.
                       SDE: what you told them directly, and what you agreed.
                       Senior: what you changed for your team, and its cost.
                       Staff: what managers you don't run agreed to, and why.
                       Principal: how you reached the executive, the technical
                       call you kept, and its business cost.
RESULT         (15s) — One number at your level's scale, and what it cost: ______
REFLECTION     (20s) — The difference that's still there, how you work with
                       it, and what you do differently now: ______

Aim for about two minutes, two and a half at most, with a 30-second cut ready.

Step 3: Calibrate it

If your answer says… It reads as… Fix
"She came from a big enterprise, so she loved process", or anything about who they are The stereotype: a red flag at any level What you saw them do, and the reason they gave you
"She's just difficult" Contempt Two things they did, described so they'd agree
"I adapted completely, and it went great" No judgment of your own, and too clean One thing you held to, and what adapting cost
A clash inside your own team, told at Staff Senior Another team, and managers who changed something
One colleague you learned to work with, told at Principal Staff or below The executive you brought along, and what changed in the org

Step 4: Rehearse the follow-ups

Prepare these four, and say each answer out loud once:

  1. "What would they say was hard about working with you?" The most dangerous one. Say something true about how you work, not a strength in disguise.
  2. "What do you mean by a different background?" The stereotype trap. Say what they did, and at most their work history.
  3. "What's still hard about working with them?" Something that still bothers you, and how you work anyway.
  4. "Did you tell them directly? When?" The honest timing, and what delay cost.

Common mistakes

  • Diagnosing someone, even kindly. Use what they did and the reason they gave you, or say you don't know.
  • Telling a conversion. "They came round to my way" means you needed them to be like you. Say what each of you still does differently.

Key takeaways

  • It tests whether you need people to work like you, and whether you'd make a team narrower or wider.
  • Say what you saw them do, never what kind of person they are.
  • You don't need them to convert, or to become friends.

Test yourself on this question's key ideas:

Sign in to MAANG.io

Use your Google or Microsoft account — no password to remember.

Continue with Google Continue with Microsoft

Please accept the terms above to continue.