paint-brush
How I Tried to Automate Job Applications as a Software Engineer in Canada (and Failed)by@ukrainian
482 reads
482 reads

How I Tried to Automate Job Applications as a Software Engineer in Canada (and Failed)

by GeorgeApril 30th, 2024
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

A job hunt quest in a new country, using tech to make the process easier: RSS feeds, server-side scripts, custom Chrome extension and AI to add a personal touch
featured image - How I Tried to Automate Job Applications as a Software Engineer in Canada (and Failed)
George HackerNoon profile picture

Starting my job hunt in a new country felt like stepping into a massive library with no idea where to find the book I needed. Coming right after the neighboring country's violent invasion of Ukraine in 2022, I arrived with high hopes but quickly encountered a wall.


The job market here was a whole new world, and my usual approach just wasn't cutting it. Friends and settlement organizations suggested trying online job boards such as Job Bank Canada and Indeed.

The concept of Job Application Automation with a Human Touch

I wasn't aiming to spam companies with my resume. Instead, I sought to automate certain aspects of the process to save time and target suitable jobs for me in a more personalized manner. Moreover, it wasn’t solely about finding a job; it was also about learning how to use technology and AI, in particular.


In sharing this story, I hope to inspire others to look at their challenges differently and maybe even find new ways to tackle them.

Here's how I pieced it together, combining RSS feeds, server-side scripts, custom Chrome extensions, and the innovative use of AI to enrich data and personalize applications:

Step 1: RSS for Job Listings

Daily, a script on a Linux server I set up would fetch RSS feeds from Job Bank Canada, filtering opportunities based on my predefined keywords. It would store the data gathered into a cache file that another part of the system would work with later.


This step appreciates the enduring value of RSS, allowing me and other old-school guys to stay updated with minimal effort. So a big special thank you to the services and platforms like Job Bank for maintaining it.

Technologies used

  • PHP
  • PHP Simple XML
  • Linux Bash Scripting
  • Crontabs

Step 2: The Manual Touch: Reviewing Matches

Despite the automation intention, I chose to review the matches manually, ensuring that only the most relevant opportunities were considered, at least at the beginning. This blend of automation and personal oversight was enough to maintain quality in the job hunt. I figured out there were too many vague jobs that didn't sound legit to me.


Technically, the script reads the cached file and displays the number of items found for each keyword. At first, I was copying job posting details manually, but I gave up doing so for each listing. Even so, sometimes the same position can be seen twice or more if it contains different keywords, so…

Technologies used

  • PHP

Step 3: Crafting a Custom Chrome Extension


Screenshot of the extracted data (link)


..to expedite the review process and eliminate duplicates, I developed a simple parsing Chrome extension. The details it captured included the position name, salary range, contact info, and other essential data. I opted to automate this aspect in later versions of the system and either discard or repurpose the extension.


Once I obtained the data, if I deemed the listing worthwhile, a click would save it directly to a Google Spreadsheet. Initially, I didn't want to set up a separate database for this project. Therefore, this convenient and widely used Google product suited my needs, allowing me to maintain simplicity

The extension:

Install the extension

View Github source code

Technologies used

  • Google Spreadsheets API
  • Google Chrome’s extension
  • JavaScript

Step 4: Enriching Data with Server-Side Scripts and AI

I then enhanced my spreadsheet's listings using a server-side script to extract insights from employer websites, such as career page addresses, additional contact details, and social media links. More technical details were also gathered, like the server software and programming languages used.


The major breakthrough came from integrating OpenAI's API, which summarized websites and classified industries, enriching each saved job listing with valuable context. To optimize OpenAI token usage, I trimmed the content to focus on the most relevant sections for analysis, avoiding excess from footers or irrelevant links.

Technologies used

  • PHP cURL
  • Prompt Engineering
  • OpenAI API
  • Google Spreadsheets API

Step 5: Personalizing Cover Letters and resumes objectives

To avoid the impersonal nature of mass applications, I used OpenAI's API selectively to tailor cover letters, inserting placeholders for the company name, industry, and the software they utilize. When you know the product or service the company produces, you understand the value you may provide to it.

That was the only way to stand out among other applicants who used the semi-cold outreach approach. This strategy demonstrated a genuine interest in each employer even if I visited the website automatically in less than a second.

Technologies used

  • OpenAI API
  • PHP

Step 6: Generating PDFs for Applications

Aware of the limitations and risks associated with direct links in emails, I opted for a more conservative approach: converting resumes and cover letters into PDFs. Despite my preference for digital simplicity, the goal was to ensure my applications reached their destination with a reduced chance of being sidelined into spam folders or worse.


The generated PDF files were cached on the server side and attached to my emails.

Technologies used

  • PHP
  • DomPDF
  • Ubuntu Linux
  • JavaScript

Step 7: Enhancing Communication and Email Dispatch

After the initial steps of data enrichment and personalization, it is now time for the critical phase — communication. Upon selecting a potential opportunity, a predefined email template is loaded into a text area, ready for any final, personal touches.


The interface was similar to Gmail's one, where email addresses and subject lines were populated automatically. I used the position name, my name, and the company name in the subject. Sometimes I had to visit the website of a company of my interest again to ensure I don’t like or sound mistaken.


Anyway, I reviewed and, if necessary, customized each message before proceeding. This part can be automated later too. At least I thought I would do so.

To further avoid the stigma of automated spam, emails were dispatched at random intervals. This careful timing was designed to mimic human irregularity, reducing the likelihood of triggering spam filters and increasing the chance of email deliverability.

Technologies used

  • Gmail’s SMTP
  • CronJobs
  • Water.css
  • PHP

Step 8: Refining Email opening Tracking

Another gem of my job application toolkit was an email tracking system. I implemented a technique to outsmart tracker caching, subtly changing the tracking image's color scheme embedded in my email signature with each dispatch.

This ensured each email open was uniquely recorded, triggering a script to log the activity directly into my Google Spreadsheet against the respective employer. This method provided precise insights into who engaged with my emails and how many times, significantly informing the effectiveness of my approach.


While this tactic faced limitations with Gmail, it proved highly effective with other providers, particularly corporate ones.

Technologies used

  • cURL
  • Google Spreadsheets API
  • PHP

Conclusion

Sending each resume out of over 400 felt like giving away a great book to someone who's already received 400 others. The rare responses  I got were like small beams of light—rare but motivating. Adding a tracking system helped me see if my book even stood out in the pile.


It was a journey of patience, perseverance, and a personal test showing that job platforms like Job Bank might not be the best for IT jobs. It seems employers prefer traditional methods like recruiters, LinkedIn, or employee referrals.


Automating my job search was a huge learning curve. It was more than just speeding up applications; it was about making technology an ally in a personal quest. By blending RSS feeds, a Chrome extension, AI, and clever email strategies, I made my job hunt more efficient yet personal.


The experience taught me valuable lessons about using technology wisely and staying true to myself. It's not about replacing the personal touch with technology but enhancing it, showing that with the right approach, we can push beyond what we thought was possible.