DEV Community

E Daugherty
E Daugherty

Posted on

Job hunting as a developer on a Mac in 2026: my application workflow, 8 apps from tracker to thank-you email

The hard part of a job search isn't the first application. It's application number 30, when you can't remember which company asked for a portfolio link, which recruiter you owe a reply, and whether you already sent that thank-you note.

So here's the workflow I'd set up on a Mac before sending a single application, in the order the work actually happens. Every app has one job.

Stage 1: Keep track of everything

1. Notion, as the job tracker

One database, one row per application: company, role, link to the posting, stage, next step, date. A board view grouped by stage turns "where am I with everyone?" into a glance instead of a search through your inbox.

Cost: free plan; Plus (one member) is free for students and educators, otherwise $10 a month. notion.com/pricing

2. Notion Calendar, for interview slots

It syncs Google, Outlook and iCloud calendars in one view and can auto-block busy slots across all of them, so a recruiter screen never lands on top of a class or a standup. It also shows Notion database dates next to your events, which pairs nicely with the tracker above.

Cost: included free with Notion. notion.com/product/calendar

Stage 2: Make the portfolio easy to look at

3. CleanShot X, for screenshots that look finished

Recruiters skim. A clean, annotated screenshot of your project at the top of a README or portfolio page does more than a paragraph about it. CleanShot X adds backgrounds, arrows, blur for anything private and scrolling captures, plus screen recording.

Cost: $35 once (one year of updates), with a 30-day money-back guarantee; also on Setapp. cleanshot.com/pricing

4. Kap, for a 10-second demo GIF

If your project does something visual, record it. Kap is an open-source screen recorder that exports GIF, MP4, WebM or APNG with trimming and click highlighting, and a GIF plays right inside a GitHub README.

Cost: free, open source. getkap.co

Stage 3: Fill out the applications

5. Rectangle, to put the posting next to your resume

Half of tailoring an application is reading the job description while you edit. Rectangle snaps windows to halves, thirds and corners with keyboard shortcuts or by dragging to the screen edge, so the posting sits on the left and your resume on the right.

Cost: free and open source, macOS 14+. rectangleapp.com

6. Raycast snippets, for the links you paste 50 times

GitHub profile, portfolio URL, LinkedIn, email, a two-line intro. Save each one as a Raycast snippet with a keyword and it expands in any text field, so every application form takes a few keystrokes instead of a hunt through old tabs. Clipboard History is built in too.

Cost: free for personal use; AI features are in paid Pro plans. raycast.com/pricing

7. Wispr Flow, for the "tell us about a project" boxes

Long free-text questions are easier to answer out loud first. Wispr Flow lets you dictate into any app on your Mac, so you can talk through a project the way you'd explain it in an interview, then cut it down to the word limit.

Cost: free on Mac, Windows, iPhone and Android; paid plans add team and admin features. wisprflow.ai/pricing

Stage 4: Follow up

8. DraftKey, for the follow-up and thank-you emails

These are short emails you'll write a lot, and they're easy to get wrong when you're tired. DraftKey lives in the menu bar and suggests the next few words as you type in your Mac apps, so you press Tab to accept and keep going. Select a paragraph to Fix writing, make it Shorter or Clearer, or change the tone, then review the result before you insert it.

DraftKey writing panel with Fix writing, Shorter, Clearer and Tone options above an Ask for a change box

Cost: $4.99 once for up to 3 Macs, with 500 free words per Mac to try it. Needs Apple Silicon, macOS 14+ and 8 GB of RAM (about a 1.12 GB download). getdraftkey.com

The whole workflow on one screen

  • Track: Notion database + Notion Calendar
  • Show: CleanShot X screenshots + a Kap GIF in the README
  • Apply: Rectangle split view, Raycast snippets for links, Wispr Flow for long answers
  • Follow up: DraftKey for the emails

Total cost if you skip every paid upgrade: $0 for six of them, $35 for CleanShot X and $4.99 for DraftKey.

What's the one step in your job search that eats the most time: tailoring, applying, or following up?

Top comments (4)

Collapse
 
ayushdhanani369 profile image
Ayush Dhanani •

Applying, for me. The Rectangle split view is the right idea. The posting on the left and the resume on the right only gets you so far. The form itself is the slow part. Each one asks for the same facts in different words. I build Aladdin, a job agent. It reads the actual page and form for each application instead of working from the posting alone. When a field is not covered by the user's own facts, it asks instead of guessing.

Collapse
 
jeff_feldman_7ab3898 profile image
E Daugherty •

Agreed, the form is where the time goes. Split view helps with reading the posting, but retyping the same work history into differently worded fields is the real drag. Asking instead of guessing is the right call for things like work authorization or salary expectations, since a confident wrong answer there is worse than a blank. Do you keep a reusable answer bank per person, or does it build each answer fresh from the page?

Collapse
 
ayushdhanani369 profile image
Ayush Dhanani •

Both, in a way. The user's own facts carry over, and an answer the user gives when asked is saved, so a differently worded field can reuse it. Each application still starts from a fresh read of the actual form, so it does not paste an old answer into a field that means something different. That split is what keeps the retyping down without letting a stale answer slip through.

Thread Thread
 
jeff_feldman_7ab3898 profile image
E Daugherty •

That split makes sense. Reusing the fact but re-reading the field every time is where plain autofill usually goes wrong, since "Why this company?" and "Why this role?" look almost identical but want different answers. Thanks for walking through how it handles that.