DEV Community

Cover image for 23 Rejections, Multiple Offers: What I Learned From My 2-Month SWE Job Search
Julien Avezou
Julien Avezou Subscriber

Posted on

23 Rejections, Multiple Offers: What I Learned From My 2-Month SWE Job Search

Includes stats from 72 applications sent

Feels like it's been more than a minute since my last post. A lot has happened in my life over the past weeks: I searched for a job, travelled to Portugal, got married and started a new job!

Now that I am settling back into a routine, I am eager to start writing again. I have a long list of topics that I want to explore further and share with you all.

A first resource I want to share is a collection of all my thoughts, observations and advice from my recent job search, which lasted just under 2 months and resulted in multiple offers.

I break this collection down into several sections:

  • Mindset
  • Immediate Actions
  • Further Actions
  • Tips
  • Observations and Trends
  • Discussion

This is the guide I wish I had when I started.

Before we dive in, here is my job search by the numbers:

Duration: ~7 weeks
Applications sent: 72
Rejections: 23
Offers: 2
Enter fullscreen mode Exit fullscreen mode

Disclaimer: I was applying primarily for Senior Software Engineer positions. I had several years of professional engineering experience going into the search, so these numbers shouldn't necessarily be treated as representative of someone looking for their first engineering role. Your results will vary depending on experience, location and the types of roles you're targeting. But I have included advice that should be applicable to anyone on the job hunt, regardless of experience.


Mindset

Entering your job search with the right mindset is foundational and key to success.

  • Consistent and steady wins the race. Job searching is a marathon. Manage your energy well. Keep your momentum up with a few small daily wins. Send out a few applications every day. Even 2 focused hours a day can be enough.

  • Gamify the job hunt experience: make it a daily challenge to send out at least a couple of applications then learn something new for potential roles, take this as an opportunity to learn more about companies and learn from interviewers.

  • Rejection does not mean failure. It's part of the numbers game. You will most likely go through multiple rejections before getting a job offer. I did. 23 times to be exact! Always ask for feedback if rejected, you can learn and improve the next time thanks to feedback. Each rejection is a chance to improve and increase your odds of succeeding in your next interview.

  • If you fail an interview, don't panic, it's not a nice feeling but as long as you take away a lesson to improve on for next time, that is called progress. Also over time you will get used to interviewing and it will feel more natural, and with repetition you will force luck and get that job. Don't linger on your failure, take away your learnings and shift your focus towards your next interview and opportunity.

  • Prioritise yourself. Job searching takes a toll, mentally and sometimes physically. It is hard to deal with rejection. Take time in the day for yourself. Start your day with sunlight, mindfulness and movement, spend your evening doing an activity you enjoy.

  • Don't put all your eggs in one basket. In other words, don't rely heavily on one single interview process. Always be working on backup processes. Your interview pipeline should always be growing until you secure that offer.

  • Think out of the box. Build a portfolio of personal projects to stand out and give you more talking points during interviews.

  • Stay accountable. Tell your family and friends that you are applying for jobs and update them regularly on both your successes and failures.


Immediate actions

Complete these actions within your first week so that your results can start compounding fast and early on.

  • Spend a full day updating your CV/resume and making sure it contains all the relevant experience and keywords. A solid resume is foundational. Make sure your resume passes ATS screening.

  • Update your LinkedIn. Include keywords in profile title and description. Set status to open to work. Post regularly.
    I personally like the new 'Featured' section where you can showcase your latest accomplishments such as highlighting personal projects and activities

  • Leverage your own close network of family/friends. You might be surprised by the amount of referrals just under your nose that might be working at a company you could apply for.

  • Prepare a cover letter template and include one section you can personalise using AI to speed up the process. I copy and paste the job description into an LLM and combine it with my resume as context. The LLM outputs a section tailored towards the company you are applying for that you can paste within the more generic template used.

  • Create a job application tracker to stay organised and follow up on status when necessary. I set up a spreadsheet with the following columns: company, status (null | applied | interview | offer | declined), actions, date, rejection reason

  • Join talent pools, job portals & recruiter networks to get inbound job opportunities over time. They might not be as relevant on average as outbound reach but it allows you to keep practicing interviewing. I actually got one of my offers through a recruiter network, so this channel certainly paid off for me.


