Ashby AI CV Screening Integration: How It Works

Ashby already gives hiring teams a place to manage jobs, applications, and candidate stages. Marxel adds a focused screening workflow so recruiters can review applications against clear criteria and see the evidence behind each evaluation.

The aim is not to create another pipeline. It is to help the team make the first pass through Ashby applications more consistent while keeping Ashby as the place where the wider hiring process is managed.

What the Ashby connection helps you do

With the connection in place, Marxel can bring the role and its applications into a screening job. The recruiter can then:

• review the hiring brief and the criteria for the role;
• screen candidates against that shared standard;
• see which parts of a CV support the evaluation;
• identify concerns or information that needs human review;
• keep screening context available alongside the Ashby candidate record.

Each candidate is placed in one of four screening buckets: Aligned, Potential, Hold, or Unclear. The placement is a way to organise the review. It is not an automatic hiring decision, and the evaluation remains available for a recruiter or hiring manager to inspect.

How a recruiter uses it

The workflow is designed to be familiar:

1. Connect the Ashby workspace to Marxel.
2. Select the role and applications to review.
3. Confirm the hiring brief and screening criteria.
4. Review the evaluations, evidence, and concerns.
5. Add a screening note and review link back to the candidate record when useful.

That means the team can spend less time moving CV files between systems and more time discussing the candidates whose experience needs context.

Explanations make the shortlist easier to use

A candidate list is only useful if the recruiter can explain why someone needs attention. Marxel shows the criteria that matched, the evidence found in the CV, and the points that remain uncertain.

That helps in three situations:

• a recruiter wants to check an Aligned candidate before recommending next steps;
• a hiring manager wants to understand why a Potential candidate deserves a closer look;
• a team needs to resolve a Hold or Unclear evaluation with a specific follow-up question.

The result is a shared starting point for discussion. It does not ask the hiring team to accept an unexplained score.

Stay in Ashby while adding screening context

The ATS remains the source of truth for candidate records and stage decisions. Marxel can add a screening note and a link to the full review, but the current Ashby connection does not move candidates between Ashby stages automatically.

That boundary is deliberate. Screening can help the team decide where to look first, but moving a candidate forward is a decision that needs the full context of the hiring process. Recruiters stay in control of that next step.

Automatic updates with a manual fallback

Ashby can be configured to notify Marxel when relevant candidate activity changes. That helps keep a screening job current as new applications arrive.

Manual sync remains useful when you want to refresh a role yourself, check that a recent application is available, or recover from a missed update. You do not need to choose between automation and control: automatic updates reduce waiting, while manual sync gives the recruiter a clear way to check the latest state.

A controlled rollout for enabled teams

The Ashby connection is being introduced to enabled organizations while we validate the workflow. If your organization has access, the Ashby integration guide explains how to connect Ashby, configure candidate updates, sync applications, and add screening notes.

The goal is a simple addition to the recruiter’s day: start from the Ashby applications already in front of you, see why Marxel highlighted each candidate, and keep the final hiring decision with your team.