Engineer

The architect of the systems that carry signal at scale.

The Engineer owns systems, RevOps, GTM engineering, and agent orchestration. You design, automate, and protect the machinery that carries signal across marketing and sales. AI can wire tools together and fire sequences; you decide what should be connected, build the quality gates that stop noise from scaling, and turn signal into compounding leverage. You think like an architect, not a campaign runner.

What you’d do

Design the GTM/RevOps stack end-to-end — enrichment, scoring, routing, enablement
Build signal-based systems that connect directly to pipeline, not vanity dashboards
Orchestrate AI agents (via MCP) so outputs inherit who-it's-for and what-it's-for without drift
Build quality gates and privacy-by-design so scaling creates clarity, not entropy
Design growth loops that compound signal over time instead of one-off campaigns

How it’s different from a traditional seat

You're not running campaigns in someone else's stack. You design the architecture and the guardrails — and increasingly you orchestrate the AI agents that do the running.

Where you might come from

Marketing-ops and RevOps pros, growth engineers, marketing automation specialists, and analytically-minded marketers who like building systems more than running them.

You might be a fit if…

You instinctively ask "what should this connect to?" before adding another tool
You measure success in meetings booked and hours saved, not tools launched
You're excited (not threatened) by orchestrating multiple AI agents

Three ways to be a Engineer

The role has one job; the people who do it well start from different places. These are the three ways we have seen it done. Each has a different first move and a different idea of what counts as evidence, and T2D3 OS names the one that fits whenever it does this kind of work.

Marketing Operations Engineer

Daniel Osei

First move. Opens the CRM before opening a conversation: which objects exist, which fields are populated, which lifecycle stages actually fire, and where the same concept lives under three names. Does not trust a funnel report until he has traced one record from form fill to closed-won by hand.

How they explain a decision. Explains decisions in terms of what the data will and will not be able to prove afterward. Never calls a setup best practice — says what question it answers and what question it makes unanswerable.

Strongest evidence: A pipeline report that finance stopped rebuilding in their own spreadsheet.

Web and Performance Engineer

Lucía Fernández

First move. Starts with a Lighthouse run and a DNS lookup. Before reading the design she wants to know how the site is hosted, what sits in front of it, how many third-party scripts load before the first byte of content, and who owns the domain registrar login. A beautiful site on a broken foundation is a liability with a launch date.

How they explain a decision. Explains decisions in milliseconds, error rates, and what happens when a vendor goes down. Never calls a stack modern — describes its failure modes and how long recovery takes.

Strongest evidence: A site with no unplanned outage in a year that still scores green after a dozen content releases she was not involved in.

AI Workflow Engineer

Arjun Mehta

First move. Finds where the signal lives and how it gets to the model. A prompt is the least important part of a workflow; what feeds it and what checks the output matter more. He traces a piece of content from the customer call that inspired it through the transcript, the verbatims, the voice guide, the generation step, the human review, and the published page, looking for the point where quality leaks.

How they explain a decision. Explains decisions in cost per accepted output, review time saved, and how often a human overrode the machine. Never calls a workflow intelligent — describes what it gets right unaided and what still needs a person.

Strongest evidence: A CMO who has stopped re-explaining context to a chatbot, and a monthly AI bill that went down while output went up.

The people named here are composites, not staff or candidates — each one describes a way of doing the role, drawn from the practitioners we have worked with.

How you grow as a Engineer

Designs, automates, and protects the systems that carry and amplify signal across marketing and sales. AI can stitch tools together and fire sequences; the Engineer decides what should be connected, builds the quality gates that stop entropy from scaling, and turns signal into compounding leverage. Thinks like an architect, not a campaign runner.

1
Operator
Level 1 of 4
Runs the tools, campaigns, and data hygiene that keep the GTM machine moving.
- Keeps the stack, sequencers, enrichment, and routing running without breakage
- Executes campaigns and reporting reliably and on time
- Follows the playbook accurately and keeps data clean
Level up: Stop running campaigns and start building the systems that run them — automate the repeatable and instrument the rest.
2
Builder
Level 2 of 4
Builds AI-driven systems — enrichment waterfalls, signal scoring, routing, and multi-agent and sales-enablement workflows.
- Ships signal-based systems (intent scoring, enrichment, routing) that connect directly to pipeline
- Treats ICP, personas, and messaging rules as infrastructure the AI consumes, not static docs
- Runs experiments to optimize resonance, measured on meetings booked and hours saved, not dashboards launched
Level up: Think like an architect — design the stack end-to-end and add quality gates that preserve clarity as you scale, rather than adding one more tool.
3
Architect
Level 3 of 4
Designs the GTM and RevOps stack end-to-end — outbound, ABM, enablement — with coherent agent and MCP orchestration.
- Designs growth loops that compound signal over time instead of one-off campaigns
- Builds quality gates and privacy-by-design so scaling does not create entropy
- Orchestrates multiple agents through MCP so outputs inherit the syntropy map (who it's for, what it's for) without drift
Level up: Make growth compound across marketing and sales — coach other operators to use the systems to their fullest instead of owning every build yourself.
4
Systems Strategist
Level 4 of 4
Runs an instrumented, compounding growth engine across marketing and sales; coherence is preserved at scale.
- Success is measured by signal preserved and amplified across the funnel, not campaigns launched
- Reusable workflows scale clarity instead of complexity; the Frankenstack shrinks as the architecture matures
- Coaches the whole team so the system multiplies everyone's output, not just their own
At the top: Ceiling rung; the move is outward — set the GTM engineering standard others in the org and market are measured against.

What the Engineer actually does all day

The long-form piece on how this seat changed, and why the work is worth doing now.

Read the Engineer deep dive

Do Engineer work, starting now

List yourself on the T2D3 marketplace and B2B SaaS teams bring you scoped briefs — no proposals, no bidding, paid straight to your bank.

Join as a Engineer

Looking for a salaried seat instead? See open Engineer roles