ArcLens works as a decision engine. It reads the posting against your background, scores the fit on ten measures, checks the posting itself, and gives you one call: Pursue, Conditional or Pass, with the reasons.
3.1Fit Read
The Fit Read is the full picture — your Career History read against the job through your Lens. It's what comes after the score: a qualitative synthesis of where you're strong, where you're thin, and what a hiring manager would likely flag if they opened your résumé right now.
The Fit Read has three parts. The opening is a read on the job itself — a compressed version of the Job Read written in terms of what it means for your specific fit. This isn't boilerplate; it changes based on your Lens and Career History, because what matters about a job depends on who's applying to it and through which Lens.
The middle is your evidence against the job's demands: what you have that's directly relevant, what's adjacent and could transfer, and what's absent. Absent doesn't always mean disqualifying — the Fit Read distinguishes between gaps that are likely to be screened for and gaps that appear in the posting but aren't what the job actually weights.
The close is what you'd need to prove in an interview: the gaps you'd have to address, the questions you should expect, the narrative thread you'd need to hold from first screen to final round. This section isn't hypothetical — it's derived from the Job Read and your specific coverage gaps.
The Fit Read is written for you, not for a recruiter. The language is direct and specific. It will tell you things a résumé reviewer won't say to your face — that's the point. Use it before you build, not after.
A Fit Read consumes a read token. You can re-read the same job under a different Lens without consuming an additional token if the posting hasn't changed. Changing your Lens and re-running generates a new Fit Read.
The Fit Read
Technical Program Manager
Blue Orbit · Van Horn, TX · On-site
5.6/10
PASS
Read throughCapstone Director ICCapstone Director — Delivery & GovernanceEXECUTION CREDIBILITY GAP
The Job Read
What this job really is
A senior TPM embedded in Blue Orbit's Operations organization, stitching together cross-functional initiatives across Integrated Supply Chain, Test Operations, Safety, and Mission Assurance. The job exists to prevent the misalignment — duplicate spend, missed deadlines, safety compromises — and translate high-level strategy into executable plans engineering teams can actually follow.
What's broken right now
The portfolio lacks a single throat to choke for cross-organizational initiatives, causing duplicate spend on overlapping vendor contracts. The org is flying blind on systemic risks — unprotected APIs, gaps in QA — because no one is proactively mapping failure modes before they become incidents.
What makes a safe hire
Someone who can walk into a room of engineers and business leaders and get everyone to agree on what 'done' looks like — without escalating every minor disagreement. Can turn vague organizational goals into concrete milestones and hold teams accountable without being the smartest person in the room.
Capstone Director IC · the read
The only real question
Can this candidate transition from portfolio governance in hospitality and public sector IT to hands-on technical program management for aerospace systems, with the execution credibility to own cross-functional delivery in a high-stakes engineering environment?
Where it may not fit
Lens emphasizes portfolio governance and financial stewardship, but the job requires hands-on TPM in an engineering-driven environment. Preference for 'fixing the process' may create friction where TPMs are expected to dive deep into system design and technical dependencies.
Career in hospitality, public sector, and automotive IT does not prepare for aerospace systems — safety-critical engineering, low-tolerance failure modes, or the physical constraints of a remote, high-stakes site.
What you must prove
Technical depth and system ownership
Show experience owning technical requirements and driving decisions in an engineering context — not just coordinating across teams.
"Walk us through a time you had to dive deep into a technical system to identify dependencies or risks. How did you use that knowledge to drive delivery?"
Execution credibility in engineering-driven environments
Provide examples of managing programs where engineering teams were the primary stakeholders, balancing governance with hands-on problem-solving.
"Describe a program you managed where engineering teams were your primary stakeholders. How did you deliver on time in a high-stakes environment?"
Alignment by dimension
Industry Fit3.0
Altitude6.0
Scope5.5
Risk5.0
Background5.5
Composite5.6
Specific Gaps
MISSINGNO EVIDENCE
Direct experience leading end-to-end program management for aerospace, defense, or safety-critical system delivery.
Career History shows governance and cross-functional coordination, but does not include examples of engineering-driven delivery in safety-critical environments. No evidence for this in your Career History. If most gaps look like this, this isn't the right role.
WEAKNO EVIDENCE
Proven track record delivering results for large cross-functional initiatives in an engineering-driven environment.
Large-scale delivery experience exists, but framed around governance and compliance — not engineering execution. Your Career History doesn't show these were engineering-driven environments.
What They're Actually Buying
PRIMARY
Technical depth sufficient to challenge engineering assumptions and diagnose systemic failure modes
PRIMARY
Experience shipping complex technical products in high-stakes environments where delays have severe consequences
context the posting won't give you
5.6/10 = fit through the Capstone Director IC Lens
the Fit Read — your experience matched against this job
3.2Gap Check
Before you commit a build, the Gap Check shows you what your Career History doesn't have for this posting. It runs between the Fit Read and the build decision — a final inventory of distance before you spend a build token.
The Gap Check categorizes what's missing into three types. The first is a real gap: a skill, credential, or domain of experience the job genuinely requires and your Career History doesn't contain. The second is an apparent gap: coverage your history has but that didn't surface clearly in the Job Read — often because your source material described it in different terms than the posting used. The third is an irrelevant gap: a requirement that appears in the posting but isn't what the job actually weighs, typically boilerplate added by HR or a line inherited from a previous posting.
For each gap, you have a decision to make. You can address it in the build — surface adjacent evidence and frame it toward the requirement. You can acknowledge it — proceed with the build knowing the gap exists and prepare your interview answer. Or you can walk away — decide the gap is disqualifying given where you are today and direct your build tokens toward a better-fit posting.
Committing a build token on a posting with unexamined gaps is the most common source of a build that doesn't land. The Gap Check exists specifically to surface this before you commit, not after. Don't skip it.
The Gap Check doesn't prevent you from building — it informs the decision. Every gap isn't a reason to walk away. Some of the best builds come from postings with one significant gap and strong coverage everywhere else, where the candidate has a clear answer for the gap and the Fit Read surfaces exactly what that answer needs to be.