Founding Full-Stack Engineer

Ignizia; San Francisco, Northern (CA, KY); Hybrid; USD 180,000 - 260,000; Full time

Benefits offered by this job

Meaningful founding equity

Founding seat with real ownership

Hybrid work in SF Bay Area

Job summary

Qualifications

• 6+ years of senior engineering experience with at least one product taken from zero to production as primary owner.
• Deep TypeScript and production Next.js experience.
• Strong Postgres/Supabase depth: schema design, row-level security, migrations.

Responsibilities

• Own the architecture of the platform from zero to one: TypeScript, Next.js, Supabase/Postgres.
• Implement the relational spine faithfully: entities, provenance, privacy guarantees enforced in code and policy.
• Build platform surfaces against a fully specified canvas, collaborating with the founding designer.
• Set engineering culture: testing where it matters, code review, pragmatic quality, weekly shipping.
• Mentor junior engineers as the team grows; you will be the anchor around which new hires are built.

Skills

TypeScript

Next.js

Postgres

Supabase

Data modeling

Migrations

Tools

PostgreSQL

Supabase

SQL migrations

Job description

Senior, zero-to-one. Own the architecture; the data model is your contract.

San Francisco Bay Area Hybrid, in-person by default Senior Meaningful founding equity + salary

The mission

Make collaboration work between people, machines, and AI.

Twenty years ago organizations coordinated people. Today they coordinate people and software. Tomorrow they will coordinate people, AI agents, machines, and humanoids. Nothing in the modern stack was built for that. Organizations do not fail because people lack intelligence; they fail because that intelligence is not coordinated, and coordination failures already cost the economy roughly $2 trillion a year.

Ignizia is building the operating layer for human-AI-machine coordination. This is the unsolved layer of the AI transition: independent research keeps finding that capable AI agents lose much of their capability the moment they have to work together, and that the hardest problems in enterprise AI are organizational, not technical. Coordination cannot be downloaded. It has to be captured and shaped from how a real organization actually works, and whoever holds that teaming-context layer holds something no one else can import.

So we start at ground zero: small and mid-size manufacturing, the most coordination-dependent, least digitized work there is. We are live with a design partner, a 60-person luxury footwear manufacturer, where the platform is being shaped view by view against real operations. We are founder-led, early stage, and hiring our founding team.

Why this role is unusual

You will not be starting from a blank page. Ignizia already has an unusually complete product definition: a 33-view interactive product canvas simulating the platform 30 days into a live pilot, a canonical naming and information-architecture brief, established navigation and accessibility patterns, and an engineering-grade relational data model. The founder holds the product vision and has set the frame.

Alongside the canvas sits a full relational data model written as an engineering contract: design laws, roughly 29 entities, a provenance spine (source, confidence, fidelity level, consent scope, validation dates), and explicit privacy rules. That document is your contract. You own how it becomes a real system. And it is not just a schema: it is the teaming-context layer itself, the system of record for how a real organization coordinates. If the thesis is right, what you build here is the foundation everything else stands on.

What you will do

• Own the architecture of the platform from zero to one: TypeScript, Next.js, Supabase/Postgres.
• Implement the relational spine faithfully: entities, provenance, and privacy guarantees (such as small-group aggregation thresholds) enforced in code and policy, not by convention.
• Build the platform surfaces against a fully specified canvas, working with the founding designer.
• Set the engineering culture: testing where it matters, review, pragmatic quality, weekly shipping.
• Be the anchor. As the team grows, junior engineers are hired against your mentorship; you are the person the next hires are built around.

What we are looking for

• A senior engineer, roughly six or more years, who has taken at least one product from zero to production as a primary owner.
• Deep TypeScript and production Next.js experience.
• Real Postgres/Supabase depth: schema design, row-level security, migrations, and the judgment to know when to denormalize.
• Data-modeling strength: you can read a relational spec and see the edge cases before writing code.
• Pragmatic zero-to-one instincts: ship weekly, harden what matters, do not gold-plate.
• Comfortable being the technical anchor others are hired around, including mentoring a junior engineer later.

How we will interview

We will walk the data model together and ask where it breaks: which entities are underspecified, which constraints are expensive, what you would build first and why. Expect a working session, not a whiteboard puzzle.

What we offer

• A problem worth a decade: the coordination layer of the AI transition, started where it is hardest and most real.
• Meaningful founding equity, plus a salary range shared early in the process.
• A founding seat with real ownership: the architecture is yours to define.
• A live design partner, not a hypothetical market: your work ships against a real factory and real people from week one.
• San Francisco Bay Area, hybrid with in-person time as the default. Occasional travel to the design partner is possible, never required.