Summary

We are in the middle of a major product pivot. This isn't a role for someone who wants to sit in the back and wait for a Jira ticket to tell them what to do. We need an engineer who can own the "why" as much as the "how." You’ll be joining an existing product squad as a lead individual contributor, responsible for driving velocity, untangling legacy constraints, and shipping the foundation of our next chapter.

Your goal is to be the engine of the squad: someone who makes the hard technical decisions quickly so the team can stay in flow.

In this role, you will:

In your first month, we expect you to be fully integrated into our stack and development lifecycle. Within 14 days, you should have pushed your first meaningful feature to production. You’ll spend this time mastering our CI/CD pipelines and becoming fluent in our codebase so you can begin picking up complex tasks without supervision.

By six months, you will have become a pillar of the squad. You’ll have led the end-to-end delivery of at least two major features for the new product direction—handling everything from technical design to final deployment. Beyond your own tickets, you’ll be the person raising the bar for the rest of the team through code reviews that don't just catch bugs, but improve our overall architectural thinking.

At the one-year mark, you will have measurably increased the squad’s shipping speed. You’ll have identified and executed a major refactor or system improvement that removed a legacy bottleneck, ensuring the pivot can scale. You’ll be recognized as the owner of a critical domain, having built the patterns that make it impossible for others to write bad code.

What you need to be successful:

We are looking for a high-bar engineer who prioritizes user outcomes over technical purity. You should have 5-8+ years of experience in high-growth environments where speed was a competitive advantage.

You should be the type of engineer who:

1. Thinks about the user's "Job to be Done" before writing a single line of code.

2. Moves fluidly across the entire stack, from database migrations to polished UI interactions.

3. Practices "Elite Pragmatism"—you know exactly when to write a perfect abstraction and when a quick, robust solution is the better business move.

4. Takes proactive ownership of the system. If you see a load-bearing wall that's crumbling, you don't wait for permission to fix it.

5. Communicates with clarity. You can explain complex trade-offs to a PM or a Designer without getting lost in technical jargon.

7. Our Technical Environment

8. Our current tech stack is robust, utilizing TypeScript, React, and React Native for the frontend development, while the backend is powered by a combination of Node.js, Golang, and C/C++ for performance-critical components. Our data stack is powered with PostgreSQL and S3, while our infrastructure is hosted on Amazon Web Services (AWS).

Skills

• AWS
• C++
• Communications Skills
• Development
• React
• Software Engineering
• Team Collaboration
• TypeScript