The role
What an outbound engineer does
An outbound engineer builds and runs the system, not the messages. The job is the five properties, kept true every day.
The title is starting to appear in job listings, usually meaning someone who wires cold email tools together. In outbound engineering it means something more specific: the person accountable for the sending infrastructure, the data layer and the handoff, and for the readings that show whether any of it is working.
The writing is not the center of the job. Copy is written with the sales team and changed by experiment. The center is the machine around the copy: a subdomain that stays warm, addresses that carry evidence, sequences that branch on behavior, and a board that shows what was measured.
The role can sit inside a company or inside a managed service. Either way the output is the same: conversations with people who fit the profile, in front of a salesperson within 60 seconds of the reply, and readings that say so.
What the work looks like in a week
Keep the domain healthy
Read each mailbox's placement daily, move caps with the reading, watch bounces and complaints, and hold or roll back a mailbox before a slip becomes a reputation loss. Warmup runs 6 to 8 weeks before any mailbox sends for real.
Keep the base honest
Score new companies against the written profile, grade every address as published, verified or inferred, and never let an inferred address reach a sequence.
Run the experiments
One change per segment per week, measured per message against real Gmail and Outlook. A change that does not move replies is rolled back.
Keep the handoff fast
Check the time from an interested reply to a person on the board, and fix the routing when it grows.
Publish the readings
Every number with its status and source. What is not yet measured is shown as not measured.
Not to be confused with. An outbound engineer in a call-center or telephony context designs dialing systems; an outbound engineer in logistics handles shipping. Those are different roles that share the words. This page describes the outbound engineering practice defined on this site.
Questions
Is this the same as a GTM engineer?
It overlaps. A GTM engineer wires the whole go-to-market stack. An outbound engineer goes deeper on one slice, the sending layer, the data layer and the handoff, and is accountable for the readings. The comparison page covers the difference in detail.
What skills does it take?
DNS and email authentication, enough data work to build and score a base with provenance, the discipline to run experiments and roll them back, and comfort reading readings rather than dashboards. Writing helps. It is not the job.
Can one person do it?
For one program, yes, with the components already built. The managed service on this site is one person running the machine for clients, on infrastructure built for exactly that.
The practice is defined on what is outbound engineering.
Bring your ideal customer profile. Leave with a plan for the first eight weeks.
Three screens, then thirty minutes with the person who builds the system. If outbound is not worth running for you, you hear that too.
Get your planAlready running outbound? Say so and we start from your deliverability numbers.