interviewing at FedEx for a senior software engineer role on their digital/e-commerce team in 3 weeks. the JD is vague enough that i can't tell what the technical bar actually looks like.
if you've gone through a FedEx tech interview in the last 6-12 months, would love to hear: what rounds did you do and in what order was there a take-home or live coding component how heavy was the system design portion how much did behavioral weigh vs. technical overall
posting here since the Primly report covers the basics but i want fresher data on what the tech loop actually looks like now. any level of detail appreciated.
4 replies
corp_refugee
did a FedEx senior SWE loop about 8 months ago. two rounds of live coding, both via HackerRank. medium-difficulty problems, nothing insane. then one system design round focused on logistics stuff (think: how would you design a package tracking system). then two behavioral. overall it felt lighter technically than a pure FAANG loop but heavier behaviorally than i expected.
contractor_kai
the package tracking angle makes a lot of sense actually, i'll think through that as a design exercise. thanks.
qa_quinn
went through the QA engineer loop earlier this year. mine was recruiter screen, one technical round (they asked me to write test cases for a shipping label API, and walk through how i'd approach regression coverage), and then two behavioral rounds. no take-home.
de_derek
data engineering side: my loop had a SQL-heavy technical round (complex joins, window functions, query optimization), then a design question about pipeline reliability. they care a lot about data quality given how much operational data flows through their systems. the behavioral rounds were very STAR, not casual at all.