← Back to Directory

Headway

Mid-sized

Screna has 10 Headway interview write-ups. The most reported round is the system design round (4).

10 interview notes · updated Jun 2026

Headway·Software Engineer·Technical Phone Screen

Jun 2026
Headway software engineer interview, part of a three-question object-oriented design scenario that built on itself. The journey-counting problem was the middle chunk and it had more edge cases than I expected going in.
  • Given a log of road events parsed into typed objects (ENTRY, MAINROAD, EXIT), implement a function that counts the total number of complete journeys across all vehicles, where events from different vehicles may be interleaved.

“My first instinct was to just count ENTRY events and call it a day, which is wrong the moment you think about interleaving.”

View Post

Headway·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Headway for a software engineer role. One question, pretty math-heavy, and I felt okay about my answer but not great.
  • Given a user count and per-user activity rate, estimate the server capacity needed: CPU, memory, disk IOPS, and network bandwidth. Walk through the math explicitly and state your assumptions.

“I started from DAU and worked toward QPS, which felt natural, but then I got a bit tangled trying to map per-request costs to actual instance types.”

View Post

Headway·Software Engineer·Online Assessment (OA)

Jun 2026
Headway gave me a CodeSignal assessment for a Software Engineer role where the whole thing was one coding problem: add rate limiting to a pre-built REST API skeleton. More implementation-heavy than I expected, with some real gotchas around thread safety and window reset logic.
  • You're given a REST API project skeleton. Add rate-limiting middleware that enforces a global limit of 100 requests per minute across all endpoints and a per-endpoint limit of 3 requests per second, returning 429 when either is exceeded. Use a fixed-window approach and make sure the limiter wraps all handlers automatically so new endpoints inherit the limits without extra work.

“The fixed-window part tripped me up more than I expected.”

View Post

Headway·Software Engineer·Onsite - System Design / Architecture

Jun 2026
A 20-minute system design discussion at Headway for a software engineer role, focused entirely on designing a comment service. Pretty conversational, no coding, just a lot of back-and-forth on tradeoffs.
  • Design a comment service where users can add and read comments on articles, with pagination support.
  • How would you handle caching for a read-heavy comment feed, and how do you deal with cache invalidation when new comments are added?
  • How would you partition the comments table to handle storage and query performance at scale, especially for articles that get a lot of traffic?
  • For displaying a comment count per article, would you use a denormalized counter or compute it on the fly? What are the tradeoffs?
  • How would you approach spam prevention and content moderation for user-submitted comments?

“The core ask was two endpoints basically: add a comment and list comments with pagination.”

View Post

Headway·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at Headway for a Software Engineer role. One problem, fairly involved, built around a speed camera system on a segmented road. More edge cases than it looked at first glance.
  • Given log entries from road cameras placed every 10 km, implement a function that returns the sorted list of license plates belonging to speeding vehicles. A vehicle is flagged if any single segment has an average speed of 130 km/h or more, or if at least two separate segments each hit 120 km/h or more.

“I got the basic structure pretty quickly: parse, group by plate, sort by timestamp, compute speed per segment as (10 * 3600) / delta_t.”

View Post

Headway·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Headway for a software engineer role, focused entirely on building the search experience for a short-term rental platform. Pretty deep dive, they wanted specifics on everything from the data model to ranking signals.
  • Design the search experience for a short-term rental platform like Airbnb, covering functional requirements, data modeling, API design, indexing strategy, ranking, and scalability.
  • Walk through your data model in detail, specifically the listings table and the availability/calendar table.
  • How would you handle availability filtering, would you do it inside the search index or through a separate calendar service?
  • How would you design the ranking system, what signals would you use beyond basic relevance?
  • How would you handle caching for popular search queries and what are the tradeoffs?

“This is one of those questions that feels manageable at first and then just keeps expanding.”

View Post

Headway·Software Engineer·Onsite - Multi Round

May 2026
Headway software engineer interview that mixes deep technical dives with behavioral leadership questions. Not a pure coding round, so if you show up expecting leetcode you'll be caught flat-footed.
  • Walk me through a technically challenging project you worked on. What was the problem, what design and implementation choices did you make, and what trade-offs were involved?
  • Looking back at that project, what would you do differently and what was the actual outcome?
  • Tell me about a significant conflict you had with a peer, cross-functional partner, or manager. How did you understand their perspective and what did you do to resolve it?
  • Describe a time you showed technical leadership, whether that was driving a key decision, mentoring someone, raising quality standards, or pushing through a difficult change.

“This is the kind of question where you think you're prepared and then realize mid-answer you skipped the interesting part.”

View Post

Headway·Software Engineer·Technical Phone Screen

Apr 2026
Headway software engineer interview that was basically a debugging and probability exercise disguised as a coding problem. The core task was fixing a buggy implementation and adding tests, which sounds manageable until you're staring at a stats formula you half-remember from college.
  • Given a list of racers each with their own completion time history, implement a function that returns the single smallest personal-best time across all racers.
  • Given a racer's history of times, estimate the probability that a new candidate time would be a personal best. The expected approach models the history as samples from a normal distribution and uses the standard normal CDF.
  • Identify all the bugs in the provided starter code and add unit tests covering the fixed implementation.

“Felt easy at first.”

View Post

Headway·Software Engineer·Technical Phone Screen

Apr 2026
Headway gave me a debugging scenario involving a log parsing class, which sounds straightforward until you're staring at a TypeError and can't figure out why the speed math keeps blowing up. Three-part problem, and this was just the first piece.
  • You're given a LogEntry class that parses a whitespace-separated string. The catch_speeders function never flags any vehicle even on clearly speeding entries. Find the bug, fix it, and write a small test to confirm the time-delta math works.

“Took me an embarrassingly long time to find it.”

View Post

Headway·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Headway for a software engineering role. The question was a classic 'your server is melting' scenario but they wanted real depth across a lot of different dimensions, not just 'add more servers'.
  • A server is getting slow under high request volume. How do you diagnose and fix it?

“Broader than it sounds.”

View Post