AI Workflow Automation Engineer
4y relevant experience
EU engineers, ready to place with your US clients
Pre-screened on AI. Remote B2B contracts. View 5 full profiles free — AI score, skills report, interview questions included.
Executive Summary
On paper, the resume of Marcin Pham presents a strong alignment with the AI Workflow Automation Engineer role, featuring directly relevant experience in RAG systems, LLM deployment, agentic frameworks, and cloud-native ML infrastructure. However, the application is fundamentally compromised by a critical red flag: the LinkedIn profile provided belongs to a completely different individual (a frontend developer in Spain), creating an unresolvable trust issue without direct outreach to clarify. Additionally, the absence of any public code or portfolio prevents independent validation of the senior-level technical claims. Even if the identity issue is resolved and the resume is genuine, the candidate's background skews more toward pure ML/data science than product-grade API engineering and workflow automation for a SaaS platform. Salary expectations based on the claimed experience level would also likely exceed the posted range. A NOT_FIT decision is recommended unless the identity discrepancy can be immediately and satisfactorily resolved.
Top Strengths
- ✓RAG system design and deployment (FAISS, LanceDB, Qdrant) with measurable precision improvements
- ✓Agentic AI workflow engineering using LangChain, LangGraph, and LangSmith
- ✓Production LLM deployment experience including fine-tuning (LoRA on LLaMA 2/Mistral)
- ✓Cloud-native ML infrastructure (Docker, Kubernetes, AWS SageMaker, Azure OpenAI)
- ✓Cross-industry ML breadth spanning healthcare, retail, supply chain, and enterprise AI
Key Concerns
- !Critical identity discrepancy: LinkedIn profile does not match the resume, making the entire application unverifiable and raising fraud concerns
- !No public code, GitHub, or portfolio to substantiate senior-level technical claims across 15 years of experience
Culture Fit
Growth Potential
Moderate
Salary Estimate
$95k-$130k (based on claimed 10+ years ML experience, though mid-range role budget is $65k-$95k — likely misaligned)
Assessment Reasoning
The NOT_FIT decision is driven primarily by a critical application integrity issue: the LinkedIn profile submitted belongs to 'Marc G', a Senior Frontend Developer in Catalonia, Spain, with no connection to the ML field — while the resume belongs to 'Marcin Pham', a Senior ML Engineer in Warsaw, Poland. These are clearly two different individuals. This mismatch either reflects a deliberate attempt to submit a fraudulent application or a severe administrative error, either of which disqualifies the candidate at this stage without further verification. Secondarily, even evaluating the resume in isolation, the candidate skews toward ML research and data science rather than product-grade workflow automation engineering; lacks demonstrated experience with FastAPI/Django API design and workflow orchestration tools (Temporal/Airflow) that are explicitly required; provides no public code to validate claims; and with 10+ years of experience would likely expect compensation above the posted $65k-$95k range. The resume-only technical score would be borderline (~55), but the identity/integrity concern drops the overall score to NOT_FIT territory.
Interview Focus Areas
Experience Overview
15y total · 4y relevantThe submitted resume shows a technically strong ML/AI profile with directly relevant LLM and RAG experience, particularly from the Novartis and Viridien roles. However, there is a critical mismatch between the LinkedIn profile provided (a frontend engineer in Spain named Marc G) and the resume submitted (a Warsaw-based ML engineer named Marcin Pham), raising serious concerns about application integrity. The technical content of the resume alone would be borderline for this role but cannot be evaluated without resolving the identity discrepancy.
Matching Skills
Skills to Verify