Full-stack software developer
Full-stack web product · Job-search operating system
Roleway gives each focused job search its own Workspace, connecting Jobs, Opportunities, next actions, interviews, contacts, documents, and outcomes while an optional Agent prepares work that users approve.
Product showcase
Selected product surfaces from the live experience, presented without simulated chrome or scroll-driven effects.
A serious job search spreads across browser tabs, spreadsheets, calendars, documents, and notes. Different career targets blur together, follow-ups are missed, preparation loses context, and it becomes difficult to decide what deserves attention next.
An Account owns a Career Profile and multiple Workspaces, each with its own Jobs, Opportunities, preferences, people, documents, goals, and results. Home orders current work, Opportunities retain the complete dossier and one Next Action, and Roleway Agent prepares grounded drafts or internal changes without taking external action.
Roleway is a pnpm and Turborepo TypeScript monorepo. A Next.js application composes shared workflow rules and Zod schemas, while Supabase provides authentication, PostgreSQL, row-level security, and the durable records behind Workspaces and Agent runs.
Server Components load authenticated Workspace data and Server Actions handle mutations. Client components stay focused on interactive controls, editors, collection views, onboarding, and the installable PWA shell.
Opportunity transitions, workflow labels, Agent permissions, and Zod boundary schemas live in shared packages so domain rules can be tested independently of route components.
Supabase migrations are the source of truth for Workspaces, Jobs, Opportunities, tasks, contacts, interviews, documents, notifications, analytics, and Agent records. Row-level security and server checks enforce ownership.
User-supplied provider credentials are encrypted server-side. Agent runs disclose their context, validate tool output, record steps and approvals, and keep external actions outside the available permission model.
These decisions affect what users can do, where product rules live, and how the system handles failure or change.
An Account can hold separate Workspaces for different career targets. Preferences, Jobs, Opportunities, documents, people, goals, notifications, and analytics stay isolated instead of becoming one shared junk drawer.
A Job stores discovered listing data. Tracking it creates an Opportunity with a stage and one concrete Next Action, so the active list represents deliberate work rather than another bookmarks folder.
Core tracking works without AI. Roleway Agent reads disclosed context, prepares grounded work, and presents exact internal mutations for approval; it cannot apply to jobs or contact employers.
PostgreSQL row-level security scopes records to their owner and Workspace, while server actions independently authenticate callers and constrain mutations by owner and Workspace IDs.
The live product and public repository provide concrete evidence of the implemented features, architecture, tests, and documentation.