Job search toolkit.

Application tracker

Track every role you apply for — status, contacts, resume version, and follow-up dates in one place.

Interview tracker

Log each round as it happens — format, topics covered, how it went, and what to follow up on.

Offer comparison

Evaluate offers side by side — comp, culture, stack, and gut feel in one honest view.

Networking tracker

Keep contacts warm — who you know, when you last spoke, and when to reach out again.

Follow-up after applying

When: Send 5–7 days after submitting your application if you have not heard back.

Subject: Following up — [Role] application · [Your name]

Hi [Name],

I applied for the [Role] position at [Company] on [date] and wanted to briefly follow up. I am genuinely interested in this role — [stack] is where I spend most of my time, and the team's work on [specific area] caught my attention.

Happy to answer any early-stage questions or share more about my background. Is there a next step I should be watching for?

[Your name]

Recruiter cold message

When: Short LinkedIn intro to a recruiter or hiring manager you have not spoken to before.

Hi [Name],

I'm a QA engineer with [X] years of experience in [stack], currently open to [type of role] opportunities. I came across your profile while researching teams at [Company].

Would you be open to a brief conversation? I'd love to hear more about what you're looking for on the QA side.

[Your name]

Post-interview thank-you

When: Send within 24 hours of any interview round.

Hi [Name],

Thank you for the time yesterday — I enjoyed the conversation, especially the discussion around [specific topic from the interview].

One thing I'd add to my answer on [topic]: [brief clarification or addition — shows you kept thinking about it].

Looking forward to hearing about next steps.

[Your name]

Responding to a rejection

When: Reply to a rejection email — gracious, keeps the door open, and asks for feedback.

Hi [Name],

Thank you for letting me know, and for the time you invested in the process. I genuinely enjoyed learning more about the team and the role.

If you're able to share any feedback on where I could improve, I'd welcome it — it helps me get better for future opportunities.

I hope our paths cross again. I'd be happy to stay in touch.

[Your name]

Reconnecting / referral ask

When: Reaching out to a past contact when you see a role at their company.

Hi [Name],

Hope things are going well — it's been a while since [last context, e.g. we worked together at / we connected at].

I'm currently exploring new opportunities in [type of role / stack] and noticed [Company] is hiring for [Role]. I wanted to reach out before applying — if you think I'd be a good fit, I'd really value a referral or just your honest read on the team culture.

No pressure — happy to chat briefly or just send my CV if that's easier.

[Your name]

Company research checklist

Run this before every interview. Know the company before you walk in.

• ☐Check the company's public product — sign up for a trial or read the changelog. Know what they ship.
• ☐Read recent company news: funding rounds, acquisitions, product launches, layoffs, or strategy pivots.
• ☐Find the engineering or QA team on LinkedIn — note team size, tenure, and tools they mention publicly.
• ☐Research the interviewers you know about: LinkedIn, GitHub, or any talks and articles they've published.
• ☐Check Glassdoor, Blind, and Levels.fyi for interview process signals, culture notes, and compensation.
• ☐Understand their tech stack from the job description, engineering blog, or GitHub org.
• ☐Prepare 3–5 specific questions for them about the QA process, team structure, and current challenges.
• ☐Know the role's level and reporting structure — IC or lead, and who does QA report to.

Pre-interview prep checklist

Logistics and content prep. Do this the day before and again 30 minutes before.

• ☐Confirm the interview time in your local timezone and add a calendar block with the meeting link.
• ☐Test your audio, video, and internet connection at least 30 minutes before the call.
• ☐Have your CV open in a second tab or printed in front of you.
• ☐Prepare 3 STAR stories: a defect you found, a process you improved, and a disagreement you resolved.
• ☐Know 2–3 things about the company you can reference naturally — not just 'I love your product.'
• ☐Set up a clean background or use blur. Close non-essential tabs and silence notifications.
• ☐Have water nearby and a notepad for notes during the interview.
• ☐Know the expected format — behavioural, technical, live coding, or take-home — and prep accordingly.

Application-ready checklist

Check this before you hit apply. A rushed application is worse than a late one.

• ☐Resume is tailored to the role — keywords from the job description appear naturally in your bullets.
• ☐Resume is one page (under five years of experience) or two pages max with no filler bullets.
• ☐All portfolio links in your resume are live, public, and load without errors.
• ☐CI badge in your primary GitHub repo is green.
• ☐LinkedIn profile matches your resume — no gaps or inconsistent dates.
• ☐LinkedIn headline includes your role and primary stack (e.g. 'QA Automation Engineer | Playwright · TypeScript').
• ☐At least one GitHub repo has a complete README with installation steps and a run command.
• ☐References are lined up and know they may be contacted.