Full-Stack Developer

>The Role

We are looking for a stellar full-stack engineer to build and ship vital product functionality as part of our core engineering team. From Python to React, you’ll own entire features end to end. You’ll use AI to augment and accelerate your implementation tasks, but it won’t replace your critical thinking, architectural judgment, or engineering intuition; we are seasoned engineers, not newly-minted vibe-coders. This role demands a blend of deep systems expertise, thirst for the intractable, and voracious appetite for mastering frontier tech. You are building agentic systems at the limit of what's possible to solve problems no one has solved before.

001Key Responsibilities

• Design the Feature: Working from high-level goals, formulate inventive, robust approaches to problems without obvious solutions, owning key architectural decisions along the way.
• Implement the Solution: Build it by directing, managing, and correcting AI agents when they can help, but ultimately asserting your own judgment and engineering prowess.
• Ship the Code: Test and integrate your work into production, then own it, bugs and all.

002You're a good fit if you...

• Build Systems, Not Just Ship Code: You have expertise architecting complex systems under hard constraints. You think in terms of first principles, and your solutions have held up under real load.
• Move Fluidly Up and Down the Stack: You may have a favorite, but can easily jump between front end and back end ecosystems, including asynchronous frameworks. If for you that means React on Vercel and Python/Celery on AWS, all the better.
• Distrust Your Agents: You plan before you prompt and expect one-shot failure, so you interrogate what comes back from an agent: reading every line, uncovering assumptions, challenging decisions, and launching multiple subagents for every concern. You set the architecture yourself and hold the agent to it, because you're thinking about the whole system, not trying to avoid thinking.
• Are an Incurable Autodidact: No one taught you most of what you know. You see a problem, do the research, run the experiment, and show up saying "this is better, we should switch." Figuring it out isn't a chore for you; it's what drives you.
• Are Not Precious: Not every problem is a novel one. You implement the boring endpoint as carefully as the hard architecture, because shipped product is what counts. The last 20% is rarely the fun part, but you do it well anyway.
• Run on Your Own Fuel: You do your best work armed with a goal and the freedom to execute it. On a remote team this small, no one hands you a task list and checks your homework; you look for ways to act effectively without waiting to be told, and you answer for the results.

003Why you should apply now

• Join the core team: Work directly with serial entrepreneurs, on a product with an endless array of challenging problems and difficult architectural decisions ahead of it.
• Ship at full speed: No approval chains, no release trains, no waiting two weeks for a review. You build it today, it's in production this week.
• True autonomy: Work remotely with freedom, responsibility, and trust. There are no corporate silos here; the whole system is yours to shape.
• Build AI systems, don't get replaced by them: With the rise of AI coding, many people wonder what’s left for the engineer. What's left is the best part: the judgment, the architecture, the system insights. You'll spend your time building the skills that are appreciating in value.