Lead Full-Stack Engineer

About the role

About Roame

Roame is a flight and hotel search engine for points and miles.

Booking business or first class with points instead of cash saves travelers thousands of dollars on a single trip. The hard part is finding the seats. Award space is scattered across dozens of airline and hotel programs, it moves constantly, and the best deals get taken. Doing it by hand means hours across a dozen browser tabs, and often days.

Roame finds those deals in seconds. Members also book hotels through us and get our commission rebated back to them immediately. Roame was founded by Tim and Zi. Tim spent the previous decade covering consumer and travel companies on the hedge fund side. Zi ran data encryption systems at Airbnb.

We started Roame after losing dozens of hours hunting for first class award space to Asia across a dozen browser tabs. Award travel is a data problem. Humans shouldn't have to solve it by hand.

Why join Roame now?

- Profitable. We run on revenue, not runway. We can start multi year technical work and actually finish it.

- Loved product. We're the default tool for a lot of the points and miles community, and our users are vocal about it.

- Scope. This is the top engineering role at the company. There is no larger org above it.

- AI native. A large share of our engineering is agent assisted and our whole workflow is built around it.

About the role

- Own engineering at Roame. You would be the most senior engineer here, reporting to the founders.

- Set technical direction across our Go backend and web app. We also ship a native iOS app, and every API decision has an iOS client on the other end of it. You need to account for that, not build it.

- Finish our move to a modern Go service architecture and retire what's left of the old one.

- Own correctness where money moves: booking, checkout, payments.

- Set the engineering bar on testing, review, documentation, and hiring.

- Grow into the senior most technical role at the company as we scale.

How we work

- Write it down before building it. Specs and architecture live in the repo.

- Test first. Most work starts from a written test plan.

- Ship in small increments. Days, not sprints.

- Nothing waits until tomorrow if it can go out today.

- Disagree out loud, early, to the person. Then pick something and move.

- No task is beneath anyone.

- Spoon feed yourself, learning is free, generate a video from the code and learn it

Your first 90 days

- Week 1. Ship something to production. Small is fine. Nobody here spends a week reading code before they touch it.

- Day 30. You own a meaningful piece of the booking and checkout path and have shipped a significant update to it.

- Day 60. You own the migration plan. Your sequencing, your call on what gets cut.