Founding Product Engineer

About the role

As a Product Engineer at Cardinal, you'll work on the surfaces our customers — founders, GTM leaders, sales engineers — live in every day. This includes our sequence and enrollment system, the Cedar agent layer, and the eval and observability tooling.

Responsibilities

• Work on the surfaces our customers live in every day, including our sequence and enrollment system, the Cedar agent layer, and the eval and observability tooling.
• Ship to production every week.
• Have an outsized influence on what the product becomes.

Requirements

• You're your own worst critic. You don't ship at 90%. You don't just file the bug — you fix it.
• You can tell the difference between a UI that feels good and one that doesn't, and you can articulate why.
• You think from first principles about user workflows, not feature checklists.
• You've worked at a sales-adjacent company — an outbound tool, a CRM, a sales intelligence platform, a revenue-tech startup — or you've been the technical person at a startup who actually built and ran the outbound motion yourself.
• You've worked on real-time collaborative interfaces, agent UIs, or eval/observability tooling.
• You care about design at the level of Linear, Attio, Raycast, or Vercel — and have shipped UIs at that quality bar.

Qualifications

• Have founded a company, been an early engineer at a YC-stage startup, or shipped a product 0→1.
• Have built or worked at a GTM/sales/CRM/enrichment tool — Apollo, Outreach, Clay, Attio, HubSpot, Salesforce, Gong, Common Room, or anything in that orbit.
• Are a power user of GTM tools yourself — you've actually run outbound, written sequences, and fought with deliverability.
• Have worked on real-time collaborative interfaces, agent UIs, or eval/observability tooling.
• Care about design at the level of Linear, Attio, Raycast, or Vercel — and have shipped UIs at that quality bar.