Interviews: a page for each interview that gathers what to prepare from, and prints #1091

New issue

Open

opened 2026-10-30 21:25:12 +00:00 by tiagoagueda · 0 comments

tiagoagueda commented

2026-10-30 21:25:12 +00:00

Owner

What exists today

Interview (applications/models.py:773) has a start, an end, a place, a kind, the contacts attending and an outcome. Its addresses are create, edit, outcome and an .ics file (applications/urls.py:56-88). No page shows one interview.
The listing's text, the company's facts (hiring signals, legal state, parent, names from Wikidata), the contacts, and the frozen PDFs of what was sent (RenderedDocument) all exist, each on its own page.
Themed PDFs exist for CVs, letters and the period report, and #341 and #342 add lists and the calendar.

What would change

An interview page: when and where, who attends (each contact's details and the person's own note on them), the listing's text, the company in brief, the documents sent for this application (the snapshot, not the current CV), the timeline so far, earlier interviews for the same application and their outcomes, and a preparation notes field.
A PDF of it through a theme, so postulo-templates can offer a design.
Linked from the calendar, the interview list and the application page.

Decisions

Where the notes live. Recommended: a preparation notes field on Interview; the outcome stays a timeline entry as it is.
Theme kind. Recommended: a kind of its own, so a theme can be written for this page alone.
Nothing here asks a model for anything. The questions to expect are the person's own to write.

Checked against main at daee30b15 (2026-10-30). From the status review and feature suggestions of 2026-10-30.

Before an interview a person opens four or five pages to remember what they applied for: the listing, the company, the contacts, the CV and letter they sent, the timeline. This asks for one page per interview that gathers them, and that prints. ## What exists today - `Interview` (`applications/models.py:773`) has a start, an end, a place, a kind, the contacts attending and an outcome. Its addresses are create, edit, outcome and an `.ics` file (`applications/urls.py:56-88`). No page shows one interview. - The listing's text, the company's facts (hiring signals, legal state, parent, names from Wikidata), the contacts, and the frozen PDFs of what was sent (`RenderedDocument`) all exist, each on its own page. - Themed PDFs exist for CVs, letters and the period report, and #341 and #342 add lists and the calendar. ## What would change - An interview page: when and where, who attends (each contact's details and the person's own note on them), the listing's text, the company in brief, the documents sent for this application (the snapshot, not the current CV), the timeline so far, earlier interviews for the same application and their outcomes, and a preparation notes field. - A PDF of it through a theme, so postulo-templates can offer a design. - Linked from the calendar, the interview list and the application page. ## Decisions - **Where the notes live.** Recommended: a preparation notes field on `Interview`; the outcome stays a timeline entry as it is. - **Theme kind.** Recommended: a kind of its own, so a theme can be written for this page alone. - Nothing here asks a model for anything. The questions to expect are the person's own to write. Checked against `main` at `daee30b15` (2026-10-30). From the status review and feature suggestions of 2026-10-30.

tiagoagueda added this to the 0.6.0 milestone

2026-10-30 21:25:12 +00:00

tiagoagueda added the

interface

enhancement

labels

2026-10-30 21:25:12 +00:00