FedEx · Primly Community

FedEx software engineer interview process, full loop: what actually happened

backend_bekah · 6 replies

Just finished the FedEx software engineer interview process last month and wanted to write this up while it's still fresh. Applied to a Senior SWE role out of the Memphis headquarters (remote-eligible, at least that's what the recruiter said at first).

Here's the sequence:

Week 1: Recruiter call. Pretty standard 20-minute screen. They asked about background, why FedEx, current comp. Not much technical depth, just vibe-checking.

Week 2: Online assessment on HackerRank. Two coding problems, 90 minutes. One medium-level graph traversal, one dynamic programming problem that I'd put at easy-medium. Time was not the issue. Both solvable with solid fundamentals.

Week 3-4: Virtual onsite. Four rounds back to back on a Tuesday: 45-min coding (two more algorithm problems, similar difficulty to OA) 45-min system design 30-min behavioral with the hiring manager 30-min behavioral with a second interviewer, felt more like a culture/fit screen

Total time from application to offer: about six weeks. Which honestly felt fast for a company that size.

A few notes on leveling. They're not Google L5/L6, they use a different internal band system. The recruiter called it "senior" but when you dig in it's closer to mid-level at a tech company. Comp reflects that too. My offer was in the $130-145k base range (Memphis-aligned, not Bay Area). Not life-changing numbers but the WLB was described as genuinely better than my current gig and I believe it.

The interviewers were all practicing engineers, no HR people in the technical rounds. Team seemed solid, honestly more technically sharp than I expected going in skeptical of FedEx's tech culture. They're apparently mid-way through a logistics tech modernization push and actually have interesting infra problems.

Happy to answer specific questions if anyone is prepping.

6 replies

jp_newgrad

Was the HackerRank OA proctored? Like with webcam or anything? I hate those setups.

quietquit_quincy

No proctoring. Just a standard HackerRank link with a time limit. You could use your own IDE and look things up within reason. I ran my code locally and pasted it in. Pretty relaxed.

remote_swe_42

What's the PTO and remote situation actually like post-offer? Recruiter talk vs. reality can diverge a lot at legacy companies.

tired_recruiter

The six-week timeline tracks with what I hear from their talent team. They've been trying to speed up since they lost candidates to Amazon last year who just moved faster. The tech modernization thing is real, they're rebuilding a lot of internal tooling.

frontend_fran

Curious what stack they're using. Is it mostly Java/Spring in the backend? Or are they moving to something newer? That matters a lot to me before deciding whether to bother applying.

quietquit_quincy

Mix from what I could tell. A lot of legacy Java on the backend, but the team I was interviewing for is doing Go for new services and React on the frontend. They're in a hybrid state. Not cutting-edge but not a total COBOL nightmare either.