- Company Name
- EvenUp
- Job Title
- Senior Machine Learning Engineer - Systems
- Job Description
-
<think>
Okay, let's start by looking at the user's query. They want 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. They also want it in English, translated if needed, and to keep it ATS-friendly and globally neutral.
First, I need to parse the job title. It's "Senior Machine Learning Engineer - Systems". The user wants the job title as is, so I'll keep that.
Looking at the job description, the core responsibilities are about designing ML systems for RAG, vector search, optimizing data pipelines, developing frameworks, collaborating with teams, researching techniques, implementing evaluations, ensuring scalability, integrating with production environments, and documenting best practices. These should be condensed under Role Summary and Key Responsibilities.
The Required Skills mention experience with vector databases, retrieval frameworks, software engineering skills, transformer models, and evaluation methodologies. These need to be listed clearly under Skills and possibly split into Required Skills and Optional Skills if needed. The user specified to exclude fluff, so optional skills might go under Required Skills if they're listed as required, or maybe just combine them. Wait, the original has "Required Skills" and "Optional Skills", but the user says to exclude fluff, but also they want Required Skills and Required Education. The original has Optional Skills as some items, but since the user says to exclude fluff, maybe we can include them under Required Skills if they are necessary. Let me check the instructions again. The user says "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff." The Optional Skills section in the job description: should those be considered? The user says to include "Required Skills", so maybe the Optional ones aren't required unless specified. Wait, the user's output structure includes "Required Skills" so maybe include the ones listed under "Required Skills" and maybe the "Optional Skills" as additional if needed. But the user wants it ATS-friendly, so it's better to be factual and not include optional unless they're essential. However, the original job listing under Core Responsibilities and then Optional Skills. Wait, the job description says "Optional Skills", so those are not required, so we can exclude them. But maybe some of them are actually required? Let me read the job description again. The Core Responsibilities are under the Core Responsibilities section, and then there's an Optional Skills section. The user instruction is to exclude fluff. The Optional Skills are listed as "Optional Skills" which likely means they are not required but preferred. Since the user says to include "Required Skills", maybe we should only include the required ones. However, the job might actually require those optional skills, but the way it's presented in the job description is as optional. So perhaps we need to list the required ones and maybe mention the others as preferred if needed. But the user's instruction is to keep it factual and ATS-friendly, so maybe just list what's required. Hmm, need to be careful.
The Required Education section: the user wants to include that. The job description doesn't mention education or certifications, so maybe it's left blank if not provided. But the user says to include "Required Education & Certifications". Wait, the original job description under "Notice to Candidates" doesn't mention education. However, the user wants to include "Required Education & Certifications". Since there's no information in the provided job description about education or certifications, perhaps that section is left blank. Wait, let me check again. The job description under "Core Responsibilities" and "Optional Skills" doesn't mention education or certifications. The "Education & Certifications" part is missing. The user might expect to include something there, but if it's not provided, perhaps we just leave it as "N/A" or omit? But the user's output structure requires it, so maybe we include "Not specified" or leave it blank. The user says "Exclude company details, location, benefits, or fluff." So if the job description doesn't mention education or certifications, we can't make up anything. Therefore, the Required Education & Certifications would be empty or not included. However, the user's example output includes it, so maybe we need to include it but state "Not Applicable" or similar. Wait, maybe the user example will show, but given the user's instructions, even if it's not present, include a line. Let me check the initial example. The user provided an example output with "Education & Certifications: Not specified" but maybe that's a placeholder. Since the job description doesn't mention education or certifications beyond the skills, perhaps we can't infer any. So for Required Education & Certifications, it's best to leave it as "Not specified" or just omit it, but the user says to output only the specified sections. The user says "Include all sections: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications."
Wait, the original job description doesn't have a section called "Role Summary". The user wants a Role Summary. So I need to create a concise summary that encapsulates the main aspects of the role. The job title is Senior Machine Learning Engineer - Systems. The role involves developing ML systems, data pipelines, collaboration with teams, research, etc. So the Role Summary should be a brief overview.
The user also wants "Expectations", which might be the core responsibilities. Wait, the user's output includes "Expactations" which is a typo for "Expectations". Let me confirm. Yes, in the user's instruction, it's written as "Expactations" with a typo. That must be intentional, so I'll follow that. So "Expactations" is a typo but part of the structure.
So to structure:
Job Title: Senior Machine Learning Engineer - Systems
Role Summary: Develop and deploy ML models for legal claims platform. Collaborate with teams to integrate data into workflows.
Expactations (Expectations): Maybe this refers to the key responsibilities, but I need to structure according to the user's requested sections. Wait, the user's output structure is:
Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications.
Looking back at the user's instruction, they might have intended "Expectations" as a section, but the typo is "Expactations". The user says "Expactations", so I have to follow that. The "Expactations" section might be where they list what the job seeker is expected to do, which is similar to Key Responsibilities. Alternatively, maybe "Expactations" is the core expectations of the role, while Key Responsibilities are the actual tasks. Let me parse the original job description again.
In the job description, "Core Responsibilities" are listed. The user wants to map these to "Expactations" and "Key Responsibilities". The user's example output probably groups these into the appropriate sections. Let me think. The user's structure includes "Expactations" and "Key Responsibilities". Since the user mentioned "Expectations", perhaps "Expactations" is meant to be the core expectations or main points, while "Key Responsibilities" are the detailed tasks. However, the user's structure may have a typo and actually mean "Expectations" as the section title. Since the user says to output "Expactations" exactly as written, I have to go with that.
Now, structuring each section:
Role Summary: A concise overview of the role. The job is for a Senior ML Engineer focusing on systems, working on AI for legal claims platform. They develop models, optimize pipelines, collaborate with teams, etc.
Expactations: This would likely be the key responsibilities. But since the user included "Expactations" and "Key Responsibilities" as separate sections, I need to make sure how to split them. Let's check the original job description's Core Responsibilities. The core responsibilities include designing ML systems, building data pipelines, developing frameworks, collaborating with teams, researching techniques, implementing evaluations, ensuring scalability, working with platform engineers, documenting best practices.
These are all under Core Responsibilities. The user wants "Expactations" and "Key Responsibilities". Maybe "Expactations" is the list of what the job entails, while "Key Responsibilities" is another list. But the user might be using these terms differently. Alternatively, maybe "Expactations" is a typo and should be "Expectations", which could mean the expectations from the candidate. Wait, the user's structure is:
Role Summary, Expactations, Key Responsibilities.
But "Expactations" is misspelled. Let me check the user's instruction again:
They wrote: "Provide a concise summary for job matching. Max 50,000. Exclude... Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications."
So it's definitely "Expactations". That must be a typo. Maybe they meant "Expectations" but it's a typo for "Expectations". Alternatively, maybe the user intended it to be "Expectations", but wrote "Expactations" by mistake. Since I need to follow the user's exact instructions, even if there's a typo, I'll write "Expactations" as the section title.
So for the sections:
Role Summary: Concoct a brief summary of the role, what the person does.
Expactations: Maybe this refers to the key expectations from the role, i.e., what the job expects from the candidate. But in the job description, the Core Responsibilities are the key tasks. Since the user has both "Expactations" and "Key Responsibilities", perhaps "Expactations" is a typo for "Expectations" which would be the key tasks, and "Key Responsibilities" is another list. But given that the user