Proliferate, a YC‑S25 startup, is looking for a founding engineer to create the core product that lets engineers manage AI‑powered agents from a desktop. The role offers a $200‑$350 k salary, 0.5‑2 % equity and a health‑focused benefits package, and comes as the company prepares its first funding round after a successful YC batch.
)
The problem Proliferate is trying to solve
Software teams are increasingly relying on AI agents—code‑generating bots, automated reviewers, and context‑aware assistants—to speed up development cycles. Yet most of these tools live in isolated CLIs or cloud dashboards, forcing engineers to juggle multiple windows, switch contexts, and manually resolve conflicts between human and AI output. The result is fragmented workflows, duplicated effort, and a lack of visibility into what the agents are actually doing.
Proliferate’s answer is an operating system for modern engineering: a desktop‑first interface that lets teams launch, monitor, and steer a fleet of AI agents as if they were ordinary processes. By surfacing agent runtime, decision points, and suggested code changes in a single pane, the platform promises to turn “human‑agent collaboration” from a novelty into a repeatable part of the software delivery pipeline.
Funding, traction and market positioning
The company emerged from Y Combinator’s Summer 2025 batch (S25) and is currently preparing its seed round. While the exact raise amount has not been disclosed, YC‑backed S25 startups typically raise between $1 M and $3 M after demo day, and Proliferate’s early traction—securing a handful of pilot customers in high‑tech firms—suggests it will be on the higher end of that range. The startup positions itself against a crowded field of AI‑code assistants (e.g., GitHub Copilot, Tabnine) by emphasizing team‑level orchestration rather than individual developer augmentation.
The role: founding engineer (full‑stack)
- Location: San Francisco, CA (in‑person team in SoMa)
- Compensation: $200 k–$350 k base salary, 0.5 %–2 % equity, full health/dental/vision, meals, equipment budget, and a monthly wellness stipend.
- Tech stack: TypeScript, React, Next.js, Python, Postgres, Redis, AWS, Rust.
- Key responsibilities:
- Build end‑to‑end workflows that tie together the agent runtime, UI, and cloud infrastructure.
- Design the interface for human‑agent collaboration that leverages a newly released model capability.
- Rapidly prototype solutions to real customer pain points, turning rough feedback into polished product surfaces within days.
- Rethink code‑review pipelines so that teams can review, redirect, and trust agent‑generated work before merging.
- Interview process: a short questionnaire, a 15‑minute call with founder Pablo Hansen, a 30‑minute live coding session, a paid 1‑3‑day work trial (USD 1‑3 k), followed by references and an offer.
Why this matters for the broader ecosystem
If Prolinate can deliver a cohesive UI that makes AI agents feel like first‑class citizens in a developer’s toolchain, it could set a new baseline for engineering productivity platforms. Current AI assistants excel at point‑in‑time suggestions but leave the orchestration problem to developers. A desktop‑centric OS that surfaces agent intent, confidence scores, and conflict resolution paths would let teams measure the impact of AI on velocity and quality—something investors and large enterprises are actively seeking.
About the founder
Pablo Hansen completed a master’s in AI at 19, then joined Onyx (YC W24) as its first engineer, where he built an enterprise AI search product. His short‑form portfolio is available on his personal site and the shipped Onyx demo can be viewed in the linked YC batch showcase.
Who should apply?
The posting is open to anyone who can demonstrate a history of taking products from 0 to 1, enjoys a high‑ownership environment, and is comfortable working in a flat, talent‑dense team. Recent grads are welcome, provided they can show strong fundamentals and a willingness to learn quickly.
Proliferate’s hiring push underscores a growing belief that AI‑augmented development will need dedicated infrastructure, not just plug‑in assistants. The founding engineer role offers a rare chance to shape that infrastructure from the ground up.
Comments
Please log in or register to join the discussion