ANQ Next Step
A personal application workspace for cover letters, status, next actions, conversations and follow-ups.
Live read-only demo
- Type
- Full-stack application
- My focus
- Forms, validation and draft protection
- The outcome
- A clear view of applications, conversations and the next follow-up.
Fictional applications. The public workspace is read-only.
Keep the next action clear
Applying for a job involves more than moving a card across a pipeline. There is the listing to return to, a cover letter to prepare, a conversation to remember, and a date to follow up.
ANQ Next Step keeps those details with each application. Save a role, prepare its cover letter, record the submission, and keep the next action visible through interviews and offers. A separate private deployment provides the owner workspace; the public demo contains fictional examples.
Forms that preserve your work
A failed save leaves the form and its text open. Leaving an edited form asks for confirmation, and closing the browser warns about an unsaved draft. Only a successful save stores the record; the warnings help protect the editing process.
Two open sessions can otherwise overwrite each other's changes. Version checks reject an older edit so the user can reload and review the current record. Recording a follow-up saves its note, next action and next date together, keeping the conversation history and current plan consistent.
Applications, Follow-ups and Activity have direct links. The selected application survives refresh and Back/Forward navigation. Shared forms, labelled fields and error messages keep the views consistent as the workflow changes.
Keep dates and history dependable
PostgreSQL transactions save stage changes with their history events. Follow-up days are calendar dates, so changing timezone does not move a follow-up to the previous day. Closed and archived applications leave the due-follow-up view while retaining their history.
React and TypeScript handle the interface; Fastify validates each API request. An authenticated owner can edit records and export the complete history as JSON. The public demo uses a separate database and rejects changes at the API boundary.
Evidence to inspect
The record form contains the draft-preservation and discard behavior. Browser tests exercise adding a role, changing its stage, recording a note and follow-up, refreshing, archiving and exporting. API tests check stale edits, dates and access. GitHub CI runs these checks automatically.
Saved materials and history survived application-container replacement and an isolated database restore. The public demo includes fictional cover letters, application addresses and next actions without exposing owner records.
Scope and implementation
This is a single-owner workspace. Applications are submitted outside Next Step; follow-ups are a view to consult rather than delivered reminders. Cover letters are plain text. JSON export complements the database backup but has no matching import endpoint.