AI Research Engineer (Early Career)
0.5y relevant experience
Executive Summary
The candidate is a technically capable engineer with a solid foundation in production Python/C++, applied ML, and cloud infrastructure, built through 3 years of professional experience in the automotive software industry. Their background is genuinely strong for certain engineering roles, but it is substantially misaligned with this AI Research Engineer position. The role demands hands-on experience with LLMs, RAG pipelines, vector databases, and agentic frameworks — none of which appear anywhere in their resume, skills list, or public presence. They have not submitted code samples or a GitHub profile, which are critical signals for an entry-level role where projects compensate for limited industry experience in the target domain. Without evidence of LLM curiosity or self-directed projects in applied AI, recommending them for interview would require significant speculation about transferability.
Top Strengths
- ✓Production-grade Python and C++ engineering in a demanding automotive software environment
- ✓Hands-on ML experience with LSTM-based neural networks and real sensor data at scale
- ✓Cloud and infrastructure experience (AWS, Azure, Docker, CI/CD, Databricks, Kafka)
- ✓MSc in Big Data Analytics adds academic rigor alongside industry exposure
- ✓Strong engineering discipline: unit testing, code review tools, version control in large teams
Key Concerns
- !No demonstrated experience with LLMs, RAG, vector databases, AI agents, LangGraph, or prompt engineering — these are the core requirements of this role
- !No public code, GitHub, or project portfolio to evaluate applied AI curiosity or initiative outside of employment
Culture Fit
Growth Potential
Moderate
Salary Estimate
$45,000 - $60,000 (EU-based, Poland, entry-to-mid level)
Assessment Reasoning
The NOT_FIT decision is based on a fundamental domain mismatch rather than a lack of engineering ability. The candidate is a competent engineer, but the required skills for this role — LLMs, RAG, AI agents, LangGraph, vector databases, and prompt engineering — are entirely absent from their profile. They meets only 2 of 9 required skills (Python, C++) and has no demonstrated experience or public artifacts in the applied AI/NLP domain. The role explicitly calls for candidates who have built LLM-related projects (even personal or academic), yet there is no GitHub, no portfolio, no open-source work, and no cover letter to provide compensating context. Their ADAS/sensor-processing background is a legitimate ML track, but it does not translate directly to the agentic AI systems work described in this job. A score of 48 reflects that they have real engineering value, but not for this specific position as defined.
Interview Focus Areas
Experience Overview
3y total · 0.5y relevantThe candidate is a competent ML/systems engineer with a solid foundation in Python, C++, and applied machine learning for autonomous driving. However, their experience is almost entirely in sensor data processing, computer vision, and embedded systems — with no visible exposure to LLMs, RAG, vector databases, or agentic AI frameworks. The role's core requirements are fundamentally misaligned with their demonstrated skill set.
Matching Skills
Skills to Verify