FedEx · Primly Community

FedEx behavioral interview questions and values: what they actually asked me across two rounds

returner_ren · 4 replies

I went through the FedEx interview process this spring, targeting a senior individual contributor role on their supply chain tech team. Two separate behavioral rounds, which surprised me. Sharing what they asked because behavioral prep is underrated and FedEx has a specific flavor to their questions.

Round 1: Hiring manager (45 min)

This one was more structured. She had a list and worked through it: Tell me about a time you worked on a project that had a tight deadline with incomplete requirements. What did you do? Describe a situation where you disagreed with a technical decision made by your team. How did you handle it? Give me an example of a time you had to influence someone who wasn't your direct report. Tell me about the most complex system you've owned end to end.

FedEx's underlying values show through in what they probe for. They care a lot about reliability under pressure (makes sense for a logistics company), cross-functional collaboration (their engineering teams work closely with ops and business units), and ownership without authority (lots of their problems require engineers to work across silos they don't control).

Round 2: Cross-functional peer (30 min)

Lighter, more conversational. Two questions, more discussion: How do you build relationships with non-technical stakeholders? Tell me about a time a project you worked on failed. What happened and what did you learn?

One thing I noticed: they're not running Amazon LP-style behavioral interviews. There's no specific framework they're trying to map to named principles. It's more traditional: can you work well with people, do you take ownership, are you someone we'd want on a team with complex stakeholders.

Tips: Have 5-6 strong STAR stories ready covering: technical ambiguity, cross-team influence, failure/recovery, deadline pressure, and disagreement. Be concrete. Vague answers didn't land well from what I could sense in the follow-up probing. They do ask "why FedEx" sincerely. Having a thoughtful answer about their logistics-tech modernization push went over better than generic "I love the scale" stuff.

I got the offer. The process was more rigorous than I expected going in, in a good way.

4 replies

recruiter_rita

The "ownership without authority" angle is real for enterprise companies like FedEx. Engineers there are constantly needing buy-in from business units, ops teams, drivers' union considerations, etc. If your behavioral stories don't demonstrate you can operate in messy stakeholder environments you'll struggle there even if you're technically strong.

analyst_ana

The failure question is the one I always freeze on. How did you frame yours? Like did you pick something genuinely significant or something safe-ish?

returner_ren

I picked something real, a project I owned that shipped late and caused downstream problems for another team. I talked about what I missed in the planning phase, what I should have escalated sooner, and how I changed my habits afterward. They seemed to appreciate that it was genuine and not a "failure" that was secretly a success. The follow-up question was what I actually changed, so if you pick something fake you'll get exposed quickly.

growth_gabe

The "why FedEx" question is interesting because most candidates probably give generic answers about scale. The logistics tech modernization angle is a much better hook if you've done even a little research. Good tip.