- Company Name
- Doctolib
- Job Title
- Staff AI Data Engineer (x/f/m)
- Job Description
-
<think>
Okay, let's see. The user wants me to normalize a job description into a concise mini-job profile for job matching. The key points are to exclude company details, location, benefits, and fluff. I need to follow the structure: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. Keep it factual and ATS-friendly.
First, the job title is given as "Staff AI Data Engineer (x/f/m)". The parenthetical might be gender-neutral, but since the user asks for globally neutral language, I should omit that. So the job title becomes "Staff AI Data Engineer".
Next, the role summary. The original description talks about building data pipelines for AI systems, ensuring compliance with GDPR, working in agile teams, and collaborating with various teams. I need to condense that into a concise summary. Focus on the core mission: building robust data pipelines for AI systems, compliance, and collaboration.
Expectations would cover the experience and collaboration skills. The job requires at least 7 years of experience as Senior or Staff Data Engineer in AI/ML, proficiency in specific tools, etc. So expectations should be about the required experience and collaboration.
Key responsibilities are listed in the job description. They include designing data capture systems, building pipelines with Python, Dagster, BigQuery, developing monitoring solutions, etc. I need to list these in bullet points without fluff. Make sure to use the key technologies mentioned like Kafka, Dagster, GCP.
Required skills are Python, SQL, DBT, hands-on experience with AI/ML pipelines, understanding of ML lifecycle, GCP experience. Also, desirable skills are Vertex AI, MLflow, monitoring tools, annotation platforms, GDPR knowledge. But since the user said to exclude fluff, maybe stick to the required ones and mention the extras in a list if necessary. Wait, but the user said "Required Skills" so maybe just list the required ones there, and the "Now it would be fantastic if you" part as Optional Skills or not? The user didn't mention optional, so maybe just required skills. However, the user mentioned "required skills" and "required education & certifications". The original says "now it would be fantastic if..." which are optional. But the user wants to exclude fluff. So maybe only list required skills. But the user provided an example where in the required skills they included both required and optional, separated by "Now it would be fantastic if you". Hmm, but the user's instructions say to exclude fluff. Wait, the user wrote: "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff."
So "Now it would be fantastic if you" part: are those required or optional? The job says "if you have" but they are preferred. Since the user wants to exclude fluff, but the example might include both required and optional. Let me check the example given in the problem. The example output includes Required Skills and then under Required Education & Certifications. So maybe the required skills are only the ones listed under "You must have..." and the optional ones are in another section. Wait, the user's example includes Required Skills and Required Education & Certifications. The problem mentions including "Required Skills, Required Education & Certifications". So perhaps in the Required Skills, list the mandatory ones, and if there are optional, maybe not. But the instructions say to exclude fluff, which could mean optional skills might be considered fluff. However, the user wants to keep it factual and ATS-friendly. Many ATS systems look for keywords, so both required and optional might be important. But the user's instruction says "exclude fluff". The "Now it would be fantastic if you..." are optional. So maybe in Required Skills, only the mandatory ones. However, the user's sample includes them in Required Skills but as bullet points. Wait, the user's example includes Required Skills and Required Education & Certifications. The sample output for Required Skills lists all required and the optional as subpoints. Wait, looking back at the user's message, they provided a sample where Required Skills includes both, but then under another section for Optional. Wait, maybe the user expects to list all the skills in Required Skills, even if they are optional. Let me recheck the user's instruction. They said "Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. Keep it factual, concise, ATS-friendly, and globally neutral."
So, the "Required Skills" should include all the skills that are required or desired? The problem states "Provide a concise summary for job matching." So perhaps including both required and optional as part of Required Skills, but differentiating with bullet points or not. However, the user's example output (hypothetical) might have both. Since the user's instruction says to "exclude fluff," perhaps the "fluff" refers to benefits, company details, etc., not the skill requirements. So the required and optional skills are necessary for job matching. Therefore, include them all under Required Skills, perhaps with a note indicating required vs preferred. But the user specified "Required Skills". Hmm. Let me check the structure again.
In the job description, under "Who You Are", there are two parts: the first lists required experience and skills, then "Now it would be fantastic if you..." which are preferred. Since the user's instruction says to exclude fluff, but these are skills relevant for matching, perhaps I should include all under Required Skills, but indicate which are required vs optional. However, the user's output structure only has Required Skills, not optional. So perhaps the answer is to list all required skills in a bullet list under Required Skills, including both the mandatory and the "fantastic if you" ones. Wait, but the user's instruction says "Exclude fluff". The "fantastic if you" are optional, but they are not fluff. They are desired skills. For job matching, it's important to include these because they might be keywords. So maybe include them all as bullet points under Required Skills, even if they are optional. The user says "Keep it factual, concise, ATS-friendly". ATS-friendly means using keywords. If the job requires them, even as optional, including them can help. So perhaps list all skills in Required Skills, even if some are preferred.
Now, the Required Skills section in the job description includes:
- Proficient in Python, SQL, DBT
- Hands-on experience building data pipelines for AI/ML systems in production
- Understanding of ML model lifecycle
- Experience with GCP stack
- Strong collaboration skills
Then, under the "fantastic if you" part:
- Experience with Vertex AI, MLflow
- AI model monitoring and observability tools
- Annotation platforms and labeling workflows
- Cursor / Claude
- GDPR regulations
But GDPR is mentioned in the responsibilities (privacy compliance) as required, so maybe GDPR is a required skill. Wait, in the "Who You Are" section, GDPR is listed under the "fantastic if you" part, but the responsibilities mention ensuring GDPR adherence. Hmm. The job says "You have a first experience with Google Cloud Platform (GCP) stack" as required, but GDPR is listed under the optional. However, the job's responsibilities require GDPR compliance. This might be conflicting. Wait, in the responsibilities: "Design and implement data capture and ingestion systems ensuring data quality, privacy compliance (anonymization, consent, retention), and GDPR adherence". So GDPR is a required aspect of the role, but the candidate is not required to have prior GDPR experience. Wait, the job says under "Who You Are": "You are proficient in Python, SQL, and DBT for building data pipelines. You have hands-on experience building data pipelines for AI/ML systems in production. You have a good understanding of ML model lifecycle (training, evaluation, deployment, monitoring). You have a first experience with Google Cloud Platform (GCP) stack." Then the "fantastic if you" includes "Are familiar with GDPR regulations". So GDPR is not a required skill but preferred. But the responsibility mentions GDPR. So maybe the candidate is expected to comply with GDPR but not necessarily have prior experience. However, the user's instruction says to keep it factual. So perhaps include GDPR in the required skills if it's mentioned in the responsibilities. But since the hiring company doesn't require prior GDPR experience (only familiarity is nice-to-have), maybe it's not a required skill. This is a bit ambiguous. To resolve, perhaps include GDPR under required skills if it's part of the job functions, as per the responsibilities. Since GDPR adherence is part of the data pipeline responsibilities, the skill of ensuring GDPR compliance might be a required skill. But the candidate might not need prior experience, just the ability to comply. So maybe list GDPR as a required skill: "Ensure GDPR compliance in data pipelines".
Now, structuring all this into Required Skills. The job requires Python, SQL, DBT, hands-on experience with AI/ML data pipelines, GCP, collaboration skills. The optional ones are Vertex AI, MLflow, model monitoring tools, annotation platforms, Cursor/Claude, GDPR familiarity.
For the job matching profile, since ATS looks for keywords, it's better to include all relevant skills, even if optional, under Required Skills. But the user's structure specifies "Required Skills" and "Required Education & Certifications". So perhaps the "Required Skills" should include both required and preferred, but mark them as such. But the user's instructions don't allow adding extra structure. Alternatively, list all as Required Skills with some indicating mandatory or preferred. However, the user wants it concise. So maybe list the mandatory ones under Required Skills and the optional ones under the same section with a note. Let me check the example given