← Back to Directory

BNSF

Large Enterprises

Screna has 3 BNSF interview write-ups. The most reported round is the technical phone screen (2).

3 interview notes · updated Jun 2026

BNSF·Software Engineer·Technical Phone Screen

Jun 2026
BNSF Software Engineer interview had a pretty technical slant, at least for the round I went through. The main prompt was about writing a unit test suite from a spec alone, no source code, which was more involved than I expected.
  • You're given a function specification but no implementation. Write a unit test suite that covers as many meaningful cases as possible, including happy paths, boundary conditions, invalid inputs, equivalence partitions, idempotency, and any concurrency or stateful behavior implied by the spec. Also explain how you'd prioritize if time-boxed.

“This was the whole interview basically.”

View Post

BNSF·Software Engineer·Take-home Assignment

May 2026
BNSF had me do a take-home where I built a small REST API from scratch. The twist was that the request body came in as plain text instead of JSON, which I did not expect at all.
  • Build a REST API supporting full CRUD operations where the request body uses Content-Type 'text/plain' instead of JSON. You must parse the body yourself and return both appropriate HTTP status codes and a JSON response with a message field.

“The plain-text body thing tripped me up more than I want to admit.”

View Post

BNSF·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a software engineer role at BNSF Railway and got a graph problem that was more straightforward than I expected once I stopped overthinking it.
  • Given an undirected unweighted graph with a set of source nodes, find the shortest distance from every node to its nearest source.

“My first instinct was to run BFS from each source separately and merge results, which would've been way slower.”

View Post