Geodis Behavioural Interview: 6 Competencies, STAR Answers
A practical guide to the competencies logistics employers like Geodis typically assess in behavioural interviews, with a worked STAR answer and a preparation checklist.
What a behavioural interview looks like at a logistics employer like Geodis
Geodis is a global transport and logistics business, and employers in this sector generally use behavioural (competency-based) interviews to predict how you will act in real operational situations. The questions usually start with phrases like "Tell me about a time when…" or "Give me an example of…". The logic is simple: past behaviour is the best available evidence of future behaviour.
We don't have insider knowledge of Geodis's current question bank, scoring or stages, and these differ by country, business line and role level. Depending on the vacancy, you might face a phone screen, a live video or in-person interview, or a recorded one-way video format. Your invitation email is the most reliable guide to the format, timings and any preparation advice. Also read the job description closely and the values on the Geodis careers site, because that is where the competencies you need to evidence are most likely to appear.
Six competencies logistics interviewers commonly assess
Whatever the exact wording, behavioural questions in supply chain and logistics tend to cluster around the themes below. Treat this as a well-founded starting point for your preparation, not a leaked list of what Geodis will ask.
- Safety and compliance: following procedures, spotting risks, speaking up when something is unsafe, and working accurately when the pressure is on.
- Customer focus and service reliability: keeping promises on delivery windows, handling complaints, and communicating early when something goes wrong.
- Teamwork and collaboration: working across shifts, depots, drivers, planners and clients, and supporting colleagues when workloads spike.
- Problem-solving under time pressure: dealing with delays, shortages, system errors or last-minute changes and still reaching a workable solution.
- Adaptability and resilience: staying effective when priorities change, plans fall through or conditions are unpredictable.
- Ownership and continuous improvement: taking responsibility for outcomes, admitting mistakes, and making a process faster, safer or cheaper.
Use STAR to structure every answer
STAR keeps your answer focused and makes it easy for an interviewer to score. The four parts are Situation, Task, Action and Result.
Most weak answers fail in the same place: they spend too long on the Situation and rush the Action. Aim for roughly 10-15% Situation, 10% Task, 50-60% Action and 20% Result. Use "I" rather than "we" when describing the Action, because the interviewer is assessing you, not your team.
- Situation: where and when, in one or two sentences of essential context.
- Task: what you were responsible for and what success looked like.
- Action: the specific steps you took, and why you chose them.
- Result: the outcome, ideally measurable, plus what you learned or changed afterwards.
Reading about it isn't the same as doing it on camera.
Run a free timed mock interview →Worked example: "Tell me about a time you solved a problem under time pressure"
This is an illustrative answer, written for a candidate with warehouse or dispatch experience. Swap in your own details and only use figures you can stand behind.
Situation: "In my job at a distribution centre, a pallet of time-sensitive orders was found to have mismatched labels about 90 minutes before the carrier's cut-off."
Task: "As the team member on the outbound bay, I was responsible for getting the correct goods onto the right vehicle without compromising accuracy."
Action: "First I told my supervisor straight away so the carrier could be warned of a possible delay. Then I split the pallet into sections and asked two colleagues to help me check each one against the dispatch notes, rather than rushing and risking more errors. While they scanned, I re-labelled the cartons and logged the discrepancy so the cause could be traced. I checked the final count against the order system before it was loaded."
Result: "The order left on time and with no mismatches. Afterwards I suggested a label check at the packing stage, and my supervisor trialled it for a few weeks. It caught several similar errors earlier, so I learned that raising problems quickly and fixing the root cause matter as much as the rescue itself."
Do and don't: what separates strong answers from weak ones
Small habits make a noticeable difference to how competent and trustworthy you sound.
- Do choose examples where safety, accuracy or service genuinely mattered. Don't pick a story where the stakes were trivial.
- Do show the reasoning behind your actions. Don't just list tasks.
- Do own mistakes and show what you changed. Don't claim you've never failed, because it sounds evasive.
- Do quantify results where honest (time saved, errors avoided, feedback received). Don't invent numbers.
- Do keep answers to around two minutes. Don't ramble through background detail.
- Do be ready for follow-ups such as "What would you do differently?". Don't memorise a script word for word.
Build your example bank and practise out loud
Rather than prepping a separate answer for every possible question, prepare five or six strong stories from work, study, volunteering or sport, and map each to several competencies. A single story about a delayed order can flex to answer questions on problem-solving, customer focus, teamwork or ownership, depending on which part you emphasise.
Write each story in STAR bullet points, not full sentences, then say it aloud and time it. Reading silently hides rambling and filler words. If your interview might be recorded, practising to a camera helps you get used to the lack of live feedback. A tool such as ScreenReady lets you answer timed questions on video and then review feedback on structure and clarity, though a friend or your phone's camera works too.
Finally, prepare a couple of thoughtful questions about the role, such as how teams measure on-time performance or what safety training new starters receive. They show genuine interest in the operation.
Frequently asked questions
Does Geodis use competency-based questions for every role?
We can't confirm the exact process for every role or country, but competency-based questions are very common across logistics employers, from operational positions to graduate and management roles. The depth and seniority of the examples expected will vary. Check your invitation and the job description for guidance.
What if I have no logistics experience?
Interviewers are assessing behaviours, not only industry knowledge, so examples from retail, hospitality, education, volunteering or sport can work well. Choose stories involving reliability, teamwork, safety awareness or solving problems quickly, and explain clearly what you personally did.
How long should a STAR answer be?
Aim for around 90 seconds to two minutes. That is long enough to cover the Action in real detail and short enough to keep the interviewer's attention. If the interview is a timed one-way video, rehearse with a timer so you finish the Result before time runs out.
Can I reuse the same example for multiple questions?
Occasionally, yes, especially if the story is rich, but try to avoid repeating it within one interview. Having five or six varied stories lets you pick the best fit each time and shows a broader track record.
Practise for these companies
Put this into practice
ScreenReady builds a realistic, timed mock interview around your target role, records your answers on camera, and gives AI feedback on structure, evidence and delivery.
Start a free mock interview →