Further actions

These actions are optional and take more time but can definitely pay off big time.

  • Connect with recruiters directly on LinkedIn and ask for opportunities

  • Go to networking events and ask people if they are actively hiring.

  • Set up coffee chats with leads, this makes the connection more personal than calls and you can get more valuable information from these meetings.


Interview preparation

Once you start getting leads and first round interviews, practice your technical and behavioral interviews.

Technical interviews

  • Prepare for coding and system design interviews - no need to memorize hundreds of problems, focus on the common data structures and algorithms and have a few system design templates ready. I created my own free tool for this purpose, no signup required.

  • Create flashcards to learn technical terms

Behavioral interviews

  • Do high-level research on the company and read the job description before the interview - skills company is looking for, identify keywords to use in interview, mission statement, engineering principles, key features, latest news. AI is great for this use case. I have used it to research jobs and dig deeper into job descriptions.

  • Use the STAR methodology for behavioral interviews - prepare 6-8 answers to common questions.

  • Have a project deep-dive story prepared - story, features, tech stack, tradeoffs, lessons learned.

  • Always have a couple of questions handy to ask the interviewer if they ask if you have any questions at the end.


Tips

Here is some personal advice that helped me a lot.

  • Schedule your top choice company interviews slightly after your lower preference companies so you can practice beforehand with lower-ranked companies.

  • If targeting a certain industry, become more knowledgeable about said industry. This will give you an edge vs other engineers who often would only know technical aspects, not sector-wide trends and dynamics. For example, I did this with FinTech and got a bunch of books from my local library to read up on indsutry specific concepts.

  • Interviewing is a skill. Keep your interview skills fresh even when you're employed. It's good practice to keep interviewing occasionally and assess what your market value is. Also to maintain a fresh network of recruiters and protect yourself in a volatile job market.

  • Track metrics to know if you are on the right path. Treat your job search like a funnel:

Applications -> Responses -> Recruiter screens -> Technical rounds -> Final rounds -> Offers
Enter fullscreen mode Exit fullscreen mode

Identify where your funnel breaks:

  1. Few responses, consider tweaking your resume.
  2. Screens but few technical rounds? Rework your positioning and storytelling.
  3. Failing at technical rounds? Practice more.
  • Don't be afraid to follow up after an interview if no answer after a week or so. Only follow up a few times. If there's still no answer, you have probably been ghosted. Don't take it personally, it has happened to me countless times. The company may simply have shifted priorities.

Observations and Trends

Searching for a job this time felt very different compared to just a few years ago.

  • AI screening is becoming more common. I encountered several AI-led interview processes throughout my search. Some felt opaque about how the recording or data would be used and rarely led to any human follow-up. I would strongly recommend researching the company and understanding what you're consenting to before completing these types of interviews.

  • Authenticity is more important than ever. Many recruiters have told me that there is much slop out there with candidates overrelying on AI tools to pass interview rounds leading to inauthentic responses.

  • Interview strategies are all over the place. With the widespread adoption of AI tooling, some companies have shifted away from traditional LeetCode to more project-based evaluation. I felt that you never knew what to expect for each hiring process. I went through it all from LeetCode, to AI-assisted project building and discussions. This is arguably a good and bad thing as it gives opportunities to ace an interview in different ways but it also leads to confusion at times and a lot of context switching.


Discussion

Let's leverage this community to share our experiences.

What advice would you give for any job seekers out there?

Any useful resources you can share to help job seekers in our community?

Feel free to reach out to me in the comments or directly and connect, I would be happy to give you more personalised advice!

