Founding Engineer

About the role

Founding Engineer — Orange Slice (YC)

About Orange Slice

Orange Slice helps revenue teams prospect, enrich, qualify, and automate GTM work with AI. Customers use it to turn messy intent and company context into actionable lists, enriched records, and workflows—from firmographics and contact verification to web research, social signals, and outreach drafting. The product spans a polished web experience (including spreadsheet-like execution and an AI agent) and tooling for builders who want the same capabilities in code or in Claude Code via a single install path.

We sit at the intersection of B2B data, LLMs, and workflow automation—where reliability, cost control, and great UX matter as much as model quality.

The role

We’re hiring a Founding Engineer to own major slices of the product and infrastructure alongside the founders. This is a high-ownership, high-trust role: you’ll ship user-facing features, harden core systems, and help define how we scale—not just close tickets.

You might work on:

-

Core product: Next.js App Router surfaces (dashboard research tools, spreadsheet workflows, agent/chat UX), performance, and end-to-end flows from signup to paid usage.

-

Data + AI execution: orchestrating long-running enrichment and research jobs, streaming UX, provider integrations, and guardrails (cost, retries, observability).

-

Billing and usage: subscriptions, credits/ledger, org vs. personal accounts—systems that must be correct under load and easy to reason about.

-

Platform: Supabase-backed Postgres (including RLS-aware patterns), background jobs (e.g. Inngest), and services that fan out heavy work reliably.

30 days

You’ll ship improvements to our multi-step agentic research workflow (tool orchestration, reliability, and UX at the boundary between LLM reasoning and real data execution) and take primary ownership of our Inngest pipeline—event design, step boundaries, retries, observability hooks, and safe rollout patterns—working closely with whoever owns the batch service and API routes today.

60 days

You’ll own a measurable slice of production reliability: cut a class of failures (timeouts, stuck runs, duplicate side effects, or stream resume issues), and instrument it so regressions are obvious (logs/traces/metrics—bonus if you’ve used LLM observability tools).

90 days

You’ll lead a multi-sprint initiative that compounds—examples: faster/cheaper agent execution, a major schema/migration win, a billing/credits hardening project, or a step-change in streaming UX quality under load—documented with before/after metrics from production.

What we’re looking for

- Strong TypeScript and comfort owning features full-stack (React/Next patterns, server routes, database design).

- Bias to ship: you break work into milestones, default to simple designs, and iterate with real users.