How do you work in a team? Examples that convince

What the employer is actually testing

Swiss employers rarely state the purpose as plainly as armasuisse, the Federal Office for Defence Procurement, does on its public page about the job interview: the focus, it says, is on seeing whether your personality enriches the team, whether you are socially competent, and whether your professional skills match the profile. The order of that sentence is not accidental — the professional skills come last, because the dossier has already largely settled them.

The same page lists, among the questions you should prepare for, one that belongs exactly here: what was your most positive experience in a team, and why. That is the teamwork question in its friendliest form, and it is still an assessment. What you remember as positive says which kind of collaboration you are looking for, and whether it resembles the kind on offer.

It is worth knowing that in many Swiss organisations this question is not improvised — it sits on a form. The interview guide published by the personnel office of the canton of Solothurn is one such template: under "questions to the applicant" it lists administrative knowledge, key competencies, and, on a line of its own, teamwork. The column beside it tells the hiring manager the method to use: set out typical situations and requirements, and have the applicants describe their own behaviour in that situation.

So the expectation is settled before you answer. What is wanted is not your view of collaboration but an account of your behaviour. And because the same template also asks that both genders be represented on the selection panel, you are frequently facing several people — often including someone who would sit next to you afterwards.

One note for readers preparing in English: this federal employer publishes that guidance in German, French and Italian. Its English site carries the vacancies, the graduate and professional pages and the company values, but not the interview article. Where guidance exists only in a national language, that is usually a sign of who the page was written for — and reading it anyway is one of the cheaper advantages available to an applicant from abroad.

What Swiss adverts say about the team — and what they leave out

Most preparation fails on a simple gap: nobody knows which team they would be joining. We counted what an advert actually gives away. Among the adverts open with us — one per employer, apprenticeships and internships excluded — 32.1 per cent of English-language adverts describe a team as a place you would join. German-language adverts do so in 22.5 per cent of cases, French in 13.2, Italian in 7.3.

The demand runs the other way round. Asking for teamwork as a personal quality — "team player", "team spirit", "ability to work in a team" — appears in only 2.3 per cent of the English-language adverts, against 14.8 per cent of the German ones. English-language adverts in Switzerland sell the team; German-language adverts require the trait. If you read only the English part of the market and then interview in German, that difference is worth knowing before the question arrives.

What almost no advert gives you, in any language, is a fact. Of the adverts that mention a team at all, 15.3 per cent of the English ones attach an adjective — dynamic, motivated, collaborative, diverse — and well under one per cent name how many people are in it. Across the whole English-language stock, 0.3 per cent give a team size. Where a number does appear, it is often an advert for the person who would lead the team rather than join it.

The one thing English-language adverts do supply more often than the others is the reporting line: 6.7 per cent name who the role reports to, against 0.2 per cent of German-language adverts. That is a convention of international employers writing in English, not a Swiss one. Do not assume its absence from a German advert means anything; it is simply not how those adverts are written.

The half of the question people drop: independence

The most common incomplete answer is caused by something already written in the advert, just not where people look for it. Among the employers whose German-language adverts explicitly ask for teamwork, 47.2 per cent also ask for independent or self-responsible working in the same text, and 24.2 per cent put both demands in a single sentence. In the French-language adverts the pairing is tighter still: 51.9 per cent and 34.6 per cent.

That is not a contradiction. It is an accurate description of working life in the flat structures common in Swiss organisations: fit into the arrangement, and still decide, without asking upwards for every small thing. An answer that only offers adaptation — I listen, I balance people out, I contribute — covers one half and leaves the other side with a doubt they will often not voice.

English-language adverts ask for the trait too rarely for a rate to mean much, which is exactly why an English-speaking applicant can walk into this unprepared. The demand does not disappear when the advert is written in English; it is simply not spelled out.

In practice the fix is one extra sentence at the end of your example: what you decided on your own in that situation, and the point at which you stopped deciding on your own. That boundary is the real information. It shows judgement, and it is the part nobody can assert without a story behind it.

The shape of an answer that holds

