Founding Engineer (Full Stack)

About the role

Merrily reads every customer conversation, meeting, product event, invoice, and contract across the tools a SaaS company already runs, and turns them into a live health score for every account. As a founding engineer you will own large surfaces of that product end to end, from the integrations that pull signal out of Slack, Gmail, HubSpot, and Stripe, to the scoring pipelines, to the dashboards customer success and RevOps teams live in every day.

This is an early, high-trust role on a small team. You will help set the technical direction, the bar for quality, and the way we work. The product is AI-heavy, but most of the job is excellent, pragmatic full-stack engineering: clean data models, reliable pipelines, and interfaces people trust enough to act on.

What you'll do

• Build and ship features across the stack: TypeScript and React on the front end, Node and PostgreSQL on the back end.
• Design the integrations that ingest customer signal from Slack, Gmail, meeting notes, HubSpot, Stripe, PostHog, Postgres, and PandaDoc, including auth, sync, and backfill.
• Turn raw signal into account-level health scores that teams can trust, and surface the evidence behind every score.
• Own data modeling decisions for a system where freshness, lineage, and correctness all matter.
• Partner directly with early customers in customer success and RevOps to understand what actually moves a renewal.
• Set up the boring-but-critical foundations: observability, testing, and CI that keep a fast-moving team honest.

What we're looking for

• 5+ years building and shipping production web applications, with real ownership of features from idea to launch.
• Strong full-stack fundamentals: a modern typed front end (we use React and TypeScript) and a server-side language with a relational database (we use Node and PostgreSQL).
• Comfort designing schemas and writing SQL for systems where data quality is the product.
• A bias toward shipping, paired with the judgment to know when correctness cannot be compromised.
• Strong written communication and the self-direction to thrive in a small, remote, early-stage team.

Bonus points

• You have built third-party integrations (OAuth flows, webhooks, rate-limited sync) before.
• You have worked on data-intensive products: pipelines, event ingestion, or analytics surfaces.
• You have shipped LLM-backed features and understand their failure modes.
• You have been an early engineer at a startup and know what the first 18 months actually feel like.

Why Merrily

Customer success and RevOps teams still find out about churn too late, from surveys nobody fills out and CRM fields nobody updates. We think the signal is already there, in the conversations and the product, and the job is to read it well. If building that sounds like your kind of problem, we would love to talk.