← Back to Directory

Bridge

Small

Screna has 6 Bridge interview write-ups. The most reported round is the system design round (3).

6 interview notes · updated Jul 2026

Bridge·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Bridge SWE interview that was basically one big system design question dressed up as a coding problem. They wanted a full Minesweeper implementation plus a follow-up on scaling it to huge sparse boards, which honestly felt like two separate interviews crammed into one.
  • Design and implement a Minesweeper game: initialize an m×n board with k randomly placed bombs, implement a printBoard() method that returns the current player-visible state, and implement a click(r, c) method that handles bomb hits, cell reveals, and BFS/DFS flood fill for zero-adjacent-bomb regions. Discuss data structures, algorithms, and time/space complexity, and provide test cases.
  • For very large, sparse boards (huge m and n, but very few bombs), how would you optimize click() to be fast and memory-efficient? Walk through options like lazy board generation, sparse data structures, on-demand neighbor counting, caching, and pruning, and discuss the trade-offs.

“I started with a 2D array for the board and a separate boolean grid for revealed state, which felt clean at first.”

View Post

Bridge·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Bridge.Xyz for a software engineer role, focused entirely on building an email/password auth service from scratch. No scaling tricks, just get the security fundamentals right. Trickier than it sounds.
  • Design a basic email and password authentication service supporting user sign-up and login, without using any third-party identity providers.
  • How should passwords be stored securely, and why can't you just use a standard hash like SHA-256?
  • How do you manage login state after a user authenticates, and what are the tradeoffs between opaque session tokens and JWTs?
  • What is user enumeration and how do you prevent it, including the timing side channel?
  • How would you handle 'log out from all devices' and force re-login after a password change?
  • Where would email verification and password reset flows attach to this design, and what new tables or tokens would they require?

“Big open-ended question to start.”

View Post

Bridge·Software Engineer·Technical Phone Screen

May 2026
Did a technical screen for a Software Engineer role at Bridge with two coding problems back to back. Nothing too wild but the second one had some depth to it if you actually thought about the lazy vs eager tradeoffs.
  • Given a string representing an absolute Unix file path, implement a function to return its canonical (normalized) form. Handle '.', '..', consecutive slashes, and trailing slashes correctly. Walk through your algorithm and give time and space complexity.
  • Design an iterator for a nested list structure that can contain integers or other nested lists at arbitrary depth. Implement hasNext() and next() using a lazy stack-based approach, and optionally discuss an eager flattening alternative. Compare the tradeoffs between both designs.

“Stack-based solution, pretty standard.”

View Post

Bridge·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at bridge.xyz for a software engineer role, focused entirely on building an auth service from scratch with no third-party OAuth allowed. Pretty meaty for a single question but it covered a lot of ground fast.
  • Design a simple authentication service that handles user sign-up and login, built entirely in-house without relying on any external auth providers.

“Covered the API layer first since that felt most concrete.”

View Post

Bridge·Software Engineer·Technical Phone Screen

May 2026
Got a technical phone screen for a Software Engineer role at Bridge.Xyz. Single coding question, file path normalization, felt straightforward on the surface but there are enough edge cases to trip you up if you're not careful.
  • Given an absolute Unix-style file path as a string, implement a function that returns its canonical normalized form. Handle dots, double dots, consecutive slashes, and trailing slashes correctly.

“Stack-based approach is the right call here.”

View Post

Bridge·Software Engineer·Technical Phone Screen

May 2026
Coding round at bridge.xyz for a software engineer role. One question, file path simplification, which sounds like a warmup but has enough edge cases to trip you up if you're not careful about the stack logic.
  • Given an absolute Unix-style file path string, return the simplified canonical path. Handle '.', '..', consecutive slashes, and trailing slashes correctly. Walk through test cases and discuss time/space complexity.

“I went straight to a stack and split on '/' which is the right call, but I fumbled the edge cases for a bit.”

View Post