- Company Name
- Elevance Health
- Job Title
- Full Stack Engineer III
- Job Description
-
<think>
Okay, so the user wants me to normalize a job description into a concise job profile for matching. Let me first read through the job description they provided.
The job title is Full Stack Engineer III. The original job description has a lot of details about location, company info, benefits, hybrid work policy, and more. The user wants me to exclude all company details, location, benefits, and fluff. Just the facts: Job title, role summary, expectations, key responsibilities, required skills, required education and certs. And keep itATS-friendly, so using standard keywords.
First, I need to extract the relevant parts. Let me look at each section.
The role summary should summarize the position's purpose. The job description says the Engineer III is responsible for delivery of end-to-end system development and maintenance on complex systems. That's the summary.
Expectations: How they make an impact includes working on complex platforms, stakeholder relationships, analyzing change requests, knowing industry trends, collaborating with teams, defining application scope, analyzing requirements, understanding product analytics, problem identification, coding, mentoring, test case reviews, system testing, integration with other IT departments, on-call support.
Key responsibilities can be distilled from the expectations. The responsibilities should list the main duties without specifics like company policies. The user wants this concise, so maybe combine some points. For example, the development of system components, stakeholder collaboration, system testing, etc.
Required skills from the job description: Strong front end experience, JavaScript/TypeScript, React, Vite, Material UI, responsive/accessibility, client-side routing, form handling, REST APIs, authentication, testing tools. Also, coding and system maintenance, code reviews, mentoring.
Education: BA/BS in IT, CS, or related, 3 years exp on multi-platform systems.
I need to structure this without company info, location, hybrid policy, benefits, etc. Also, ATS-friendly. So using standard terms like "Full Stack Engineer III", listing skills as bullet points, maybe using technical keywords.
Check for max 500 words. The example output they provided is a good template. Make sure to avoid any fluff. Also, translate if needed, but the input is in English, so probably not needed.
Make sure the role summary is a concise sentence or two. Expectations can be bullet points. The rest as per the sections.
Wait, the user said "Exclude company details, location, benefits, or fluff." So the part about the hybrid work policy at the start and the company name, etc., are all to be excluded. Also, the preferred skills section has some specific tech stacks that need to be included as required skills in the new profile.
Check that the required skills include both what's listed under Minimum Requirements and Preferred Skills. Wait, the "Minimum Requirements" in the original have some technical requirements, but the "Preferred Skills" are more specific. However, the user says "Required Skills" and "Required Education & Certifications". The original lists "Requires an BA/BS..." as the Minimum, so that's the required education.
But the Preferred Skills section might have other skills that the company is looking for, but the user says to exclude "fluff". Since the Preferred Skills are listed as "preferred", but in the normalized profile, the user might want to include all skills that are required or preferred? Wait, the user instructions say "Required Skills" and "Required Education & Certifications". So probably only include what's in the "Minimum Requirements" as required, but perhaps some preferred skills are also required. Wait, the original says "Preferred Skills, Capabilities, And Experiences".
But in the job description, under the Minimum Requirements, it's "Requires an BA/BS..." followed by the preferred skills. However, in the normalized profile, we need to split into Required Skills and Required Education. Hmm. It's possible that the "Preferred Skills" are actually not required but preferred, but maybe some of them are part of the required skills. But the user's instruction is to list Required Skills and Required Education. The job description might present some of the skills as required and others as preferred. But in the given job description, the "Minimum Requirements" are the education and experience, and the "Preferred" are listed in a separate section. Therefore, the Required Skills should probably include the technical skills listed under the Minimum Requirements (like "3 years experience on one platform, multi database, multi language or multi business application") but maybe also include the preferred skills if they are mentioned as required elsewhere.
Wait, looking back, the "Minimum Requirements" say "Requires an BA/BS... and a minimum of 3 years experience..." but the preferred skills are a separate section. So perhaps the required skills are the 3 years experience in certain areas, and the preferred skills are optional. However, in the new profile, the Required Skills would be the ones that are absolutely necessary. But the job description includes under the expectations some of the preferred skills as part of the responsibilities. For example, "Strong front end experience", "JavaScript and TypeScript", etc. So maybe those should be included as required skills because they are part of the key responsibilities.
This is a bit ambiguous. The user wants the Required Skills to be factual, so I need to check if those preferred skills are actually required. In the job description, under the "How You Will Make An Impact" section, it mentions working on medium to large complex customer technology platforms, collaborating with designers, coding, code reviews, etc. Then under the "Preferred Skills" section, it lists specific technologies like React, TypeScript, etc. However, since those are under "Preferred", perhaps they're not strictly required but are desired. However, in the normalized profile, the instruction is to provide Required Skills. So I need to decide whether to include these as required or preferred. But since they are listed in the Preferred section, but in the role's responsibilities, they are mentioned.
But the user says to exclude fluff, so perhaps the Required Skills would include both the minimum requirements and any skills that are essential for the job. For example, if the job requires front-end development, then those skills would be required. The user might have a mix of required and preferred, but since the user is asking for a job profile for matching, the system will probably need the skills that are actually required. Since the preferred section includes specific tech stacks, but the job is a Full Stack Engineer III, which likely requires those skills. However, the original job description's Minimum Requirements do not specify the specific tech skills, only the platform, multi-database, etc.
This is a bit tricky. But since those preferred skills are important for the role, even if preferred, maybe they should be included as required skills for accurate job matching. Otherwise, if left out, the matching might not pick up on the necessary technologies. The user instruction says "factual, concise, ATS-friendly", so perhaps include the specific tech skills as required even if they are in the preferred section, because they are part of the job's requirements for candidates applying.
Therefore, in the Required Skills section, include all the specific technologies listed in both Minimum and Preferred, as those are the key skills needed for the role. However, the user's instruction may not want to include optional skills. But given that those preferred skills are part of the actual job responsibilities (like working with React, etc.), it's better to include them as required.
Therefore, the final Required Skills would include all the technical skills listed in the job description under Minimum and Preferred sections.
The Required Education is the BA/BS in IT, CS, etc., plus 3 years experience on specific platforms.
Now, structuring all that into the required format. Let's start drafting:
Job Title: Full Stack Engineer III
Role Summary: Deliver end-to-end system development and maintenance on complex technology systems.
Expectations:
- Develop and maintain complex customer technology platforms.
- Collaborate with stakeholders to define business requirements.
- Analyze and document system enhancements.
- Collaborate with engineers and designers to develop solutions.
- Create technical specifications.
- Evaluate business/technical requirements.
- Identify and mitigate system issues.
- Code and maintain complex system components.
- Mentor on coding standards and perform reviews.
- Test systems, fix defects, validate tests.
- Integrate with IT departments for project success.
- Provide on-call support and monitor systems.
Key Responsibilities: [Similar to the expectations but maybe more structured]
Wait, the user says to have separate sections for Expactations and Key Responsibilities. Need to clarify. The example the user provided in the instructions shows:
Expactations (probably a typo for "Expectations") and Key Responsibilities. So maybe "Expectations" is a section for what they expect from the candidate, but the Key Responsibilities is the job duties. However, in the example given, perhaps the user intended "Expectations" as the requirements for the role, and Key Responsibilities as the duties.
Looking back at the original job description: "How You Will Make An Impact" lists the responsibilities. So in the normalized profile, the Key Responsibilities would include those actions, while the Expectations could be the required skills and experience.
But the user instruction says: "Expactations" (probably a typo) and then Key Responsibilities. Maybe they meant "Expectations" as in what the role requires from the candidate (skills, education), and Key Responsibilities as the actual duties. However, in the input example given by the user, the user's own sample shows:
Role Summary
Expactations
Key Responsibilities
Required Skills
Required Education & Certifications
Assuming that "Expactations" is a typo for "Expectations", perhaps it's supposed to be part of the role summary. Alternatively, maybe the user meant "Expectations" as the candidate's expectations but that's not likely. Given the ambiguity, but following the structure of the original job description, perhaps "Expectations" could be the minimum requirements, and Key Responsibilities are