Canadian Jobs amid a Pandemic: Examining the Relationship between Professional Industry and Salary to Regional Key Performance Indicators
Bibliographic record
Abstract
The COVID-19 pandemic has contributed to un-precedented rates of unemployment and greater uncertainty in the job market. There is a growing need for data-driven tools and analyses to better inform the public on trends within the job market. In particular, obtaining a “snapshot” of available employment opportunities mid-pandemic promises insights to inform policy and support retraining programs. In this work, we combine data scraped from the Canadian Job Bank and Numbeo globally crowd-sourced repository to explore the relationship between job postings during a global pandemic and Key Performance Indicators (e.g. quality of life [QOL] index, cost of living) for major cities across Canada. This analysis aims to help Canadians make informed career decisions, collect a “snapshot” of the Canadian employment opportunities amid a pandemic, and inform job seekers in identifying the correct fit between the desired lifestyle of a city and their career. We collected a new high-quality dataset of job postings from jobbank.gc.ca obtained with the use of ethical web scraping and performed exploratory data analysis on this dataset to identify job opportunity trends. When optimizing for average salary of job openings with QOL, affordability, cost of living, and traffic indices, it was found that Edmonton, AB consistently scores higher than the mean, and is therefore an attractive place to move. Furthermore, we identified optimal provinces to relocate to with respect to individual skill levels. It was determined that Ajax, Marathon, and Chapleau, ON are each attractive cities for IT professionals, construction workers, and healthcare workers respectively when maximizing average salary. Finally, we publicly release our scraped dataset as a mid-pandemic snapshot of Canadian employment opportunities and present a public web application that provides an interactive visual interface that summarizes our findings for the general public and the broader research community.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.007 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.003 | 0.007 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".