How RoleSprint evaluates job fit
RoleSprint evaluates one specific job against one specific person. It reads the job description you paste, compares it with the experience evidenced in your resume and the targets and standards saved in your profile, and returns a fit score from 0 to 100 together with an Apply, Consider, or Skip verdict.
The purpose is deliberately narrow: to help you decide whether a role is worth your time before you invest time applying to it. This page explains how that judgment is formed, what the fit score does and does not mean, and what RoleSprint cannot know.
What RoleSprint evaluates
The analysis works from the job information you provide, the experience evidenced in your resume, and the targets and standards saved in your profile.
Where a practical constraint such as location, work arrangement, or compensation needs clarifying for a particular role, your answer about that role can inform the verdict as well.
The job description
The analysis reads the posting you provide. The more complete that text is, the more the analysis has to work with. You can paste a link instead, and RoleSprint will try to read the posting from that page, but some job boards block automated reading. When that happens RoleSprint asks you to paste the description rather than analyzing a bare link, which carries almost no information about the role.
Your resume
Your resume is the evidence base. What appears there is what the analysis treats as demonstrated experience. If no resume text is available, RoleSprint still runs the analysis against your profile alone and reports lower confidence, because there is less evidence to reason from.
Your targets and standards
Your profile tells RoleSprint what you are aiming for: your target roles, current title, experience level, preferred work styles, target locations, whether you are open to relocating, your minimum compensation, the standards you have set for your search, and whether you are changing careers. These shape the result. The same role can be a reasonable fit for your background and still fall outside what you have said you want.
RoleSprint does not research the employer, look up market pay data, or consult outside sources as part of the fit analysis. It works from the information you give it.
What the fit score means
A RoleSprint fit score is a 0 to 100 rating of how well one specific job matches one specific person, based on the evidence provided.
RoleSprint does not apply a fixed point value to each skill, title, or year of experience. The analysis evaluates the available evidence in context rather than calculating the score from a published weighting formula.
The score is role-specific and person-specific. The same job can score differently for two people, and the same person can score very differently across two roles. Requirements the role treats as essential, where your evidence does not support them, can lower the score.
The fit score is not a probability. It does not estimate your chance of getting an interview, receiving an offer, or being hired. It is decision support for a narrower and more answerable question: whether this specific opportunity appears worth your effort, given what you have shown you can do and what you have said you want.
What Apply, Consider, and Skip mean
The verdict is RoleSprint's recommendation about how to spend your time.
Every completed analysis returns exactly one of three.
Apply
Apply means the role is worth your time. The role lines up with your evidenced experience and your search standards closely enough to justify a focused application.
Consider
Consider means the role is worth a closer look. There is a real case for it and a real gap to weigh. RoleSprint recommends deciding deliberately rather than applying on reflex.
Skip
Skip means the mismatch is large enough that applying is unlikely to repay the time it would take. RoleSprint recommends protecting that time for stronger opportunities.
Skip is guidance, not a prohibition. If you have a reason to pursue a role that RoleSprint scored as Skip, you can still choose to pursue it. RoleSprint treats that as a deliberate stretch rather than the recommended move, and it will say so: choosing to go ahead does not close the gaps the analysis found.
No verdict is a prediction of what the employer will do.
Capability fit and practical compatibility
RoleSprint judges two different things about a role and keeps them separate: whether you can do the job, and whether the job works for you.
| Comparison | Capability fit | Practical compatibility |
|---|---|---|
| The question | Can you do this job? | Does this job work for you? |
| What it considers | Skills, seniority, domain background, responsibilities, and scope, as evidenced in your resume | The role's stated location and work arrangement, and its compensation, against the standards saved in your profile |
| How a concern appears | A requirement the role states that your resume does not evidence | A stated condition of the role that conflicts with what you have said you need |
| What can resolve a concern | Relevant experience you already have that is not yet clear in your resume or profile | An answer you give about this specific role, clarifying a preference or constraint |
This separation matters because the two fail differently, and the response to each is different. Being professionally well matched to a role you cannot practically take is not the same problem as wanting a role your experience does not yet support. RoleSprint says which of the two is driving the verdict.
Resolving a practical condition does not add capability. Confirming that you would relocate for a role removes a logistical objection; it does not add domain experience you have not had. The reverse holds too: being well qualified does not resolve a compensation conflict.
Where a posting states a location, work arrangement, or pay range that appears to conflict with your saved preferences, RoleSprint may ask you one short question about that specific role before producing the verdict. Your answer applies to that role and is treated as more current than your saved defaults. A condition you have already settled is then treated as settled, rather than counted against the role a second time.
How RoleSprint handles evidence and gaps
RoleSprint treats your resume and profile as the evidence base. A requirement the evidence does not support is reported as a gap rather than assumed to be met.
Keyword overlap alone is not treated as evidence of fit. A term appearing in both the job description and your resume is not by itself a reason to rate the role higher. The analysis looks for evidence of relevant experience and qualifications in context: what you did, at what level, in what domain, and at what scope.
Every analysis returns its reasoning alongside the score, not just a number:
- Strengths. Points where your background genuinely matches the role.
- Gaps. Requirements the role states that your resume does not evidence.
- Risks. Concerns visible in the posting itself, such as vague scope, unstated compensation, a seniority mismatch, or a role that blends two functions.
- Reasoning. A plain-language explanation of the decision, referencing the specific alignment and the specific gaps.
Because the reasoning is shown, you can evaluate it. If a gap reflects experience you have but did not include, the useful response is to make that experience visible in your resume rather than to discount the score.
What RoleSprint cannot know
RoleSprint evaluates the information it is given. Several things that shape a real hiring decision are simply not available to it.
- It does not research the employer as part of the fit analysis. It does not check company reputation, verify that a posting is genuine, or estimate market pay.
- It cannot see the employer's candidate pool. It does not know who else applied or how you compare with them.
- It cannot see internal referrals. It has no view of candidates already moving through the process.
- It cannot know a hiring manager's undisclosed preferences. Only what the posting states is available to the analysis.
- It cannot know criteria left out of the posting. If a requirement was never written down, RoleSprint cannot weigh it.
- It does not predict interviews, offers, or hiring outcomes. A high fit score is not a forecast that you will be contacted.
- It depends on how complete your inputs are. A thin job description or a missing resume leaves less evidence to reason from, and RoleSprint reports lower confidence when that happens.
These limits define what the result can support. Read the fit score as a reasoned assessment of whether an opportunity appears worth your effort, not as a measurement of your chances of being hired.
How confidence works
Confidence reflects how complete the available evidence was. It is not an estimate of how likely you are to be hired.
- High
- A full job description and a substantive resume were both available.
- Medium
- One of the two inputs was thin, such as a short job description or a partial resume.
- Low
- No resume text was available, or the job input was a bare link or very short.
When no resume text is available, the analysis reports low confidence and says so in its summary.
Confidence and fit score answer different questions, and reading one as the other is the most common way to misread a result. A high fit score with low confidence means the available evidence pointed toward a strong match, but there was not much of it. Treat that as a reason to supply a fuller posting or add your resume before leaning on the result, not as a weaker recommendation.
How to use the result
RoleSprint is decision support. It gives you a reasoned recommendation and the evidence behind it. You make the call.
When the verdict is Apply
Read the gaps before you apply, not after. Tailor your resume and cover letter to this specific role, keep your strongest proof points aligned to what the role actually asks for, and be ready to speak to any gap the analysis found.
When the verdict is Consider
Use the gaps to decide whether this is a realistic shot. If you go ahead, strengthen the fit honestly rather than overstating experience, and compare the role against your stronger matches before you commit time to it.
When the verdict is Skip
Move on to a stronger opportunity, and use the reasoning to sharpen what you are searching for. If you still want to pursue this one, treat it as a deliberate stretch rather than your default move.
The guidance attached to a verdict does not change the score or the decision. It is a recommended path, not a gate.
When a role is worth pursuing
When the analysis says a role deserves your effort, RoleSprint can help you prepare for it: a role-specific resume, a cover letter, a recruiter note, and outreach drafts, grounded in the experience and history you provide. You review everything yourself before anything is sent.