- Company Name
- Puratos
- Job Title
- Internship : R&D : GCMS data analysis
- Job Description
-
<think>
Alright, let's tackle this query. The user wants me to normalize the job description into a concise mini-job profile for job matching. They specified to exclude company details, location, benefits, and fluff. The output should be in English and include specific sections: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
First, I need to parse the given job description. The title is "Internship : R&D : GCMS data analysis". I should make sure the title is clean and follows the required structure. Next, the role summary should capture the essence of the internship. The original job description mentions evaluating analytical software for GC-MS data under the R&D manager, working on integrating tools into an existing pipeline, and using real-world data from chocolate aroma analysis. I'll condense that into a short summary focusing on the main objectives and tasks.
Looking at the expectations and key responsibilities, the internship tasks include testing and comparing tools, evaluating their accuracy and automation, integration into pipelines, working with large datasets, and developing workflows. I need to list these concisely under the respective sections.
For required skills, the job description lists a Bachelor’s degree in relevant fields, strong stats/data science background, proficiency in R/Python, English fluency, pipeline experience, and handling large datasets. Optional skills include GC-MS familiarity, interest in food science, and analytical chemistry knowledge. I should separate required from optional but the user said "required" so maybe just list the required ones. Wait, the user specified "Required Skills" so include those mandatory, and maybe mention the optional ones under a different section if allowed, but the instructions say to exclude fluff. The output example includes "Plus, but not mandatory" but the user says to exclude fluff. Hmm. Wait, looking back: the user says "exclude company details, location, benefits, or fluff". The optional skills are under "Who are we looking for?" and the user lists "Plus, but not mandatory" as part of the job description. The instruction says to exclude fluff, so maybe those optional items should be excluded. However, the example output in their problem includes the optional ones as "Plus, but not mandatory: ..." but the user here says to exclude fluff. So perhaps the optional skills are considered fluff and should be excluded. Wait, but the user also says "keep it factual and concise, ATS-friendly". ATS systems often prioritize required skills. The example response includes the optional as non-required, but the user instruction says to exclude fluff. Maybe "fluff" here refers to things like company culture statements, not the skills. Since the user says to exclude only the specified items, perhaps the optional skills are acceptable if they are part of the required skills. Wait, but the user says to exclude "fluff", so maybe even optional skills are considered fluff. Let me check the original query again: "Exclude company details, location, benefits, or fluff." The optional skills are under "Who are we looking for?" and in the job description. Since the user says to exclude fluff, but the required skills are mandatory. The user wants all required skills and maybe the optional ones, but the example output includes both. Let me look at the example they provided in their problem. In the sample output, they listed "Required Skills" and then "Plus, but not mandatory: ...". So maybe the user wants both. However, the instruction now says to exclude fluff, so perhaps the optional skills are fluff. But the user's sample response includes them. Maybe in the context, the user wants all necessary skills for ATS matching, so including the optional as non-essential. But the user says to exclude fluff. This is a bit conflicting. Since the example includes them, perhaps the user expects that even optional skills are included under a separate bullet, even if labeled as non-mandatory. But the user's instruction says "exclude fluff", so I need to be cautious. Let me proceed to include required and then mention the optional as "Plus, but not mandatory" as per the example, but only if they are part of the key responsibilities. However, the user also says to make it ATS-friendly, which would prioritize required skills. The optional ones might not be required for the ATS but could be helpful for a more accurate match. Since the user's example includes them, I think it's safe to include them as part of the required skills section with a note that they are additional. So, in the required skills, list the mandatory ones, and then under another section or just mention the optional. However, the user's output structure specifies sections: Required Skills, Required Education & Certifications. The optional skills are not certifications or education, so maybe they go under Required Skills with a note. Alternatively, perhaps the user wants only the mandatory skills. But the example shows both. To resolve this, I'll check the user's exact output example again. In their example, under "Required Skills", they have: "Strong background in statistics and data science. Proficiency in R, Python, or similar programming languages. Proficiency in English (written and spoken). Experience in developing analysis pipelines and handling large datasets. Plus, but not mandatory: ...". So in the example, they included the optional ones after "Plus, but not mandatory". Therefore, despite the "exclude fluff" instruction, the user wants those optional skills included as they are part of the job description's requirements, albeit optional. So I'll follow that structure. So the required skills list the mandatory ones, and then the optional are mentioned as "Plus, but not mandatory".
Now, compiling the sections:
Job Title: Internship - R&D - GCMS Data Analysis (cleaned up the colons to hyphens for consistency)
Role Summary: Supports R&D projects in GC-MS data analysis, evaluating analytical software for integration into analysis pipelines. Focuses on accuracy, automation, and workflow efficiency using real-world data from chocolate aroma analysis.
Expectations: Not specified in the job description, but the project duration is 4-6 months. However, the user wants to exclude practical info, so this section can be omitted. Wait, the user's instruction says "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff." The sections to include are: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. So "Expectations" here might refer to what's expected from the candidate, which in the job description is the "Who are we looking for?" section. But the user says to exclude fluff. However, "Expectations" in the structure is likely about what the job expects in terms of project duration or structure. The job description mentions "4 to 6 months" under practical info, which is to be excluded. So perhaps "Expectations" in this context could be about the internship duration or other expectations from the candidate, but since the user wants to exclude practical info, maybe this section can be omitted or left blank. Wait, the user's example includes "Expectations" as part of the output. Let me check the original instructions again: "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So the "Expectations" is part of the required output. The job description doesn't mention expectations beyond what's in the key tasks. Wait, maybe the "Expectations" section is for the candidate's perspective: what is expected of them. The job description under "What you will do" lists the key responsibilities. But maybe the "Expectations" is more about the project duration or other structural aspects. However, since the user says to exclude practical info, which includes the duration, perhaps the "Expectations" section can be omitted. But the user's example includes an "Expectations" section. Wait, looking at the example given in the problem statement, the user provided a sample output where "Expectations" was included. Let me check the sample input and output. The sample input is in French, and the sample output includes "Expectations", but in the current case, the job description's "practical info" includes the duration. Since the user wants to exclude that, perhaps "Expectations" here relates to the skills and experience required. But in the structure, "Expectations" is a separate section. Alternatively, maybe the user intended for the "Expectations" section to be what is expected from the candidate, but given the instructions, maybe the user wants it to be part of the key responsibilities. However, the user's structure includes both "Expectations" and "Key Responsibilities" as separate sections. This is a bit confusing. Let me re-examine the original instructions. The user says: "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So "Expectations" is a separate section to be included. Perhaps "Expectations" is the candidate's expectations from the job, but the user wants to exclude fluff, so perhaps in this context, it's about what the role expects from the intern. Alternatively, maybe it's about project duration, but since that's in the practical info and should be excluded, perhaps this section is left blank or inferred. However, since the instruction requires the "Expectations" to be present, perhaps it's better to include the project timeframe even if it's mentioned in practical info. Wait, but the user says to exclude practical info, which includes the period of the internship. So maybe the "Expectations" section should
Groot-bijgaarden, Belgium
On site
13-03-2026