The Bench
A standing invitation, for operators the firm may one day engage.
Keystone Meridian runs lean on purpose. The firm works with a small number of organizations at a time, and staffs each engagement with a small number of operators who have already done the work elsewhere. The bench is the list of people the firm considers when an engagement opens and the work calls for more hands than the firm carries in-house on a given day. This page is how an operator lands on that list.
Who We're For
Most of the people who land on this page will not be a fit, and that is the honest starting point. The bench is not a pool the firm draws from indiscriminately; it is a set of operators the firm knows by name, whose work the firm has read, and whose posture the firm recognizes. Three things tend to hold across the operators the firm actually engages.
They have shipped agent-based systems into production at an organization where the consequences were real — money moving, communications going out under the firm's own name, production infrastructure touched. They have lived with the system after delivery. They have answered for it.
They are comfortable working inside an approval structure. The firm's operating posture is documented publicly on the homepage, and it applies to the operators the firm engages, not only to the clients the firm serves. Operators who find approval gates annoying, optional, or a thing to be argued around will not enjoy the work and will not last on the bench.
They are direct. In submissions, in correspondence, in the short exchanges that happen before an engagement forms. The firm does not read pitches well. It reads plain descriptions of work done, problems encountered, and decisions made.
Disciplines
The bench is organized the way the firm's engagements are organized. An operator typically sits in one lane; a few sit across two. The lanes below are the posture the firm considers when an engagement opens, not a list of open requisitions.
01
Operators who design and build Claude-based agent systems — tool selection, approval-gate wiring, audit-trail instrumentation, the plumbing that keeps a production deployment answerable. Typically comes from senior engineering or platform backgrounds.
02
Operators who design the operating model around the system — risk tiering, approval criteria, audit surfaces, incident response patterns. Typically comes from model-risk-management, internal audit, regulated-industry compliance, or a senior engineering role where these surfaces were owned end-to-end.
03
Operators who come in cold to an existing deployment and read it — safety boundaries, observable-versus-intended behavior, credential hygiene, data-flow review — and write findings the owners can act on. Typically comes from security review, SRE, or audit practice.
04
Operators who run the engagement with the client organization — scoping, pacing, translating between the firm's operating posture and the client's internal governance structure. Typically comes from senior consulting, program management in regulated industries, or a CIO-adjacent staff role.
05
Operators who write and deliver the enablement materials and live sessions that transfer the operating discipline to the client's internal teams after the firm leaves. Typically comes from practitioner-turned-educator backgrounds, or from internal enablement functions at large-scale AI programs.
Two Paths
The bench accepts two kinds of submissions, and the choice between them is about what the operator has to hand that represents them best. Neither path is preferred by the firm over the other. Both are read.
Quick Apply is the short path. Name, contact, location, engagement posture, lane interest, and the standard artifacts — resume, portfolio, short text responses. It is the appropriate path for operators whose record is legible from a resume and a short written exchange, and for operators who are early in the decision to engage with the firm at all.
Prove It is the longer path, and it is titled the way it is on purpose. It is appropriate for operators whose work lives in the work itself — repositories, implementations, architecture writeups, recorded decisions. The path asks for those artifacts directly and treats the resume as optional. For operators with this kind of record, the Prove It path is a faster read for the firm than the Quick Apply path is, and it tends to produce clearer signal in both directions.
Quick Apply
The conservative path. Twelve short fields.
Prove It
The longer path. Skip the resume; show us the work.
Plain Terms
The firm operates in plain terms with the organizations it serves, and the same posture applies here. The following is written to be read, not to be buried. It is also, on some points, drafted for counsel review before it ships publicly — those lines are marked.
A submission to the bench is a record that the firm keeps on file.
It is read by the firm, not by an outside service, and it is considered when an engagement opens and the firm is sizing what the work calls for. That is the full scope of what happens to it.
A submission is not an application for a role.
The firm does not post roles. It does not maintain a queue of open positions. The bench is a list the firm draws from when work calls for it, on the firm's timing.
A submission does not commit the firm to an engagement type.
When work opens, the firm scopes each engagement on its own terms. Some of the firm's work is carried out by contract engagement; some is carried out by direct employment. Which posture applies is determined at the point an engagement opens, not at the point of submission.
A submission does not commit the firm to a compensation posture.
Scope, posture, and compensation for any engagement are agreed at the point that engagement opens — not inferred from a submission and not back-derived from a compensation expectation given at submission time. The field asking for compensation expectations on the Quick Apply path exists to give an operator a voice at the opening of an exchange, not to establish a binding number.
A submission does not oblige the firm to reply.
The firm reads what arrives, but the volume of submissions it receives means the firm does not commit in advance to a reply on every one. When the firm has something to say in response — a question, an invitation to a short exchange, a note that an engagement may open soon in the operator's lane — it says so directly. Silence means the submission is on file and not currently matched to opening work; it does not mean the submission was not read.
A submission stays on file for a bounded period, and can be withdrawn at any time.
Submissions are retained for up to twenty-four months from the date of submission, after which they are removed from the firm's records unless the operator has asked for earlier removal or has been engaged by the firm in the interim. An operator may withdraw a submission at any time by writing to contact@keystonemeridian.mgvhq.com; a confirmation of removal is sent within ten business days. Submissions are held inside the firm's own records and are not sold, licensed, or shared with third parties. The only exceptions are (a) service providers the firm uses to receive and store the submissions themselves, under a confidentiality obligation, and (b) any disclosure required by law.
How the Firm Replies
The firm commits to reading every submission that reaches it, and to considering each one against the lanes that currently sit near opening work. It does not commit to a reply timeline. When a reply is appropriate — a question about the submission, an invitation to a short exchange, a note that an engagement may open soon in the operator's lane — the reply comes directly from a named member of the firm, not from a queue.
This is the full description of what happens next. The firm does not maintain an applicant tracking system that sends automated status updates. It does not have a recruiting function. The work of reading submissions and responding to them is done by the firm directly, which is also why the firm is careful about how many it invites at once.