About the role

Deployed Agent Orchestrator
Vulcan Technologies · Austin, Texas · weekly travel
$100,000 to $250,000 base | $50,000 to $200,000 equity | weekly and quarterly competitive bonuses
The thesis
The job is bringing frontier AI to government and the institutions around it, end to end. That means state agencies, legislatures, law firms, policy organizations, and government relations teams.
End to end means one person handles the whole arc. You find the account, learn the work it does, build the system that does that work faster, and remain responsible for whether anyone is still using it six months later. No solutions engineer follows you in, and no customer success manager takes it over afterward.

The three parts of the job
1. Government consultant
You have to understand an agency's work before you can automate any part of it: how a permit moves, who signs it, which rule sets the deadline, and where the time goes. Orchestrators here have produced fifty-state licensing reciprocity surveys, regulatory cost-benefit analyses, fiscal notes, five-year rule review calendars, and Medicaid program integrity screens.
You will have the full corpus of American law available to you, and you are expected to understand a customer's regulatory obligations at least as well as the consultants they already pay to explain them.
2. Account executive
You own a book of accounts, a number, and the renewals. Books currently range from 115 to 332 seats across the U.S. Federal Government, California, Louisiana, Arkansas, Texas, Utah, Mississippi, Oklahoma, West Virginia, Idaho, Connecticut, and North Carolina, along with commercial and gov-adjacent accounts.
A separate SDR team supports the orchestrators. The SDRs source and qualify leads and hand them over, so prospecting is not your job. Everything after the handoff is: you run the pilot, expand inside the agency, write the proposal, and answer the RFI.
You are measured on how much your accounts use the product, not on how many meetings you booked.
3. Forward deployed engineer
You build during the meeting, using the customer's own data. Dashboards, agents, scheduled flows, hosted apps, tracked-changes redlines, and daily audio briefings are all things orchestrators put together in a session. You will not write code, and you will not hand the work to an engineer. You assemble it yourself in Justinian while the customer is in the room, and they should be able to use it that day.
When an agency needs data we do not hold, you go get it. One recent example is the Louisiana state land sales register, 619 sale records across 82 parishes, which came out of a customer conversation and was searchable within the week.

The week
Most orchestrators are on the road Monday through Thursday, usually in a different state than the week before, and in several states each week.

• Book your own visits. The SDR team supplies qualified leads, and you decide which accounts justify the trip.
• Prepare for each meeting: who is attending, what they have run in Justinian, and what we owe them from last time.
• Build in the session rather than promising to send something later.
• Look for the records that would make the product difficult for that agency to work without.

How you are measured
Four things: new users activated, users retained, total weekly usage across your book, and new datasets you bring into the corpus. Every orchestrator can see every other orchestrator's numbers, and standings are published weekly.

Who we hire
Ruthless
You will have several hundred accounts and time for a few dozen a week. The job requires deciding quickly which ones deserve your calendar, ending pilots that are not going to convert, and telling us when an account is dead rather than carrying it another quarter. You should also want to finish at the top of the standings.
Futurist
You should already expect agents to do a large share of the work inside a state agency within a few years, and you should be able to show a skeptical civil servant why, using their own records rather than a presentation about AI.
Conscientious
The role runs on staying on top of deals and schedules. You will carry dozens of accounts, overlapping pilots, renewal dates, RFI deadlines, and a travel calendar you manage yourself. Nothing should slip because you lost track of it.

What the role requires

• Weekly travel. Most orchestrators are away Monday through Thursday.
• The ability to work without direction. Leads come to you from the SDR team, but nobody will plan your week or tell you where to be next.
• Building and selling in the same meeting.
• No engineering background. Policy, government, consulting, and sales backgrounds all work. You need to understand somebody else's job well enough to automate part of it the same day.
• Persuasion. The people across the table have sat through many software rollouts that did not work, and you usually get one meeting.

Who should not apply

• Account managers who want a fixed territory and a quota
• Engineers who want to only write code
• Consultants who want to present findings and leave
• Anyone who needs a manager to set their week

Compensation

• Base salary: $100,000 to $250,000, depending on experience and the size of the book you take
• Equity: $50,000 to $200,000
• Weekly and quarterly competitive bonuses
• Travel covered

Vulcan Technologies is an AI legal intelligence company in Austin, backed by General Catalyst and Y Combinator. We are mapping every law, regulation, and court case in America. Eight orchestrators are in the field today.

About the interview

1. Interview\
2. Reference screening\
3. Work trial