Built for job seekers
The service is free to use and focuses on helping applicants find openings faster and organize their experience against job requirements.
2026 Product Systems Case Study
A FastAPI-based career support system that validates official job sources, matches profile facts against job requirements, and generates fact-grounded resume and portfolio drafts.
Live Public Service
CareerFit RCR is a free public webpage for discovering job postings and drafting application materials. The public origin runs in a stateless mode designed so user-entered information is not stored in the server database.
The live server currently reports disabled user-data and document storage through its stateless health check.
The service is free to use and focuses on helping applicants find openings faster and organize their experience against job requirements.
Job data comes only from public recruitment APIs, Seoul/Busan public jobs OpenAPI, and company career pages individually checked for robots.txt, public URL access, and source status.
Profiles, answers, selected jobs, and generated documents are not collected, processed, sold, or shared with third parties, and are not stored in the server database.
The system does not use login bypass, CAPTCHA bypass, WAF bypass, paywall bypass, private APIs, proxy rotation, or reused accounts and tokens.
If terms, robots policy, public access, or automated-collection permission is unclear, the source stays in review or fail-closed status and is excluded from recommendation evidence.
In public mode, profile, jobs, collect, documents, and admin-like settings APIs are blocked so local operations stay separate from the public demo.
The public demo avoids server-side storage of user profiles, answers, and generated documents. SQLite state and Cloudflare Workers AI settings only open in local stateful mode.
CAREERFIT_PUBLIC_STATELESS_MODE./docs, /redoc, and /openapi.json, and served a deny-all robots.txt.The public origin can be shared for demos without persisting profile data, answers, or generated document text on the server.
Scores, gate reasons, evidence coverage, and requirement-match summaries show why a job is recommended or held for review.
Official APIs and robots validation come first; private hosts, unclear source evidence, and automated-collection blocks fail closed.
The system avoids inventing experience or metrics and moves weak claims into excluded suggestions or follow-up questions.
FastAPI keeps product policy and scoring authority while the Rust collector handles network-heavy validation and collection work.
Docker Compose, pytest, ruff, mypy, and stateless health checks define the development and operations verification loop.
The work includes not only implementation, but also public-demo storage policy, source-verification policy, document evidence, and operations validation commands.