--- title: The bottleneck moved from writing code to reviewing it (and that changes who you hire) description: "Agents multiplied code volume; review is now the constraint. A playbook for hiring review judgment: what to test, how to score it, what to change in the brief." image: https://blog.nexton.dev/hubfs/Dise%C3%B1o%20sin%20t%C3%ADtulo-Oct-29-2026-04-20-41-9745-PM.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 # The bottleneck moved from writing code to reviewing it (and that changes who you hire) ![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/the-bottleneck-moved-from-writing-code-to-reviewing-it-and-that-changes-who-you-hire) [Share this blog post on Facebook](http://www.facebook.com/share.php?u=https://blog.nexton.dev/industry/the-bottleneck-moved-from-writing-code-to-reviewing-it-and-that-changes-who-you-hire) [Share this blog post on LinkedIn](http://www.linkedin.com/shareArticle?mini=true&url=https://blog.nexton.dev/industry/the-bottleneck-moved-from-writing-code-to-reviewing-it-and-that-changes-who-you-hire) ![](https://blog.nexton.dev/hubfs/Dise%C3%B1o%20sin%20t%C3%ADtulo-Oct-29-2026-04-20-41-9745-PM.png) Two years ago the slow part of shipping software was writing it. On most teams using coding agents, that is no longer true. The code arrives faster than anyone can read it, and the queue forms at review. In a Harvard study of 718 companies using engineering analytics data, teams that adopted AI agents merged 23% more pull requests, but the time a pull request spent in review rose 49%, and the number of issues actually resolved barely moved ([Chen & Stratton, August 2026](https://fion.ac/jellyfish.pdf)). The constraint moved. The hiring brief, in most companies, has not. This playbook is for a CTO or VP of Engineering planning 2027 headcount. It explains why review capacity is now the scarce resource, what that means for the profile you hire, and how to test for it in an interview, since neither a résumé nor a certification shows it. ## What do you need before you start? You need your own review numbers, because the industry average will not tell you where your queue is. - Pull requests merged per engineer per week, now and a year ago. - Median time from "review requested" to "approved," over the same period. - The share of engineers who actually review, and how concentrated it is. If three people approve 70% of merges, that is your bottleneck, whatever the headcount says. - Incident and change-failure numbers alongside throughput, so you can tell speed from recklessness. ## Why did the bottleneck move to review? Because agents multiplied the volume of code without multiplying the number of people who can judge it. Why this matters: Will Larson, writing about his own company's data, reports that the average engineer at Imprint merges four times the pull requests of two years ago, two teams merge ten times as many, and the median review went from about 33 minutes to about 77 ([Larson, October 2026](https://lethain.com/small-changes/)). The Harvard data shows the same shape across hundreds of firms: more code, longer reviews, more "changes requested," and productivity gains that "do not fully pass through to changes in software output." The engineer who can decide whether code they did not write is safe to merge is doing the work that gates everything else. What good looks like: a team that measures review latency as a first-class delivery metric, next to deploy frequency, and staffs against it. ## What skill are you actually hiring for? Judgment about code the candidate did not write: can they scope it, find what is wrong with it, and decide what to do about it. Why this matters: writing code with an agent is now a commodity skill; most of your candidates have it. Reviewing generated code well is not. It requires reading before running, knowing the system well enough to spot a plausible-looking change that breaks an invariant, and being willing to send work back. Larson lists what review is for: sharing knowledge, catching errors, preventing bad actors, and compliance. Three of those are judgment tasks. None of them appears on a résumé as a line item, and no certification tests them. What good looks like: a senior candidate who, shown a generated pull request, asks what the surrounding system assumes before commenting on the diff. ## How do you test review judgment in an interview? Give the candidate a real pull request to review, with a planted defect that is findable by reading, and score the review rather than the code. Why this matters: a live review segment mirrors the job better than a coding exercise now does. Thirty minutes, a 200-line change with one logic error and one design problem, and the question "would you approve this, and what would you write?" Score four things: whether they read the whole change before running anything, whether they found the defect and how, whether their comments distinguish "must fix" from "preference," and whether they asked about context the diff does not show. What good looks like: a written review you would be comfortable sending to the author as is. If you want a parallel segment on how candidates work with the tools themselves, [How to evaluate AI experience when hiring engineers](https://blog.nexton.dev/industry/how-to-evaluate-ai-experience-when-hiring-engineers) covers it. ## How do you change the brief? Move "review" from a nice-to-have to a stated responsibility with a number attached. Why this matters: most briefs still describe output ("ships features in a modern stack") and treat review as something everyone does on the side. If review is your constraint, the seat should say so: expected share of time in review, ownership of a service's merge standard, responsibility for the automated checks that decide what needs a human at all. Larson's own fix is to route the smallest, lowest-risk changes past human review entirely, which only works if someone senior owns the rules. That is a role. [How to write an engineering brief that hires for judgment, not throughput](https://blog.nexton.dev/industry/how-to-write-an-engineering-brief-that-hires-for-judgment-not-throughput) has the template. What good looks like: a brief that names the systems the hire will be the reviewing authority for. ## What are the common mistakes? - **Hiring for throughput you no longer need.** Another fast writer adds to the queue; it does not drain it. - **Treating review as overhead to automate away.** Automated sensors handle the mechanical checks; they do not replace judgment on design and risk, and the Harvard data shows humans still write most review comments. - **Letting "meat proxy" review count as review.** An engineer relaying an AI reviewer's comments without reading the change is not reviewing, in Larson's phrase. - **Reading a résumé for review skill.** It is not there. It only shows up when you watch someone do it. ## 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 evaluation is, literally, a review artifact: an engineer's written judgment about another engineer's work, with the reasoning shown. It is the same skill this playbook asks you to hire for, applied one step earlier. When you build a team through Nexton, the first matched candidate arrives in under 72 hours, matched, interested, and engineer-vetted, and the average from brief to signed offer is four weeks. For why a matching system needs that independent review step at all, see [MatchIQ as an architecture: why matching needs independent verification](https://blog.nexton.dev/industry/matchiq-as-an-architecture-why-matching-needs-independent-verification). For what "senior" should mean when agents flatten raw output, see [How to define "senior" when agents compress the output gap](https://blog.nexton.dev/industry/how-to-define-senior-when-agents-compress-the-output-gap). If your review queue is the thing slowing 2027 down, it's worth a conversation. ## FAQs **Should I hire fewer engineers now that agents write most of the code?** The data says the gains do not pass through to output on their own; they get absorbed by review. Hire for the constraint, which today is review and verification, rather than cutting seats on the assumption that writing was the expensive part. **Can automated review tools replace a human reviewer?** They replace part of the work: formatting, known patterns, obvious errors. Larson's approach routes small, low-risk changes past humans entirely. Design judgment, system context, and the decision to send work back still need an engineer, and the share of comments written by AI was under a quarter in the Harvard sample as of March 2026. **How do I know if review is my bottleneck?** Compare review latency and pull requests merged over the last year. If merges rose and review time rose with them while issues resolved stayed flat, the queue is at review. --- Sources: [Chen & Stratton, "Artificial Intelligence in the Firm: Bottlenecks in Software Production"](https://fion.ac/jellyfish.pdf), Harvard, August 2026 · [Will Larson, "Speeding up code review with small-change"](https://lethain.com/small-changes/), October 2026. Verified October 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-10-29T16:21:05.221Z", "datePublished" : "2026-10-29T16:21:05.000Z", "headline" : "The bottleneck moved from writing code to reviewing it (and that changes who you hire)", "image" : [ "https://blog.nexton.dev/hubfs/Dise%C3%B1o%20sin%20t%C3%ADtulo-Oct-29-2026-04-20-41-9745-PM.png" ], "mainEntityOfPage" : { "@id" : "https://blog.nexton.dev/industry/the-bottleneck-moved-from-writing-code-to-reviewing-it-and-that-changes-who-you-hire", "@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?" } ] } ```