Direct Hire

Engineers who have run it in production.

Senior and staff engineers, platform and SRE, data and AI, QA automation and security, hired permanently for B2B SaaS and payments teams. Before you meet anyone, they have walked our Technical COO and partner engineers through a system they built and an incident they handled, live.

  • 15 daysfrom submittal to signed hire on average across our technology searches (range 9–21).
  • 3 daysfrom contract to the first slate for a senior release-automation engineer.
  • 4 hiresfrom a panel of more than a dozen agencies; the client told the others to find candidates “more in-line with” ours.
  • 2 years onour DevOps hire was a senior release manager in the client’s DevSecOps group.

Senior roles take a median 71 days to fill, and technical roles take longer still. Ashby, Talent Trends Report, May 2026

When to call us

When engineering leaders call us

  • Uptime in the contract

    Platform and SRE

    Enterprise customers want an SLA, and the on-call rotation is one person deep.

  • Moving to the cloud

    Engineers who have migrated before

    A legacy platform is heading to the cloud, and the team has never run a migration.

  • Money movement

    Payments engineers

    Ledgers and reconciliation, built by people who have owned them in production.

  • Releases you can audit

    DevOps and QA automation

    Releases are unpredictable, and compliance wants a pipeline it can follow.

  • Data and AI from zero

    Your first data and ML engineers

    People who have built a data platform from nothing and taken a model to production.

  • Legacy code, modern stack

    Modernization engineers

    A .NET Framework or monolith codebase has to move to a current stack without a big-bang rewrite.

How we work

Engineers screen them before your engineers meet them.

A stack intake before we search

We agree the architecture, languages, tooling, team shape and what the roadmap needs next with the hiring manager, and what would rule a candidate out.

A live technical review

Every candidate goes through a live technical review with our Technical COO and partner engineers: a system they built and an outage they dealt with, the scale, the trade-offs, what broke and what they changed. Tool lists don’t get through.

Your engineers run the technical loop

We send a short slate with the evidence and the questions worth asking, so your engineers spend interviews on depth, not discovery.

See a sample summary

What we screen for

The engineering practices we screen for

We screen every candidate on the practices your team actually uses, and give your interviewers the gaps worth testing.

  • Architecture and design patterns

    Domain-driven design and bounded contexts, event-driven services, CQRS and event sourcing where they earn their place, and when a modular monolith beats microservices. Candidates explain the trade-off, not just the pattern name.

  • Modernization without a rewrite

    Moving legacy code, such as .NET Framework to current .NET, in increments: tests around the old code first, new services routed in alongside it, and old and new running side by side until the cutover.

  • Reusable by design

    Shared libraries and internal platforms, versioned API contracts, design systems and service templates that let the next team ship faster instead of copying code.

  • AI in the product

    AI features in production, from model APIs and retrieval to agents, with evaluation, guardrails, customer-data privacy and a cost per request someone is watching.

  • AI in the engineering workflow

    AI coding assistants such as Claude Code, Cursor and Copilot, and AI code review, in daily use, with the human review, tests and security checks that keep generated code safe to ship.

  • Automation and quality

    CI/CD, infrastructure as code, automated tests on every change, observability, and delivery measured by cycle time, deployment frequency, change failure rate and time to restore.

Domain

Where we have done this before

Each one is drawn from a search we have completed, not a keyword list.

  • Payments and fintech platforms
  • .NET Framework to current .NET on AWS
  • Release pipelines auditors can follow
  • Data and QA engineering through live coding rounds
  • AI-forward engineering leaders
  • Leaders of offshore and distributed teams
  • Developers, architects and a VP of Engineering for one sports SaaS platform
  • Engineering, product and contract build-outs
Technical interviews

Questions we give your engineers

From a recent modernization search: the client’s CTO asked finalists about domain-driven design, event sourcing and how they would modernize legacy .NET without stopping delivery. We prepare your interviewers with questions like these, built from each candidate’s own record.

