• Helping people manage the work. Exception queues, reconciliation reviews, approval flows, and financial reports. You’d learn how people use these tools and make the daily work easier.
• Giving people control. Making it clear what an agent is doing, what needs attention, and how to review, correct, or stop an action.
• Making decisions understandable. Helping someone trace a result back to the records, actions, and approvals behind it, without needing an engineer to interpret a log.
• Building the APIs behind the experience. Deciding what information the interface needs, how updates reach it, and what happens when a workflow is slow, incomplete, or fails.
• Improving our agent SDK. Building tools and abstractions that help other engineers turn a customer’s workflow into a working deployment.
• Finding what belongs in the product. Understanding when requests from different customers point to the same underlying need, and when they should remain separate.

You’d 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.

Who 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.

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.

Experience with React, Node, real-time interfaces, or equivalent. 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.

• 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.

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.

Who you’d work with

We keep our hiring bar high, even when that means leaving a role open for months. Our engineering team is small and moves quickly, led by Thomas Le Jeune , formerly eng 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 , our Head of FDE, previously served as COO at Citadel Securities. You’d work with all of them directly and help shape how we build as the company grows.

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 get to see whether what you built actually helped. You can talk directly with customers, watch them use the product, and follow up after a release. That gives you a chance to catch the gap between what seemed useful when you built it and what turns out to matter 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.

How we work

We work in San Francisco, in person, five days a week. We expect all 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.

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.

Applying

Email with whatever best shows us how you think and build: a repo, something you shipped, or a paragraph about a product you’ve owned. We’d love to hear who you built it for and what changed once people started using it.

We read every application.