Capability is often under-described.
Informal work, foreign experience, volunteer work, practical skills, documents and lived responsibility may never reach a conventional resume in employer-readable form.
Layer 01 · People · workforce intelligence
FastPath connects the whole path from “what have I done?” to “what do I do next?”
FastPath is not only an ATS checker and not only a job board. It is a candidate-controlled evidence and opportunity system. A person can find a real role, upload or explain their work history, compare that evidence against the job’s actual requirements, see what is Supported, Partial, Unknown or a Gap, receive specific evidence/training/credential/support pathways, and produce a reviewable employer-facing packet without exposing private support information by default.
MVP / pre-pilotCross-industryResume + image + voice evidenceCurrent job-source architecture
Important distinction: this IZZYAKOS page explains the complete product. The separate interactive demo is a fictional-data reviewer surface. The deeper FastPath web application contains the full routed product and remains separately controlled for technical review while production protection is being finalized.
The actual problem
The employment journey is fragmented into separate systems.
A resume tool may rewrite words. A job board may show openings. A workforce program may offer training. A case manager may know the transportation or credential problem. FastPath is designed to connect those states around one specific person and one specific opportunity.
Missing proof gets confused with missing ability.
FastPath preserves an explicit Unknown state so “we do not have evidence yet” is not silently converted into rejection or false confidence.
Training is often generic instead of gap-specific.
The system is designed to route a real unresolved requirement to the smallest legitimate next action: stronger evidence, credential recovery, training, apprenticeship or support.
End-to-end user journey
What happens when a person actually uses FastPath.
Each step is a distinct product surface in the full application. The user does not have to complete every step before browsing jobs or support.
Choose an industry or role
FastPath includes cross-industry packs rather than forcing every person into clean energy. The user can start broad or choose an industry context that changes job-search terms and pathway context.
Search current jobs
Enter a job or skill, ZIP and distance. The application calls its jobs API and can aggregate configured employer/API sources such as Greenhouse, Lever, JSearch, Adzuna and USAJOBS, with Remotive/other source fallbacks where appropriate. A vacancy is only presented as a job card when it has a source/application URL.
Make a posting the target
“Check my fit” carries the title, employer, source URL and available job-description text into the evidence workflow. FastPath then reasons against that specific posting instead of a generic occupation label.
Upload evidence
The Resume/Evidence route accepts text, PDF, DOCX and common resume images for local browser extraction. The user can also paste work history, record a voice story or add a transcript so experience omitted from a resume can still be reviewed.
Confirm what the evidence means
Extracted statements retain source type and candidate-confirmation state. FastPath does not automatically upgrade an extracted sentence into a verified fact.
Run ATS Core V3
The target job is parsed into requirements and each requirement is mapped to Supported, Partial, Unknown or Gap with explanation, priority, evidence and next action. This is not a hiring probability or an “ATS pass” prediction.
Route the unresolved requirement
Automatic recommendations can point toward evidence strengthening, a relevant credential or training route, education-record recovery, apprenticeship/represented-work options or local continuity support depending on the actual gap.
Review the candidate packet
The person can save profile/intake information and export a candidate packet. Employer-facing disclosure is intentionally separated from private continuity/support data and candidate-reported evidence remains distinguishable from independently verified evidence.
Full application map
What every major FastPath CTA actually opens.
These are routed product pages in the full FastPath application. The descriptions below explain the user action, system behavior and expected output rather than using label-only navigation.
Industry-specific jobs + training links
User action: choose industry, role/skill, ZIP and radius. System action: request current listings from connected sources, separate live vacancies from general source-door links and preserve original application URLs. Output: job cards with employer/source context plus “Check my fit.”
Multimodal work-evidence intake
User action: upload TXT/PDF/DOCX/image evidence, paste work history or add voice/transcript. System action: extract readable claims locally where supported, retain provenance and leave them unconfirmed until reviewed. Output: candidate evidence ready for target-job comparison.
ATS Core V3 requirement alignment
User action: choose/paste a real target job and run the review. System action: parse job requirements, apply transferable/synonym matching and evidence rules. Output: Supported, Partial, Unknown and Gap requirements with explanation and action.
Continuity + pathway analysis
User action: provide profile/evidence/support context. System action: distinguish qualification evidence from continuity barriers. Output: recommendations where support-only items explicitly carry no ATS-merit impact.
Gap-to-pathway routing
User action: review the unresolved target-job requirement or choose an occupation. System action: route toward official/public training, workforce-funded options, apprenticeship, education recovery and represented-work resources. Output: source links where the external provider confirms eligibility.
Employment-continuity support
User action: choose ZIP/radius and support need such as food, transportation, clothing, reentry, GED or legal/record barriers. System action: surface local/state resources without treating the support condition as qualification merit. Output: practical source handoffs.
From current state to next evidence milestone
User action: review gaps and recommendations. System action: organize unresolved requirements into a practical sequence instead of generic “improve your resume” advice. Output: next-step plan connecting evidence, training and support.
Candidate-reviewed output
User action: review what is ready to share. System action: keep candidate working records, provenance and private support context separate from disclosure. Output: exportable candidate/intake packet for controlled review.
Persistent candidate state and consent
User action: add identity/contact/profile fields and consent choices. System action: save locally when unsigned and to Supabase when authenticated/connected. Output: continuity across the routed experience without requiring login just to browse.
Institutional side of the system
User action: workforce/training partners, sponsors or employers review participation pathways or submit roles. System purpose: create the B2B2C operating bridge around the free candidate experience rather than monetizing candidate access as the primary model.
Jobs integrity
“Verified” must mean something specific.
FastPath code distinguishes live listings, official source doors and fallbacks. The platform should never imply that a general job-board search link is a specific vacancy.
Current source/application URL required
The jobs UI only treats an item as an actual listing when it has a title, employer/organization and source or application URL. Job cards open the original listing rather than pretending FastPath is the employer.
Government/public pathways remain labeled
OhioMeansJobs, USAJOBS and Apprenticeship.gov can be presented as official source doors. Those are trusted places to continue the search, not fabricated vacancy cards.
Provider connectivity determines breadth
The API can use configured Greenhouse, Lever, JSearch, Adzuna and USAJOBS credentials/tokens plus public-source integrations. If live feeds return nothing or are unavailable, the UI must say so and expose trusted source searches instead.
Pathway suggestions
The recommendation engine is supposed to answer “why this next step?”
A pathway is not simply a list of courses. It is a response to a specific unresolved requirement or continuity barrier.
Evidence, credential or training action
If a job requirement is Gap, Partial or Unknown, FastPath can recommend strengthening proof, confirming a credential, recovering education evidence, finding a relevant training route or considering an apprenticeship/represented-work pathway where requested.
Support without lowering merit
Transportation, housing, food, childcare, tools, reentry or schedule barriers may determine whether work is sustainable, but they are structurally separated from qualification merit. Support recommendations can therefore be operationally useful without becoming hidden penalties.
What the public demo shows
The account-free reviewer demo intentionally shows only the central evidence-to-requirement mechanism with fictional data. It is not the entire FastPath application and should not be used as the product feature inventory.
Functional truth boundary
What is built, and what still has to be proven.
The current FastPath production deployment builds successfully and recent Vercel runtime-error aggregation reports no runtime errors in the selected seven-day window. That is engineering evidence, not customer validation.
AreaCurrent stateRemaining proof
Product routesJobs, Profile, Resume/Evidence, Analysis, ATS Lab, Intake, Bridge Plan, Academy, Packet, Partners, Sponsors and related routes exist in the application.Logged-out public production access is still intentionally controlled while deployment protection is being finalized.
Evidence modelMultimodal intake, provenance, candidate confirmation and requirement-state logic exist.Real-user usability and defect discovery need human acceptance testing.
JobsLive-provider API architecture and official-source fallback logic exist.Each production source must be confirmed configured and each displayed vacancy must remain current at review time.
MarketMVP/pre-pilot product and commercialization hypothesis exist.Structured customer interviews, buyer/budget-owner evidence, willingness to pay and partner-pilot proof remain the critical unknowns.