Does your story hold up?
The Senior Software Engineer stint at Halyard Holidays lasted six months with no stated reason, and the next role reverts to the Software Engineer title, which is a pattern worth asking about.
The recruiter's read, before you apply.
See your CV the way a recruiter does.
A recruiter-designed framework, applied by AI. A human recruiter does not personally review each CV.
AVAILABILITY
Paid ordering is not open yet.
Explore the sample now. Reviews of your own CV are planned for public launch.
Built around five recruiter questions.
- Do I know what you do?
- Do I buy it?
- Have you done it at this level?
- Does your story hold up?
- Would I invite you to a call?
Every observation points at a line of your own CV. A recruiter-designed framework, applied by AI. A human recruiter does not personally review each CV.
The Yes Pile looks at how your experience comes across to a recruiter, and explains what it finds in words rather than a score.
A sample read
The sample read, in full
An invented CV and its recorded review. Five questions, the lines behind each answer, and the verdict.
Read it through one question
The CV
The verdictLikely a callAn invented CV, shown as extracted text.
- Casey Ferris
- IT Professional
- Leeds, UK | casey.ferris@example.com
- IT professional with six years' experience across insurance, travel and logistics.
- Looking to join a team where I can keep learning and take on more responsibility.
- This line drives the answer to: Does your story hold up? Select it to move to that answer.
- Motor and home insurer. Quotes platform team of six engineers.
- This line drives the answer to: Do I know what you do? Have you done it at this level? Select it to move to the first of them.
- This line drives the answer to: Do I buy it? Have you done it at this level? Would I invite you to a call? Select it to move to the first of them.
- This line drives the answer to: Do I buy it? Have you done it at this level? Would I invite you to a call? Select it to move to the first of them.
- Led the migration to the new event platform.
- Wrote the service's runbook and on-call guide, now used by all four teams in the platform group.
- Pair with the pricing analysts each sprint to turn rating changes into releases: 31 rating changes shipped in 2025 with no customer-facing pricing incident.
- Interviewed for the team and onboarded two graduate engineers in 2025.
- This line drives the answer to: Does your story hold up? Select it to move to that answer.
- This line drives the answer to: Do I know what you do? Select it to move to that answer.
- This line drives the answer to: Do I buy it? Select it to move to that answer.
- Reviewed pull requests across the booking team and introduced a release checklist.
- Software Engineer, Quillon Freight Jan 2022 - Jan 2024
- This line drives the answer to: Do I know what you do? Have you done it at this level? Select it to move to the first of them.
- Wrote the integrations with two courier partners, handling 40,000 parcels a day at peak.
- Moved the team's builds from Jenkins to GitHub Actions, taking the average build from 22 minutes to 7.
- Took the on-call rota for the allocation service and cut the pages per week from 11 to 2 by fixing the three noisiest alerts.
- Junior Software Engineer, Quillon Freight Jun 2020 - Dec 2021
- Maintained the depot scanning app's backend in Java and fixed the sync bug behind most of its support tickets.
- Built the internal tool that operations used to re-plan routes when a depot closed at short notice.
- Promoted to Software Engineer in January 2022.
- This line drives the answer to: Would I invite you to a call? Select it to move to that answer.
- Each change used to need a code release and a two-week regression run; the pricing service now loads tables from a versioned store and checks them against the previous version's quotes automatically.
- This line drives the answer to: Do I buy it? Would I invite you to a call? Select it to move to the first of them.
- BSc Computer Science, 2:1, Westbridge University
- AWS Certified Developer, Associate
- Go, Java, TypeScript, PostgreSQL, Redis, Kafka, AWS, Terraform, GitHub Actions
The read
Select a question to find its evidence. Select a marked CV line to return to an answer.
Yes
WorkingThis one is working in your favour.
It's clear you build and own backend services and APIs (pricing, booking confirmation, delivery allocation) across insurance, travel and logistics, with performance and reliability ownership shown at Tarnbrook Mutual and Quillon Freight.
From the CV:Own the quote pricing service, which prices about 1.2 million quotes a month, including its on-call rota shared with three other engineers.
From the CV:Built the delivery slot allocation API for 300 depots, replacing a nightly batch job with a service that answered in under 200 milliseconds.
From the CV:Built the booking confirmation service in Go, replacing templated emails sent from a legacy PHP system.
I believe this
WorkingThis one is working in your favour.
Most claims carry a clear baseline, method and result (response time, failure rate, regression run time, contract-test catches), which makes them easy to believe rather than generic.
From the CV:Cut the median quote response time from 2.4 seconds to 650 milliseconds by caching rating tables and removing two synchronous calls to the policy system.
From the CV:Reduced failed quote requests from 3.1% to 0.4% over six months by adding retries with backoff and fixing a race condition in the session store.
From the CV:Rating changes went from monthly releases to same-week releases, and the regression run dropped from two weeks to a day.
From the CV:Added contract tests between the booking and payments services, which caught 14 breaking changes before release in four months.
Right at the level
WorkingThis one is working in your favour.
Owning a pricing service end to end, making the specific technical calls behind its improvements, and independently building a depot allocation API are solid mid-level ownership and judgement.
From the CV:Own the quote pricing service, which prices about 1.2 million quotes a month, including its on-call rota shared with three other engineers.
From the CV:Cut the median quote response time from 2.4 seconds to 650 milliseconds by caching rating tables and removing two synchronous calls to the policy system.
From the CV:Reduced failed quote requests from 3.1% to 0.4% over six months by adding retries with backoff and fixing a race condition in the session store.
From the CV:Built the delivery slot allocation API for 300 depots, replacing a nightly batch job with a service that answered in under 200 milliseconds.
This raises a flag
Holding you backThis one is holding the CV back.
The Senior Software Engineer stint at Halyard Holidays lasted six months with no stated reason, and the next role reverts to the Software Engineer title, which is a pattern worth asking about.
From the CV:Senior Software Engineer, Halyard Holidays Feb 2024 - Aug 2024
From the CV:Software Engineer, Tarnbrook Mutual Sep 2024 - Present
A strong case for a call
WorkingThis one is working in your favour.
You show solid ownership of the quote pricing service at Tarnbrook Mutual, with clear, quantified improvements to its performance and reliability, and you redesigned how rating-table changes are released, moving the process from monthly releases to same-week releases with the regression run cut from two weeks to a day. This is good mid-level technical ownership and judgement.
Strongest reason to speak to you: You own the quote pricing service end to end and have made concrete, well-evidenced technical improvements to it, cutting median response time from 2.4 seconds to 650 milliseconds and failed requests from 3.1% to 0.4%. You also redesigned how rating-table changes are released, moving from a code release and two-week regression run to same-week releases with the regression run cut to a day, which is solid mid-level ownership and judgement.
Greatest risk in doing so: The claim that you 'led the migration to the new event platform' has no detail on scope, your specific contribution or outcome, unlike the other bullets in this role which all carry a baseline, method and result. Separately, the six-month Senior Software Engineer stint at Halyard Holidays and the subsequent return to a Software Engineer title are unexplained, which is worth raising as a question rather than treating as a flaw.
From the CV:Cut the median quote response time from 2.4 seconds to 650 milliseconds by caching rating tables and removing two synchronous calls to the policy system.
From the CV:Reduced failed quote requests from 3.1% to 0.4% over six months by adding retries with backoff and fixing a race condition in the session store.
From the CV:Rebuilt how the quotes platform handles rating-table changes.
From the CV:Rating changes went from monthly releases to same-week releases, and the regression run dropped from two weeks to a day.
Would I invite you to a call?
Likely a call
The page is easy to follow: a backend engineer who has owned pricing, booking and logistics services across three employers, with plenty of concrete before-and-after numbers.
On this read, a recruiter would set up a call as it stands. Nothing here would stop them picking up the phone, and anything still open below can wait for the call.
This is a decision about a document. It is not a measure of your ability or your worth.
THE SERVICE AND ITS PRICE
An initial read, or a detailed review of your whole CV.
Explore the sample now. Reviews of your own CV are planned for public launch; paid ordering is not open yet.
Know what to work on first.
Free first read at public launch
- Five questions a recruiter asks
- What works and what raises questions
- The changes to focus on first
One initial read per verified account when public sign-up opens. The sample above is available to explore now.
Go through your whole CV.
£9.99 GBP per review
- Comments linked to the passages they refer to
- Strengths, concerns and suggested changes
- A report you can revisit and download
Planned public offer. One CV submission, no subscription. A new or edited CV needs a new purchase. Paid ordering is not open yet.
Recruiter-designed coaching, delivered with AI. A human does not personally review each submission. Your feedback is not sent to an employer and cannot guarantee an interview.
Invented sample
What the reports look like.
Excerpts from an AI read of an invented CV, and one passage from an AI full review of the same invented CV.
Invented sample
Before and after.
A line from an invented CV, and the possible wording an AI review suggested for it. Check wording like this is accurate before using it.
The interactive sample uses an invented CV and a recorded review. Exploring it does not upload a document or start a review of your own CV.