Our approach · Engineering & Tech

How we run a search: less noise, more signal.

Five deliberate steps from the first brief to the first day. AI sharpens the work at every step; people make every decision. Here is each step, where AI helps, who decides, and what your team receives.

From the first brief to the first day

We call this the CLEAR search method: Clarify, Locate, Explore, Align, Run.

  1. Define the signal

    Most job descriptions are wish lists. We work with your leaders to separate the must-haves from the nice-to-haves: the systems, stack, team, delivery model and outcomes the role really depends on. The agreed brief becomes a written rubric, so every candidate is measured against the same signal, not the loudest resume.

    Where AI helps
    Turns intake notes into a structured draft brief and rubric, and surfaces what we learned on similar searches.
    Who decides
    Your leaders and our recruiter agree the brief.

    What your team receivesA written search brief and rubric: priorities, essential experience, compensation, interview plan, and update cadence.

  2. Market research

    We map the companies, teams, and talent pools where the right person is most likely working now, including the strong performers who are not looking and will never apply to a job post. Outreach is written for the role and the person, drawing on our network, our own recruiting database, and the wider market.

    Where AI helps
    Searches our recruiting database and the wider market by meaning, not just job titles, and brings back people we have met before.
    Who decides
    Recruiters choose who to approach and write to them personally.

    What your team receivesA market view: target companies, where candidates are coming from, and early compensation signals.

  3. Precision screening

    Every profile and resume is compared against the rubric from your brief, so a large pool narrows to the people who match what matters, consistently and quickly. Then we interview them: what they built and ran, the scale it ran at, the design decisions they owned, and why they would move. Technical candidates go through a live technical review with our Technical COO and partner engineers. Summaries separate what a candidate told us from what has been confirmed.

    Where AI helps
    Helps compare profiles and resumes against the rubric and organizes interview notes.
    Who decides
    Recruiters evaluate every candidate. AI does not reject or rank anyone on its own.

    What your team receivesInterview notes and a technical review on each candidate’s work, operating context, and motivation.

  4. Calibrate together

    You receive a focused slate, not a stack of resumes. Each summary explains why the background fits, what has been checked, and which questions deserve your interview time. After the first introductions we review your feedback together and recalibrate the rubric, so every introduction after that lands closer.

    Where AI helps
    Drafts candidate summaries for recruiters to check, correct, and sign off; records your feedback so the search keeps it.
    Who decides
    You choose who to interview.

    What your team receivesCandidate summaries and a calibration review after the first introductions.

  5. Close with confidence

    We keep both sides informed through interviews, references, and the offer conversation, anticipating concerns before they become reasons to say no. References are taken at the agreed stage with the candidate’s permission, and we stay in touch through the start date and beyond.

    Where AI helps
    Keeps scheduling, notes, and follow-ups organized so nothing is dropped.
    Who decides
    Your team makes the hiring decision.

    What your team receivesCoordinated interviews, references at the agreed stage, and support through the offer and start date.

What your team receives

A sample candidate summary

Each introduction comes with a summary like this. It explains why the background may fit, separates what the candidate told us from what has been checked, and lists the questions worth your interview time.

This is a preview. The full sample summary is available on request.

Request the full sample summary
Candidate summaryCandidate BDirector of Engineering · vertical SaaS
Why this background is relevant
Led an incremental move from .NET Framework to current .NET on AWS while the product kept shipping: the same situation as your role.
Team and scope
Leads 14 engineers across two time zones and stays about 60% hands-on. Reports to the CTO.
Architecture
Set domain boundaries and an event-driven integration layer; walked us through the trade-offs and what they would change.
Candidate-reported results
Reports moving from monthly to weekly releases and roughly halving the change failure rate. Not yet confirmed.
Illustrative example. Candidate B is fictional, not a real or available person.
Assessment

What we explore in technical interviews

A title says little about the systems someone has built. We ask about the work itself, the scale it ran at, and the decisions the candidate owned.

  • Architecture and design patterns
  • Modernization without a rewrite
  • Reusable components and APIs
  • Testing, CI/CD and release
  • Delivery, measured
  • AI in the product
  • AI in the engineering workflow
  • Security and reliability
  • Ownership of the work

For leadership roles, we also explore architecture judgment, how delivery is measured, hiring and team structure, distributed teams, and how AI is used in the product and by the team.

We distinguish candidate-reported information from details confirmed through agreed checks. Reference checks are handled at the appropriate stage, with the candidate’s permission.

Our full approach and the interview questions we use are shared on request.

Request our full approach and interview questions
People and AI

AI does the legwork. Our recruiters lead every interview and make every recommendation.

The recruiter should become more valuable through AI, not more dependent on it.

How we use AI
  • Each recruiter works a limited number of searches at a time, so every search gets real attention.
  • Cookie, our AI recruiting assistant, helps our recruiters search our recruiting database and the wider market, compare profiles against the search rubric, organize interview notes, and prepare first drafts of candidate summaries.
  • Recruiters review every candidate and every summary before it reaches you, and they make every recommendation. Your team makes the hiring decision.
  • AI does not reject, rank, or select anyone on its own, and we do not treat an AI output as a prediction of success.
  • Because AI-written applications and identity fraud are rising, candidates we present have spoken with a recruiter in a live conversation.

Questions about our process

How do you use AI in a search?

Cookie, our AI recruiting assistant, gives a small senior team the reach of a much larger one. It searches our recruiting database and the wider market by experience rather than job title, so it finds strong people we met on earlier searches; it compares every profile with the rubric you agreed; and it organizes interview notes and drafts candidate summaries. Every brief and calibration call is kept, so your next search starts ahead instead of from a blank page. Recruiters check, correct and sign off everything before you see it, and make every recommendation; your team makes the hiring decision. AI never rejects, ranks or introduces anyone on its own, never interviews a candidate, and never judges personality or tone.

How do you assess an engineer’s track record?

We ask about the work itself: what they built and ran, the scale it ran at, the architecture and design decisions they owned and the trade-offs, how it was tested, released and measured, and how they use AI in the product and in their own workflow. Technical candidates go through a live technical review with our Technical COO and partner engineers, and your team can run any technical interview or exercise it wants. Every summary separates what the candidate told us from what we have confirmed, and lists the questions worth your interview time.

When do you check references?

At the stage agreed with you, usually when an offer is in view, and always with the candidate’s permission, because an early call can expose a candidate who has not told their employer. Before then, facts such as employment dates and titles can be confirmed, and every candidate we present has had a live conversation with one of our recruiters: Gartner expects one in four candidate profiles to be fake by 2028. Your summary always shows what has been checked and what is still self-reported, so nothing unverified is presented as fact.

Can you support our internal recruiting team?

Yes. We can run one focused search alongside your team or work as an extension of it. The CTO we placed at a PE-backed sports-management platform used us as his hiring partner for the engineering and product build-out: 22 seats in 15 months, 15 permanent and 7 contract. At the start we agree who owns which roles, how candidates hear from us and how feedback flows, so the work fits your hiring process.

Let’s discuss the team you need to build.

Tell us which roles you are hiring for and what the business needs from them.

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.