Good luck to you if you're currently job searching! Keep going!

Top comments (38)

Collapse
 
francistrdev profile image
FrancisTRᴅᴇᴠ •

Julien Avezou has return to DEV! We are so back :D

Collapse
 
javz profile image
Julien Avezou •

lets gooooo!! so good to be back!

Collapse
 
heytechomaima profile image
Omaima Ameen •

i'd love to have a little conversation with you about your experience as a senior full-stack dev, would you be up for a quick chat sometime???

Collapse
 
javz profile image
Julien Avezou •

Yes let's do it! Sometime next week? Do you have LinkedIn?

Thread Thread
 
heytechomaima profile image
Comment deleted
Thread Thread
 
heytechomaima profile image
Comment deleted
Thread Thread
 
javz profile image
Julien Avezou •

I sent you a connection request! Feel free to send me a message.

Collapse
 
naveen_alavilli profile image
Naveen Alavilli •

Useful writeup, and congratulations on both the job and the wedding. Let me add the view from the other side of the table, since I spend a fair amount of time writing the scoring rubric before anyone is in the room.

On asking for feedback after a rejection: keep doing it, but calibrate your expectations, because in most structured processes the person you are asking is not permitted to answer. The scores exist, they are written down, and they usually cannot leave the building. That is legal exposure rather than rudeness, and it means silence is not a signal about you. The feedback loop you actually control is your own: within an hour of the interview, before the memory smooths itself out, write down the question you answered worst and what a better answer would have contained. Twenty-three of those is a dataset. Twenty-three unanswered emails is not.

On your numbers, 72 applications, 23 rejections, 2 offers: the ratio worth watching is not applications to offers but applications to first human conversation. Those two ratios fail for completely different reasons. A bad application-to-screen ratio is a resume and keyword problem, which is fixable in an afternoon. A good screen rate with a bad interview-to-offer rate is a performance problem, which is fixable but not in an afternoon. Most people I talk to are optimizing the wrong one because they only track the number at the end.

The thing I wish more candidates knew: where the rubric is written in advance, the interview is not a conversation searching for the best person. It is an evidence-collection exercise against criteria that were fixed before your name came up. So answer in a shape the scorer can write down. What the situation was, what you specifically did, what it cost, what changed afterwards. Being impressive in a way that does not map to a criterion scores zero, and the interviewer often cannot tell you that is what happened.

Collapse
 
javz profile image
Julien Avezou •

Thanks Naveen! Great insights.

Collapse
 
naveen_alavilli profile image
Naveen Alavilli •

Glad it was useful — and thanks for writing up the process in enough detail that the "other side of the table" view actually had something to respond to.

Collapse
 
sinarezaei profile image
Sina Rezaei •

One thing I would be careful with is treating rejection itself as data.
23 rejections tell us that 23 processes ended without an offer, but they don't necessarily tell us why. The reason could be technical skills, experience, timing, location, budget, another candidate, or even an evaluation that simply wasn't accurate. So I think the useful distinction is between an outcome and an explanation. A rejection is an outcome. Without knowing the cause, we shouldn't automatically turn it into evidence that someone needs to improve.
The feedback you can actually verify is much more valuable than the rejection itself.

Collapse
 
javz profile image
Julien Avezou •

I completely agree with you Sina. In my application tracker I added a column 'rejection reason' for this purpose.

Collapse
 
sameerqaisar17 profile image
Sameer Qaiser •

The line that hit me: "Rejection does not mean failure. It's part of the numbers game."

I'm not job hunting — I'm two weeks into learning Python and trying to break into technical writing. But I've been running the exact same playbook without realizing it.

I've sent 7 pitches to companies that pay for Python tutorials. Zero replies so far. Four of them were closed doors entirely — "not accepting new authors." Two never responded. One form only had options for other languages.

