Senior Software Engineer - Distributed Systems, Fanatics Markets

The interview process was extremely disappointing, primarily because the actual coding assessment was completely misaligned with the preparation guidance provided by the recruiter.

Before the technical interview, I was explicitly told in writing that the assessment would focus on "real-world backend problem-solving rather than abstract puzzles," emphasizing correctness, speed, and resource efficiency. The interview preparation materials reinforced expectations around practical engineering, high-volume systems, and real-world technical problem-solving.

Based on those instructions, I spent considerable time preparing for practical Java backend scenarios involving event processing, state management, data handling, performance, and correctness.

The actual assessment was nothing like what had been communicated.

Instead, the entire 60-minute technical interview consisted of a single abstract word-chain graph traversal problem. Given a list of words, I had to find a path connecting a starting word to an ending word based on matching letters. The interviewer initially required the shortest path before relaxing the requirement to any valid path. The solution involved graph-search concepts, recursion, visited-node tracking, and backtracking.

There was no practical backend scenario, no API design, no event processing, no distributed systems problem, and no meaningful connection to the engineering work emphasized in the preparation materials. It was a traditional algorithmic coding puzzle - the exact type of exercise the recruiter had explicitly said the assessment would not emphasize.

The problem wasn't simply that the assessment was challenging. The problem was that candidates were given materially misleading information about what they would be evaluated on. I have no objection to companies conducting algorithmic interviews, including difficult ones. But if that is how candidates will be assessed, communicate that clearly so they can prepare accordingly.

I subsequently sent the recruiter detailed, professional feedback explaining the discrepancy. I received no acknowledgment or explanation of that feedback before receiving a generic rejection stating that other candidates' technical backgrounds more closely aligned with the team's needs.

For a Senior Software Engineer - Distributed Systems position, I expected a more transparent and consistent interview process. Instead, the preparation guidance and actual evaluation felt like two entirely different interview processes.

My advice to future candidates: Do not rely on the preparation materials provided by Fanatics Markets. Even if you are explicitly told to expect practical backend problem-solving rather than abstract puzzles, be prepared for a full algorithmic graph-search assessment.

The lack of alignment between what was promised and what was delivered made this one of the most frustrating technical interview experiences I've had.