Technical Co-Founder (Backend / Execution & Integrations)
We are building
ZeroDrift™
, a patent-pending execution layer for AI systems. This work is based on engineering discovery and applied research, including white papers and empirical analysis informed by benchmarks such as the ARC evaluation framework. The core finding is simple but non-obvious: intelligence and execution are fundamentally different problems, and scaling one does not fully resolve reliability.
- Alan Turing proved computation itself could be formalized, giving us the theoretical foundation for all computing.
- Claude Shannon proved information could be transmitted reliably through noisy channels, giving us the engineering foundation for all digital communication.
- ZeroDrift™
proves stochastic intelligence can be forced into deterministic behavior through external constraint architecture, giving us the reliability foundation for all AI systems at scale.
Rather than making models smarter, this layer makes execution deterministic, auditable, and reliable. It allows organizations to deploy AI systems in production with guaranteed consistency and control.
This architecture eliminates the need for RAG workarounds, orchestration frameworks, and the endless retries and reruns that characterize current AI systems.
The core system architecture for this execution layer is already designed and protected. The remaining work is to implement it as a production-grade platform. We are looking for a technical co-founder who owns backend execution, integrations, and operational correctness, and not frontend polish, AI research, and architectural reinvention.
Most AI products avoid execution safety because it's difficult and unglamorous. We didn't.
This is infrastructure work at the boundary where computation turns into consequence.
You'll be implementing infrastructure that lets organizations use AI without giving it authority, a problem most teams don't know how to solve
Required skills & experience
- Strong backend / platform engineering background (7+ years)
- Extensive experience building and operating production APIs
- Experience integrating with third-party systems and external APIs
- Solid understanding of authentication, authorization, and secure system design
- Comfort working on systems where
blocking or refusing execution
is often the correct outcome
- Experience with approval flows, permissioned actions, or audit systems
- Preference for boring, explicit, durable systems over clever abstractions
- Founder-level ownership mindset
Backend & platform engineering
- 7+ years of professional backend or platform engineering experience
- Strong proficiency in at least one backend language, preferably:
- Python
- Go
- TypeScript (Node.js)
- Java
- Rust
API & integrations
- Extensive experience designing and implementing REST and/or gRPC APIs
- Hands-on experience integrating with third-party APIs (e.g. email, payments, repos, internal tools)
- Experience handling:
- retries
- rate limits
- idempotency
- partial failures
- webhooks
Security & access control
- Experience implementing:
- authentication (OAuth, JWT, service-to-service auth)
- authorization (RBAC, scoped permissions)
- Secure handling of secrets, credentials, and API tokens
- Experience building or operating systems with privileged actions
Data & state management
- Strong experience with relational databases (e.g. PostgreSQL, MySQL)
- Experience modeling explicit state machines or approval workflows
- Understanding of transactional integrity and consistency guarantees
Action gating & execution
- Building systems that intercept and evaluate actions before execution
- Implementing validation gates or pre-flight checks
- Experience with middleware/interceptor patterns
- Building systems where blocking execution is preferable to guessing
Reliability & operations
- Experience with:
- production monitoring
- logging
- alerting
- incident response
- Comfort reasoning about failure modes and unsafe edge cases
- Experience building systems that explain why they blocked or allowed actions
Strongly preferred (but not required)
- Experience in regulated or high-risk domains (finance, infra, security, compliance)
- Experience building audit trails or append-only logs
- Experience with deterministic rule evaluation or policy enforcement
- Familiarity with cloud infrastructure (AWS, GCP, or Azure)
- Experience using AI coding tools (e.g. Claude Code, Copilot) productively
- Preference for simple, explicit, boring systems over clever abstractions
What you would own
You will co-own and implement the
execution side
of the platform, including:
- Backend services and APIs that enforce execution safety
- Integrations / connectors with real systems (e.g. email, payments, repos, internal tools)
- Authentication, authorization, secrets, and privileged operations
- Deterministic execution flows, failure handling, and refusal conditions
- Audit logging and execution receipts
The architecture is fixed. Your responsibility is to
make it real, reliable, and safe
.
What you will
not
own
- AI research or model training
- Prompt engineering
- Redefining system philosophy or architecture
The UI is intentionally
boring, thin, and secondary
. It will be built as a minimal admin interface on top of backend APIs, using standard frameworks and AI-assisted coding tools where appropriate. All authority lives in the backend.
What this is not
- Not a salaried role (equity only until research grants close, then salary + equity)
- Not a full-stack or frontend role
- Not an “agent” or autonomy project
- Not a greenfield architecture exercise
The hard thinking is done. The hard building remains.
Rad na daljinu: Da