Reading your post, I realized: 23 rejections and 2 offers is a 91% rejection rate, and you still won. My 7 pitches with 0 replies is nowhere near enough data to conclude anything.

The funnel breakdown is what I'm stealing. "Few responses? Tweak your resume. Screens but no interviews? Rework your positioning." I need to figure out where my funnel is breaking. Are my pitches not landing? Is my portfolio not strong enough? Am I pitching the wrong companies?

Right now I don't know. But your numbers make me realize I need to send way more before I can diagnose anything.

Thanks for writing this. Saving it.

Collapse
 
javz profile image
Julien Avezou •

Thanks Sameer! Absolutely, that is the right minset. Keep sending more, pause, evaluate, tweak and send another batch again. Repeat. Good luck!

Collapse
 
meltoteng profile image
Mel Toteng •

Thanks for sharing. I am three weeks into my own job search and your interview preparation advice is spot on. Also as an experienced engineer, opportunities and interviews don’t always come as quickly as expected. So learning to handle rejection and keep going is just as important as preparing technically.

Collapse
 
javz profile image
Julien Avezou •

Best of luck with your job search! I hope this guide can help you in some way. Let me know how it goes.

Collapse
 
leonore_fcf3095de32ca8433 profile image
Leonore •

Really useful breakdown, especially the focus on treating the job search like a funnel and learning from each rejection. The 72 applications, 23 rejections, and 2 offers also make the advice feel very practical rather than theoretical. The interview preparation and AI screening sections were especially interesting. I’ll definitely check out more developer and career resources on codecan.net as well.

Collapse
 
javz profile image
Julien Avezou •

Thanks Leonore, glad you found this resource useful.

Collapse
 
marina_eremina profile image
Marina Eremina •

Really liked the idea of gamifying the job search - it for sure helps to reduce stress and keeps you motivated. Overall, all the mindset and immediate actions tips are really useful, how you approach the job search can make a huge difference. Congrats on the new job! 🎉

Collapse
 
javz profile image
Julien Avezou •

Thanks Marina! :)
Continuous action without the right mindset can be problematic which is why I wanted to introduce a guide that combines both.

Collapse
 
unitbuilds profile image
UnitBuilds •

Resume Helper I made this a while ago. I find that we all tend to be too scattered in our approaches, so fill it up with your experiences, then it'll compile a CV based on the job description, from your own words (not AI generated, AI curated, there's a difference). Run the red-team check to do an 'ai test' whether your CV will pass automated review and it'll give you questions on any gaps it found, who knows, you likely have the experience, you just didnt remember to write it.

If you score 85+ on your red team, chances are good that you'll be a solid candidate for it.

Otherwise if you wanna read about some tips I discovered while writing an automated recruitment app:

Collapse
 
javz profile image
Julien Avezou •

Nice!

Collapse
 
henry786 profile image
Henry •

Huge congrats on the new role! Trackers like that are a lifesaver. We actually use similar pipeline tracking at The Printing World for managing new client onboarding and custom packaging specs—keeping data organized really makes all the difference.

Collapse
 
javz profile image
Julien Avezou • • Edited

Thanks Henry! I agree.

Collapse
 
leob profile image
leob •

Good points/advice! Just curious, why did you need to go job hunting - were you not completely satisfied with the job you had, looking for something else/better?

Collapse
 
javz profile image
Julien Avezou •

Thanks leob! I moved to another country and had to leave my job as there was no possibility to work from abroad. And there was a timing issue for obtaining the work permit. That's why :)

Collapse
 
leob profile image
leob •

Ah okay, thanks! Must have been a busy time getting all of that done and organized ...

Thread Thread
 
javz profile image
Julien Avezou •

yeah the paperwork and uncertainty were definitely stressful with everything else going on :D

Thread Thread
 
leob profile image
leob •

Big changes, nice that it all worked out for you, well done!

Some comments may only be visible to logged-in visitors. Sign in to view all comments.