Questions we give your engineers
AreaExample question
Inheriting a modernization“You inherit a .NET Framework codebase halfway to current .NET, and bugs are reaching customers. What do you look at in your first two weeks before you change anything?”
Sequencing“How do you decide which part of a monolith moves first, and what would make you stop and reverse?”
Domain-driven design“Show us where you drew bounded-context boundaries on a real system. Which one turned out wrong, and what did it cost?”
Event sourcing and CQRS“Where have you used event sourcing or CQRS, and where would you refuse to?”
Running old and new“How do you run the legacy and new code side by side? Where does the data live during the transition, and how do you cut traffic over?”
Quality“Bugs keep reaching customers despite automated tests. What do you measure first, and what do you change?”
AI in the product“Describe an AI feature you shipped to customers. How did you evaluate it, and what does each request cost?”
AI coding tools“Where have AI coding and review tools actually sped up your team, and how do you review and test the code they produce?”
Distributed teams“How do you keep ten offshore engineers productive and accountable when you’re 75% hands-on yourself?”
Roles

Every seat in the engineering team, leadership first.

  • Engineering managers
  • Staff and principal engineers
  • Senior backend and full-stack engineers
  • Platform, DevOps and SRE
  • Data and analytics engineers
  • AI and ML engineers
  • QA automation and SDET
  • Security and AppSec
  • Payments engineers
  • Technical product managers

See what we explore in technical interviews

For your talent team and your finance team

For your talent team

We take the seats your team has been carrying.

We agree up front which roles we own, how candidates hear from us and how feedback flows, so we fit your process instead of adding to it.

For finance

Clear terms. A fee when you hire.

Individual hires run on contingency: the fee is due only when a hire is made. Team build-outs can run on a retainer. Fees, payment terms and replacement provisions are agreed in writing before any work begins.

Proof

Results, not resumes.

Engineers and teams we have hired. Filled roles, not open jobs.

  • Director of Engineering

    Flooring field-service SaaS · PE-backed · Lehi / Salt Lake City, UT · Direct hire, hybrid

    Hiring need
    A newly acquired SaaS company needed a player-coach to modernize legacy .NET as its engineering lead retired.
    Result
    A former CTO, about 75% hands-on, accepted in about five weeks across the holidays.
    The client at 30 days

    “So far, so good.”

    Hiring need
    A newly acquired, fast-growing PE-backed SaaS company needed a hands-on Director of Engineering to replace a retiring lead on a fixed date: modernize a legacy .NET Framework codebase to current .NET on AWS without stopping delivery, get product quality under control, and lead a mostly offshore team of about ten.
    Result
    Anew found a former CTO willing to be about 75% hands-on. The client’s CTO tested each finalist on domain-driven design, event sourcing and CQRS, how they would modernize legacy .NET in increments rather than rewrite it, and how they use AI coding and code-review tools. Intake to accepted offer took about five weeks, across the holidays.
    The client at 30 days

    “So far, so good.”

    Learn more about the Director of Engineering case study (Flooring field-service SaaS)
  • Data and QA Engineering Hires

    Sports-betting B2B platform · New York metro · Permanent, agency panel

    Hiring need
    A fast-growing sports-betting platform needed senior data and test-automation engineers.
    Result
    Four senior hires, and the client told rival agencies to find more like Anew’s.
    The talent lead

    “We thank you for all the hard work you put in … we do appreciate it!”

    Hiring need
    A fast-growing sports-betting platform needed senior data and QA engineers who could pass live SQL and coding rounds and a full interview day. Anew was one of more than a dozen agencies on its panel.
    Result
    Four permanent hires, two placed in the same week. The client told its other agencies to find candidates “more in-line with” Anew’s automation hire. Within weeks the first hire was running the client’s data hiring, and two Anew hires sat on the panel for the fourth.
    The talent lead

    “We thank you for all the hard work you put in … we do appreciate it!”

    Learn more about the Data and QA Engineering Hires case study (Sports-betting B2B platform)
  • Senior DevOps / Release Automation Engineer

    FinTech · Chicago, IL · Permanent

    Hiring need
    A FinTech company needed a senior engineer to automate its releases and make them auditable.
    Result
    First slate in three days; the hire cleared a six-interviewer loop and moved up into release management.
    The hiring manager, one month in

    “…no concerns.”

    Hiring need
    A Chicago FinTech company running a DevOps program to make releases predictable and auditable needed a senior release-automation engineer to build CI/CD pipelines across hybrid cloud.
    Result
    Anew presented its first slate three days after the contract arrived, and the client asked to screen at least six Anew candidates. The hire cleared an on-site loop with six interviewers and, two years later, was a senior release manager in the client’s DevSecOps group.
    The hiring manager, one month in

    “Everything has been going well … so far – no concerns.”

    Learn more about the Senior DevOps / Release Automation Engineer case study (FinTech)
