Debugging “Where to spend my time?” in the job search 🌲

Source: Dev.to

Something I hear a lot from job‑seekers is, “I don’t know where to spend my time.”
There is so much you could do—resume tweaks, projects, networking, interview practice—but little signal about which would help most.

Below is the “decision tree” I guide my mentees down, organized by stuck point. After identifying where they’re stuck, we pinpoint why, then use that to define top priorities.

I don’t know what career direction to take

This “quadrant” could help:

• If you need a job ASAP, choose in‑demand roles that want what you’re already good at (Quadrant 1), even if you don’t enjoy it (Quadrant 2).
• As you gain seniority, you’ll unlock more Quadrant 1 and 3 opportunities.
• Avoid Quadrant 4.

Don’t sweat being hyper‑specific if you’re entering a new field; entry‑level roles are often generic.
Example: Stuck between “accessibility guru” or “design‑systems specialist”? You’ll start as a full‑stack generalist anyway.

Should I broaden the roles I’m applying to?

Weigh the potential upside of more opportunities against the extra time required:

• Writing a resume version tailored to that role
• Learning skills that you’re missing for that role
• Preparing for role‑specific interview formats

If the effort overlaps with your existing skill‑set and the interviews you’re already doing, it’s often worth trying.

I’m applying but not hearing back

I check for these three common reasons:

1. Missing skills / experience

Go line‑by‑line through a target role and grade each job requirement:

• My resume…
  • demonstrates several examples of it
  • has it but not deeply enough
  • is missing it

Confirm your grading with industry folks if possible. Job descriptions are often unrealistic wish‑lists; insiders know what actually matters.

• Prioritize gaps that are “3” (missing).
• “2” (present but shallow) should be noted, but rank them relative to other gaps.
  • Example: Shallow React experience may be lower priority if your resume isn’t finished.

Action: Add projects to your resume that address the gaps. If you don’t know what to build, aim for “technically robust and universal” over “creative.” Companies prefer candidates who have built features like theirs in the exact stack.

• Use the most popular tools for the field (React for frontend, Python/pandas for data science, etc.).
• Focus on features every app has: authentication, forms, data tables, plus hot topics like LLM agents.

2. Resume / LinkedIn not doing you justice

You may be qualified, but your profile isn’t written to fully showcase that.

Common mistakes & fixes

1. General resumes where all skills get equal space.

   • Fix: Let relevant experience occupy at least 60 % of the page; shrink less‑related points.

2. Omitting specifics, leaving recruiters unclear about depth.

   • Generic: “Built a chat app with React.”
   • Better: “Built a chat app (React, Socket.IO, Node) supporting 500 concurrent users. Added OAuth and reduced message latency by 40 % by batching events.”

3. Unclear relevance for experiences from previous careers.

   • Unclear: “Managed inventory for grocery store.”
   • Better: “Managed inventory for a 5,000‑SKU store using performance reports and weekly audits. Identified 12 % overstock through an Excel script.”

LinkedIn tip: Follow Emily Worden’s content, e.g.:

• How to Write a LinkedIn Headline
• How to Effectively Announce ‘Open To Work’

3. Weak network

If your resume reads well to both you and industry insiders, the best use of your time could be sourcing quality job leads.

• Dedicate time to finding job sites, forums, or people that specialize in your industry, match your values, are local, etc.
• They can surface less‑known, strongly‑aligned opportunities.
• Be active on LinkedIn to boost visibility:
  • If you see a good role that closed, connect with people who work there and ask them to keep you top‑of‑mind for future openings.

I’m hearing back but failing technical screens

Prioritize technical interview prep over projects and networking.

Focus your study scope by format

• LeetCode / algorithms – typical at larger companies; tests data‑structure knowledge.
• HackerRank / take‑homes – common at larger orgs; time‑limited tasks requiring implementation of larger functions using data structures.
• Build a small feature – more common at startups; incorporates LeetCode‑easy concepts in a practical context, letting “on‑the‑job” skills translate naturally.

Strategy: Prioritize companies whose interview formats you’re stronger at.
Example: I’m extraordinarily talented at misreading take‑home instructions and implementing the wrong thing. A human interviewer correcting me before I start drastically improves my success rate, so I prioritize interviews at companies without take‑homes.

Technical interviews consist of these sub‑skills

• Knowing key syntax by heart: print, string/array manipulation, sorting, etc.
• Data‑structure patterns: see 15 LeetCode Patterns – complete many problems to internalize them.
• Advanced topics (dynamic programming, heaps, etc.) are less frequently asked. Unless you are going for MAANG companies, focus first on the fundamentals.

---

Use this decision tree to diagnose where you’re stuck, then act on the highest‑impact priority.

Prioritizing Your Interview Prep

• Talk out loud – articulate your thought process as you solve a problem.
• Find resources that match your learning style and practice your main gaps in isolation, then all together.

I’m Struggling with Soft‑Skill / Manager Interviews

These interviews often ask variations of the following questions:

What to do

1. Prepare 1‑3 specific stories for each category using the STAR format.
2. Rehearse those stories out loud.

Tips

• Writing a strong résumé doubles as prep for these interviews.
• Record yourself to simulate performance pressure.
• For remote interviews, keep your prepared answers on‑screen (the interviewer can’t see them).

I’m Reaching Final Rounds but Not Getting Offers

If you’re consistently making it to the final stage, you’re likely qualified; other candidates are just edging you out.

What to Ask Recruiters

• Technical bar – If they mention you didn’t meet it, double‑down on technical interview skills.
• Manager screen – If they’re silent on technical issues, the problem may be your manager‑screen answers.

Some feedback can be unfair or not reflective of a “good engineer.” Disregard it and be glad you avoided a bad fit.

Next Steps

1. Show recruiter feedback to a hiring manager who actually hires for your role.
2. Present your manager‑screen answers and ask for pinpointed improvement areas.

Time‑saving tip: Space out final rounds and use the gaps for reflection.

I once scheduled three final rounds back‑to‑back, used the same approach, and got rejected by all three. After coaching on my manager‑screen answers, I received an offer soon after. Those three rounds felt like needlessly hitting the same wall.

Beyond the “Priority Playbook”

Balance Priorities with What’s Fun

The guide points to your next best step, but that step can be the toughest. Pair it with tasks that energize you and still advance your growth.

• Web dev who prefers Vue? Focus on Vue – the fundamentals transfer.
• Early‑stage candidate who dreads LeetCode but loves system design? Dive into system design now; you’ll need it later anyway.
• Enjoy writing? Blog about what you’re learning to broaden your network.

Focus on the Current Step

It’s overwhelming to think about all the up‑skilling and interviewing you’ll need. You don’t have to solve everything at once—just ensure each current step is a must‑do toward your destination. Think of it like a video game: one level at a time.

Be Curious, Not Pressured

“I’m ‘running my code’ to see what knowledge gaps pop up”
is more approachable than “I have to nail this interview.”

• Reframe “I’m stuck and making no progress” → “I’m stuck because something isn’t working, and that’s valuable information. It tells me what not to do and brings me closer to what does work.”

Closing Thoughts

Your job search is like a decision‑tree algorithm: each step finds your next best move, not the whole solution at once. Aim for continuous, intentional iteration.

Any questions or want a deeper dive? I couldn’t possibly fit all my mentoring and résumé‑writing experience in one post. Let me know what you’d find helpful—I’d love to help!

Also available in Bluesky thread format 🧵:

• How to get past “I don’t know where to spend my time” in the job search, a thread 🧵 — Shell 🍋 UX Dev / Resume Writer (@miffens.bsky.social)

(Editorial assistance: Claude 3.5 Haiku)