Open roles
Positions at companies building their go-to-market team around the four Syntropy roles. New to the model? Explore the four roles.
Engineering Intern
Engineering Intern for T2D3 OS The ground floor of the platform team — where the Systems Engineer path begins. The Engineering Intern is the newest builder on the core T2D3 OS team, learning the platform from the ground up. AI can wire infrastructure together, fire deploys, and pass the easy tests; you learn to read what it produces, catch what it gets wrong, and keep the gates honest before anything ships. The founder writes the product with Claude Code, the product lead shapes what gets built, and the Founding Systems Engineer owns the platform it all runs on — you come in alongside them, on the real codebase, from your first week. You come in curious, not finished. This starts as an unpaid, semester-length internship built around your class schedule — the pay up front is real production experience, mentorship, and work that ships to customers from day one. It's built to grow: strong interns convert to a paid part-time seat, and from there become eligible for founding equity as the platform and the team grow. Most internships won't look at you before your junior or senior year. We will, because we hire for trajectory, not résumés. Come in with curiosity, drive, and a sense of ownership, and we'll meet you at the very start of the ladder below — the same ladder the Systems Engineer sits further up — and grow together, teaching, pairing, and backing you the whole way. What you'd do Write and run the tests that prove new code is sound, and keep them green Help keep deploys, environments, and monitoring healthy — and learn the runbook by working it Build small, well-scoped features and fixes behind the platform's security, with a human check before they merge Wire up and test MCP connectors and agent workflows, and keep the AI's output honest before it ships Help stand up and drill the backup instance, and see for yourself what proven recovery actually means Turn a vague problem into a small, shippable piece — and then ship it How it's different from a traditional seat You're not fetching coffee or writing throwaway scripts that never see daylight. This is real work on the real platform, next to the founders. The founder owns the functionality, the Systems Engineer owns the platform and the gates — and you're here to learn how both hold, by doing the work under people who want you to get good. AI does the boilerplate, so what you're really building is judgment: the ability to tell when the machine is wrong before it reaches production. Where you might come from First- and second-year CS or related students, self-taught builders, hackathon regulars, and anyone who's shipped a side project, a bot, a game, or a script for the fun of it. A curiosity about how systems fail — and how you'd stop them — is worth more to us than a long résumé. You don't need to have done this before; you need to want it. You might be a fit if… You've built something real, and you can show it to us You're curious about how things break and who they expose, not just how to make them work You already use AI tools, and you're honest about where they help and where they lie You can read code you didn't write and work out how it behaves You're energized, not threatened, by an AI-native workflow with tools like Claude Code and agents The stack you'll work in Next.js 15 on Vercel, with Supabase at the heart: Postgres across roughly 150+ production tables, authentication, 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. You won't know all of it on day one — nobody does. You'll learn it by building in it, next to the person who owns it. 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. Interns join at the ground floor of the Operator rung and grow from there — the same path the Founding Systems Engineer is further along. 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. A friendly note on the journey: the real unlock isn't typing faster than the AI — it's the judgment to know what's worth building and when the model is wrong. That's a muscle we help you build, and it's what opens up the next rung. How to apply We'd love to see something real. Send us one thing you built — a repo, a live site, a game, a script, anything — and a couple of sentences on what you'd change if you built it again. And if you have one, show us something you made with an AI tool and tell us what you had to fix in what it gave you. That last one tells us more than any transcript could — we're looking for the person who can tell when the machine is wrong. We read for judgment, not buzzwords, and we reply to everyone who writes something real.
Product & Usability Research Intern
Product & Usability Research Intern for T2D3 OS The person who watches real users and tells us the truth. The Research Intern owns the outside-in view of the product. AI can generate infinite UI and infinite copy; it cannot watch a real person get confused, hesitate, and quietly give up. You can. You run usability sessions, find the friction, and turn what you see into evidence the team acts on. The founder builds the product with Claude Code, the product lead shapes what gets built — you're the one who brings them the ground truth about how it actually lands. You come in curious, not finished. This starts as an unpaid, semester-length internship built around your class schedule — the pay up front is real product experience, mentorship, and findings that change what gets built. It's built to grow: strong interns convert to a paid part-time seat, and become eligible for equity as the team grows. CS, HCI, design, and psychology-curious students all fit. Most internships won't look at you this early. We will, because we hire for trajectory, not résumés. Come in with curiosity, care, and a good ear, and we'll meet you at the start of the ladder below and grow together — teaching, pairing, and backing you the whole way. What you'd do Run moderated usability sessions on onboarding and the core flows, and take careful, honest notes Turn what you observe into prioritized, evidence-backed findings — not opinions, not vibes Read basic product signal (funnel drop-off, Sentry web-vitals) to back a finding with a number Partner with the engineering intern to turn "this was confusing" into a reproducible issue Help decide what we test next, and close the loop by checking whether a fix actually worked How it's different from a traditional seat You're not filling out survey busywork that no one reads. Your findings go straight to the founder and product lead and change what gets built next. AI can draft the screens; you're the reason the right screens get drafted. What you're really building is judgment — the ability to separate what a user says from what a user does. Where you might come from First- and second-year students in CS, HCI, design, psychology, or anything adjacent — plus self-taught tinkerers who've always been the friend people hand their phone to and say "why won't this work?". A genuine curiosity about why people get stuck is worth more to us than a long résumé. You don't need research experience; you need to want to understand people. You might be a fit if… You can say why a flow is confusing and what specifically you'd change You'd rather watch one real person use the product than guess with ten opinions You write findings other people can actually act on You're honest — you report the awkward truth even when it's about work someone loves You already use AI tools and are clear-eyed about where they help and where they mislead The stack you'll work in The live T2D3 OS product itself, plus the tools around it: session recording and note-taking, funnel and drop-off signal, Sentry for real front-end performance data, and Claude Code and MCP agents as part of the daily working environment. You'll learn it by doing the work next to the people who own the product. How you grow as a Scribe Investigative journalist, researcher, and storyteller. AI can rearrange words it has already seen; the Scribe uncovers the primary truth — the unspoken customer phrase, the real reason a flow fails — that AI cannot invent because it exists nowhere else yet. Interns join at the ground floor and grow from there. Drafter, Level 1 of 4 Produces clean, clear findings and notes with AI assistance. Captures sessions accurately and writes them up clearly and without spin Every finding has a stated "what happened" and "why it matters" Reliable turnaround, session after session Level up: Stop just recording sessions — go find the friction no one has named yet, and own one flow's research end-to-end. Researcher-Interviewer, Level 2 of 4 Extracts signal from real users — sessions, interviews, primary observation. Runs sessions that surface an unspoken truth the team hadn't seen Captures the exact words and moments where users get stuck Backs findings with real signal and lets AI handle the secondary research Level up: Turn one-off findings into a system — build a living map of where the product creates friction and set the bar others research to. Narrator, Level 3 of 4 Owns the point of view on how the product actually lands; sets the research standard. Maintains the living canon — personas, journey notes, the friction map Produces insight the team can't get anywhere else because it rests on primary observation Trusted to say what the product gets wrong, and heard when they do Level up: Stop generating findings and start generating understanding — define how the whole team thinks about the user. Voice, Level 4 of 4 The org's understanding of its users is theirs; the research itself changes the roadmap. The team's picture of who it's for and what they need is one they authored Answers user questions no one else has answered well Insight alone moves what gets built Level up: Ceiling rung; the move is outward — mentor the next researcher and put the standard into the system so it outlives you. A friendly note on the journey: the real unlock isn't running more sessions than anyone else — it's the judgment to tell what a user says from what a user does, and to know which friction actually matters. That's a muscle we help you build. How to apply Tell us about a time you watched someone use something — an app, a form, a game, a tool — and spotted why it was confusing. What did you notice, what would you change, and how would you know the change worked? If you've ever done this with something you built yourself, even better. We read for judgment, not buzzwords, and we reply to everyone who writes something real.
Growth Engineer
Growth Engineer for T2D3 OS The architect of the systems that carry signal across marketing and sales. The Engineer owns the GTM and RevOps systems that move signal across marketing and sales — enrichment, scoring, routing, enablement, and the CRM backbone underneath them. AI can stitch tools together and fire sequences; you're the one who decides what should connect, builds the quality gates that keep things clean as they scale, and turns raw signal into real, compounding leverage. The Scribe shapes the story and the Navigator sets the strategy — you build the systems both run on. In short: you love designing the machine, not waiting around for the next task. And here's the best part — this is a real seat on a working pod, and it's built to grow. We hire for trajectory, not for a finished résumé, so you don't need to know everything on day one. Come in with curiosity, drive, and a sense of ownership, and we'll meet you wherever you are on the ladder below and grow together, teaching, pairing, and backing you the whole way. The kind of teammate we're looking for This is the heart of the role, so we want to be warm and upfront about it. In our pod, you get to own real outcomes — not just the tasks that sit neatly inside your specialty. That's the fun part: you'll often pick up something a little beyond your current toolkit, and that's exactly where the growth happens. Owning an outcome doesn't mean knowing it all up front. It means you're the one steering, with the whole team — and a flex pod of specialists — ready to jump in and help you land it. We love teammates who are resourceful and collaborative. When something's in the way, you go find the answer or the person who has it, and you keep a human eye on what the AI produces before it ships. You'd rather cut a noisy signal than pile on one more tool, because here, good judgment beats raw volume every time. If that sounds energizing rather than daunting, you're going to feel right at home. What you'd do Own the GTM/RevOps stack for the pod's accounts end to end — enrichment, signal scoring, routing, enablement, and the HubSpot/CRM backbone Build signal-based systems (intent scoring, enrichment waterfalls, routing) that connect straight to pipeline, not vanity dashboards Treat ICP, personas, and messaging rules as living infrastructure the AI consumes — kept locked in T2D3 OS, not scattered across docs and one-off LLM sessions Orchestrate AI agents through MCP so every output inherits who-it's-for and what-it's-for without drift, with a quick human review before anything reaches a rep or client Build the quality gates that catch bad data or weak signal early, before it scales Own the plumbing in your lane — HubSpot setup, forms, workflows, CTAs, DNS, ABM systems — bringing in specialist help when it speeds things up, while keeping the result yours How it's different from a traditional seat This is bigger than running campaigns or living inside a single tool. You own the systems that carry signal across the whole funnel, and you've got real room to shape them. You can pull in the flex pod for specialist work, and the outcome still belongs to you — that clarity is exactly what lets the pod move fast. And whenever you can build the system once instead of doing the task by hand forever, you go for it. Where you might come from RevOps and marketing-ops engineers, marketing-automation specialists ready to grow past a single tool, GTM and growth engineers, demand-gen ops, sales engineers, and technical marketers who'd rather build the systems that run go-to-market than run them by hand. Strong HubSpot/CRM, data, and automation instincts are what we value most — paired with a real appetite to keep learning. You might be a fit if… You naturally ask "who is this signal for, and is it worth acting on?" before reaching for another tool or campaign You measure a good week in meetings booked and hours of busywork eliminated, not dashboards launched You enjoy owning outcomes, even when the work stretches past your specialty — you bring in help, and you see it through You don't need to know it all; you're genuinely excited to learn the next thing, and you keep a human check on what the AI gives you You're energized, not threatened, by an AI-native workflow with tools like Claude and MCP agents The stack you'll work in T2D3 OS is home base — it brings together signals, locked-in ICP and personas, OKRs, KPIs, and the projects and tasks that connect to them, plus the AI creation tools the pod builds on. Around it: HubSpot at the center of the CRM, forms, workflows, and website plumbing; enrichment, sequencing, and routing tools; DNS and domain setup; data analysis; and AI agents orchestrated via MCP, with Claude as a daily working environment. And a flex pod of specialists is always there to pull in when a task needs an extra set of hands. How you grow as an Engineer Designs, automates, and protects the systems that carry and amplify signal across marketing and sales. The Engineer is the Syntropy job family that turns signal into leverage. AI can stitch tools together and fire sequences; the Engineer decides what should be connected, builds the gates that keep clarity as you scale, and makes growth compound instead of crack. Thinks like an architect, not a campaign runner. Here's the path, whichever rung you join on. A friendly note on the journey: a lot of engineers find the real unlock isn't sending more, faster — it's the judgment to know which signal deserves action and when to simplify. That's a muscle we help you build, and it's what opens up the next rung. How to apply We'd love to hear a real story or two. Tell us about a GTM or RevOps system you built, or a manual process you automated — what was getting messy, what you changed, and how you knew it worked (meetings booked, hours saved, errors caught). And if you have one, share a time you took on something new and made it happen: what you learned along the way, and who you leaned on to get there. We read for judgment and ownership, not buzzwords, and we reply to everyone who writes something real.
Founding Systems Engineer
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.