Roles we recruit
Seven practices, 27 functions. Start at the practice when you cannot yet name the title; go straight to the function when you can.
Browse all 229 roles Brief us on a seatFlat 15% of first-year base · shortlist in 10 working days
Eight seats sit under IT and GTM infrastructure: the engineers who connect your CRM to billing, product and data tools, and who run the cloud, access and security beneath them. We split them by the part of the stack each owns, screen for outages they fixed, and charge a flat 15% only once your hire starts.
A request for a DevOps engineer can describe a broken sync, an access problem or a cloud bill nobody owns, and each of those belongs to a different seat. We start with what is failing, then the title.
The stack revenue runs on, and the seat that owns each stage
Moves: the time and cost of adding each new system
1 seat
How the stack fits together as you grow: which system holds each record, how CRM, billing, product and data tools share it, and what to build, buy or retire.
Brief us when every new tool needs custom work, and nobody can draw the whole stack on one page.
Moves: sync errors and data latency between systems
2 seats
The syncs between CRM, marketing, billing, product and data tools: field mapping, retries and monitoring, in code or on a platform such as MuleSoft or Workato.
Brief us when bookings, billing and the CRM disagree, or syncs fail silently until a customer notices.
The APIs and webhooks that customers, partners and your own systems call: endpoint design, authentication, versioning, documentation and rate limits.
Brief us when prospects ask for an integration you cannot offer, or partners build on endpoints that change without warning.
Hire an API DeveloperMoves: uptime, capacity and cloud spend
2 seats
Your AWS, Azure or Google Cloud environments: accounts, networks, compute, storage and managed services, built as code and kept within budget.
Brief us when the cloud bill grows faster than usage, or the environments your integrations run on were built by hand.
Hire a Cloud EngineerThe foundations under every system: networks, servers, storage, capacity, backups and disaster recovery, across cloud and any on-premises estate.
Brief us when launch days strain capacity, outages trace back to the network, or the estate has outgrown one generalist.
Moves: deployment frequency, failed changes and time to restore
1 seat
The path from code to production: CI/CD pipelines, infrastructure as code, containers and monitoring for the product and the integrations revenue depends on.
Brief us when releases are manual and risky, a deploy can break signup or billing, or customers spot outages first.
Hire a DevOps EngineerMoves: day-one access, clean offboarding and license spend
1 seat
Accounts, servers and the tools people log into: SSO, devices, licenses, patching and backups, with CRM and sales tool access ready on day one.
Brief us when new hires wait days for logins, leavers keep access to customer data, or nobody knows which licenses you pay for.
Moves: security reviews cleared and incidents contained
1 seat
Controls that protect customer data across your tools: access policies, vulnerability management, logging, incident response and SOC 2 evidence.
Brief us when enterprise deals stall in security review, an audit is coming, or nobody checks what each new tool can access.
Hire a Security EngineerMeasured on
Infrastructure interviews tend to test tools and whiteboard designs, and both reward fluent talkers. We screen for the evidence underneath: an outage worked to the end, trade-offs on your own stack, judgment with access and customer data, and the trust of the teams who depend on them.
We ask for one incident they worked from alert to postmortem: how it was found, what they did in the first hour and what changed afterward. A story where someone else made the fix is where we dig.
Candidates work through a short scenario built from your brief, such as syncing a CRM with billing and a warehouse or rebuilding a hand-built environment as code. We score the trade-offs they raise before they name a tool.
We ask how they handled service accounts, API keys, admin rights and customer records in their last role. An integration running on an admin key with no logging is a liability, however well it works.
We check with someone in RevOps, sales or engineering who relied on their work: whether requests were handled, changes explained and outages communicated before anyone had to ask.
Not sure which seat you need? Tell us what broke last, whether a sync, a login, a release or a security review, and we will tell you which of the eight owns it.
Public US benchmarks, read October 2026. Infrastructure pay is mostly base salary: Built In’s self-reported additional cash for DevOps engineers averages $16,538, against an average base of $133,817. Sources conflict on cloud engineers: Built In’s self-reported median base is $160,000, above the Salary.com band shown.
Each bar runs from the 25th to the 75th percentile, the middle half of reported pay.
Base salaryWages including commission (BLS)Average total pay, base plus variable
Solutions Architect
Salary.com base benchmark
$118,623 to $139,366 base
DevOps Engineer
Salary.com base, Built In total
$122,133 to $142,408 base$150,355 average total
Cloud Engineer
Salary.com base benchmark
$96,514 to $117,252 base
Security Engineer
BLS information security analysts, Built In total
$97,810 to $163,500$153,053 average total
Systems Administrator
BLS network and computer systems administrators
$78,010 to $126,640
Solutions Architect, DevOps Engineer and Cloud Engineer: Salary.com base salary, 25th to 75th percentile, United States, as of October 1, 2026. Security Engineer and Systems Administrator: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025, annual wage at the 25th and 75th percentiles for information security analysts (SOC 15-1212) and network and computer systems administrators (SOC 15-1244), all industries. Rings and lead figures: Built In average total compensation, average base, additional cash and median base salary for DevOps, security and cloud engineers, self-reported, reviewed October 7, 2026. Public aggregates, not ZaphyrRecruit placement data.
The clock starts when the brief is signed and stops when three to five calibrated candidates are in front of you. Most of that time is spent talking to people, not searching for them.
Day 1
Forty-five minutes with whoever the hire reports to. We leave with the number the seat owns, the range you can pay and the two or three things that genuinely disqualify.
Days 2 to 7
We build the list from people doing the job now, approach them directly and screen every name against the brief before it reaches you.
Days 8 to 10
Three to five people, each with a page: what they have run, why they fit this seat, pay expectations, notice period and where they are weak.
After the shortlist
Interviews run at your pace. We handle scheduling, references and the counter-offer conversation, and nothing is payable until your hire starts.
Three clients, quoted as they wrote to us about searches we ran for them. We publish no names or logos without permission.
A solutions architect decides how your systems fit together before anyone builds: which system holds each record, how data moves between them, and what to build, buy or retire. For a go-to-market team, that means the CRM, marketing automation, billing, product data and warehouse designed as one stack, with standards your engineers follow. Hire one when every new tool needs custom work. The title also names a customer-facing pre-sales role, which sits with our sales engineering seats, so say which you mean.
A DevOps engineer owns how software reaches production; a cloud engineer owns the environment it runs in. DevOps work is CI/CD pipelines, release automation, containers and monitoring. Cloud work is accounts, networks, compute, storage, managed services and cost on AWS, Azure or Google Cloud. Both write infrastructure as code, in tools such as Terraform, and small teams often hire one person for both. If releases are the problem, brief for DevOps. If the environment or the bill is, brief for cloud.
We charge a flat 15% of the hire’s first-year base salary, payable only once they start. On a $140,000 base that is $21,000, and the same 15% applies to every seat on this page. Bonus and equity are not part of the calculation, there is no retainer, and nothing is payable if the search does not produce a hire. If a placement leaves inside the guarantee period, we rerun the search at no further fee.
Salary.com puts DevOps engineers at $122,133 to $142,408 base, with Built In reporting $150,355 average total compensation (October 2026). Cloud engineers sit at $96,514 to $117,252 on Salary.com, though Built In’s self-reported median base is $160,000, and solutions architects at $118,623 to $139,366. The BLS puts the middle half of information security analysts between $97,810 and $163,500 a year (May 2025). Stack, scope and on-call duty move the number.
Ten working days from a signed brief to a shortlist of three to five calibrated candidates. Interviews and the offer then run at your pace. A design scenario on your stack sits inside our screen, so your own loop can focus on your environment and your team. Strong cloud engineers rarely run one process at a time, so a decision within a week of the final interview is what keeps them.
Hire for what is failing now. If new starters wait for logins, leavers keep access and nobody owns SSO or licenses, start with a systems administrator. If records disagree between the CRM, billing and product, or syncs break without anyone noticing, start with an integration engineer. Cloud and DevOps seats follow the infrastructure you host yourself, and the first security hire often follows the first enterprise security review.
Yes. The Security Engineer seat on this page is a cybersecurity hire: access policies, vulnerability management, logging, incident response and the controls behind SOC 2 audits and enterprise security reviews. We brief it around the systems and customer data your revenue team depends on, and screen with an incident walkthrough and a scenario on your environment. The fee is the same flat 15% of first-year base, payable only once your hire starts.
Yes. Several seats hired as one structure is how we run a pod: an integration engineer, a systems administrator and a security engineer, for example, briefed together so later hires do not restart the search. The same 15% applies to each hire, payable as each one starts. We usually suggest hiring the solutions architect or the most senior engineer first, so they can shape the rest of the team.
Tell us your stack, what broke last and who the hire reports to. We reply within one business day with which of the eight seats it is and what it pays.
We build every shortlist from people already doing the work, approached directly the week an employer briefs us. Set up a job alert for IT and infrastructure roles, or send your CV and we will come to you when a seat opens.
IT & GTM Infrastructure sits in our RevOps, Systems & Data practice, next to the operations, CRM and data teams whose tools it connects, hosts and secures. Sales engineers and AI-native roles build on the same stack, so they are here too.