Founding Systems Engineer for T2D3 OS

The architect of the platform everything else runs on.

The Systems Engineer owns the platform, its security, its reliability, and the quality system that decides what ships. AI can wire infrastructure together, fire deploys, and run tests; you decide what the platform should be, build the gates that stop bad code and entropy from scaling, and turn raw infrastructure into compounding leverage. While the founder writes the product code with Claude Code and the product lead shapes what gets built, you own the ground both stand on. You think like an architect, not an operator waiting for the next alert.

This starts part-time and is paid mostly in equity, a real founding stake, not a contract in disguise. And while the description above is the senior end of the work, we hire for trajectory. If you are earlier in your career but bring ambition, grit, and aligned values, we are open to meeting you lower on the ladder below and leveling up together.

What you'd do

• Design the platform end-to-end, security, scalability, deployment, and disaster recovery
• Own Supabase Row Level Security so tenant data stays sealed as we scale
• Build the CI/CD gates and automated tests that stop bad code and entropy from shipping
• Stand up a tested backup instance with a real recovery point and recovery time, proven by drill
• Orchestrate monitoring and runbooks so the system self-heals before a human is needed

How it's different from a traditional seat

You're not babysitting someone else's infrastructure or living in a support queue. You design the architecture and the guardrails, and increasingly you automate the operations that used to eat the day. The founder owns the code. You own the platform, the gates, and the quality system. We move faster because those don't blur.

Where you might come from

Site reliability engineers, platform and DevOps engineers, security-minded backend engineers, and infrastructure-leaning full-stack developers who would rather build the systems that run the product than run them by hand. Strong Supabase and Postgres experience, especially Row Level Security and performance, is the thing we value most.

You might be a fit if…

• You instinctively ask "how does this fail, and who does it expose?" before adding capacity
• You measure success in incidents prevented and hours of toil eliminated, not systems shipped
• You're excited, not threatened, by building in an AI-native workflow with tools like Claude Code
• You'd rather ship a runbook and a self-healing system than be the hero who's always online

The stack you'll work in

Next.js 15 on Vercel, with Supabase at the heart: Postgres across roughly 126 production tables, authentication, Row Level Security, storage, and edge functions. GitHub for source and CI. Capacitor for mobile, MCP connectors for AI agents, and Claude Code as the daily working environment.

How you grow as a Systems Engineer

Designs, automates, and protects the systems that carry the product at scale. The Engineer is the Syntropy job family that turns infrastructure into leverage. AI can stitch infrastructure together and fire deploys; the Engineer decides what should exist, builds the gates that stop entropy from scaling, and makes the platform compound instead of crack. Thinks like an architect, not an operator. Here is the path, whichever rung you enter on.

Operator, Level 1 of 4

Keeps the platform running. Deploys, environments, monitoring, and backups stay healthy and on time.

• Keeps deploys, environments, monitoring, and backups running without breakage
• Executes test runs and routine operations reliably and on time
• Follows the runbook accurately and keeps the alerting clean and trustworthy

Level up: Stop doing ops by hand and start building the systems that do it for you. Automate the repeatable, instrument the rest.

Builder, Level 2 of 4

Builds the automation and the gates. CI/CD, infrastructure as code, and the test suites that protect every merge.

• Ships CI/CD pipelines, infrastructure as code, and automated tests that gate every merge
• Treats security checks and quality gates as code the pipeline enforces, not manual reviews
• Reduces toil measurably, judged on incidents prevented and hours saved, not scripts written

Level up: Think like an architect. Design the platform end-to-end and own the security and scalability calls, not just the automation beneath them.

Architect, Level 3 of 4

Designs the platform end-to-end. Security posture, scalability, and disaster recovery, with judgment that cannot be scripted.

• Owns security posture, Row Level Security design, scalability architecture, and disaster recovery
• Builds privacy-by-design and a recovery capability proven by drill rather than asserted on a slide
• Makes the high-leverage calls, including when the modular monolith should begin to fracture

Level up: Make reliability and security compound across the product. Set the standards and coach others to build to them instead of owning every system yourself.

Systems Strategist, Level 4 of 4

Runs an instrumented, compounding platform. The product scales without the operational load scaling with it.

• Success is measured by uptime sustained, breaches avoided, and toil eliminated across the org, not systems shipped
• Reusable platform and guardrails let the product grow while the Frankenstack shrinks and the architecture matures
• Coaches and hires the platform team so reliability multiplies everyone's output, not just their own

At the top: Ceiling rung. The move is outward, setting the platform and security standard the org and market are measured against.

How to apply

Tell us about the hardest reliability or security problem you have personally solved, what broke, what you changed, and how you knew it was fixed. If you have ever stood up a backup of a production system, tell us your recovery point and recovery time and how you proved them. We read for judgment, not buzzwords, and we reply to everyone who writes something real.