A convincing answer has four parts and runs for about a minute. First, the placement: the size and make-up of the team, and your role in it. Second, the working method, in one sentence — how you coordinated, not how well you got on. Third, a friction: the point where something collided. Fourth, your action and its outcome, including the line between what you decided and what you handed over.

The second part is the one nearly everyone skips, and it carries more than it promises. "We got on well" is not a working method. "Twenty minutes on Monday morning, and after that everything ran through one shared list, with whoever picked something up putting their name against it" is one, and it can be questioned further. That is precisely what the Solothurn method is designed to elicit.

Choose the situation from the advert, not from memory. If it mentions cross-functional work or an interface, take an example with two departments and opposing interests. If it mentions customers, take one where the team had to speak to a client with one voice. If it says nothing about collaboration at all — which is the majority case — take the example with the most at stake, because that is where the follow-up questions have somewhere to go.

How you build a single behavioural answer in detail, and what the follow-up questions test, is a separate question. This page is about the choice before that, and about what makes this particular question different from the others.

A worked example

"There were five of us in order processing, plus two colleagues in the field who formally reported elsewhere but whose orders landed with us. I handled the orders for the French-speaking region and I was the link to production."

"We coordinated for twenty minutes on Monday morning; everything else ran through one shared list. In the spring the same conflict kept coming back: the field team promised delivery dates that production could not hold that week. Both sides were right, and both raised it with us."

"I spent two weeks writing down which orders it happened on — almost always the same two articles. I took that to the production manager and we set a fixed lead time for those two that the field team is allowed to promise. I decided that myself, because it concerned my own orders. What I did not decide myself was changing what we tell customers; I took that to my line manager, because it went beyond my orders."

"After that the queries coming back from production dropped by roughly half, and they still use the list. What I took from it: the conflict was not between people, it was between two different logics about dates. Until I wrote it down it sounded like an argument."

That answer runs about seventy seconds. It contains a number, a role, a friction, an action, a boundary that was drawn and a checkable outcome — and it leaves the other side at least three places to ask a follow-up question.

The classic mistake: the harmony story

The most common mistake is not boasting but its opposite: the example from the team where everything went well. It gets chosen because it feels good, and it proves nothing. If nothing ever collided, nobody had to decide anything — and the decision is what the question is aimed at. An answer without friction is an answer without information.

The same mistake has a second half: choosing by affection rather than by resemblance. Describing the settled three-person office where everyone understood each other instinctively, in an interview for a role whose advert names work across departments, is a selection error rather than a storytelling error. Five minutes of preparation prevents it.

The third version is the string of adjectives. "Team player, communicative, resilient" is not an answer; it is the claim the example was supposed to support. It also has a side effect people underestimate: in a structured interview, a personal quality asserted about yourself almost inevitably triggers the request to describe a situation that shows it. Say it only when the case is ready.

And one special case that comes up more often than you would think: the story about difficult former colleagues. It answers a question nobody asked — namely how you will talk about the people currently sitting across the table, two years from now. The friction belongs in the answer; the blame does not.

When you do not know the team: ask

Because the advert almost never tells you, asking about the team is the single most effective piece of preparation available, and it costs nothing. armasuisse itself lists "how is the team set up?" among the questions you should bring with you. Ask it early rather than at the end: what you say afterwards can then be aimed at the answer.

Three formulations that yield more than the general version. "How many people are in the team, and how is the work divided between them?" — that replaces the number the advert left out. "Which departments does this role deal with day to day?" — that settles whether collaboration here means proximity or an interface, and the two call for different examples. "What has been difficult in the team over the past few months?" — the only one of the three that forces an honest answer, and the most useful one for your own decision.

If you get the answer early, aim your example at it. A small, settled team makes the everyday-coordination story land. A team working across departments makes the opposing-interests story land. You prepared both; you choose in the room.

One last use of the same figures: if an advert describes the team unusually precisely — size, make-up, reporting line — it belongs to the small minority of adverts that do. That is rare enough to be worth mentioning in the interview. It shows you read the advert, and it is the same attention the question is testing in you.