Client stories

Client stories

Longer engagements: the situation, what we did and how it turned out.

  • A former CTO, about 75% hands-on, to modernize legacy .NET as the engineering lead retired.

    Field-service SaaS, newly acquired · A Director of Engineering and lead developer: about 75% hands-on, 25% leading the team.

    Hiring need
    The engineering lead was retiring, with the gap starting in early January. A legacy .NET Framework codebase was being modernized to current .NET on AWS, bugs were reaching customers despite automated tests, and most of the team of about ten was offshore.
    Result
    A former CTO accepted about five weeks after intake, across the holidays. Five months in, he told us he was loving it.
    Hiring need
    Revenue was growing fast and the company needed continuity, not a restart: a leader who could write .NET Framework and current .NET code, modernize in increments instead of a big-bang rewrite, fix product quality, lead engineers across time zones and bring AI tools into the team’s daily work.
    What we did
    We calibrated with the client’s CTO before sourcing. Every finalist walked us through a modernization they had led and how they measured quality. The CTO then tested domain-driven design, event sourcing and CQRS, how each would organize teams around the architecture, and how they use AI coding and code-review tools, including how that code is reviewed and tested before it ships.
    Result
    A former CTO accepted about five weeks after intake, across the holidays. Five months in, he told us he was loving it.
    Learn more about the A former CTO, about 75% hands-on, to modernize legacy .NET as the engineering lead retired. case study (Field-service SaaS, newly acquired)
Client experience

What engineering leaders say

“I had to build an entire tech hub in a new city with a new company and I went to Anew Recruit because they deliver. We are a very intense tech shop, too. They placed one of our best leaders on the team in addition to many more.”

Martin L.CPO & CTO, Sports-betting technology company

“We needed a Vice President of Product for our payments company and Anew Recruit came through! They identified outstanding talent and we were able to choose someone who checked every box. We are planning to use them again for more executive level and tech searches as we continue to grow.”

Bob B.PE-backed SaaS payments company
FAQs

Questions engineering leaders ask

Who does the technical evaluation?

Our Technical COO and partner engineers run a live technical review of every candidate before you see them: a system they built, an incident they handled, the design patterns and testing behind it and how they use AI tools. Your engineers still run their own technical interviews, and we give them the evidence and the questions worth asking.

How fast will I see a shortlist?

A senior release-automation search had its first slate three days after the contract. Across our technology searches, hires signed 9 to 21 days after we submitted them, 15 on average. Published research puts the median for senior roles at 71 days, longer for technical ones. Your interview availability is the biggest factor, so we agree it at kickoff.

Do you understand payments and compliance constraints?

We have hired for payments and compliance-heavy teams, including a VP of Product at an embedded-payments platform, a release engineer who made a FinTech’s releases auditable and an ERP administrator with SOX experience. We screen for engineers who have owned those systems, not only worked near them.

Do you hire leaders for offshore or nearshore teams?

Yes. For a PE-backed field-service SaaS company we hired a player-coach, about 75% hands-on, to lead a mostly offshore team of about ten while modernizing a legacy .NET Framework codebase to current .NET on AWS. We screen for how candidates have run handoffs, code review and on-call across time zones.

How do you work with our internal recruiters?

We agree up front which roles we own, how candidates hear from us and how feedback flows, so hiring managers get one process, not two.

Contingency or retainer?

Individual hires run on contingency, where the fee is due only when a hire is made. Team build-outs have run on a retainer. Terms are agreed in writing before any work begins.

Tell us which engineers your roadmap needs this quarter.

Share the roles, the stack and what the team has to ship, and we will show you how we would run the search.

What happens next

  1. Share a few details. Six short fields about you and your company.
  2. Choose a time. Pick a slot on our calendar for a conversation with Anew Recruit.
  3. Talk through the search. We discuss the roles, priorities, and timing, then confirm scope and terms in writing before any search starts.

Tell us about your company.

Step 1 of 2: share your details. Step 2: choose a time on our calendar. All fields are required.

Prefer email? Write to info@anewrecruit.com. Looking for a job? Visit For Candidates so your application reaches the right place. See our privacy notice.