Founding engineer vs first AE: which unlocks growth sooner?

Founders often ask a binary question after raising: should we hire a founding engineer or our first AE first? The useful answer is not binary; it’s bottleneck-first.

Hire engineering first when the product cannot yet support the GTM story you’re selling. Signs: roadmap slips every sprint, founders own most production code, enterprise pilots stall on missing features, or technical debt blocks shipping. A senior/founding engineer (or eng lead) creates leverage so the next hires have something to build on. Scaling sales into a product that isn’t ready burns pipeline and reputation.

Hire GTM first when the product is good enough and revenue is the constraint. Signs: inbound or outbound demand exists, founders are the only closers, and you have at least a rough repeatable motion. An AE who can run a cycle, or an SDR/AE pair once infrastructure exists, converts capital into ARR. Hiring a VP Sales before that motion exists is a common Series A failure mode.

A practical heuristic used across startup recruiting: if engineering can execute but the roadmap is incoherent, you may need product leadership. If the roadmap is clear but delivery is slow, you need eng leverage. If delivery is fine but pipeline is thin, you need GTM after basic CRM/process hygiene.

Wrong-order hires are expensive. An AE without a shippable product churns. An engineer without a path to customers builds in a vacuum. Sequence the seat that unlocks the next milestone, then hire the other.