To answer “tell me about a time you worked on a cross-functional team,” describe a project where people from different functions, such as engineering, sales, finance, operations or legal, had to deliver one result, and name the tension between their goals. Then show what you did to line them up: a shared goal, clear owners and decision rights, a common vocabulary and a regular check-in. End with the outcome and what each function got out of it, because interviewers are testing collaboration and influence without authority.
Below: what the question tests, how it differs from similar questions, a STAR structure with timings, four sample answers for different levels and fields, the mistakes to avoid, the follow-up questions to expect and a ten-minute practice routine.
What “tell me about a time you worked on a cross-functional team” really tests
Most work that matters crosses team lines, and each function is measured on something different. The interviewer is checking whether you can:
- Understand other functions' incentives. Sales is measured on bookings, finance on control, engineering on reliability; you can say what each side needed.
- Translate. You turned one team's language into terms the other could act on.
- Create clarity. You made it obvious who owned what and who made which decision.
- Influence without authority. You moved people who didn't report to you.
- Share credit. The result belongs to the group, and you say so.
Public frameworks describe the same skill. The UK Civil Service Success Profiles list “encourage joined up team work within your own team and across other groups” among examples of the Working Together behaviour at the Higher and Senior Executive Officer grades (GOV.UK guidance updated 29 January 2025, checked November 16, 2026). Google's re:Work guide to team effectiveness, originally published in 2015, lists structure and clarity among the five dynamics of effective teams, describing it as people understanding what their job requires, how to meet those expectations and what follows from their performance.
Common tensions between functions, and what resolves them
| Functions | Typical tension | What usually resolves it |
|---|---|---|
| Sales and engineering | A date promised to a customer vs. the scope engineering can deliver | A scope cut agreed in writing, with the customer told early |
| Finance and marketing | Spending controls vs. growth targets | A pilot budget with a metric that unlocks the rest |
| Operations and product | Stability vs. change | A phased rollout with a way back |
| Legal or compliance and the business | Review time vs. speed | Standard terms for most cases, early review for the exceptions |
| Customer service and finance | Fast refunds vs. loss controls | A threshold below which agents can act on their own |
Keep this story separate from working on a diverse team, which is about differences in background, location or working style, and from persuading someone, which centers on changing one person's mind. When the other side is one senior person whose expectations you had to reset, your stakeholder expectations story fits better. For the wider set, see our teamwork interview questions.
A STAR structure with timings
| Step | What to say | Time |
|---|---|---|
| Situation | The goal and which functions were involved. | About 15 seconds |
| Task | Your role, and the tension between the functions' goals. | About 15 seconds |
| Action: align | The shared goal, and how you made owners and decision rights clear. | About 20 seconds |
| Action: run it | How you translated between teams, the check-in rhythm and the conflict you helped settle. | About 25 seconds |
| Result | The outcome, and what each function got out of it. | About 20 seconds |
Name each function and its goal in one short sentence; that's what shows you understood them. If you used a simple ownership grid, such as a RACI chart (responsible, accountable, consulted, informed), mention it in a phrase.
Four sample answers to “tell me about a time you worked on a cross-functional team”
These are example answers we wrote to show the structure at different levels and in different fields; they are not real candidates' stories. Swap in your own situation, and use only numbers you can back up if asked.
Entry-level (marketing coordinator): a product launch
“For a product launch, I coordinated marketing, design, sales and customer support, and nobody owned the full checklist. I built a shared launch tracker with an owner and a date for every item and ran a 15-minute check-in twice a week. In the second week I noticed support had no answers ready for the questions customers would ask, so I drafted a short FAQ and got the product manager to review it. We launched on the planned date, and the support lead told us ticket volume in launch week was lower than for the previous launch.”
Manager (operations manager): a faster refund process
“I led a project to speed up refunds across the warehouse, customer service and finance. Customer service wanted instant refunds; finance wanted every return inspected first. I got both leads in a room with three months of returns data, which showed that low-value orders were rarely a loss problem. We agreed to pilot instant refunds below a value threshold, with finance setting the threshold and reviewing results monthly. Refund complaints fell during the pilot, finance saw no rise in losses, and the rule became permanent.”
Technical (data engineer): one definition of an active customer
“Finance and sales operations each had a revenue dashboard, and their numbers disagreed every month because they defined an active customer differently. I was asked to build one dashboard for both. Rather than pick a side, I ran a one-hour workshop with both teams, showed exactly where the definitions diverged and wrote a short data dictionary that both leads signed off. The new dashboard became the one used in the monthly business review, and the arguments over whose number was right stopped.”
Customer-facing (account manager): a large client's onboarding
“A new enterprise client needed onboarding that involved our engineering, security and legal teams, and legal review was on track to delay signing by a month. I replaced three separate email threads with one joint call. We found that most of the client's requests matched our standard terms, so legal reviewed only the two clauses that didn't. The contract was signed two weeks ahead of the forecast, and I kept a monthly check-in with the same group through implementation.”
Mistakes to avoid
- “We all got along.” With no tension, there's no story.
- Taking credit for other functions' work. Say “I” for your part and name what the others delivered.
- Disparaging another function. “Legal always slows things down” tells the interviewer how you'll talk about their teams.
- A team that wasn't cross-functional. Five engineers on different services is a team project, not a cross-functional one.
- No decision rights. If nobody knew who decided, show how you fixed that.
Follow-up questions to expect
- “What did you do when two functions' priorities conflicted?” Describe the trade-off and who made the call.
- “Who made the final decisions?” Name the owner, even if it wasn't you.
- “What did you learn about how the other function works?” One specific insight is enough.
- “How did you handle someone from another team who didn't deliver?” Talk to them first, then their lead.
- “How did you keep everyone informed?” Give the rhythm and the channel.
A ten-minute practice routine
- Minutes 0–2: list projects where at least two other functions were involved, and pick the one with a real tension.
- Minutes 2–4: write one sentence per function: what it needed and how it was measured.
- Minutes 4–6: write how you made ownership clear and the one conflict you helped settle.
- Minutes 6–8: say it aloud in about two minutes, and check that you credited other teams by function.
- Minutes 8–10: answer “who made the final decisions?” aloud, then run the question in a mock interview.
Where CoPilot Interview fits
Cross-functional stories get tangled with too many teams; saying yours aloud shows where to trim. CoPilot Interview is an AI interview assistant whose free AI mock interview reads behavioral questions like this one aloud and scores each spoken answer out of 10, and whose browser demo has 145 practice questions in 10 tracks and scores typed answers out of 10, with no signup. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included; the desktop app runs on Windows 10 and 11 and macOS 12 or later. Practice is the use nobody objects to; if you ever consider live help in a real interview, follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What counts as a cross-functional team?
Any group where people from different functions, such as engineering, sales, finance, operations, legal or support, worked toward one result. It can be a formal project team or an informal group formed around one problem.
What if I'm entry-level?
A school project with students from different majors, an internship launch, or a volunteer event with fundraising, logistics and publicity roles all work.
How is this different from the diverse-team question?
Cross-functional is about different jobs and goals; diverse is about different backgrounds, locations or working styles. Prepare a story for each.
How long should the answer be?
About two minutes.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview