Skip to content

For hiring managersIn your recruiter’s Marxel workspace

See why every Candidate is where they are.

Your recruiter invites you to their workspace. Shape the criteria, read the CV evidence, compare finalists side by side and make the call, with your notes kept on the record.

Before screening

Your briefing call becomes the criteria.

What you tell your recruiter (“portfolio matters more than years”) becomes the criteria. Each one shows the line it came from, judgement calls come with a reason, and nothing is screened until it’s confirmed.

Criteria features →
From the briefing call

“Portfolio matters more than years. Must have run accessibility audits, we failed one last year. Fintech is a bonus, honestly.”

Screening criteriaConfirmed3 must-haves · 1 nice-to-have
Portfolio qualityCall notes · “Portfolio matters more than years.”
Must-haveNice-to-have
Accessibility auditsCall notes · “Must have run accessibility audits.”
Must-haveNice-to-have
Design systemsJob description · “You’ll own our component library.”
Must-haveNice-to-have
Fintech experienceJob description · “Fintech experience required.”
Must-haveNice-to-have

The JD says required, but the hiring manager called it a bonus, so it’s a nice-to-have. Switch it back if you’d rather screen on it.

Left out “owns the design roadmap”: it’s a duty, not something a CV can evidence.Add back

Screening 42 CVs

Reviewing a shortlist

Evidence, not a score.

Every Candidate shows which must-haves the CV meets, the quote behind each one, and what is missing. You can see why someone is where they are without rereading the CV.

  • StrongEvery must-have met, with strong evidence
  • GoodEvery must-have met, with gaps elsewhere
  • PartialA must-have is missing or the fit is weaker: worth a look
  • LowNo must-have evidenced in the CV
Screening features →
PotentialBest match Partial · 3 of 4 must-haves met
Criteria match10View all
  • Design systems

    Must-haveWeight High

    “Led the design system at a Series B fintech, 40+ components.”

    Met
  • User research

    Must-haveWeight High

    “Ran 30 interviews a quarter and set up the research repository.”

    Met
  • Mobile and web

    Must-haveWeight Medium

    “Shipped iOS, Android and web apps for 2M users.”

    Met
  • Accessibility audits

    Must-haveWeight Medium

    No mention of WCAG audits or accessibility testing in the CV.

    Missing
  • Fintech experience

    Nice-to-haveWeight Low

    Two years at a payments start-up, mostly marketing site work.

    Partly

Suggested follow-up

“Have you run or commissioned an accessibility audit? What changed as a result?”

A Candidate’s Best match with the CV evidence for each criterion

Choosing between finalists

Compare finalists. You make the call.

Open two to four Candidates side by side, switch on Differences only, and read the CV quote behind every cell. Marxel doesn’t rank them. You choose the Screening Bucket and add a note.

See the compare view
All candidatesComparing 3In the order you picked them. You make the call.Differences onlyAdd to compare
Criteria4 must-haves · 3 nice-to-haves
1 soft criterion · 1 red flag
PSPriya ShahSenior SRE · Leeds
Must-haves4/4
TOTom OkaforPlatform Engineer · Manchester
Must-haves4/4
LFLena FischerDevOps Lead · Remote, UK
Must-haves3/4
Must-haves · 43 where everyone matches, hidden
Runs Kubernetes in production
Evidenced“Ran 40+ EKS clusters serving payments traffic, 2021 to present.”
Evidenced“Migrated the monolith to GKE; 12 services now in production.”
Evidenced“Led Kubernetes adoption across four product teams.”
Infrastructure as code (Terraform or similar)
Evidenced“Moved all infrastructure to Terraform modules; provisioning went from days to minutes.”
Evidenced“Terraform for GCP projects, networking and IAM.”
Evidenced“Owned the Terraform and Ansible estate for 30 services.”
On-call ownership of production services
Evidenced“Primary on-call for the payments platform on a 1-in-6 rota.”
Evidenced“Weekly on-call for checkout and order services.”
Evidenced“Ran the incident rota and escalation policy for the platform team.”
Writes tooling in Go or Python
Evidenced“Built deploy tooling in Go, used by 60 engineers.”
Evidenced“Wrote Python CLIs for release automation.”
CV contradicts this“I don’t write application code; tooling is handled by the platform team.”
Nice-to-haves · 3
AWS at scale
Evidenced“Multi-region AWS across three regions, 99.99% uptime.”
Not in CVThe CV describes GCP only. Worth asking.
Evidenced“AWS Solutions Architect, Professional. Ran EKS and RDS for 2m users.”
Mentors other engineers
Not in CVNo mentoring or line management mentioned.
Evidenced“Mentored two graduate engineers through their first year.”
Evidenced“Line-managed five engineers; two promoted to senior.”
Observability (Prometheus, Grafana or similar)
Evidenced“Rolled out Prometheus and Grafana; cut alert noise by 70%.”
Unclear“Improved monitoring for checkout.”
Evidenced“Built the Grafana and Loki stack used by every team.”
Your decisionMarxel won’t pick for you.
Aligned
Potential
Unlikely fit

2 to 4 Candidates

Pick them from the Candidates list. Add or remove people without leaving the view.

Differences only

Hide the rows where everyone has the same result and look at where they differ.

Re-screen in place

Re-screen anyone from the view, so the evidence matches the criteria you have now.

Your decision, recorded

Set each Screening Bucket and add a note. The change is saved with who made it and when.

Between meetings

Ask a question. Approve the emails that go out.

Communicate features →

Ask Marxel, with approvals

Ask anything about your Candidates. Marxel shows the line in each CV, and any move it suggests waits for approval.

User research for Product Designer

Has anyone run user research themselves, not just sat in?

Worked for 5s
ExperienceSenior Product Designer, Ledgerly2021 – presentPlanned and ran 24 moderated usability studies, then turned the findings into the 2023 onboarding redesign.Cut onboarding drop-off by 18% with a shorter identity check.
PSPriya ShahAlignedRan it1 / 3Open full CV
Move Priya Shah to AlignedMoved by youCancelMoved

Approve decision emails

With Admin access, the decision emails your recruiter drafts wait for you in Needs approval. Approve them, or send one back with a note.

Needs approval4
Rejection emailsSends Thu 09:00
+9To 12 Candidates · Product Designer
From julia@northwind.healthTemplate · After screening

Hi first_name, thank you for applying for Product Designer…

ApproveSend back with a note
TRNext steps for Priya ShahFrom Tom Reyes · OutlookReview
SPInterview invite to Amira HassanFrom Sam Patel · GmailReview
JKDecision for Lena FischerFrom Julia Kent · GmailReview
This week18 approved · 1 sent back

Bring your next role into Marxel.

Start with one job and the CVs you already have. Free plan, no card required.