Career exploration with more honest context

What the platform supports today

The current application uses Supabase-backed identity and marketplace data, role-aware protected routes, employer review, moderated job publication, candidate applications, private document handling, lifecycle tracking, and employer review tools.

Community discussions and replies use server APIs, free Academy courses can store account-backed progress, and signed-in job seekers can keep a home address for commute estimates with persistent route reuse.

What still gates public launch

The source is in launch preparation rather than a verified public release. Production rollout still depends on deploying and verifying the current build, completing authentication and lifecycle email configuration, enabling private malware scanning for resume uploads, enabling production Maps services, and finishing the release checklist for monitoring, backups, cron, staging, legal, and support operations.

How the experience connects

RedTabl is designed around the decision journey between understanding how you prefer to work, discovering a role, evaluating the employer and practical constraints, applying, building skills, and discussing career questions with other people.

The goal is not to maximize feed volume or application volume. The product should make important context easier to compare and carry useful account state from one step into the next.

How we intend to earn trust

Work-style reflection is intended for candidate decision support, not automated hiring decisions or an employer-facing fit score. Employer access, moderation, reporting, and private data visibility should remain explicit and auditable.

RedTabl will publish traction, outcome, adoption, or market claims only when the evidence and method can be explained. Future paid placement must remain clearly labelled and should not hide the organic relevance layer.