---
title: How to interview engineers for judgment about AI agents
description: "Good engineers are often wary of AI agents. How to interview for that judgment: five questions, a scoring rule and who should run it."
image: https://blog.nexton.dev/hubfs/INC%20Masters%20%26%20Fast%20Company%20publishing%20(4).png
---

[![nexton-logo-black-blue-1](https://blog.nexton.dev/hubfs/nexton-logo-black-blue-1.svg "nexton-logo-black-blue-1")](https://nexton.dev)

Open main menu Close main menu

# How to interview engineers for judgment about AI agents

![Nexton](https://blog.nexton.dev/hs-fs/hubfs/circle-cropped%20(8).png?width=45&name=circle-cropped%20(8).png) 

[Nexton](https://blog.nexton.dev/industry/author/nexton)

[Share this blog post on Twitter](https://twitter.com/intent/tweet?text=I+found+this+interesting+blog+post&url=https://blog.nexton.dev/industry/how-to-interview-engineers-for-judgment-about-ai-agents) [Share this blog post on Facebook](http://www.facebook.com/share.php?u=https://blog.nexton.dev/industry/how-to-interview-engineers-for-judgment-about-ai-agents) [Share this blog post on LinkedIn](http://www.linkedin.com/shareArticle?mini=true&url=https://blog.nexton.dev/industry/how-to-interview-engineers-for-judgment-about-ai-agents)

![](https://blog.nexton.dev/hubfs/INC%20Masters%20%26%20Fast%20Company%20publishing%20(4).png)

Ask a room of senior engineers about agentic development and the most experienced ones often hesitate. Many interview loops score that hesitation as a gap: the candidate "isn't adopting AI." Rachel Laycock, CTO at Thoughtworks, argues the opposite. Good developers are wary because they know that a system being built is not the same as a system working in production. This playbook turns that idea into an interview segment for CTOs and VPs of Engineering. At the end you will have five questions, a scoring rule that does not reward enthusiasm, and a clear answer on who should run the conversation.

## What do you need before you start?

A real change from your own system, a short list of how production breaks for you, and an engineer to run the conversation.

- One recent change that touched a sensitive boundary: payments, permissions, data migrations, or a shared contract between services.
- Two or three incidents your team has had, described in one line each, so you know what "failure" means in your context.
- A list of the checks your pipeline runs today: tests, contract tests, architecture checks, deploy gates.
- Forty minutes inside the existing technical interview. This replaces questions; it does not add a round.
- An interviewer who has shipped to production and been paged for it.

## Why is "how much do you use AI agents?" the wrong question?

Because it measures volume of use, and volume says nothing about whether the work survives production.

AI use is close to universal. The 2025 DORA report, which surveyed nearly 5,000 technology professionals, found that nearly 90% use AI in their work, and that AI adoption is now linked to higher delivery throughput while delivery instability continues to rise. A question that every candidate can answer with "a lot" separates nobody. Worse, it rewards the candidate who sounds most excited, which is not the same as the candidate who knows where an agent should stop.

What good looks like: you stop asking about frequency and tools, and start asking about consequences.

## What should you ask instead?

Ask the candidate how an agent-built change fails before you ask how they would build it.

Use your own change. For example: "An agent opened a pull request that passes every test and modifies the retry logic in our payment service. What would stop you from merging it?" Then stay quiet. The answer you want names a specific failure mode: a retry that is not idempotent and charges twice, tests written by the same agent that wrote the code, a contract with a downstream service that nothing checks. A weak answer is generic: "I would review it carefully."

What good looks like: the candidate names at least one failure that is specific to your system, not to software in general.

## How do you test where they would put the guardrail?

Ask which check has to exist before an agent is allowed to make that change without a person watching.

Laycock describes an experiment led by Giles Alexander at Thoughtworks: one week, no hand-written code, an application about 80% complete. Roughly two thirds of the time went to the whiteboard, defining the domain, the boundaries and the plans for the agents, and one third went to the harness: tests, contracts, architecture checks and the delivery pipeline. The application ran, but the build was red much of the time. The lesson for an interview is that the harness is the work. A strong candidate places the guardrail precisely: "a contract test at the boundary with the ledger service, owned by a person, and the agent cannot edit it."

What good looks like: a named check, a place in the pipeline, and an owner who is not the agent.

## How do you separate "built" from "working in production"?

Ask what would have to be true after three rounds of change, not after the first demo.

Laycock cites Martin Fowler's view that the value of a heavily agent-built system is unproven until it has run in production through several rounds of change. Turn that into a question: "Six months from now, this module has been changed by agents a dozen times. What do you want to be able to see?" Good answers mention observability, how a rollback works, who owns the module when it breaks at night, and how the team would know that a green build still means something.

What good looks like: the candidate talks about the system's next year, not its first week.

## How do you score hesitation without rewarding refusal?

Score how specific the concern is, not which direction it points.

A candidate who says "I don't trust AI" has told you as little as a candidate who says "agents can do everything." Both are positions, not judgment. Calibrated caution names a failure mode and proposes a fix; it also says where an agent is fine to run unsupervised. [How to tell useful caution from resistance](https://blog.nexton.dev/industry/how-to-tell-useful-caution-from-resistance-to-ai-agents-in-a-senior-engineer) goes deeper on this distinction, and [the scorecard template](https://blog.nexton.dev/industry/how-to-build-an-interview-scorecard-that-does-not-reward-ai-enthusiasm) gives you the rows to score it.

## Who should run this part of the interview?

An engineer who has shipped and been paged, because only they can tell a real failure mode from a rehearsed one.

A recruiter can confirm that a candidate uses agents. A coding test can confirm that they can produce code with one. Neither can tell whether "I would add a contract test at the boundary" is experience or vocabulary. That takes a follow-up question that only someone who has owned a similar system knows to ask.

## What are the common mistakes?

- **Treating a certification as the answer.** AI certifications are issued by AI platforms and industry bodies, and they show that someone learned the tools. They do not replace this conversation. [Which AI certifications for engineers actually mean something](https://blog.nexton.dev/industry/which-ai-certifications-for-engineers-actually-mean-something) covers how to read them.
- **Asking about tools by name.** The tools change every quarter; the failure modes do not.
- **Scoring enthusiasm.** Energy about agents is pleasant in an interview and says nothing about production.
- **Running it as a separate round.** Put it inside the technical interview so the candidate answers about real code.

## How does Nexton do this?

Every engineer is interviewed by another engineer before you see the profile, and the written evaluation comes with the candidate.

That interview is where questions like the ones above happen, run by engineers who know the systems they are asking about. Through Nexton AI Ready, engineers earn AI certifications issued by recognized AI platforms and industry bodies; those sit next to the engineer-to-engineer interview, never instead of it. The first matched candidate arrives in under 72 hours: matched, interested and engineer-vetted. [When caution is the wrong signal](https://blog.nexton.dev/industry/how-to-hire-for-agentic-development-when-caution-is-the-wrong-signal) covers the roles where this playbook needs adjusting.

## FAQs

**Should I avoid hiring engineers who are skeptical of AI agents?**  
No. Skepticism that names a specific failure mode and a fix is a strong signal of production experience. Skepticism that rejects agents in general is a weak signal, in the same way that general enthusiasm is.

**What is a good interview question about agentic development?**  
Give the candidate a real change from your system that an agent made, and ask what would stop them from merging it. Score how specific the failure mode is.

**Do AI certifications replace a technical interview?**  
No. Certifications are issued by AI platforms and industry bodies and show what someone learned. A live conversation with an engineer shows how they apply it to a system that can fail.

If you want to see how this reads in a written evaluation for one of your open roles, it's worth a conversation.

---

Sources: Rachel Laycock, "Why are good developers so wary of agentic development?", martinfowler.com, October 29, 2026 (verified November 2026). 2025 DORA report on AI-assisted software development, as reported by InfoQ, September 2025 (verified November 2026).

![Nexton](https://blog.nexton.dev/hs-fs/hubfs/circle-cropped%20(8).png?width=150&name=circle-cropped%20(8).png)

#### Nexton

**Blog Team**   
 Nexton empowers companies connecting them with the strongest engineering talent in LATAM.

### Leave a Comment

[![Isologotype](https://blog.nexton.dev/hubfs/Isologotype.svg "Isologotype")](https://nexton.dev/)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Nexton",
    "url" : "https://blog.nexton.dev/industry/author/nexton"
  },
  "dateModified" : "2026-11-17T16:54:24.204Z",
  "datePublished" : "2026-11-17T16:54:24.000Z",
  "headline" : "How to interview engineers for judgment about AI agents",
  "image" : [ "https://blog.nexton.dev/hubfs/INC%20Masters%20&%20Fast%20Company%20publishing%20(4).png" ],
  "mainEntityOfPage" : {
    "@id" : "https://blog.nexton.dev/industry/how-to-interview-engineers-for-judgment-about-ai-agents",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.nexton.dev/hubfs/Nexton%20Hubspot.webp"
    },
    "name" : "Nexton"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/#organization",
  "@type" : "Organization",
  "address" : {
    "@type" : "PostalAddress",
    "addressCountry" : "US",
    "addressLocality" : "Miami",
    "addressRegion" : "FL"
  },
  "aggregateRating" : {
    "@type" : "AggregateRating",
    "bestRating" : "5",
    "itemReviewed" : {
      "@id" : "https://nexton.dev/#organization"
    },
    "ratingCount" : "12",
    "ratingValue" : "4.9",
    "url" : "https://clutch.co/profile/nexton"
  },
  "areaServed" : {
    "@type" : "Country",
    "name" : "United States"
  },
  "description" : "Nexton is a human-powered company building nearshore engineering teams for US companies. Senior Latin American engineers, hand-matched and vetted by engineers. 1,500+ engineers matched with 350+ US companies.",
  "disambiguatingDescription" : "Nearshore technology staffing company (nexton.dev) serving US companies with software engineers from Latin America. Not affiliated with Nexton, the master-planned residential community in Summerville, South Carolina (nexton.com); nor with NEXTON Group, the French digital consulting and IT services company (nexton-group.com); nor with the Navee Nexton electric scooter.",
  "employee" : [ {
    "@id" : "https://nexton.dev/#lucas-arana"
  } ],
  "founder" : [ {
    "@id" : "https://nexton.dev/#diego-sternberg"
  }, {
    "@id" : "https://nexton.dev/#agustin-di-luciano"
  } ],
  "foundingDate" : "2017",
  "knowsAbout" : [ "Nearshore engineering teams", "Software engineering recruiting", "Latin American engineers", "AI engineers" ],
  "legalName" : "Nexton",
  "logo" : "https://nexton.dev/Nexton/nexton-logo.png",
  "makesOffer" : [ {
    "@type" : "Offer",
    "itemOffered" : {
      "@type" : "Service",
      "description" : "Nexton's primary model: embedded, long-term engineering capacity. Nearshore LATAM engineers join the client's team as fully integrated, ongoing members rather than short-term contractors.",
      "name" : "Staff Augmentation"
    }
  }, {
    "@type" : "Offer",
    "itemOffered" : {
      "@type" : "Service",
      "description" : "Direct recruitment of LATAM engineers for full-time positions at US companies, with a technical validation process run by engineers.",
      "name" : "Direct Hiring"
    }
  }, {
    "@type" : "Offer",
    "itemOffered" : {
      "@type" : "Service",
      "description" : "Onboarding LATAM engineers as international team members, with no local legal entity required.",
      "name" : "International Team Member"
    }
  }, {
    "@type" : "Offer",
    "itemOffered" : {
      "@type" : "Service",
      "description" : "Payroll management and legal compliance to hire international talent without administrative friction.",
      "name" : "Payroll Processing (EOR/PEO)"
    }
  } ],
  "name" : "Nexton",
  "numberOfEmployees" : {
    "@type" : "QuantitativeValue",
    "minValue" : 50
  },
  "sameAs" : [ "https://www.linkedin.com/company/nexton", "https://clutch.co/profile/nexton", "https://www.crunchbase.com/organization/nexton-b25a", "https://www.trustpilot.com/review/nexton.dev", "https://www.wikidata.org/wiki/Q140867481", "https://www.inc.com/profile/nexton", "https://blog.nexton.dev/" ],
  "slogan" : "Hand-matched Engineers. Vetted by Engineers.",
  "url" : "https://nexton.dev/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/#diego-sternberg",
  "@type" : "Person",
  "jobTitle" : "Co-Founder & CEO",
  "name" : "Diego Sternberg",
  "sameAs" : [ "https://www.linkedin.com/in/diegosternberg" ],
  "worksFor" : {
    "@id" : "https://nexton.dev/#organization"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/#agustin-di-luciano",
  "@type" : "Person",
  "jobTitle" : "Co-Founder",
  "name" : "Agustín Di Luciano",
  "worksFor" : {
    "@id" : "https://nexton.dev/#organization"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/#lucas-arana",
  "@type" : "Person",
  "jobTitle" : "COO",
  "name" : "Lucas Arana",
  "sameAs" : [ "https://www.linkedin.com/in/lucasarana" ],
  "worksFor" : {
    "@id" : "https://nexton.dev/#organization"
  }
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/#website",
  "@type" : "WebSite",
  "description" : "Nearshore tech staffing: hand-matched LATAM engineers, vetted by engineers, for US companies.",
  "inLanguage" : "en",
  "name" : "Nexton",
  "publisher" : {
    "@id" : "https://nexton.dev/#organization"
  },
  "url" : "https://nexton.dev/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/ai/#webpage",
  "@type" : "WebPage",
  "about" : {
    "@id" : "https://nexton.dev/#organization"
  },
  "description" : "Structured information for LLMs and AI about Nexton: value proposition, services, ICP, competitors, and citable data. Includes links to llms.txt, JSON-LD, and sitemap.",
  "inLanguage" : "en",
  "isPartOf" : {
    "@id" : "https://nexton.dev/#website"
  },
  "name" : "Nexton — AI Hub | Nearshore Tech Staffing",
  "url" : "https://nexton.dev/ai/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/#salary-report-2026",
  "@type" : "Report",
  "author" : {
    "@id" : "https://nexton.dev/#organization"
  },
  "datePublished" : "2026",
  "description" : "Nexton's proprietary report with compensation data for LATAM software engineers, used as a reference by CTOs and Engineering leaders in the US to plan hiring and budgets.",
  "name" : "Nexton 2026 Salary Report",
  "publisher" : {
    "@id" : "https://nexton.dev/#organization"
  },
  "url" : "https://nexton.dev/salary-report"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nexton.dev/ai-feed.jsonld#faq",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Nexton is a nearshore tech staffing company that connects US companies with hand-matched LATAM engineers, vetted by engineers, with candidate delivery in 72 hours and hiring in 4 weeks."
    },
    "name" : "What is Nexton?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "For US tech-driven companies, remote-friendly, at Series B+ stage or established, with 50 to 1,000 employees, with buyers such as CTOs, VPs of Engineering, and Engineering Directors, in verticals such as HealthCare, Insurance, and E-Learning."
    },
    "name" : "Who is Nexton for?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Every candidate is technically evaluated by Nexton engineers before being presented to the client, reducing the risk of failed hires compared to traditional staffing processes."
    },
    "name" : "How does the hand-matching process work?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "MatchIQ is Nexton's proprietary AI matching engine, built in-house. It is the methodology behind every Nexton hiring decision rather than a product sold separately. It narrows a database of more than 500,000 LATAM engineers to roughly 500 matching candidates, which then pass three layers of review — MatchIQ matches, handpicked by a recruiter, vetted by an engineer — producing matched and vetted candidates in under 72 hours. Details at https://nexton.dev/matchiq."
    },
    "name" : "What is MatchIQ?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Plans and engagement models (Staff Augmentation, Direct Hiring, International Team Member, Payroll Processing) are quoted based on client needs. For a proposal, reach out via https://nexton.dev."
    },
    "name" : "How much does it cost and how do I get started?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Compared to alternatives such as BairesDev, Toptal, Andela, Turing, Globant, Revelo, Near, or AgileEngine, Nexton stands out for engineer-validated hand-matching, candidate delivery in 72 hours, and a 4-week time-to-hire."
    },
    "name" : "What makes Nexton different from its competitors?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Nexton is US-based, headquartered in Miami, Florida, and specialized in nearshore, sourcing engineers across Latin America."
    },
    "name" : "In which countries or regions does Nexton operate?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A 4.9/5 rating on Clutch and an active LinkedIn presence with nearly 29,000 followers."
    },
    "name" : "What certifications or recognitions does Nexton have?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Yes. Nexton publishes an annual Salary Report with LATAM engineer compensation data, used as a reference by Engineering leaders in the US. Available at https://nexton.dev/salary-report."
    },
    "name" : "Does Nexton publish proprietary market data?"
  } ]
}
```