Requirements

• Build AI-natively. AI is how we work. It's not a productivity layer on top of engineering, but the default starting point for how problems get approached and solved.
• Set technical direction. You define the approach others build from. When the problem is complex or the answer isn't obvious, you're the person who leads the design discussion, writes the ADR, and makes the call.
• Invent new interfaces. Software delivery is being reinvented. Pipelines run autonomously, generate fixes, and surface results that need human judgment. The tools developers use to understand, trust, and act on that work don't exist yet. You'll define what they look like and establish the patterns the team builds on.
• Own the full stack. Build features end-to-end in Go, React, and TypeScript. You don't hand off at a layer boundary. You own the outcome.
• Obsess over craft. Reliability and responsiveness are design concerns, not afterthoughts. Care about how the interface holds up when stakes are high and hold your team to that same standard.
• Champion observability. Use Honeycomb, Datadog, and Rollbar to understand and improve your systems. Operational data drives stability, not just incident response.
• Close gaps and fix the conditions that created them. You'll notice gaps and close them. When a gap reflects something broken in how the team works, you fix that too.
• AI-native engineering practices. You use AI tools daily and can speak to what you've built, where they changed your approach, and where they fall short.
• A track record of shipping. You've built something real and put it in front of users. 5+ years of production full-stack experience, with latency, responsiveness, and reliability treated as design concerns, not afterthoughts.
• Full-stack depth. Strong React and TypeScript. Comfortable owning backend services in Go: API design, data modeling, service integration.
• System design. You lead architectural decisions on complex systems. You make conscious tradeoffs, document your reasoning, and create the foundation others build on.
• Adaptability. You don't just thrive in ambiguity, you reduce it for others. You turn unclear requirements into a direction the team can execute on.
• Technical leadership. You mentor engineers, give direct feedback on technical direction, and raise the quality bar through how you engage in reviews and design discussions, not just what you ship.

What You'll Be Doing

• Build AI-natively. AI is how we work. It's not a productivity layer on top of engineering, but the default starting point for how problems get approached and solved.
• Set technical direction. You define the approach others build from. When the problem is complex or the answer isn't obvious, you're the person who leads the design discussion, writes the ADR, and makes the call.
• Invent new interfaces. Software delivery is being reinvented. Pipelines run autonomously, generate fixes, and surface results that need human judgment. The tools developers use to understand, trust, and act on that work don't exist yet. You'll define what they look like and establish the patterns the team builds on.
• Own the full stack. Build features end-to-end in Go, React, and TypeScript. You don't hand off at a layer boundary. You own the outcome.
• Obsess over craft. Reliability and responsiveness are design concerns, not afterthoughts. Care about how the interface holds up when stakes are high and hold your team to that same standard.
• Champion observability. Use Honeycomb, Datadog, and Rollbar to understand and improve your systems. Operational data drives stability, not just incident response.
• Close gaps and fix the conditions that created them. You'll notice gaps and close them. When a gap reflects something broken in how the team works, you fix that too.

Perks and Benefits

You've stopped waiting for AI to mature and are already building with it, not as a productivity trick, but as a core part of how you think about problems. You care about the product as much as the code. You're drawn to work where the patterns don't exist yet and the best answer requires you to invent it. If that's how you already operate, we want to talk.