Layout reference — not a numerical reference. The scores below are from the original Mach1 evaluation, produced by a narrower model with no Manager DNA, no Company DNA, and no behavioural taxonomy. Recomputing against the rebuilt framework will change them by construction — that is the build working, not drifting. This document shows the v2 structure. Grey italic notes mark what changed and why.
v2 — location is no longer flagged amber here. It is evaluated by the eligibility gate below, not decorated in the meta strip and then deducted again inside a score.
Pre-screening gates · run before scoring, not scored
Inferred · reasoning logged
Gate minimum 4.0 · cleared by +0.6
No AI-generation signals detected. Employment dates cross-reference cleanly against external data. Skill claims internally consistent with role descriptions. Language is specific and idiosyncratic — low inflation probability.
Deterministic
Gate minimum 4.0 · cleared by +0.1
Accomplishments are credible and tenure-consistent. Score reduced by technology-list repetition across roles — dilutes evidence specificity. Barely cleared; evidence quality is real but presentation is noisy.
Eligibility — location & work modelNew
Cannot evaluate
Deterministic · overridable
Required input missing
The requisition's work model was never captured, so the gate has nothing to evaluate against. Candidate is 711 mi from site. The gate is unrunnable — and it says so, rather than passing silently.
Eligibility — work authorizationNew
Cannot evaluate
Deterministic · not overridable
Required input missing
Requisition does not specify authorization or sponsorship requirements. Job DNA input required. Work authorization is a binary fact, so this gate is never overridable.
v2 — two eligibility gates added, and both return Cannot evaluate on this requisition. That is the mechanism working: a gate whose input was never captured declares itself rather than passing by default. On the original card, location appeared three times as decoration — meta strip, gaps list, and inside Bonus factors — and never once as a gate. A candidate 711 miles from site was fully scored.
Evaluation scores — scored against Job DNA, Manager DNA & Company DNA
Technical depth
1.8 /5
Missing core tools; strong only in adjacent skills
New
Manager match
No DNA
on file
30% of composite · complete Manager DNA to score
New
Enterprise fit
4.5 /5
Banking & healthcare — strong enterprise pedigree
Role requirements
1.6 /5
Critical domain gaps — Workday and Playwright absent
Informational
Bonus factors
2.0 /5
Weight 0% — not included in the composite
v2 — Bonus factors is now defined and marked Informational at weight 0. It was averaging three unrelated things into a 2.0 nobody could act on: a nice-to-have skill hit, a location risk, and a Workday penalty already counted in Role requirements. Content is now preferred-skill coverage only (CJ-A06); location moved to the gate layer; the triple-counted penalty is deleted. It computes and displays but does not feed the recommendation — promoting it later is changing one cell. Pips replaced with proportional bars: pips are five discrete states and scores are now continuous, so Enterprise fit at 4.5 was rendering with all five lit.
Composite
Overall
2.7
out of 5.0
✕ Do not screen
Recommendation rationale
Hussain is a capable Lead Python Developer with genuine enterprise depth and strong employment stability — both gates confirm the resume is credible. However, the role requires 4+ years of Workday ecosystem experience, Playwright mastery, and Core HR/HCM domain knowledge. Hussain has none of these. The misalignment is fundamental. Recommend redirecting to backend engineering or data pipeline roles where his strengths apply directly.
How the composite is computed
Dimension
Weight
Effective
Status
Candidate vs. Job
50%
71.4%
11 detail areas. Computes.
Candidate vs. Manager
30%
—
No Manager DNA on file. Drops out; remaining weight renormalizes.
Candidate vs. Company
20%
28.6%
2 detail areas. Computes.
Effective weight = dimension weight ÷ sum of applicable weights × 100. Composite 2.7 × 20 = 54 → below the 55 threshold → "Poor fit, do not submit."
v2 — this breakdown is new. The original card showed five numbers and then a sixth directly beneath them that was not their average and never could be — 2.7 is not derivable from 1.8, —, 4.5, 1.6 and 2.0 by any arithmetic. The five are a presentation view; Job / Manager / Company is the computation. The card simply never showed it. The breakdown also makes visible that 30% of this evaluation is missing while the number still looks confident.
Key strengths and gaps
Strengths
- Python and TypeScript — required for automation framework development
- Enterprise experience in banking and healthcare — gate-verified as credible
- CI/CD, REST APIs, JSON, Agile — solid supporting technical foundation
- AI/LLM integrations (OpenAI, LangChain) loosely align with nice-to-have
- Employment stability — 4+ year tenures, clean chronological history
- End-to-end project ownership with clear leadership examples
Gaps
- Zero Workday experience — 4+ years required; non-negotiable critical skill
- No Playwright — listed as top critical skill for this role
- No MCP (Model Context Protocol) — explicitly required
- No Core HR/HCM domain or Hire-to-Retire workflow knowledge
- Title mismatch — Lead Backend Developer vs. QA Automation Engineer
v2 — location removed from Gaps. It read "711 miles from site if on-site presence is required" — and that conditional was the tell. The requisition's work model was never captured, so nothing could evaluate it. It is now a gate, and the gate reports Cannot evaluate.
Skill match — required skills
| Required skill | Priority | Imp. | Match | Notes |
|---|
| Automation framework dev (Python/JS/TS) | Required | 5 | ✓ Match | Strong Python and TypeScript demonstrated across roles |
| Playwright | Required | 5 | ✕ Missing | No mention in resume or experience of any kind |
| MCP (Model Context Protocol) | Required | 4 | ✕ Missing | No experience with MCP frameworks |
| Core HR/HCM domain knowledge | Required | 5 | ✕ Missing | Background is banking and healthcare IT |
| Workday (HCM, Finance, Payroll) | Required | 5 | ✕ Missing | 4+ years required; candidate has zero Workday exposure |
| Workday integrations (Studio, EIB, APIs) | Required | 3 | ✕ Missing | No Workday integration experience of any type |
| XML/JSON, REST/SOAP | Required | 3 | ✓ Match | Well demonstrated across multiple roles |
| CI/CD and Git | Required | 3 | ✓ Match | GitHub and CI/CD pipelines used throughout career |
| Agile / SDLC | Required | 2 | ✓ Match | Agile methodology present across multiple roles |
| AI-assisted testing capabilities | Preferred | 2 | ~ Partial | AI/LLM experience is adjacent but not testing-specific → feeds Bonus factors |
v2 — Priority is now Required / Preferred from the Job DNA skills table, and an Importance 1–5 column has been added. CJ-A02 was unweighted — a candidate missing a 5-importance skill and one missing a 1-importance skill scored identically. The formula is now Σ(importance × match) ÷ Σ(importance). Preferred skills route to Bonus factors via CJ-A06 rather than having no scoring home at all. A per-skill Recency column is also added upstream — CJ-A03's logic is "used within 18 months," which is not the same as minimum experience, and recency varies per skill.
Detail areas — grouped by scoring dimension
Candidate vs. Job
50% of composite · 11 areas
1
Lead Python Developer, Senior Python Developer, Data Engineer — none align with Workday Automation Engineer. The role family is entirely different.
Technical skill alignment
CJ-A02
2
Foundational languages present and general API/CI-CD skills are real. Missing all critical domain tools: Workday, Playwright, MCP — the three most heavily weighted requirements.
Depth of technical skills
CJ-A03
2
Master-level depth in Python backend and cloud architecture — 10+ years supported. Zero demonstrated depth in Workday ecosystem, HR workflows, or Playwright. Deep expertise, wrong domain.
1
Critical gaps that prevent success: Workday (0 vs. 4+ years), Core HR domain (absent), Playwright (absent). Foundational — not addressable through onboarding or ramp.
—
New criterion. Scores the candidate's mandate experience — Maintaining / Improving / Scaling / Transforming / Building from scratch — against the requisition's. A clean ordinal axis, so distance is scoreable. Requires Job DNA.
Behavioral alignment
CJ-A07 — New
—
New criterion. The requisition ranks its top five behaviours from the 25-item taxonomy; the candidate selects theirs from the same list. Overlap is arithmetic — fully deterministic. Requires Job DNA.
4
Led development initiatives for Bank of America; architected enterprise banking applications end-to-end. Strong technical ownership — the domain is the problem, not the capability.
Credentials & domain
CJ-B03 + CJ-B04 — New
—
New area. Both criteria fed the composite and appeared nowhere on the card. Education/certification requirements not captured on the requisition — CJ-B03 previously scored against no job-side input at all.
Contract stability
CJ-C02 + CJ-C03
5
4+ years at Western Alliance Bank (2017–2021) and nearly 3 years at Banner Health (2021–2024). Reliable long-term commitment pattern. No flight-risk signal for the right role.
Compensation alignment
CJ-D02 — New
—
New area. Computed into the composite but invisible on the card. Requires the approved range and the candidate's expectation.
Communication and clarity
CJ-E01
3
Resume is comprehensive but technology lists repeat across roles — dilutes specific accomplishments. Consistent with the 4.1 Resume Confidence gate: evidence quality is real, presentation is noisy.
Candidate vs. Manager
30% of composite · 1 area
Manager match
CM-A01 … CM-C02
—
Manager DNA not on file. Once captured, Elena scores behavioural alignment against a 25-item ranked taxonomy (deterministic), personality fit against a 20-item list (deterministic), and historical success pattern (inferred — enters at low sub-weight, logs its reasoning, and migrates to deterministic via CM-C01 as placement outcomes accumulate). This dimension carries 30% of the composite.
Candidate vs. Company
20% of composite · 2 areas
Enterprise fit
CC-A01 + CC-B01 + CC-B02
4.5
Bank of America, Western Alliance, Banner Health — large-scale regulated environments, gate-verified. Scale match and complexity tolerance high. Now also absorbs procurement familiarity (CC-B02) — the same "has this person operated here before" signal. One of this candidate's strongest signals for the right role.
—
New area — and the worst offender. Culture and management-style compatibility is 25% of the Company dimension and appeared nowhere on the original card. An autonomous candidate placed into a directive culture is a retention risk that was being computed and never shown. Requires Company DNA.
Informational
weight 0% · not in composite · 1 area
2.0
Preferred-skill coverage only. AI/LLM integrations are a partial hit against the AI-assisted testing preference. Location and the Workday penalty have been removed — the first is a gate, the second was already counted in CJ-A02, CJ-A05 and CJ-B04.
v2 — 11 areas became 15, grouped under the three dimensions that actually compute. Eight of the original areas fed no dimension card at all. Five areas are new: four were criteria feeding the composite with no home on the card, and two are new criteria (CJ-A07, CJ-A08). "JD requirements fit" was retired entirely — it re-scored evidence already measured by CJ-A02, A03 and A05, which funded the mandate criterion without inflating Section A.