Job Search In A Pandemic, Part 1
Tags: reflection, jobsearch, softeng, pandemic
Published: 2020-12-06 03:53:43

---
title: Job Search In A Pandemic, Part 1
published: true
date: 2020-12-02 06:00:00 UTC
tags: reflection, jobsearch, softeng, pandemic
canonical_url: https://btruhand.github.io/blog/post/2020/12/02/job-search-in-pandemic-1
---

Recently I have just transitioned to a new job position (2 months ago from the date of this post) and the experience of the search served to be a valuable feedback for me. Now job search is not something I look forward to and doing it in a pandemic does not make me more enthusiastic. But due to personal reasons my decision to move to a new job was already set in stone pandemic or otherwise. I am sure I am not the only one that have been doing job searches during these hard times, so I feel my experience may bring some value to those that want to or still are job searching.

# Background and timeline

For background I was applying software/data engineering jobs in Toronto, Canada when I was still in Vancouver, Canada. I finished my Masters program on early April and I was targeting for a job position by end of August, which is when I planned to move to Toronto. During my job search I was working as a software engineer for a company that knows about my moving plans. Due to situation I was mostly mass applying to all kinds of software engineering jobs, though my specialty and expertise lies in backend engineering. Here is my job search timeline:

1. Started applying for jobs mid April to early May and then stopped because of a combination of a lack of motivation, jobs that match my preferences and feeling that it was a bit too far from August.
2. Restarted looking for jobs early June, this continued up to the third week of August. Applied almost daily, 1 to 3 applications
3. By early july only a handful (around 5) of recruiters/companies have contacted me back. Phone call interviews did not go well. Decided to introspect what kind of jobs I really want and the value I can bring forth as an engineer
4. In late July got a phone call interview for a node.js developer position. Flunked that one, used it as an opportunity to learn
5. Got a phone interview for my current company in early August, and managed to get past. Interview with management a week after, used the time to read up on company further and studied several materials
6. Passed interview with management and recruiter was able to put me for the technical interview with the team on the next day.
7. Technical interview went well, but with some hiccups. Ended with an offer that I took

The rest of this blog post will be structured following the timeline I laid out above as each one has a different story to tell. Since it’s quite long I will break the blog post to two parts. Link for the second part will be added on later

# Timeline #1

In mid April I was just finishing up my masters studies. Not wanting to waste time I immediately started to look for job openings. I decided to change some of the formatting of my resume to what I think is cleaner and better aligned to my goal of finding a software engineering job. I primarily used Indeed and LinkedIn for my job search and my searches were honed in to a full time job for software/data engineering positions. I’ve never really worked on a conctractual basis so I wasn’t sure if I would like that, and with the pandemic going on I wanted to find something that would be long lasting for a sense of security.

There isn’t much that happened during this period. I immediately noticed that many job positions were looking for more of a full-stack engineer and I really wanted to focus on backend. But since I do have a bit of frontend understanding (nothing modern or advanced) I soon decided to just apply to those that demanded full-stack capabilities, and even some that are purely frontend. Surely it is better to try and apply rather than not at all (right?). Of course, simply increasing the breadth of my applications did not mean it generated any positive results. Most of the applications I made were not receiving any replies, and if they were replied it was a rejection. Some of the reasons I came up for myself:

- The employers weren’t interested in my application (this is likely the case for various reasons)
- I was quite open in stating that I was looking for a job starting at the soonest on August/September and perhaps it didn’t fit with the employers timeframe
- Some wild theory that companies weren’t actually looking to hire but just scouting

While I never really know the reason, it did leave me feeling a bit dejected. Nearing May, I got a phone call from the employer that I worked for during my co-op wondering if I can come to help them on their projects. I took the offer and became busy with work and left job search on the side thinking that it may be better to try and apply another time.

# Timeline #2

In May most of my time was taken up by work and just spending my off-time relaxing by picking up some Switch games that I have neglected. When June arrived I noticed that I haven’t been looking for jobs ever since I stopped. There is only 3 months left until I move to Toronto and that felt too close comfort. It’s actually a bit funny thinking back on how a month’s difference makes my perception of time availability turn 180 degrees, from “I have time” to “I don’t have time”.

Trying to improve from my previous attempts at applications I decided to look back to my resume and cover letter once more. Some of the things that I did:

- I noticed some inconsistencies in formatting and some grammatical improvements to be made in my resume
- I put more emphasis on the job experiences that I wanted to highlight and be proud of by reordering them and using active words
- I created several copies of my resume, only differing in the job title that I wanted to present myself as depending on the application
- I decided to create a standard cover letter resume

You would think that one of the things that I would have done was to have a connection review my resume in the list above, but as you there is no mention of it. Why? The reason is simple, I was too afraid to ask it to be critiqued by another set of eyes. Honestly, I should have sought someone to critique it for me, but I was simply too scared at the thought of being shot down, getting told that what I have won’t impress anyone and overall deflating my confidence and spirit. Deep down I know I have some issues with imposter syndrome, and honestly sometimes I do believe that I am incapable. Some time in the future I would probably write another blog post about.

# Timeline #3

Job search did not go well. The number of applications that resulted into responses can be counted on one hand, while in total I probably applied to at least 50 applications (1 - 3 applications per day, at least 5 days per week). The ratio of “success”, success here simply getting a reply, is less than 1-to-10, yikes. Furthermore, I was sure not able to impress recruiters in my phone interviews. At some moments I did think that maybe it was all because of COVID19 and the job search climate. But I decided that even if that was the case, **it was something that I can’t control**. No matter how much I groan, my groaning would not lead to the outcome I desire, getting a job. So I further expanded my effort to improve my application process.

I challenged myself to answer the following questions:

1. What kind of job I really want? Does industry matter?
2. What responsibilities would I best be able to serve in? What technologies that I know that can benefit the company I apply to?

Answering the two questions above I decided to stop applying to frontend-heavy jobs. I would still apply to a full stack positions, but mostly those that are more backend oriented. While this is doubling down on a specific engineering area, it is really where I want to be and where I feel I can contribute best as an employee. With that in mind I reviewed my resume and cover letter once more to change how I present myself.

My most extensive work experience were with messaging/event-driven and data streaming oriented systems which coincidentally I enjoyed and was partly the reason to why I took a masters program. Therefore I made those experiences my main highlight in both my resume and cover letter. There isn’t many applications that directly mention such systems, but I wanted to put myself forward not as an all-rounder programmer that has no specialty. I wanted to be seen as someone that has a specialty but also possessing a broad range of skills. The next major experience that I highlight is designing and building REST APIs, which at least gets mentioned a lot in job postings. Lastly, I made sure to put myself as a developer that cares for quality in my cover letter by putting some emphasis on TDD and other engineering principles.

But the highlight of this timeline must be this: **I started blogging and putting time for personal projects**.

It is actually no coincidence that I started blogging more from beginning of July. My lack of progress in job search led me to find other avenues I can make progress in. Blogging was one of those avenues I wanted to invest myself more in, and also a relatively easy way to gain a sense of progress. For the same reason, I also started to do more programming in my own free time. While it isn’t the progress that I need, I felt it was tremendously helpful to gain a sense of momentum in life and also combating my imposter syndrome. I needed to not just feel, but know and see that I am capable of doing something I can take pride and ownership in. Had I not decided to start blog more or code on the side, I absolutely believe that it would have been much harder for me to push myself forward and continue job search.

# To be continued

This blog post has gotten quite long already and I don’t want to bore you to death with my life story. So feel free to close off the tab now, I will post the next part in the future. If you managed to read up to here, honestly thank you for reading the diary entries of a man on the internet. See you in the next part.