Founding AI Engineer (Agentic AI)
5y relevant experience
Executive Summary
The candidate is a Poland-based senior engineer with approximately 8 years of experience, the last 3–4 years of which are deeply focused on AI/ML engineering. Their resume is a strong technical match for this role, citing every major framework and pattern the position requires with credible context and quantified results. The primary uncertainty is verifiability: no GitHub, no code sample, no LinkedIn data, and no cover letter create a validation gap that is unusual for someone claiming this level of technical depth. This does not make them a poor candidate — many excellent engineers maintain minimal public profiles — but it means the hiring decision cannot be made confidently on the resume alone. A rigorous two-stage technical assessment (take-home + live technical interview) is strongly recommended before advancing to offer stage. If they validates technically, they would be a strong fit for this founding role.
Top Strengths
- ✓Exact-match technical stack covering nearly every required tool and framework from the job description
- ✓Demonstrated production AI engineering experience with quantified business impact across multiple employers
- ✓Full-stack ownership mindset spanning architecture, deployment, MLOps, monitoring, and team mentorship
- ✓8 years of progressive software engineering experience with a clear and credible specialization into AI/ML over the last 3-4 years
- ✓Startup and enterprise exposure — Roshen experience shows 0-to-1 prototyping ability while HackerEarth shows scaling and team leadership
Key Concerns
- !Near-total absence of verifiable public presence (no GitHub, no LinkedIn data, no code sample) makes independent technical validation difficult and increases resume embellishment risk
- !The resume's exceptional alignment with this specific job description warrants scrutiny — a technical interview should probe deeply into the specifics of each claimed project and metric
Culture Fit
Growth Potential
High
Salary Estimate
$70,000–$100,000 USD (Poland-based, B2B contract likely; may align to lower end of the $80–120k band depending on contract structure and timezone overlap expectations)
Assessment Reasoning
The candidate is scored as FIT at 82 points based on their resume's near-complete alignment with the required technical stack, demonstrated production AI engineering experience, and progressive career trajectory that mirrors the seniority and ownership this founding role demands. They meets or exceeds the minimum requirements and most preferred qualifications. However, confidence is capped at 72% due to a meaningful verification gap: no code sample, no GitHub, no Apollo-confirmed LinkedIn, and no cover letter. The FIT designation is conditional — it advances them to interview, where technical depth must be validated before a final hiring decision. If technical interview performance is strong, this candidate has high potential to succeed in the role.
Interview Focus Areas
Code Review
No code example or GitHub profile was provided, which is a meaningful gap for a Founding AI Engineer role. The score reflects a neutral-to-negative default due to missing evidence rather than evidence of poor quality. A take-home or live coding assessment should be considered mandatory before proceeding.
- +Cannot assess directly, but resume descriptions suggest familiarity with production-grade patterns such as containerized inference, evaluation pipelines, and MLOps tooling
- +Claims mentoring junior engineers on LangGraph and RAG patterns, implying ability to articulate and teach code-level decisions
- -No code sample was provided, making direct assessment impossible — this is a significant gap for a founding engineering role where coding ability is critical
- -No GitHub profile submitted, so no open-source work or personal projects available to review as proxy evidence
Experience Overview
8y total · 5y relevantThe candidate presents a highly curated resume that aligns almost perfectly with the job requirements, citing the exact tools, frameworks, and architectural patterns the role demands. The quantified achievements suggest solid engineering discipline and product impact. However, the absence of a GitHub profile, code sample, or verifiable LinkedIn presence means the technical depth must be rigorously validated through a structured technical interview.
Matching Skills
Skills to Verify
