M
MĂa Salazar
Guest
In recent years, finding a job in tech, especially in software development, has become increasingly challenging. The market is more saturated, competition is stronger, and fully remote opportunities are no longer as abundant or well-paid as they once were. As someone who's been through this process, I want to share some practical tips that have helped me and might help you too.
Before you start applying, think carefully about what you want to do. The more specific your goal, the harder it might be to land interviews. For instance, if you only look for React roles, you may be missing out on opportunities that require other frameworks. I recommend checking out which technologies are in demand. Then, decide what you want to prioritize, both for now and your long-term career.
Remote work is much harder to get nowadays, especially fully remote roles. These positions are often more competitive and sometimes come with lower salaries. Choosing on-site or hybrid may increase your chances of getting hired faster, depending on your location and flexibility.
Have a clear salary expectation, but verify that it's in line with market standards. Remember: fully remote jobs tend to pay less, especially if you're based in countries with lower cost of living.
If you speak other languages, consider applying internationally. English is the key to most global opportunities, but you'll need to be comfortable enough to handle technical interviews. Confidence in both communication and coding is essential.
Set time-based checkpoints to reassess your strategy. For example:
These personal deadlines help you stay grounded and prevent frustration from growing aimlessly. Adapting doesn't mean giving up, it means staying strategic.
Choose a few job platforms that work well for you, don’t try to monitor 300 websites or you might end up losing your mind. Search daily using a variety of keywords. For example, if you're a frontend developer, search terms like “frontend developer,” “front-end engineer,” “React,” etc. Keep track of where you’ve applied and what keywords work best.
Create an Excel or Google Sheets file with key information:
Use this data to identify patterns. If you’re consistently dropped at the same stage (e.g., technical interview), that’s a signal to improve in that area.
Recruitment processes can move fast. Stay reachable:
Being responsive helps you avoid missing important calls or time-sensitive opportunities.
If you're in a rush to find a job, you might feel the need to apply to everything and enter multiple processes at once. That’s okay, but you must prioritize:
Try not to schedule more than 2–3 interviews per day, and leave breaks between them to avoid mental exhaustion. If you’re not in a rush, take it slower:
Even if time is tight, structure your week so that you stay sane. Good organization beats frantic multitasking.
If you’re applying to jobs using technologies you haven't worked with in a while (e.g., Angular or Vue when you've only used React recently), be prepared. Consider building a small project (a “pet project”) with those technologies so you’re not caught off guard during technical interviews.
Your CV should be detailed and tailored to the roles you’re applying for. Include:
Forget the “1-page CV” myth. More pages are fine if the content is valuable. Have it available in multiple formats (PDF, DOC) and in all the languages relevant to your job search.
Always include a cover letter tailored to each company. Read the job description carefully, and align your message with what the company is looking for.
Before your interviews, take a moment to review local labor laws regarding job interviews. For example, in Spain it’s illegal for interviewers to ask about your age, marital status, sexual orientation, or family plans. They cannot legally discriminate based on any of those factors
If you're asked inappropriate or illegal questions:
Being aware of these laws helps you protect yourself and recognize trustworthy employers.
Make sure your answers align with your stated long-term goals.
For example:
A coherent, consistent narrative shows you’re clear about your goals and reliable in your planning.
This is one of the most common and delicate questions.
Avoid answers that:
Instead, focus on positive, professional reasons:
Frequent job changes or unexplained employment gaps can make HR suspicious:
Of course, sometimes short stays or breaks are legitimate:
If this happens, learn how to explain these gaps calmly and professionally.
Even if you had very negative experiences, avoid badmouthing previous companies or colleagues. Why?
Focus on what you learned, what you’re looking for now, and how you want to grow.
Before your interview, try to identify who will be interviewing you:
This can give you hints on the likely topics:
Once you know who you’ll be talking to, you can use AI tools like ChatGPT to:
You can also search online for "[Technology] interview questions" (e.g. React interview questions 2025) to review common technical challenges for your target role.
Before your first interview:
During the interview, confidently (but humbly) talk about what you’re proud of. Show enthusiasm and provide context for your skills and experience.
Adapt your tone and focus depending on the company: If they emphasize culture fit, show how your values align. If they stress technical depth, highlight your hard skills and project experience.
Appearances matter, especially in remote interviews. Make sure:
These small touches help you appear prepared and confident.
If a technical interview is part of the process, go over the technologies listed in the job ad. Prepare for common interview questions and brush up on both basic and advanced concepts depending on the level of the role.
If you consistently fail technical interviews on certain technologies or topics, identify them and study intentionally. Practice with exercises, tutorials, and small projects to build confidence.
At every interview stage, ask questions:
Always request feedback after interviews. Whether you pass or not, it can help you improve. After technical challenges or live coding, thank the interviewers for their time and note what you learned.
It leaves a good impression and helps build relationships.
Often, we think the interview is going either really well or terribly, and we relax, or panic, and say things we shouldn't. Don’t make that mistake.
Never assume you’ve passed or failed. The interview is still happening until you hang up the call. Stay professional throughout.
You might feel like your technical interview was a disaster, only to find out later you passed. Or you might think everything went great and slip up in the last minute with an off-hand comment. Control your nerves and your words from start to finish. Always leave the best possible impression.
If you’re doing live coding with someone watching, always:
Before these sessions, practice with coding katas or timed exercises in the relevant language/framework.
Not all live coding challenges are the same. Ask in advance what type you'll face so you can prepare properly. Common formats include:
Be aware of restrictions. Some interviews may:
Make sure you clarify the rules and, if needed, train your memory and problem-solving without relying on external tools.
If you’re given a take-home challenge:
Keep in mind: even if they say it takes “2 hours,” it usually takes more. Make the extra effort to stand out.
Don't rely only on job portals. Talk to people. Reach out to connections or professionals in your field and ask if they know of any openings. Check company websites directly and when applying, craft thoughtful answers to open-ended questions.
You can use ChatGPT to help you draft responses and improve your applications.
If you’ve been searching for a long time and keep hearing that your salary expectations are too high or that the market is tough, consider adjusting. Either adapt to the current market or be patient and wait for the right opportunity.
Job hunting, especially when you’ve set ambitious criteria, takes time. If you’re only applying to very specific roles (e.g., fully remote, niche tech stack, high salary), be ready to wait longer.
That said, it’s okay to reevaluate if your conditions are too strict and you realize you don’t have unlimited time, savings, or patience. You can always ease some of your filters.
Also, remember: many recruitment processes are slow, sometimes disorganized, and can take weeks (or months). Take breaks when needed, but trust the process and keep going.
Rejection is hard, but it doesn’t always mean you’re not good enough. Sometimes:
In other cases, you may need to improve in specific areas, and that’s okay too. Use feedback to identify those gaps and work on them. But always keep in mind: one rejection (or ten) does not define your worth or potential.
The first few interviews can be intimidating. You may feel caught off guard, especially in technical interviews or live coding sessions. But the more interviews you do, the more familiar the patterns become:
Treat each interview as practice for the next one. Confidence grows with repetition.
When you receive an offer, don’t feel obligated to say yes on the spot.
It’s perfectly acceptable, and even expected, to ask for a few days to evaluate:
Avoid making emotional decisions in the heat of the moment. Take your time to compare offers calmly and make a decision that aligns with your long-term goals.
Before resigning from your current job, request a pre-contract or offer letter that clearly states:
This provides legal and psychological security, especially if you’re leaving a stable job.
Having something signed avoids last-minute surprises and allows you to transition with confidence.
Sometimes after signing the offer, the company may share:
It’s good to prepare, but don’t burn yourself out before even starting.
If possible, negotiate a gap of a few days or weeks between jobs to:
Start your new role with energy and clarity
You’ll perform better if you start fresh, not exhausted.
Once you’ve accepted an offer, inform other companies where you’re still in process that you’re no longer continuing:
Respect the time and effort of recruiters and interviewers. It’s professional and leaves the door open for future opportunities. A short polite message is enough.
Job hunting in tech can be a marathon, not a sprint. By defining your strategy, tracking your progress, preparing thoroughly, and staying proactive, you can significantly improve your chances, even in a tough market. Treat it like a project, stay consistent, and don’t be afraid to ask for help or adjust your approach as you go.
Continue reading...
Phase 1: Define Your Strategy
1. Choose Your Focus (But Stay Flexible)
Before you start applying, think carefully about what you want to do. The more specific your goal, the harder it might be to land interviews. For instance, if you only look for React roles, you may be missing out on opportunities that require other frameworks. I recommend checking out which technologies are in demand. Then, decide what you want to prioritize, both for now and your long-term career.
2. Decide on the Work Model (Remote, On-site, Hybrid)
Remote work is much harder to get nowadays, especially fully remote roles. These positions are often more competitive and sometimes come with lower salaries. Choosing on-site or hybrid may increase your chances of getting hired faster, depending on your location and flexibility.
3. Define a Salary Range (and Make Sure It’s Realistic)
Have a clear salary expectation, but verify that it's in line with market standards. Remember: fully remote jobs tend to pay less, especially if you're based in countries with lower cost of living.
4. Open Up to International Markets
If you speak other languages, consider applying internationally. English is the key to most global opportunities, but you'll need to be comfortable enough to handle technical interviews. Confidence in both communication and coding is essential.
5. Add a Timeframe to Your Plan
Set time-based checkpoints to reassess your strategy. For example:
- “If I haven’t found a job in 3 months, I’ll start considering hybrid roles.”
- “If after 2 months there are no responses, I’ll expand my search to include more tech stacks.”
These personal deadlines help you stay grounded and prevent frustration from growing aimlessly. Adapting doesn't mean giving up, it means staying strategic.
Phase 2: Search Effectively
6. Be Systematic
Choose a few job platforms that work well for you, don’t try to monitor 300 websites or you might end up losing your mind. Search daily using a variety of keywords. For example, if you're a frontend developer, search terms like “frontend developer,” “front-end engineer,” “React,” etc. Keep track of where you’ve applied and what keywords work best.
7. Track Your Progress with a Spreadsheet
Create an Excel or Google Sheets file with key information:
- Company name
- Work model (on-site/remote/hybrid)
- Work hours and flexibility
- Salary range offered
- Link to the job post
- Contact person
- Application status (e.g., applied, phone screen, rejected)
- Phase at which you were rejected
Use this data to identify patterns. If you’re consistently dropped at the same stage (e.g., technical interview), that’s a signal to improve in that area.
8. Stay Responsive: Check Your Phone & Email Regularly
Recruitment processes can move fast. Stay reachable:
- Keep your phone on sound
- Check your email and LinkedIn messages frequently
- Save the phone numbers of recruiters with the company name, so you recognize who’s calling
- Update your Excel tracker with any contact details to stay organized
Being responsive helps you avoid missing important calls or time-sensitive opportunities.
9.Pace Yourself: Don’t Burn Out
If you're in a rush to find a job, you might feel the need to apply to everything and enter multiple processes at once. That’s okay, but you must prioritize:
- Focus on the roles that look most promising
- Sometimes you’ll need to choose between two take-home assignments. Decide which company is more aligned with you
Try not to schedule more than 2–3 interviews per day, and leave breaks between them to avoid mental exhaustion. If you’re not in a rush, take it slower:
- Space out interviews and assignments
- Be selective with where you apply
- Choose when and how to give your best energy
Even if time is tight, structure your week so that you stay sane. Good organization beats frantic multitasking.
10. Know Your Strengths (and Gaps)
If you’re applying to jobs using technologies you haven't worked with in a while (e.g., Angular or Vue when you've only used React recently), be prepared. Consider building a small project (a “pet project”) with those technologies so you’re not caught off guard during technical interviews.
Phase 3: Prepare Your Materials
11. Build a Strong CV (in All Relevant Languages)
Your CV should be detailed and tailored to the roles you’re applying for. Include:
- Exact dates of employment (month/year)
- Technologies used
- Projects and responsibilities
- Architecture, methodologies, and principles followed
Forget the “1-page CV” myth. More pages are fine if the content is valuable. Have it available in multiple formats (PDF, DOC) and in all the languages relevant to your job search.
12. Write Custom Cover Letters
Always include a cover letter tailored to each company. Read the job description carefully, and align your message with what the company is looking for.
Phase 4: Interview Preparation
13. Know Your Rights: Watch Out for Illegal Questions
Before your interviews, take a moment to review local labor laws regarding job interviews. For example, in Spain it’s illegal for interviewers to ask about your age, marital status, sexual orientation, or family plans. They cannot legally discriminate based on any of those factors
If you're asked inappropriate or illegal questions:
- Politely deflect or refuse to answer
- Take it as a red flag. If they disregard the law during recruitment, it might reflect deeper problems within the company culture
- Don’t hesitate to walk away from companies that cross these boundaries. Your well-being and rights matter more than any offer
Being aware of these laws helps you protect yourself and recognize trustworthy employers.
14. Be Consistent in Your Narrative
Make sure your answers align with your stated long-term goals.
For example:
- If you say your goal is to move into management, reinforce this by mentioning leadership experiences, mentoring juniors, taking responsibility, etc.
- Avoid giving conflicting answers that make your story seem incoherent
A coherent, consistent narrative shows you’re clear about your goals and reliable in your planning.
15. Prepare a Solid Answer for: "Why Are You Leaving Your Current Job?"
This is one of the most common and delicate questions.
Avoid answers that:
- Criticize your colleagues ("my coworkers were unbearable")
- Make you sound unstable ("I get bored quickly")
- Raise concerns about your teamwork or long-term commitment
Instead, focus on positive, professional reasons:
- Seeking new challenges
- Wanting to grow technically
- Looking for better alignment with your career path
- Company restructuring (if applicable)
16. Maintain a Stable Career Timeline (If Possible)
Frequent job changes or unexplained employment gaps can make HR suspicious:
- They may wonder if you fail probation periods
- They may worry that you’ll leave quickly again
- They may question your ability to integrate into teams
Of course, sometimes short stays or breaks are legitimate:
- You tried a company and it wasn’t the right fit
- You needed personal time off
- There were economic layoffs
If this happens, learn how to explain these gaps calmly and professionally.
17. Don’t Speak Badly About Former Employers or Coworkers
Even if you had very negative experiences, avoid badmouthing previous companies or colleagues. Why?
- It can raise red flags about your teamwork skills
- It can make interviewers wonder if you’ll speak the same way about them later
- It shows a lack of professionalism
Focus on what you learned, what you’re looking for now, and how you want to grow.
18. Research the Interviewers & Use AI to Simulate Interviews
Before your interview, try to identify who will be interviewing you:
- Look them up on LinkedIn or the company website
- Check their roles, backgrounds, technical focus, and seniority
This can give you hints on the likely topics:
- Are they more focused on culture?
- Are they technical experts in certain stacks?
- Are they product-oriented?
Once you know who you’ll be talking to, you can use AI tools like ChatGPT to:
- Generate possible behavioral or culture-fit questions based on the company’s mission and values
- Simulate technical interview questions for the specific tech stack
- Generate product-oriented questions if the role is customer-facing or domain-specific
- Practice your answers to feel more confident
You can also search online for "[Technology] interview questions" (e.g. React interview questions 2025) to review common technical challenges for your target role.
19. First Interview: Know the Company & Sell Yourself
Before your first interview:
- Review the job description
- Identify which of your strengths align with the role
- Research the company to understand their mission and product
During the interview, confidently (but humbly) talk about what you’re proud of. Show enthusiasm and provide context for your skills and experience.
Adapt your tone and focus depending on the company: If they emphasize culture fit, show how your values align. If they stress technical depth, highlight your hard skills and project experience.
20. Look Professional (Even on Camera)
Appearances matter, especially in remote interviews. Make sure:
- You have good lighting and your face is clearly visible
- Your camera angle is at eye level
- You wear clean, professional-looking clothes (even if it’s just the top half!)
- You use a neutral or blurred background if your real one isn’t suitable
These small touches help you appear prepared and confident.
21. Technical Interview: Review the Stack
If a technical interview is part of the process, go over the technologies listed in the job ad. Prepare for common interview questions and brush up on both basic and advanced concepts depending on the level of the role.
If you consistently fail technical interviews on certain technologies or topics, identify them and study intentionally. Practice with exercises, tutorials, and small projects to build confidence.
22. Ask Questions & Seek Feedback
At every interview stage, ask questions:
- In HR interviews, ask about working conditions, team structure, and expectations.
- In technical interviews, ask thoughtful questions about their stack, architecture, or dev culture. It shows interest and depth.
Always request feedback after interviews. Whether you pass or not, it can help you improve. After technical challenges or live coding, thank the interviewers for their time and note what you learned.
It leaves a good impression and helps build relationships.
23. Watch Your Words Until the Very End
Often, we think the interview is going either really well or terribly, and we relax, or panic, and say things we shouldn't. Don’t make that mistake.
Never assume you’ve passed or failed. The interview is still happening until you hang up the call. Stay professional throughout.
You might feel like your technical interview was a disaster, only to find out later you passed. Or you might think everything went great and slip up in the last minute with an off-hand comment. Control your nerves and your words from start to finish. Always leave the best possible impression.
24. Live Coding: Explain Your Thought Process
If you’re doing live coding with someone watching, always:
- Read the prompt carefully
- Explain your approach as you go
- Ask questions if something’s unclear
- Make the solution work first and then improve it
Before these sessions, practice with coding katas or timed exercises in the relevant language/framework.
25. Understand the Types of Live Coding
Not all live coding challenges are the same. Ask in advance what type you'll face so you can prepare properly. Common formats include:
- Code review of a broken or badly written snippet. Your task is to suggest improvements or spot bugs
- Fixing broken code, where you're asked to debug and correct functionality
- Katas, which may include algorithmic challenges or small component builds under time pressure
Be aware of restrictions. Some interviews may:
- Prohibit ChatGPT or other AIs
- Disallow Stack Overflow or Google searches
- Only allow access to official documentation
Make sure you clarify the rules and, if needed, train your memory and problem-solving without relying on external tools.
26. Take-Home Assignments: Impress Them
If you’re given a take-home challenge:
- Use technologies you’re strongest with
- Stick closely to the requirements
- Go above and beyond. Add documentation, tests, or even a polished README explaining your architecture and decisions
Keep in mind: even if they say it takes “2 hours,” it usually takes more. Make the extra effort to stand out.
Phase 5: Final Steps
27. Network Smartly
Don't rely only on job portals. Talk to people. Reach out to connections or professionals in your field and ask if they know of any openings. Check company websites directly and when applying, craft thoughtful answers to open-ended questions.
You can use ChatGPT to help you draft responses and improve your applications.
28. Manage Expectations
If you’ve been searching for a long time and keep hearing that your salary expectations are too high or that the market is tough, consider adjusting. Either adapt to the current market or be patient and wait for the right opportunity.
29. Be Patient (Really Patient)
Job hunting, especially when you’ve set ambitious criteria, takes time. If you’re only applying to very specific roles (e.g., fully remote, niche tech stack, high salary), be ready to wait longer.
That said, it’s okay to reevaluate if your conditions are too strict and you realize you don’t have unlimited time, savings, or patience. You can always ease some of your filters.
Also, remember: many recruitment processes are slow, sometimes disorganized, and can take weeks (or months). Take breaks when needed, but trust the process and keep going.
30. Don’t Take It Personally
Rejection is hard, but it doesn’t always mean you’re not good enough. Sometimes:
- You’re simply not the profile they were looking for at that moment
- Another candidate had just a bit more experience with the exact tool they needed
- Or your strengths lie in areas that weren’t evaluated deeply enough
In other cases, you may need to improve in specific areas, and that’s okay too. Use feedback to identify those gaps and work on them. But always keep in mind: one rejection (or ten) does not define your worth or potential.
31. Keep Going. It Gets Easier
The first few interviews can be intimidating. You may feel caught off guard, especially in technical interviews or live coding sessions. But the more interviews you do, the more familiar the patterns become:
- Many questions will repeat across companies
- You’ll get better at explaining yourself
- You’ll become more comfortable under pressure
Treat each interview as practice for the next one. Confidence grows with repetition.
Phase 6: After the Offer
32. Don’t Accept Immediately: Take Your Time
When you receive an offer, don’t feel obligated to say yes on the spot.
It’s perfectly acceptable, and even expected, to ask for a few days to evaluate:
- You may receive another offer shortly after
- You need to analyze salary, conditions, work model, growth potential, etc.
Avoid making emotional decisions in the heat of the moment. Take your time to compare offers calmly and make a decision that aligns with your long-term goals.
33. Ask for a Pre-Contract (Offer Letter) Before Resigning
Before resigning from your current job, request a pre-contract or offer letter that clearly states:
- Salary
- Start date
- Work model
- Benefits
- Any special agreements
This provides legal and psychological security, especially if you’re leaving a stable job.
Having something signed avoids last-minute surprises and allows you to transition with confidence.
34. Rest and Prepare Before Starting the New Job
Sometimes after signing the offer, the company may share:
- Technologies to review
- Tools or frameworks to familiarize yourself with
- Onboarding materials
It’s good to prepare, but don’t burn yourself out before even starting.
If possible, negotiate a gap of a few days or weeks between jobs to:
- Rest and recharge
- Reset your mind
Start your new role with energy and clarity
You’ll perform better if you start fresh, not exhausted.
35. Close the Loop: Inform Other Companies
Once you’ve accepted an offer, inform other companies where you’re still in process that you’re no longer continuing:
Respect the time and effort of recruiters and interviewers. It’s professional and leaves the door open for future opportunities. A short polite message is enough.
Conclusion
Job hunting in tech can be a marathon, not a sprint. By defining your strategy, tracking your progress, preparing thoroughly, and staying proactive, you can significantly improve your chances, even in a tough market. Treat it like a project, stay consistent, and don’t be afraid to ask for help or adjust your approach as you go.
Continue reading...
