Read-only demo

One job, from found to tracked

This is the product’s job workspace, its posting history and its board, shown with one made-up job search.

Everything here is fictional: the employers, the roles, the dates, the applicant and the application history. The prepared materials are written by hand to show their shape. Nothing on this page is a live vacancy, and nothing you do here is recorded.

1. A prepared job

Accepting a job gives it a workspace with five sections. This one is Data Engineer at Lakeshore Example, queued on the Data roles track. Its preparation reads Needs review: two drafts are waiting to be read.

Overview · Ready

What the posting states

Requirements stated

  • Three or more years building data pipelines
  • SQL and Python in production

Skills named

Python, SQL, Airflow

Interview stages stated by the employer

  1. Recruiter call
  2. Technical interview
  3. Team conversation

Resume · Needs review

Which resume to send

Recommended: 1B: Data resume, version 3. Confirms the posting’s named skills: Python, SQL.

Sample tailored draft, built only from confirmed facts:

  • Built and ran nightly SQL pipelines in Python for a 40-table reporting warehouse.
  • Cut a daily load from 50 minutes to 12 by replacing row-by-row inserts with bulk loads.

Removed, because no confirmed fact states it:

  • Led a team of five engineers

In the product the draft is yours to edit and approve, and downloads as PDF or Word.

Application answers · Needs review

Why this team?

I have spent four years keeping data pipelines dependable, and your posting describes that work plainly: SQL and Python, scheduled loads, and people downstream who notice when a number is wrong. That is the part of the job I like most.

41 of 100 words. Sample answer. A question about who you are, such as gender or ethnicity, is never drafted: you answer it yourself on the employer’s form.

Interview prep · Ready

Technical interview

A stage the employer states.

  • Walk through one pipeline end to end
  • How you found and fixed a slow load
  • What you check before trusting a table

Learning · Ready

Airflow · Named in the posting. Schedule a two-step load and make the second step wait for the first.

2. What a posting’s history looks like

Five made-up postings, one for each rating and one too new to rate. The rating, the facts and the sentence under each are what the product’s own rule gives for these dates. The pacing notes come from the fictional applicant’s earlier applications to the same company.

  • Example · not a live posting

    Software Engineer

    Northwind Example · Remote, United States

    quality: green, worth a slot, 21 days observed, not reposted, tracked since 2026-09-09. Observed 21 days, never reposted. That is under the 30-day mark.

    Provisional thresholds; calibration is pending.

    Matching skills: TypeScript, SQL

  • Example · not a live posting

    Data Engineer

    Lakeshore Example · Chicago, IL

    quality: gold, spend carefully, 45 days observed, not reposted, tracked since 2026-08-16. Observed 45 days, never reposted. That is past the 30-day mark.

    Provisional thresholds; calibration is pending.

    Matching skills: Python, SQL, Airflow

    This would be application 2 to Lakeshore Example in 90 days.

    • Analytics Engineer2 Sep
  • Example · not a live posting

    Senior Platform Engineer

    Harbor Example · Seattle, WA

    quality: orange, low priority, 67 days observed, reposted 2 times, tracked since 2026-07-25. Observed 67 days, reposted twice. That is past the 60-day mark.

    Provisional thresholds; calibration is pending.

    Matching skills: Kubernetes, Go

    This would be application 4 to Harbor Example in 90 days.

    • Platform Engineer18 Jul
    • Site Reliability Engineer6 Aug
    • Infrastructure Engineer29 Aug
  • Example · not a live posting

    Backend Engineer

    Summit Example · Austin, TX

    quality: red, probably skip, 40 days observed, reposted 3 times, tracked since 2026-08-21. Observed 40 days, reposted 3 times. Three or more reposts mean probably skip, whatever the age.

    Provisional thresholds; calibration is pending.

    Matching skills: Java

  • Example · not a live posting

    Frontend Engineer

    Cedar Example · Remote, United States

    quality: not enough history yet, tracked 6 days. Observed 6 days. A rating needs 14 days of history.

    Matching skills: React, TypeScript

3. The board

Four columns, and a job is in exactly one. Preparing a job never moves it: only your own Mark applied does.

  1. Queued

    Data Engineer, Lakeshore Example

    Preparation: Needs review

  2. Applied

    A job arrives here when you choose Mark applied, with the resume you sent. An outcome can be added later.

  3. Closed before applied

    A queued job whose posting closed first. Its materials are kept.

  4. Skipped

    A job you decided against.

That is the whole loop

Postsource is in private development and there are no public accounts yet.