How to run two different job searches without mixing them up
Senior PM in Bengaluru and fractional work abroad are not the same search.
Treat them as two searches, not one wide one. Each gets its own target roles, its own locations, its own resume version and its own tracking. Mixing them is how the fintech resume ends up at the healthcare company.
Why people run two searches
- A safe option and a stretch option: the role you can get now, and the one you want.
- Two locations: staying put, and a move.
- A career change running alongside the current career.
- Full-time roles and contract or freelance work.
All reasonable. The trouble starts when they share one resume and one list.
What to keep separate
| Row | Search A | Search B |
|---|---|---|
| Target titles | Senior Product Manager | Product Analyst, data-heavy PM |
| Locations | Bengaluru, hybrid | Remote |
| Resume | Leads with product outcomes | Leads with analysis and SQL |
| Pitch | I ship and own roadmaps | I find the answer in the data |
| Tracking | Its own list | Its own list |
Resume versions
Two versions, not twenty. Same facts, different order and emphasis. The top third of each should read like it was written for that search. Name the files so you cannot mix them up: not "resume_final_v3".
Tracking without a spreadsheet you will abandon
Whatever you track in, split by search, so you can see which one is actually getting replies. That is often the most useful thing you learn: one search is working and the other is not, and you had been averaging them together.
In HUNT, each search is its own hunt, with its own target roles, locations, sources and tailored resumes, scored and tracked separately. See pricing for how many hunts each plan runs at once.
Related: Applying more is not always a strategy and How many jobs should you actually apply to?
Published
Back to field notes