AI Research Engineer (Early Career)

Executive Summary

The candidate is an Embedded QA Engineer and Python automation developer based in Slovakia whose skills and career arc are substantially misaligned with the AI Research Engineer role. While they demonstrate real engineering competence in embedded testing, automation, and data scraping, they show no credible evidence of work with LLMs, RAG pipelines, vector databases, agentic systems, or ML model evaluation — the core technical requirements of this position. The single mention of 'Local LLMs' and 'LLM-powered development' in their skills section is unsubstantiated by any project, repository, or description. The absence of a GitHub profile, code sample, and cover letter further limits the ability to assess any latent AI/ML capability. This application does not meet the threshold for the role and should not proceed to interview.

Assessment Reasoning

NOT_FIT decision is based on a substantial mismatch across all core dimensions. The role requires demonstrated proficiency in LLMs, RAG, AI agents, LangGraph, vector databases, and prompt engineering — none of which are evidenced in the candidate's resume, project history, or online presence. They meets only 1 of 9 required skills (Python), placing them well below the 50% threshold for BORDERLINE consideration. Their current and recent roles are in Embedded QA and data scraping/automation, not ML engineering. The educational background (applied college diplomas) does not align with the 'strong CS/ML program' requirement. No code sample or GitHub profile was provided to offset these gaps. While the candidate shows genuine engineering ability in their own domain, there is insufficient signal — no projects, no coursework, no research, no community involvement — to suggest readiness for an AI Research Engineer role even at entry level.

Interview Focus Areas

No code was submitted for review and no GitHub profile is linked, which is a significant gap for an engineering role requiring demonstrated production-quality code. The resume project descriptions indicate functional scripting-level work but provide no insight into software architecture, testing discipline, or ML-relevant engineering. Without any code artifacts, this dimension cannot be favorably scored.

The candidate is a QA/Embedded engineer with a data scripting background whose core competencies lie in firmware testing, test automation, and web scraping — not AI/ML research engineering. While they lists 'Local LLMs' and 'LLM-powered development' under skills, there is no supporting evidence of real project work in this area. The educational background (Ukrainian applied college diplomas in Computer Systems and Computer Engineering) and the career arc point clearly away from the ML research engineering profile this role demands.