Interview Prep Notes on iPhone: STAR Stories, Company Research, and Post-Interview Debriefs

Job searching is one of the most information-dense activities in professional life. You are tracking dozens of applications, preparing different answers for different roles, researching companies, and managing your own anxiety.

Most people do this in a combination of browser tabs, email threads, and memory — which is why most interviews feel underprepared relative to how much time was spent on preparation.

A structured notes system converts scattered preparation into searchable knowledge.

---

The STAR Story Library: Your Most Valuable Career Asset

Behavioural interviews all follow the same structure: tell me about a time when you [demonstrated competency X]. The best answers follow the STAR format:

• Situation: the context and challenge
• Task: what you specifically needed to do
• Action: what you did (the bulk of the answer)
• Result: the measurable or observable outcome

The weakness in most interview preparation is that STAR stories are written once for a specific interview and then forgotten. Building a permanent, growing STAR story library in Nemos means every story you have ever prepared is searchable and reusable.

How to build the library:

One note per story. Title it by the competency or skill it demonstrates: `Leadership — Turnaround Project`, `Conflict Resolution — Cross-Team Dispute`, `Data Analysis — Forecasting Accuracy`.

Write the story once, in full. 200-300 words. Include the specific context, the specific actions, and the specific outcome. Numbers strengthen outcomes: "reduced customer complaints by 34%", "delivered two weeks ahead of schedule", "grew the team from 3 to 7 over eighteen months."

When a new interview requires a story about "a time you influenced without authority", search your library for relevant stories and adapt.

Competency Coverage Check

Review your STAR library against the core competency areas employers test:

• Leadership and influence
• Conflict resolution and difficult conversations
• Problem-solving under pressure
• Data-driven decision making
• Collaboration and teamwork
• Project delivery and results
• Innovation and change management
• Failure and what you learned from it

If you have no story for a competency area, your next note to write is one from your actual experience that covers it.

---

Company Research Notes

Before any interview, a company research note ensures you know the context for the role:

• Company overview: size, stage, business model, key products
• Recent news: funding, launches, leadership changes, challenges
• Competitive landscape: who are the key competitors?
• The specific team: what do you know about the people you will meet?
• Questions they are likely to ask based on the role
• Your questions for them — at least five, covering role clarity, team, culture, and success criteria

A good research note takes 60-90 minutes. The interview feel is different when you walk in having done this work.

---

The Application Tracker Note

One rolling note tracking all active applications:

``` [Company] | [Role] | [Applied date] | [Status] | [Next step] --- Fintech Co | Senior PM | 2026-05-01 | Phone screen completed | Awaiting panel date Agency Ltd | Lead Designer | 2026-05-08 | Applied | No response yet Scale-up Inc | Eng Manager | 2026-05-12 | Rejected | - ```

Update after every touchpoint. Review weekly to follow up where appropriate.

---

Pre-Interview Notes

The day before and morning of an interview:

• The role: what specifically are they hiring for, what will success look like
• The format: how many people, what types of questions expected
• Your three strongest points: what do you most want them to know about you
• The STAR stories you plan to use for likely competencies
• Two or three questions you will ask them
• Logistics: location, how to get there, contact name

Reading this note in the 30 minutes before the interview is better preparation than a final anxious review of all your notes.

---

Post-Interview Debrief Notes

Write this within an hour of finishing:

• What questions were asked — exact wording where possible
• How you answered — what you said, what worked, what felt weak
• Observations about the interviewers and the culture signals you picked up
• What you wish you had said differently
• Your overall gut feeling about fit and interest level

The post-interview debrief is valuable for two reasons: it improves your next interview, and if you get a second-round interview with the same company, your notes from round one give you a significant advantage.

---

Salary Negotiation Notes

Before any offer conversation:

• Your target salary and acceptable range
• Market data you have gathered (job boards, salary surveys, conversations with contacts)
• Your BATNA: what is your best alternative to this offer?
• Non-salary items worth negotiating: bonus structure, equity, title, remote working, start date, holiday allowance
• Your walk-away point

Negotiation notes are private. Nemos is appropriate here — this is exactly the kind of sensitive information that should not be in a cloud-synced document.

---

iPhone-Specific Advantages in the Job Search

Pre-interview on the tube or bus Reading your research note and STAR story library on the way to an interview is one of the best uses of commute time. Nemos is offline-capable and does not require connectivity.

Post-interview on the walk back Write the debrief note while you are still in the building or on the street outside. The impressions are most accurate in the first 30 minutes.

Voice dictate STAR stories If you find it easier to talk through stories than type them, dictate a rough version into Nemos. Transcription captures the structure; you clean up the language later.

Private by default Your application tracker, salary notes, and honest post-interview evaluations are the most private documents in your professional life. On-device storage is appropriate.

---

FAQ

Should I keep interview notes after I accept a role? Yes — archive them. When you are job searching again (and you will be), your STAR story library is immediately usable. Two years of stories are more valuable than starting from scratch.

How detailed should STAR stories be in the note? Full version in the note: 200-300 words with specific context and numbers. When you practise telling it, you naturally condense. The detailed version in the note ensures you have the specifics when you need to recall them.

Should I prepare different stories for different roles? Prepare the same library and select stories based on the competencies emphasised in the role. A story about data-driven decision making can be told differently for a product manager role versus an analyst role.

What if I cannot think of good stories? Most people underestimate what they have done. Start with a list of things you have worked on in the last two to three years. For each: what was the challenge? What did you do? What was the outcome? The stories are there; the work is in making them specific and memorable.

How many STAR stories should I have? Aim for at least 15 stories covering all the major competency areas. 30 is better. With a large library, you can adapt to almost any question.

---

Related Reading

• Job Interview Notes on iPhone
• How to Take Interview Notes on iPhone
• Personal CRM Notes System on iPhone
• Note-Taking for Entrepreneurs on iPhone

---

Sources

• Ahrens, S. (2022). *How to Take Smart Notes* (2nd ed.). Sönke Ahrens.
• Stone, D., Patton, B., & Heen, S. (1999). *Difficult Conversations*. Viking.
• Lencioni, P. (2002). *The Five Dysfunctions of a Team*. Jossey-Bass.

---

The job search rewards systematic preparation. Your STAR library is not built for one interview — it is built for a career. Start writing stories today.