← Back to Directory

BNSF

Large Enterprises

BNSF Railway is one of the largest freight railroad networks in North America, operating across the western United States. A subsidiary of Berkshire Hathaway, it transports goods including consumer products, agricultural commodities, industrial materials, and coal across an extensive rail system.

3 interview notes · updated Jul 2026

BNSF·Software Engineer·Technical Phone Screen

Jun 2026
Coding round for a software engineer role at BNSF. Two tasks back to back: build a REST API with some quirky plain-text input requirements, then write unit tests for a function you can't even see the source of. Weird combo but kind of interesting once you got into it.
  • Implement a basic REST API for a simple resource (like a note or message) that supports create, read, update, and delete. The request body uses plain text instead of JSON, but all responses must be JSON with appropriate HTTP status codes. Handle edge cases like missing resources and bad input.
  • Write unit tests for a function when you only have its specification, not the actual implementation code. Cover as many meaningful scenarios as possible including edge cases and failure modes.

“The plain-text body thing tripped me up at first.”

View Post

BNSF·Software Engineer·Take-home Assignment

May 2026
Got a take-home style coding problem for a Software Engineer role at BNSF. It was a REST API build from scratch, nothing crazy on the surface, but the plain-text body parsing requirement ended up being the part that actually separated people who read carefully from those who didn't.
  • Build a REST API with full CRUD operations where the request body uses plain text instead of JSON, and you have to parse it yourself. Cover validation, error handling, idempotency for PUT and DELETE, and how you'd disable automatic body parsing in your framework.

“The plain-text parsing part is what got me.”

View Post

BNSF·Software Engineer·Technical Phone Screen

Apr 2026
A technical round at BNSF for a Software Engineer role where the main prompt was to write a full unit test suite from a spec alone, no implementation provided. Pretty interesting exercise, more design-heavy than I expected.
  • You are given only a function's specification, not its code. Write a comprehensive unit test suite covering happy paths, boundary conditions, invalid inputs, equivalence partitioning, idempotency, and any concurrency or stateful effects implied by the spec. For each test case, state the input, expected behavior, and which requirement it covers. How would you prioritize if time-boxed?

“This is a meaty prompt and I spent the first few minutes just trying to figure out where to start.”

View Post