Founding Engineers

Stealth Startup | Autonomous Systems Infrastructure

A funded stealth startup is building the runtime execution control plane for agents, automation, and non-human identities.

As workflows become more autonomous, security teams can no longer rely on static access controls alone. The real risk emerges at runtime — when agents, workflows, service identities, and humans actually exercise authority across systems. We're building the platform that discovers, understands, and governs that execution layer across environments like cloud, CI/CD, developer tooling, and AI agent-driven systems.

This is a founding engineering role for someone who wants to own the core platform substrate of a category-defining control plane — the backend services, data infrastructure, connector framework, and production deployment that everything else runs on top of.

What You'll Work On

You'll help design and build the core systems behind the platform, including:

• Backend services and APIs that power the control plane — service boundaries, request flow, and internal platform abstractions
• Event ingestion and telemetry pipelines across cloud, CI/CD, and AI agent-driven workflows
• The connector framework that integrates with external platforms — cloud providers, CI/CD, developer tooling, AI-agent environments
• Persistence, schema, and storage systems that downstream product logic runs on top of
• Multi-tenant control-plane infrastructure, control plane / data plane separation, and tenant isolation
• Secure production deployment, infrastructure-as-code, operational tooling, and observability instrumentation

This is not a narrow DevOps or infra-ops role. You'll work across architecture, backend systems, product shape, and customer reality.

What We're Looking For

Strong candidates usually have experience building backend or platform systems such as:

• Control planes, developer platforms, or production backend infrastructure
• Event-driven backend systems and ingestion pipelines at scale
• Multi-tenant SaaS architecture and tenant isolation patterns
• Cloud-native systems that ingest, normalize, and process operational events
• Secure production deployment and direct operational ownership

You should be comfortable operating in ambiguous environments and building systems that other systems depend on.

Technical Requirements

We do not expect perfect overlap with every part of the stack, but strong candidates should bring experience with several of the following:

• Strong backend engineering in Go and/or Python
• Designing and operating service-oriented backend systems at scale
• Building against Postgres and designing production-grade operational schemas
• Working with AWS infrastructure services such as ECS/Fargate, RDS, VPC, KMS, Secrets Manager, IAM (for service and cross-account roles), and related primitives
• Building or owning event-driven systems, ingestion pipelines, and asynchronous workflows
• Designing APIs, service boundaries, and internal platform abstractions
• Debugging and operating production systems with strong attention to reliability, observability, and telemetry instrumentation (OpenTelemetry or similar)
• Building integrations with external platforms (GitHub, cloud provider APIs, webhooks)
• Comfort with infrastructure-as-code (Terraform, CloudFormation, or similar) and containerized deployment workflows

Experience with any of the following is a strong plus:

• SaaS product or platform experience at scale
• Control plane / data plane architecture patterns
• Strong knowledge of building secure production deployments
• Multi-system synchronization across service boundaries
• FastAPI or Next.js in production environments

Founding Engineer Expectations

Because this is a founding role, we care as much about engineering judgment as raw implementation skill. You should have:

• Strong written and verbal communication
• Comfort working directly with early customers and design partners
• Ability to explain technical systems clearly to both technical and non-technical stakeholders
• High ownership and low-ego collaboration
• Good product instincts and willingness to shape the roadmap through what you build
• Interest in helping raise the bar for future engineers as the team grows

What Makes This Role Unique

• Foundational ownership over the core platform architecture — backend, data, infrastructure
• Direct influence on how the system runs, scales, and stays up in customer environments
• Close collaboration with customers on platform integration and operational reality
• Opportunity to define the technical substrate for a new category of infrastructure
• Small, highly technical founding team with high trust and high velocity

Why Us

We believe the next major control point in enterprise security is runtime execution — not just who got access, but what is actually happening once authority is being used. If that thesis resonates, and you want to help build the system behind it, we'd like to talk.

‍