Key competencies for big data analytics professions: a multimethod study
Bibliographic record
Abstract
Purpose This study aims to identify the precise competencies that employers are seeking for big data analytics professions and whether higher education big data programs enable students to acquire the competencies. Design/methodology/approach This study utilizes a multimethod approach involving three data sources: online job postings, executive interviews and big data programs at universities and colleges. Text mining analysis guided by a holistic competency theoretical framework was used to derive insights into the required competencies. Findings We found that employers are seeking workers with strong functional and cognitive competencies in data analytics, computing and business combined with a range of social competencies and specific personality traits. The exact combination of competencies required varies with job levels and tasks. Executives clearly indicate that workers rarely possess the competencies and they have to provide additional training. Research limitations/implications A limitation is our inability to capture workers' perspectives to determine the extent to which they think they have the necessary competencies. Practical implications The findings can be used by higher educational institutions to design programs to better meet market demand. Job seekers can use it to focus on the types of competencies they need to advance their careers. Policymakers can use it to focus policies and investments to alleviate skills shortages. Industry and universities can use it to strengthen their collaborations. Social implications Much closer collaborations among public institutions, educational institutions, industry, and community organizations are needed to ensure training programs evolve with the evolving need for skills driven by dynamic technological changes. Originality/value This is the first study on this topic to adopt a multimethod approach incorporating the perspectives of the key stakeholders in the supply and demand of skilled workers. It is the first to employ text mining analysis guided by a holistic competency framework to derive unique insights.
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.026 | 0.029 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.003 |
| Science and technology studies | 0.003 | 0.003 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.000 |
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".