The posting
PRODUCT ENGINEER @ VARICK AGENTS
ABOUT VARICK:
Varick builds AI agents that take over real operational workflows inside the world's largest enterprises. Our forward-deployed engineers and strategists embed with client teams to map how work gets done and build POCs, then our engineers bring those agents into production. We're venture-backed, revenue-generating from day one, and already in production inside several of these companies. You'll join an elite team from Meta, AWS Bedrock, Citadel Securities, McKinsey, BCG, Stanford, and more.
ABOUT THE ROLE:
Our agents work inside real business operations: reconciling accounts, resolving invoice exceptions, and producing cash forecasts. The people responsible for that work need to understand what our agents are doing, review the results, and step in when something needs their judgment.
You'd build the product our customers use to work with agents, from the interface through the APIs and application logic behind it. You'd have direct access to the people using what you build and room to figure out what would actually make their work better. We're looking for an engineer who cares about making that experience useful, clear, and reliable.
Our engineering team is small and moves quickly, led by Thomas Le Jeune, formerly an engineering leader at Dropbox. The other engineers have each built their own startups focused on post-training and reinforcement learning environments, with backgrounds at Stanford, Amazon, and Waterloo. Our co-founder and CEO, Vas Moza, was an engineer at Meta before starting Varick. Daniel Kornum, our Head of FDE, previously served as COO at Citadel Securities. You'd work with all of them directly.
WHAT YOU'LL DO:
- Help people manage the work. Exception queues, reconciliation reviews, approval flows, and financial reports. Learn how people use these tools and make the daily work easier
- Give people control. Make it clear what an agent is doing, what needs attention, and how to review, correct, or stop an action
- Make decisions understandable. Help someone trace a result back to the records, actions, and approvals behind it, without needing an engineer to interpret a log
- Build the APIs behind the experience. Decide what information the interface needs, how updates reach it, and what happens when a workflow is slow, incomplete, or fails
- Improve our agent SDK. Build tools and abstractions that help other engineers turn a customer's workflow into a working deployment
- Find what belongs in the product. Understand when requests from different customers point to the same underlying need, and when they should remain separate
- Own the details that make a product feel finished: loading states, useful error messages, responsiveness, and what happens when someone uses it in a way we didn't expect
WHAT WE'RE LOOKING FOR:
We want to work with people who love technology and care about the people using it. You enjoy understanding someone's work well enough to spot a problem they've stopped noticing, then building something that helps. Our bar is the same for every engineering role:
- You've owned something in production that other people depended on, and you were the one dealing with it when it broke
- You keep up with technology out of genuine interest, not obligation. You try new tools, form opinions from using them, and rethink how you work when you find something better
- You've changed someone's mind about a technical decision with evidence, and you've had your own mind changed the same way
- You've shipped software and learned from watching people use it. You're comfortable working across the frontend and backend, and you care about how the whole experience fits together
- You can make a design decision, explain your reasoning, and change it when you learn something new
HELPFUL EXPERIENCE:
- React, Node, real-time interfaces, or equivalent
- Product work where you talked to users directly and followed a release through to how it was used
- Tools for reviewing, approving, or auditing work, especially in finance or operations
You don't need to know everything already. We care about your engineering judgment, your attention to detail, and your willingness to work through an unfamiliar problem.
CULTURE:
- High bar. We keep our hiring bar high, even when that means leaving a role open for months
- Opinions, then commitment. We expect everyone to show up to meetings with an opinion, share learnings, and whiteboard problems together. From there we commit and move on to the next problem
- Ownership. We're here to help our customers succeed. That takes care, ownership, and an honest sense of priorities. We want someone who can get deep into a technical problem and still ask whether it's the right problem to solve
- Hard work that lasts. We work hard, and we want that effort to be sustainable. There are times when we need to put in extra hours, including weekends. We take those commitments seriously, and we take people's time outside work seriously too
- In person. We work in San Francisco, in our Financial District office, five days a week. Based in SF or willing to relocate
WHAT THIS ROLE ISN'T:
- Not a client-embedded role. If you want to sit with client teams and build their agents on site, see our Senior Forward Deployed Engineer posting
- Not frontend-only. You own the experience from the interface through the APIs behind it
- Not a research role. You won't train or fine-tune models
WHY VARICK:
- You'd join while much of the product is still taking shape. We already work with billion-dollar companies, and what we learn from those deployments informs what we build next. You'd help decide which problems to solve and how the product should work
- There are design problems here worth spending time on. When an agent does work on someone's behalf, that person still needs to understand the result and know when to intervene. You'd work through those questions with the people responsible for the accounts, invoices, and forecasts our agents handle
- You'd see whether what you built actually helped. You can talk directly with customers, watch them use the product, and follow up after a release, so you catch the gap between what seemed useful when you built it and what matters in their day
- Meaningful equity in an early team. You'd help build the product and own a share of the company behind it. We'll walk you through the grant and its terms so you understand what we're offering
We are an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or protected veteran status. Employment is subject to a standard confidentiality and non-disclosure agreement.
