Pivots Hiring
A
42

AI Research Engineer (Early Career)

0.5y relevant experience

Actively looking · applied Oct 2026Not Qualified

Interested in this candidate? We'll reach out to them for you.

No cold messaging strangers - we ask if they'd like to talk and send you their contact details when they say yes. You also get all 49 candidates for this role. Free - just confirm your work email.

Executive Summary

The candidate is an intellectually serious early-career systems engineer with genuine Rust depth and curiosity about AI runtimes — qualities that could make them a strong candidate for an inference infrastructure or systems-adjacent ML role in the future. However, for this specific AI Research Engineer position at Pergola Studio, their profile is misaligned: the role requires Python-first applied ML work across LLMs, RAG pipelines, and AI agents, and the candidate demonstrates none of these skills on their resume. Their AI interest appears to be at the runtime/systems layer rather than the applied ML product layer this job demands. They would be better considered for a systems or inference-infrastructure track role, not an applied LLM engineering role.

Top Strengths

  • ✓Rust expertise at a systems level is rare for an entry-level candidate and directly matches a listed 'plus' skill
  • ✓Hands-on experimentation with inference runtimes and grammar-constrained decoding shows genuine AI-adjacent curiosity
  • ✓Real open-source contribution history (traceable PRs) demonstrates ability to work in collaborative, production codebases
  • ✓Memory management, sandboxing, and async runtime experience could be valuable for future inference infrastructure work
  • ✓Self-directed engineering instinct: builds experimental tools (plugmem, vsm-rs) proactively

Key Concerns

  • !No Python experience mentioned — the primary language requirement for this role — and no LLM/RAG/agent stack exposure at all
  • !Profile is almost entirely systems infrastructure; the role requires applied ML engineering with product-facing LLM work, which is a fundamentally different discipline

Culture Fit

55%

Growth Potential

High

Salary Estimate

$40,000 - $55,000 (based on Kazakhstan location, early career, 2 years experience)

Assessment Reasoning

NOT_FIT decision is based on a fundamental skills mismatch with the role's core requirements. The job explicitly requires Python proficiency, hands-on LLM/RAG/agent experience, and ML fundamentals (embeddings, fine-tuning, prompting, evaluation) — the candidate's resume addresses none of these. They are a Rust systems engineer whose AI exposure is limited to experimental inference runtime research. While Rust is listed as a 'plus' skill, it is a secondary signal; the primary discipline here is applied ML engineering in Python, and the candidate does not demonstrate readiness for that work. Their overall score of 42 reflects meeting roughly 1-2 of the 9 required skills (Rust, and loosely systems fundamentals) while being absent on 7 others. This is below the 50% threshold for even a BORDERLINE decision.

Interview Focus Areas

Python proficiency: does they write Python? At what level? Any ML-adjacent Python work not on resume?LLM/RAG exposure: has they worked with any LLM APIs, embedding models, or vector databases in personal capacity?

Experience Overview

2y total · 0.5y relevant

The candidate is a capable early-career Rust systems engineer with genuine depth in low-level infrastructure, but their profile is almost entirely orthogonal to this role's core requirements. The job demands Python proficiency, hands-on LLM/RAG/agent experience, and ML fundamentals — none of which appear on their resume. Their AI-adjacent experimentation (vsm-rs, plugmem) is intriguing but thin and framed as experimental rather than applied.

Matching Skills

RustPython (implied, not explicitly stated)Systems programming fundamentals

Skills to Verify

Python (not mentioned)LLM (no applied LLM work)RAGAI AgentsLangGraphvector databasesprompt engineeringML/LLM fundamentals
Candidate information is anonymized. Personal details are hidden for fair evaluation.