Senior Technical Lead

We build an AI-powered application security platform. It reads source code, finds security vulnerabilities, and then produces a fix that a person reviews and approves. Customers install it and run it inside their own cloud environment. The stack is Python (Langgraph, FastAPI, Pydantic V2), TypeScript, React, PostgreSQL, Kubernetes and the major cloud platforms.

You'll be the senior engineering owner of the backend platform, and the person everyone else learns the system from. Your job is to spread the knowledge across a team and lift engineering quality as that team grows.

The core backend service runs the analysis and remediation workflow. It's long-running and resumable, it pauses for human decisions, and it has to survive restarts without losing state.

You'll be our first engineering hire and the person who can deploy and debug the whole system. You'll also review everyone's code. Reviewing senior work and disagreeing with it is part of the job, not a rare exception.

• Own the backend service: workflow logic, the API layer, and the boundaries between internal modules.
• Review all code and set the quality bar for the team.
• Take the system from single-instance to horizontally scalable without breaking correctness.
• Technically onboard every engineer who joins after you.
• Write architecture decisions alongside the team, and challenge them.

• Substantial production Python(Langgraph, FastAPI, Pydantic V2,asyncio) including async code and static typing.
• Experience with long-running, stateful or resumable workflows: state machines, checkpointing, or jobs that have to survive interruption. The framework matters far less than having solved this class of problem.
• Strong relational data modelling, plus safe schema migrations against live systems.
• You've owned a codebase other teams depended on, and you were accountable when it broke.
• You read existing systems before you change them, and you can explain someone else's design fairly even when you disagree with it.

• A background in security tooling or developer tools.
• Experience somewhere that writes its architecture decisions down.
• Mentoring or leading a small team.

We build an AI-powered application security platform. It reads source code, finds security vulnerabilities, and then produces a fix that a person reviews and approves. Customers install it and run it inside their own cloud environment. The stack is Python (Langgraph, FastAPI, Pydantic V2), TypeScript, React, PostgreSQL, Kubernetes and the major cloud platforms.

You'll be the senior engineering owner of the backend platform, and the person everyone else learns the system from. Your job is to spread the knowledge across a team and lift engineering quality as that team grows.

The core backend service runs the analysis and remediation workflow. It's long-running and resumable, it pauses for human decisions, and it has to survive restarts without losing state.

You'll be our first engineering hire and the person who can deploy and debug the whole system. You'll also review everyone's code. Reviewing senior work and disagreeing with it is part of the job, not a rare exception.

• Own the backend service: workflow logic, the API layer, and the boundaries between internal modules.
• Review all code and set the quality bar for the team.
• Take the system from single-instance to horizontally scalable without breaking correctness.
• Technically onboard every engineer who joins after you.
• Write architecture decisions alongside the team, and challenge them.

• Substantial production Python(Langgraph, FastAPI, Pydantic V2,asyncio) including async code and static typing.
• Experience with long-running, stateful or resumable workflows: state machines, checkpointing, or jobs that have to survive interruption. The framework matters far less than having solved this class of problem.
• Strong relational data modelling, plus safe schema migrations against live systems.
• You've owned a codebase other teams depended on, and you were accountable when it broke.
• You read existing systems before you change them, and you can explain someone else's design fairly even when you disagree with it.

• A background in security tooling or developer tools.
• Experience somewhere that writes its architecture decisions down.
• Mentoring or leading a small team.