Infrastructure Engineer

📋 Job Overview

Varick helps companies doing billions in revenue transform how they operate with AI. We start by understanding how the work actually gets done, then build and deploy agent systems that handle entire process chains, from intake through execution to reporting. We’re looking for an engineer who cares about getting that foundation right.

🏢 About Varick

Varick helps companies doing billions in revenue transform how they operate with AI. We start by understanding how the work actually gets done, then build and deploy agent systems that handle entire process chains, from intake through execution to reporting. That means working inside real business operations: reconciling accounts, resolving invoice exceptions, and producing cash forecasts. These systems need to work reliably, and when something goes wrong, we need to understand what happened and be able to fix it.

🎯 The Role

You’d own the infrastructure that lets our engineers build, deploy, and operate agents across customer environments. You’d work closely with the people shipping those systems, understand where they’re getting stuck, and build things that make their work easier.

✅ Key Responsibilities

• Making workflows reliable. Scheduling, retries, checkpointing, and recovery when a run fails halfway through. Retrying a workflow should never mean posting the same invoice twice.
• Making deployment straightforward. CI/CD, customer environments, secrets, and access controls. Engineers should be able to ship confidently and know how to recover when a deployment goes wrong.
• Keeping the data layer working as we grow. Schema design, query performance, and knowing when Postgres is enough or when a workload needs something else.
• Understanding what happened. Logs and traces that let us follow a run across agents and external systems, investigate a failure, or answer a customer’s question months later.
• Handling unreliable integrations. Systems like NetSuite, Oracle, and Salesforce come with rate limits, partial failures, and their own ideas about availability. Our infrastructure needs to account for that.
• Operating what we build. Sharing on-call, responding to incidents, and following through on fixes that prevent the same problem from happening again.
• There’s plenty to build. Part of the job is deciding what needs a shared solution, what can stay simple, and what isn’t worth building yet.

📌 Required Qualifications

• You’ve operated software that other people depended on. You know what it’s like to investigate a production failure with incomplete information, make a careful fix, and come back later to address the underlying 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 because you can’t help it. 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.

⭐ Desirable Experience

• Experience with databases, distributed systems, and production operations.
• Judgment about how much complexity a problem actually needs.

🎁 Benefits

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.

🛂 Visa & Eligibility

No visa or eligibility information provided.