You open a job board, save a few interesting roles, and spend the next hour editing your CV. Then you find another opening with different requirements and start again. By the end of the evening, you have been busy without getting much closer to an application.
The way out is to make a few decisions before you start browsing. You need a working definition of a suitable job, a few places to look, and a repeatable way to apply. None of these has to be perfect in the first week.
Here is a practical starting plan. Spread it over longer if you are working, studying, or caring for someone. The useful part is the order, not finishing everything by Friday.
Day 1: Define what you are looking for
“A job in tech” is too broad to guide a search. “A mid-level developer role working mainly on web products, with remote work available from Austria” is something you can use to make decisions.
Write down three groups of criteria:
- Must have: conditions that determine whether you can accept the job, such as location, working hours, or a minimum acceptable salary.
- Prefer: things you value but could trade off, such as a particular industry or technology.
- Avoid: responsibilities or arrangements you know you do not want.
Keep these separate. If you treat every preference as a requirement, you may reject suitable work. If you ignore your real constraints, you can invest heavily in a process that could never lead to an acceptable offer.
Next, choose a primary role family and one adjacent option. A frontend developer might also consider product engineering roles with a strong frontend focus. That is a coherent search. Applying simultaneously for design, data science, IT support, and engineering management usually needs several different explanations of your experience.
You can change your focus as you learn. For now, you need a useful starting point.
Day 2: Read job descriptions before rewriting your CV
Collect a small sample of openings that look plausible. Read the responsibilities as carefully as the requirements. What work keeps appearing? What level of independence do employers expect? Which skills are essential, and which appear only occasionally?
Make a short list of recurring needs, then match each with something you have done. For example:
| Employers keep asking for | Evidence I could show |
|---|---|
| Working with product and design | Helped clarify a confusing signup flow before implementation |
| Testing and maintaining features | Added regression checks after a recurring production issue |
| Explaining technical decisions | Wrote a proposal comparing two approaches to a migration |
This is where CV preparation becomes easier. You are choosing evidence for real work rather than trying to sound impressive in the abstract.
If you cannot find evidence for most of the central responsibilities, reconsider the role level or look at adjacent positions. One missing tool is different from missing the main purpose of the job.
Day 3: Prepare one strong base CV
Build a complete working version with accurate dates, clear job titles, and useful descriptions of your recent work. Save a separate list of achievements you might use later, so tailoring does not mean remembering your career from scratch.
For each recent role, answer: what did I work on, what was my contribution, and what changed? “Worked on the customer portal” is a start. “Rebuilt the account settings flow so customers could update billing details without contacting support” gives the reader more to understand.
You do not have to make every sentence numerical. Scope, a completed outcome, and a well-explained responsibility can all be evidence.
Check the final document, not just the editor. Open it on another screen, test the links, and look for awkward page breaks. You can use the MarkdownResume editor to keep the writing separate from layout adjustments.
Day 4: Build a small employer list
Job boards are useful discovery tools, but they should not be your only view of the market. Look at companies whose products you know, organizations mentioned by former colleagues, and employers in industries you understand.
For each promising company, find the official careers page. Save the page even if there is no suitable opening today. Over time, this gives you a manageable list to revisit rather than an endless feed to scroll.
Check remote policies carefully. A role can be remote within one country, require particular working hours, or involve regular office visits. Find the actual condition before spending time on the application.
Also reconnect with a few people who know your work. Tell them what you are looking for in a sentence they can remember. “I am looking for frontend product roles, ideally on a team building customer-facing software” is easier to act on than “Please let me know if you hear of anything.”
Day 5: Send a few complete applications
Choose the most suitable openings from your shortlist. Tailor the top part of your CV to the work, answer the requested questions, and follow the employer's submission instructions.
Before sending, check the company name, role title, attachment, contact details, and links. Save the job description and the version of your CV you used. Listings can change or disappear before an interview.
Quality does not mean spending all day on each application. It means making the relevant evidence easy to find and avoiding preventable mistakes. The resume tailoring guide gives you a repeatable editing process.
Give the following week a shape
Set aside separate blocks for finding openings, completing applications, and preparing for conversations. Otherwise, browsing tends to occupy all the available time.
End each week with a short review: Which sources produced suitable roles? Which requirements kept appearing? Where did an application take longer than it should? What is the next action on each active opportunity?
Do not judge the plan by whether an offer arrives in the first week. Judge whether you now know what you are looking for, can explain your fit, and have a routine you can repeat. Those are the pieces that make the next week more useful than the last.