Full-stack engineer
Node, Next.js, Socket.IO, Kafka, Redis, Elasticsearch. Event-driven, and the events are real trips.
This role is not open yet. It describes work 745 needs doing as the platform grows, and no budget is approved for it today. Write to us anyway if it is yours. We would rather know you exist before the requisition does.
745 runs on an event-driven stack where Kafka is the source of truth, Redis holds current state and Elasticsearch holds history. Nothing here is a toy: a bug in the projection layer means a passenger's trip disappears from their own list, and we have shipped that bug and fixed it.
What you would do
- Build features across the gateway, the passenger web app and the driver app
- Write projections that are idempotent, because topics get replayed
- Care about the read path. A passenger mid-trip on a bad connection is the user you are designing for
- Review your own work honestly, and someone else's kindly
What you would need
- Real JavaScript depth. This is not a framework-shaped role
- Comfort with asynchronous, event-driven thinking
- An eye for the failure case, not just the happy path
- No degree requirement. Show us something you built and can explain
Straight with you
Small team, no layer of managers between you and the decision. That means autonomy and it also means nobody will catch your mistake before a passenger does.
Tell us what you would make more punctual. A human reads every one.