0 day streak

BEHAVIORAL · COLLABORATION AND INCLUSION

Describe a project that needed several teams. How did you get them aligned?: sample answer

Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out.

Also asked as

  • Describe a decision you argued against but then had to carry out.
  • Tell me about a time you helped a teammate succeed.
  • Describe a project that needed several teams. How did you get them aligned?
  • Tell me about a time you made someone feel included who was being left out.
  • Describe how you built trust with a new team or stakeholder.

The short version: Show how you helped others succeed and made people feel they belonged.

Sample STAR answer

An invented example from typical software engineering work, about 250 words, around two minutes spoken. Use the structure, not the story: yours should be real.

Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other.

Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me.

Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part.

Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs.

Weak answer vs strong answer

Weak

"I am a great team player. On one project, I worked closely with other teams and we communicated a lot through meetings and messages, so the project was a success."

Why it scores low: It contains no conflict or difficulty, no specific action you took to align people, and no result. Communication alone is not a story; the interviewer wants to know what you changed.

Strong

A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show how you helped others succeed and made people feel they belonged.

How the story changes with level

SDE 1

At SDE 1, helping a teammate or working well with one partner team, such as agreeing an API with the frontend developer, is the right scope.

Senior and staff

At senior or staff level, you should be the person who made several teams move together without authority, and the result should change how teams collaborate afterwards.

SDE 1 interviews · Senior interviews · Staff interviews

Follow-up questions interviewers ask

  1. What did you do when a team did not deliver on time?Show you changed the plan to help them rather than blaming them.
  2. How did you handle disagreements about the API?Written proposals, a deadline for comments and a clear decision-maker.
  3. How did you make sure the remote team was included?Mention meeting times, written updates and giving them visible credit.
  4. What would you do differently next time?Name one honest improvement, such as involving the identity team earlier.

Amazon Leadership Principles that test this

Strive to be Earth's Best Employer · Tell me about a time you made your team a better place to work.

Work every day to make the workplace safer, fairer, more inclusive and more rewarding, and help the people around you grow.

Situation Our on-call rotation was wearing people down. Engineers were paged at night about twice a week, often for alerts that needed no action, and two teammates had said in a retrospective that they dreaded their on-call weeks.

Task I was not the manager, but I volunteered to lead an effort to make on-call sustainable within a quarter.

Action I collected every page from the past three months and sorted them: about 60 percent needed no human action. I deleted or downgraded those alerts with the agreement of each service owner. For the rest, I wrote runbooks so that any engineer, including new joiners, could handle the most common pages. I also noticed that teammates in another time zone were always given the night shifts, so I proposed a rotation that followed working hours across both locations, with handovers written in a shared document. Finally, I set up a short monthly review where whoever had been on call could raise what was painful.

Result Night pages dropped from about eight a month to under two. In the next team survey, satisfaction with on-call rose from the lowest score to above average, and two newer engineers joined the rotation confidently in their second month.

Tip: Show a concrete change to people's day-to-day experience, including those easy to overlook.

All 16 Amazon Leadership Principles with sample answers

Companies that test this

Prepare your own

Write your story in the story bank and tag it "Collaboration and inclusion"; it will show up against every company value that tests this theme.

Related: Disagreement and candor · Growing others · Big impact and long-term thinking · Integrity and trust

All behavioral themes · How the behavioral round is scored