Between 2019 and 2021, the tech job market was blazing. With lots of money and more investors, demand shot up, but the supply of skilled workers dropped.
Finding expert engineers was tough. Some companies got fewer than ten applications for full-stack developer roles. This hit unicorn companies hard, with more people changing jobs and some even juggling multiple roles across borders.
By late 2021, things shifted. Experienced engineers still had lots of job options and got higher pay when they switched jobs, leading to shorter stays in companies—similar to what happened after the dotcom crash and 2008 financial crisis.
After 2021, things changed for new software engineers. Entry-level demand stayed the same, as did salaries. In 2022, uncertainty grew. COVID-19 relief money dried up, and companies faced the consequences of unchecked growth. Some companies’ values plummeted from $10 billion to under $950 million, but they hung on because they were “too big to fail.”
As we’re now in mid-2024, I’ll offer advice to software engineers with under two years’ experience. Despite my background in computer science and years since my last code in Java, I still work with software teams and hire. Hopefully, my advice can help new developers looking for jobs in Canada.
Let’s draw some conclusions about a few issues.
- If you lack basic knowledge, finding a job won’t be easy, not just in Canada, but anywhere. This might stay the same until the end of 2024, and I’m not too hopeful about 2025.
- Having a degree from a prestigious school might help, but when interviewing, the company’s HR needs to see how you’ll contribute. In this regard, real-world experience often outweighs schooling.
- Finding a job is tough right now. Really tough. Bootcamps might promise easy tech jobs and HR knocking on your door after shelling out thousands, but that’s far from reality. I’ll explain this further below.
- The job market isn’t just challenging for newbies; even experienced engineers are feeling the pinch. A friend with 14 years of experience got rejected for having “too much experience”. Sometimes, it’s tough for experienced IT people in abroad because employers struggle to envision their potential.
- Experienced engineers are also feeling the slowdown due to the reasons mentioned. Investment-backed companies and even some traditional ones are scaling back hiring. Recruiters are now prioritizing experienced candidates with a smaller pool to choose from.
In these tough times, our goal should be to give employers clear signals about our abilities and minimize distractions. We need to make their job easier and show them we’re top-notch employees.
Let’s figure out how we can navigate this job search together, especially in Canada’s IT field. While the advice mainly focuses on software developers, it’s also helpful for other IT roles like product managers, project managers, and UI/UX designers.
In these tough times, our goal should be to give employers a clear picture of who you are and minimize any distractions. This way, we can make their job easier and show them that you’re a standout candidate.
So, let’s dive into how we can tackle finding a job in Canada’s IT sector. Remember, while this guidance is aimed at software developers, it’s beneficial for others in the IT industry too.
Look for ways to overcome the Canadian experience
Newcomers often face the hurdle of “Canadian Experience.” While it’s explicitly mentioned in Canada, similar issues exist in parts of the USA, England, and Spain. Discrimination based on this is illegal, so if you suspect you’ve been turned down for this reason, it’s wise to reach out to the appropriate authorities.
This problem stems partly from past misuse of fake references and CVs, leading some companies to require Canadian work experience. While not every company follows this practice, having even a small stint in Canada can boost your chances. Just ensure it aligns with your field.
Another factor is the desire for culturally fitting immigrants. Hiring managers prefer those who smoothly integrate into Canadian culture without causing issues.
BlueWave Labs addresses this challenge by welcoming software developers, forming teams, and working on real applications. If you’re seeking Canadian experience and have at least 2 years of expertise, we suggest you contact BlueWave Labs to learn opportunities provided.
Keep your energy high throughout the process
If you apply to job postings and don’t get results, this doesn’t mean you’re bad. Recently, companies have started to choose not to send any responses in order to save time. There may be numerous reasons for receiving a rejection response or no response at all. Some companies put out a job announcement and keep it on LinkedIn for months just so that it is not obvious that they are in a bad situation.
In short, there may be dozens of reasons why you cannot get a job. None of these reasons show that you are inadequate. Even if it shows that you are inadequate, it is necessary to take action and look for ways to close the missing areas.
In short, keep applying every day. That must be your first task in the morning. Create a Kanban board and list your applications. Think of it as a real-time job, so you can relieve mental fatigue. Don’t skip days while looking for a job, think of it as your full-time job.
Don't just hang out on LinkedIn
Open an account on all job posting systems in Canada. In addition to LinkedIn, this includes Jobbank, Glassdoor, Monster, Indeed, TechTalent and places that offer job postings by state.
‘Can I work in a different province?’ Don’t say. Don’t look for hybrid or on-site announcements in the job postings there either. If you are good in your field, you may have the opportunity to work in another province without ever coming to the company. Sometimes, for jobs in smaller cities, remote working is welcomed because it is difficult to find employees in specific areas.
Think of this job as a 9-5 job and try to exceed the application you made the day before each day. Adjust the notification settings of each posting platform so that job postings containing certain keywords are delivered to your mailbox immediately.
If there is an offer, don't be too picky
I can almost hear you saying, ‘There are no offers coming so let’s be selective’, and you are right. But if you have received even a single offer, I recommend you accept it unless you have serious concerns. It is more important to start with a perfect place to start.
Once you accept the offer and work, you can also take courses to focus on your field. You will probably get experience in that workplace that you have never had before in Canada.
I mentioned bootcamps above. Bootcamps, which provide intensive training on a specific subject quickly, are no longer helpful in helping find a job, and some HR professionals do not even count bootcamp as past experience. Therefore, we recommend that you stay away and do not waste your time (unless you have a very valid reason).
Apply to early stage startups
Early stage startups, especially those that receive investment and want to grow quickly, are excited about hiring. Since they have money in the bank, they are usually eager to spend it quickly. But the way you apply to such companies should not be through job sites. Instead, you should send an email to the CEO.
You can also state the following in the letter:
- State what you want to do in the initiative (example: ‘the interface design of your application is quite dull, I want to improve its user experience’).
- Explain why you want to join this company (example: ‘I see that you do not invest in content. However, I examined your competitors and saw that each of them prepares an average of 4-15 blog posts per week. I can show my expertise in this field and help you win thanks to SEO’).
- Write why they should choose you (example: ‘I worked as a developer on both the frontend and backend side of the company I worked for before, and over time I rose to the position of team leader. Here, too, I can train employees and enable them to learn X technology).
You don’t need to have studied at the best schools or graduate with a degree to write these. Try your luck.
Another quick tip: Send this email on the weekend so the CEO has more time to read and take action.
Note: I have also received ‘desperate’ messages stating that the sender wants to get a job before but no one would hire that person. I recommend that you do not use such negative sentences, because such phrases make the other person think, ‘No one has hired this person, why should I?’.
GitHub account and portfolio
Before stepping into interviews and catching the eye of HR and hiring managers, it’s crucial to tidy up your digital presence, especially your GitHub account. A well-curated profile showcasing the applications and libraries you contribute to can make a big difference.
Keep in mind, your aim is to make a positive impression and communicate effectively with HR. This is how you can stand out from the crowd.
The most effective way to do this is through personal portfolios and real projects. HR professionals value these because many applicants from bootcamps lack practical experience and end up disappointed. While training is important, showcasing what you’ve actually accomplished is key.
Your personal portfolio can be simple, whether it’s a basic HTML page, WordPress site, or using a content management system. It should highlight your projects, open-source contributions, and demonstrate your dedication to your work, even if it’s a personal project.
Now, let’s delve deeper into personal portfolios. They don’t have to be flawless. You can create a command-line application, a library, or a product with a simple interface but great functionality. These projects provide talking points during interviews. My advice is to have one standout project and several smaller side projects you’ve dedicated time to over a week.
Meanwhile, your knowledge base (if you’re sitting idle) diminishes when you’re applying for jobs. To prevent this, focus on algorithms and question solving methods from time to time on various platforms (Hackerrank and Leetcode ). LeetCode’s ’30 days of Javascript ‘ program is particularly good.
GitHub readme structure
In my view, the Readme file is the most crucial aspect of GitHub projects. It sits at the top and is the first thing people see when they come across your project. So, it’s essential to have a clear and well-structured Readme file. Here’s what it should include:
- Title and logo
- Description
- Purpose (why/problem/goal)
- Quick start
- Usage
- Contribution
- License
The initial 10 seconds are vital for grabbing the reader’s attention. Therefore, it’s crucial to craft the description and purpose sections into two paragraphs of 4-5 lines each. If you’ve captured their interest, you can provide more details about the quick start and usage.
In addition to the GitHub Readme, don’t forget about your GitHub profile. This is also scrutinized during the recruitment process, especially after the technical team gets involved. So, it’s important to send the right message.
A tidy, well-captured photo is essential for your profile. It doesn’t have to be professional, but avoid using the default avatar. You can also use this photo on other platforms like LinkedIn or Twitter. If your GitHub username is quirky or potentially off-putting, consider changing it.
Include two paragraphs describing yourself. Instead of generic statements, highlight your personal qualities or unique features that set you apart. Additionally, list 3-4 repositories at the bottom. The first one should be the project you’ve invested the most time in. And remember, a well-written Readme file is a must for every repository.
Lastly, there’s the GitHub contribution heatmap. While it doesn’t need to be packed with activity, having some contributions shows your engagement.
Your LinkedIn account
In the tech industry, I believe GitHub holds more weight than LinkedIn. However, your LinkedIn profile still needs to send the right message to align with the signaling we’ve discussed.
In essence, LinkedIn should complement your GitHub presence. Here’s a brief checklist for LinkedIn essentials:
- Swap out the default profile picture for a nice one of yourself. You can also showcase your GitHub contributions here.
- Customize your banner image instead of sticking with the default. A picture from a conference or event works well.
- Your summary section should mirror what you’ve highlighted on GitHub. Avoid generic statements and aim to grab attention. Mention your preferred programming languages and tech interests.
- When describing your past work experiences, be specific. A vague description won’t cut it. Highlight the contributions you made to each role, especially upon completion of a project or job task.
Wrong example: ‘Worked on a backend REST API’
Correct example: ‘Built a file upload service using APIs with Docker and Go that handled 500 files per second. It replaced the previous service that had issues handling 100 files per second.’
Your resume
I saved discussing resumes for last because everything we covered for LinkedIn and GitHub also applies here.
You can use Google Docs or a similar platform to create your resume. Google Docs is great for quickly putting together a resume with various formatting options.
Now, let’s go over some key points for your resume:
- Before finalizing your resume, share it with 3-4 friends, especially those with recruiting experience, to get their feedback.
- When sending your resume via email or uploading it online, always use PDF format. PDFs are easier for HR professionals to view instantly compared to Word documents.
- While resumes generally follow a similar format, adding unique touches can make yours more memorable. Consider subtle changes like using a different color for headings or making your name slightly larger.
- Highlight your most notable and favorite project, often referred to as a ‘capstone project.’ Give it an appealing name and describe your excitement and the results achieved.
- Tailor your resume to match the job description provided by the company. Focus on highlighting skills and experiences relevant to the role, and remove any unnecessary information.
- Avoid rating your programming skills on a scale of 1-10; it’s not meaningful to the reader.
- Include your GitHub profile on your resume.
- Use ChatGPT to extract keywords from the job description and incorporate them into your resume (if applicable).
- There are many online resources for crafting resumes tailored to the IT industry. I suggest exploring articles on writing cover letters, creating ATS-compliant resumes, and incorporating keywords from job postings.
- Indeed Canada offers helpful services for newcomers, including resume feedback and interview preparation tips.
- Preparation for phone, video, and face-to-face interviews is crucial. Ensure your background is tidy and professional, even if you can’t tidy up before the interview. Consider blurring the background or using a different image. Avoid adding videos to your resume.
Good luck!
Entering the IT industry is quite challenging nowadays. If you’re constantly hearing stories like “I got 3 offers in a week,” chances are they’re either exaggerated or heavily reliant on luck.
But here’s a glimmer of hope: Once you land a job in Canada, it becomes easier with each passing year. So, don’t lose hope or worry too much.
In the meantime, consider supporting volunteer work and seeking assistance from public libraries, community centers, and non-governmental organizations. Building a network is crucial. You can attend events on platforms like EventBrite and join monthly coffee talk meetings to expand your connections. These efforts can significantly boost your networking opportunities.
