Track applications and browse jobs from reviewed public ATS feeds. Sponsorship evidence and skill matching stay clearly labeled roadmap work until they are built.
Available features are marked clearly. Planned sponsorship evidence, matching, and additional ATS providers remain roadmap items until their specs are agreed and built.
Keep applications, interview steps, notes, and salary details together in a focused tracker.
Planned government-data imports will attach evidence to employer signals. Until evidence exists, the catalog shows unknown.
Planned observable AI will compare a user profile with job requirements and show its inputs and uncertainty.
Reviewed Lever public feeds are live. Greenhouse and Ashby are the next provider slice after an agreed spec.
The tracker stores interview and offer details today. Tailored preparation and broader market insights are future work.
Protected routes verify Supabase JWTs, user-scoped tables use Row-Level Security, and backend secrets stay server-side.
The interface separates shipped capabilities from planned work so you can evaluate the product without inflated claims.
Explore what is built today. Every stage below states its real delivery status and the spec it was agreed under, and nothing here reports measured performance or live user activity.
Keep your saved applications and progress organized in one user-scoped tracker.
Browse public Lever postings from a reviewed set of company career boards.
Two more public ATS sources, agreed in spec 0004 and shipped alongside the Lever adapter.
Build source-backed sponsorship evidence and explainable skill-gap guidance in later slices.
The shipped foundation protects user-scoped data, validates public feed boundaries, and preserves uncertainty where evidence does not exist.
Protected API routes derive identity from verified Supabase JWTs, and user-scoped tables enforce Row-Level Security.
The catalog does not present a sponsorship grade without supporting evidence text.
Backend-only ingestion uses reviewed public sources, bounded requests, and deletion-safe snapshots.
CI verifies the application builds, and the deployed API exposes a health endpoint for operational checks.