We're hiring a Founding Engineer to build the agentic platform that runs the next generation of consumer brands.
## 🚀 The Opportunity
Corvera is the AI sales agent for CPG brands.
A brand's next sale might be hiding in an account that stopped ordering, a core SKU missing from shelves, or a distributor running low on stock. The evidence is scattered across distributor feeds, retailer portals, syndicated data and ERPs. Corvera brings it together and identifies what actions the sales team should do next, and soon - executes those actions autonomously.
Our near-term ambition: **enable the next billion-dollar CPG brand to be built by fewer than 10 people**.
There is serious engineering between here and there. That's the opportunity.
## 📈 Where We Are Now
* Backed by Y Combinator (W26), top 10% of the batch
* $0 to $35K MRR in 2 months, with customer demand outpacing capacity. Our plan is to grow 20% MoM all of next year and beyond.
* $6.3M raised since October 2025, from leading VCs such as Firstminute Capital, 6 Degrees Capital, 20VC, Rebel Fund, and Y Combinator
We've proven the urgency. Now we need your help to build the platform that scales it 100x.
## 🧠 The Role
We’re looking for an experienced engineer who wants to **solve hard problems**, write the code, and help shape both the platform and the company.
**You’ll wear many hats:** architect, product engineer, data engineer, SRE, FDE, AI engineer, and the person who digs into a production failure and fixes it properly. One week you might redesign how we connect a new data source; the next, ship an agent capability or make our infrastructure ready for the next wave of customers. You’ll take work from an ambiguous problem to a solution customers depend on.
And **you’ll raise the bar for engineering excellence**. Through the systems you build, the decisions you challenge, and the standards you put into practice, you’ll help us become a team that consistently ships exceptional work. We want your experience, your judgment, and your ambition in the room - and your code in production.
## 🛠 What You'll Actually Build
You’ll help us solve hard engineering problems including:
* **Enterprise integrations, productized**. NetSuite, Shopify, Xero, Walmart, Target, Amazon, ShipHero, and many more - wrapped behind one provider interface and exposed to the agent through MCP, with in-loop credential refresh.
* **Orchestration that never drops the ball**. Schedules, retries, durable execution, full run history, replay, alerts, version control. Every workflow is observable and recoverable - so a Wednesday failure isn't discovered on Friday.
* **Ontology -** the brand's business model in writing. A queryable, governed source of truth for what each customer actually means by "forecast", "SKU", or "fiscal year-end". Mappings, calendar rules, metric definitions, constraints, full lineage back to the source file and download time. You'll design the schema and the APIs agents query against it - so business logic stops being re-derived in every spreadsheet.
* **The agentic layer.** Build agents that identify sales gaps, make plans, optimize scenarios, and propose actions, eventually executing them too. Make improvement recursive: outcomes and corrections feed evaluations, validated improvements strengthen the next run, and the cycle repeats.
* **Observability across the stack**. A turn's full lifecycle inspectable from a single trace ID across Vercel, Render, Daytona/Blaxel, etc.
## 🪜 The Stack
* Backend: Python 3.12, FastAPI, React Server Actions, Next.js, MCPs, Eve Agent Harness, vector databases
* Frontend: Next.js 16, React 19, Vercel AI SDK, Tailwind, shadcn, Vercel
* Data: Supabase / Postgres, Analytical DB agnostic (Snowflake, Bigquery, Redshift, Clickhouse, etc)
* Sandboxes: Vercel sandboxes
* External: Anthropic, AgentMail
* Observability: Grafana
* Repo: Turborepo, pnpm, GitHub Actions, isolated PR previews (frontend + backend + DB branch per PR)
## 🧬 What We're Looking For
You're a great fit if:
* **You've done this before.** You helped take a startup from pre-seed or seed to Series A or B. You personally built the systems that carried it through that growth and can explain where they held up, where they failed, and what you changed.
* **You design systems, not just features.** You've given a growing codebase clear module boundaries and small interfaces. You can defend a design against a credible alternative and recognize when the alternative wins.
And you have expertise in one or many of these areas:
* **Data modelling and ontologies**. Migrations, schema design, query plans, lock contention. You've modelled domains where business meaning was load-bearing: taxonomies, lineage, versioning, governed terms.
* **AI agents.** Agentic harnesses, context management, tools and MCPs, evals, observability, memory and continual learning, search and retrieval, vector databases, knowledge graphs, coding agents and skill generation.
* **Software architecture**. You know when to apply architectural patterns including DDD, hexagonal, event-driven, state machines, modular monolith vs services, layered dependencies. SOLID and composition-over-inheritance are muscle memory. Refactors don't scare you.
* **Testing and quality**. TDD, integration, canaries, e2e - you know which to reach for.
* **SRE and DevOps**. Continuous delivery, blue/green or canary, feature flags, instant rollback. Dashboards, alerts, SLOs, preview envs. You've carried a pager.
* **Enterprise integrations.** ERP, 3PL, or retailer portal in your past. NetSuite, Shopify, Xero, SAP, Snowflake - any is a strong signal.
* **Backend in Python**. 4+ years of experience in production. FastAPI / asyncio fluency. You spot event-loop blockers in review.
* **Frontend in TypeScript.** 3+ years of experience shipping real Next.js or React.
* **Operating velocity.** AI-assisted dev as default - Claude Code, Cursor, Codex. **You dream of building a software factory.**
## 🚫 This role is not for you if
* You need heavy structure or management to be effective.
* You want the system settled before you join. It’s your job to build it.
* You think "the agent did it" is a satisfactory excuse in a post-mortem.
## 🌍 Why Join
* Build from anywhere in LATAM. Work remotely, with regular opportunities to get together in person.
* Grow with the company. Join while your decisions can still shape the product, the engineering team, and your own role. Take on bigger challenges as Corvera grows.
* Do work that matters to customers. Ship capabilities people use to grow their businesses. See the impact, hear the feedback, and make the next version better.
* Help build an exceptional engineering culture. Work with people who care about craft, welcome a challenge, share what they learn, and help each other reach a higher standard.
* Have a real stake in what you build. Meaningful equity, a competitive package, and ownership from technical decisions through to production.
## 🥇 Who Are We
We’re [Christopher Kong](https://www.linkedin.com/in/cwnkong/) (2x founder; ex-CEO of Better Nature; Forbes 30 Under 30), [Dirk Breeuwer](https://www.linkedin.com/in/dirkbreeuwer/) (ex-Google Data & AI Lead), and [Berk Güngör](https://www.linkedin.com/in/berk-g%C3%BCng%C3%B6r-35196a14a/) (Founding Engineer and Head of AI Engineering; 6+ years in applied AI).
Chris built and scaled a successful CPG brand, Better Nature, and saw costs rise in step with growth. That's where the vision for an AI-native CPG company came from. Dirk spent 10 years building data infrastructure and AI automation for retail, first at a large multi-Latin conglomerate in Guatemala, then at Google on Pixel. A mutual friend introduced us, and we both knew we were onto something. Dirk quit Google, and within two weeks we'd raised our pre-seed and got into YC.
Our mission: give every CPG sales team an AI agent that finds growth opportunities, builds plans, and turns them into action.
Our ambition: help the next billion-dollar CPG brand get there with fewer than 10 people. We’re building the technology—and the team—to make that possible.
## 📩 Applying
In your application, include:
1. A link to the most technically ambitious thing you’ve shipped, with one sentence on what made it ambitious.
2. One paragraph on the hardest engineering problem you’ve personally solved: the decisions you made, the code you wrote, and what changed because of it.
Visa sponsorship is offered for this role.
