applye
Source: soon

Interview Prep & Analytics

Keep every interview round in one timeline, and let your own data tell you how the search is going. Both screens are 0-token: plain code over your local database.

Interview Prep

  1. The list shows every application you are interviewing for, with the next date on top.
  2. Open one for the stage timeline: each round is a card with its type, date, interviewer, notes, and a colour-coded status you change in place.
  3. Add or edit stages in a small modal; reorder them; remove an application from prep without touching the job itself.
One application's interview timeline: three stages, one upcoming. A numbered rail runs down the left. Stage one, a screening call with HR held in July, is marked passed. Stage two, a technical round in August, is scheduled. Stage three, the final conversation, has no date and is awaiting scheduling. Each row can be reordered, edited or deleted, and Add stage sits above them.
One application, every round.

Analytics

Pick a period (30 days / 90 days / all time) and read:

  • Four counters - applications, response rate, interviews, offers, each with a trend vs the previous period.
  • The funnel - saved to applied to interviewing to offer, with conversion at each step and rejections tracked as leakage.
  • Applications over time - your volume, with follow-up activity overlaid.
  • Match-score distribution and score vs outcome - are you applying to well-matched roles, and do higher-fit ones actually get further?
  • Time to response, pipeline aging (stalled past 14 days gets flagged), and where you are applying.
The Analytics screen over the last 90 days. Four counters read five applications sent, a 60 per cent response rate, three interviews and one offer. An application funnel below them steps from eight saved to five applied, three interviewing and one offer, with the conversion between each pair on the right and a leakage row showing one rejection. A weekly chart of applications over time runs along the bottom.
Your search, measured locally.

With few applications it shows honest raw counts instead of misleading percentages; no external benchmarks, ever.