Founding ‐Stack Engineer; NYC

Who we’re looking for

Role:
Senior Full Stack Engineer

Team:
Engineering

Reports To:

Head of Engineering

Location:

Knit’s NYC office (Hybrid)

Operating hours:
Monday - Friday 9am - 5pm EST.

Travel:
This role will occasionally be expected to travel for in‑person internal working sessions, and our once per year US All Team Summit. (Less than 15%)

Knit is building the agentic AI platform that helps enterprise brands run end‑to‑end consumer research. We orchestrate specialized AI agents for surveys, data collection, analysis, and reporting, delivering decision‑grade insights to Fortune 1000 brands in hours, not weeks.

In under two years, we’ve partnered with 50+ leading enterprise brands, including Amazon, Mars, NASCAR, JBL, ESPN, and Paramount. Knit has grown 500% in the last 12 months and raised $30.6M to date, including a $16.1M Series A in July 2025. Here are example case studies that demonstrate the value of our platform. A product demo can be found here.

We’re building our foundational NYC engineering team from scratch and looking for exceptional builders who are resourceful, deeply technical, and thrive in high‑ownership environments.

As one of the first in‑house engineers, you’ll shape the core of our platform and the culture of a team that will scale to 20+ over the next 18 months. You’ll build and orchestrate AI agents, pioneer new UX paradigms, and tackle some of the hardest problems in applied AI with autonomy and end‑to‑end ownership.

• Own 0→1 and 1→N features across the stack, from design docs to building high‑throughput data pipelines and scalable FastAPI services.
• Architect and own the core agent orchestration engine, designing complex, multi‑agent LLM workflows (routing, tool‑use, memory, evaluation) with deterministic fallbacks, guardrails, and auditable actions required by enterprise users.
• Build AI‑native, human‑in‑the‑loop UIs. Craft React/Next.js interfaces that let users collaborate safely with agents, with transparency and explainability by design.
• Develop the “factory for the factory”:
  Build our experimentation platform: CI/CD for prompts and agents, offline/online evals, drift detection, safety layers, and rollout controls.
• Ship fast, safely. You’ll instrument everything for reliability, write concise design docs, add robust tests, and build dashboards and alerts for features you launch.
• Partner cross‑functionally with Product, AI, Design, CS; talk to customers and SMEs, and turn ambiguous problems into shipped product.
• Obsess over performance, optimizing for latency across the system: caching, model selection, distillation, batching, vector search, and infrastructure efficiency (GPU/CPU).
• Operate what you build. This includes on‑call ownership, leading incident response, and driving learning through blameless postmortems.

• Frontend:
  React, Next.js
• Backend:
  Python, FastAPI
• Data/ML:
  Mongo
  
  DB, S3, Redis, Pinecone
• Infra: AWS, Docker, Kubernetes; CI/CD with Git Hub Actions.
• Messaging: SQS; event‑driven pipelines.

• You’re a 0→1 builder who thrives in ambiguity and has shipped products from scratch at a startup or in a hyper‑growth phase. You’ve seen both early‑stage hustle and later‑stage scale and know how to build for it.
• You’re a systems thinker with deep technical chops: you design clear architectures and write clean, tested Python and Type Script.
• You think like an owner, spotting problems, proposing solutions, and building them without waiting for perfect specs. Your impact is measured in business outcomes.
• You use AI as leverage. Tools like Cursor, Copilot, or Claude Code are integral to your workflow, helping you ship faster while maintaining a high standard for correctness.
• You believe speed and quality aren’t opposites and can articulate the tradeoffs you make.
• You communicate crisply, sharing ideas effectively and thriving in tight feedback loops with product, design, and customers.
• You’ve got grit: hard problems energize you, context switching doesn’t scare you, and you’re comfortable deleting code.

• You see a hard line between "frontend," "backend," and "product."
• You are…