- Company Name
- NEOGOV
- Job Title
- Application Support Engineer
- Job Description
-
<think>
Okay, so the user wants me to normalize a job description into a concise mini-job profile for job matching. Let me read through the requirements again. The output should include the job title, role summary, expectations, key responsibilities, required skills, education, and certifications. They want it in English, translated if needed. Max 500 words, exclude company details, location, benefits, and fluff. Also, the summary should be factual, concise, ATS-friendly, and globally neutral.
First, the job title is "Application Support Engineer". I need to make sure that's the first line of the output.
Now, the original job description has a lot of fluff about the company, like being one of the top 50 fastest growing. I need to ignore that. The "About" section mentions they're a SaaS company serving the public sector, but maybe that's relevant to include in the role summary to give context without company details.
Looking at the "What You Will Do" section. The key responsibilities here include providing application support, leading testing teams, implementing automation frameworks, coordinating cross-team efforts, promoting automation, reviewing processes, creating test plans, ensuring QA testing, leading development of strategies, maintaining test suites, advising managers, collaborating with teams. I need to condense these into bullet points under key responsibilities, using precise language and avoiding fluff.
The "Who You Are" section lists personal qualities: analytical, problem-solving, communication, detail-oriented, proactive, self-driven. These could go into expectations or skills. However, the user wants "Expectations" and "Key Responsibilities" separate. Maybe expectations focus on the traits, while responsibilities are the tasks.
Under "What You Have" there are the required skills: 5+ years in QA/testing (automation/manual), experience with API testing, specific tools (Robot Framework, Postman, JMeter), IDP systems, SSO, message buses, SQL, Elasticsearch, production monitoring, observability tools, leading QA teams, AI testing, prompt engineering, cloud platforms (nice to have), Python, etc. Need to categorize these into required skills and required education/certs.
The nice to have items are proficiency in Python, cloud platforms, coding for debugging. Should I mention these? The user said to exclude fluff but maybe the "Nice to Have" is part of the required skills, but the prompt says "required skills"—so perhaps only the main requirements are included. Wait, the user says "Required Skills, Required Education & Certifications." So maybe the "required" part is only those things stated as mandatory. In the original description, "What You Have" includes the requirements. Let me check the job description's "What You Have" section again.
Original job description under "What You Have" lists:
5+ years QA/testing with automation and manual, hands-on API testing, Robot Framework, Postman, JMeter, experience with IDP, SSO, message bus, SQL, Elasticsearch, production monitoring, observability tools, leading QA teams, AI testing, prompt engineering, testing platform products (identity login, ESB, audit), communication with teams.
The "nice to have" includes Python, cloud platforms, basic coding. Since the user said to exclude fluff, maybe "nice to have" is considered fluff? Wait, the user says to exclude fluff but to include required skills. So the "required" are in the main points, the "Nice to Have" can be omitted unless they are considered required. Since the user wants only Required Skills, we should list only the mandatory ones.
The education part: The original job description doesn't mention specific education or certifications, so under "Required Education & Certifications" we can leave it blank or state that none are specified. Wait, the user says "Provide a concise summary for job matching." Maybe the user expects education and certifications, even if not mentioned. If not present in the job description, perhaps omit it. But the example might have that. Let me check the original instruction again.
The user says to include "Required Education & Certifications". In the job description, there is no mention of education or certifications required. So perhaps we can leave that section blank. However, the user's example might have it. Alternatively, maybe it's required to include even if not present. Wait, the user's example shows placeholders like "none specified" if not given. Let me check the example in the input. Wait, the user hasn't provided an example, but the initial instruction says to output those sections regardless. So if the job description doesn't mention education or certs, we can state "none specified" or similar. But given the user wants to be factual and concise, maybe leave it as empty. However, the user's instruction says "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So all those sections must be included. Therefore, if the job description doesn't mention education or certifications, we should state that none are required or specify it as "Not specified" or "none required".
Looking back at the job description: "Who You Are" includes required traits, "What You Have" includes required skills. The job description does not mention education or certifications, so in the output, Required Education & Certifications can be left blank or stated as "Not required" or "Not specified". However, the user might expect that if there's no mention, it's omitted. But the user's instruction is to output all sections. Since there's no mention, perhaps we can just leave it as a bullet point with nothing. Alternatively, maybe the original job description includes required education in the "What You Have" section. Let me recheck.
Original job description under "What You Have" does not mention any education or certifications. Therefore, in the output, under Required Education & Certifications, it would be empty. However, the user's instructions say to keep it factual and ATS-friendly, which might require stating "Not required" or "Not specified" if not present. But ATS usually looks for specific keywords. However, since the user didn't specify any education or certifications, maybe we can leave it as is, perhaps stating "Not specified". But since the user wants to exclude fluff, maybe omitting it if there's nothing. However, in the output, all the required sections must be present. Let me check the example structure the user might expect. Suppose if education isn't mentioned, perhaps just leave the section with a blank bullet point. However, the user hasn't provided an example, so I'll proceed as per instructions.
Now, the role summary should be a concise paragraph that encapsulates the role. It should include that it's for supporting platform products in production, requiring a hybrid of QA, automation, and production support, with leadership in testing teams and automation.
Expectations should reflect the required traits: analytical, problem-solving, communication, detail-oriented, proactive, self-driven.
Key responsibilities: The main tasks listed in the job description.
Required skills: The mandatory skills from "What You Have" section.
Education & Certifications: None specified.
Now, let's structure it. Make sure the language is concise, avoid fluff, use bullet points as per the example. Since the user didn't provide an example, but the output should be in the specified format.
Wait, the user says "Output only: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications." So these are the six sections.
Let me start drafting.
Job Title: Application Support Engineer
Role Summary: Provides application support for platform products, ensuring stability and performance in production. Combines QA, automation, and production support expertise to lead testing teams and implement automation frameworks. Requires exposure to AI testing and platform ecosystems.
Expectations:
- Analytical, debugging, problem-solving, communication, and collaboration skills.
- Detail-oriented, proactive, self-driven.
- Comfortable in dynamic, fast-paced environments.
Key Responsibilities:
- Provide application support for platform products, ensuring stability/performance.
- Lead testing teams in manual/API test automation, performance testing.
- Implement automation frameworks for issue resolution.
- Coordinate cross-team efforts to resolve application issues.
- Review application support processes, monitor defect status.
- Develop test plans for projects, identify risks.
- Maintain test suites, advise on project quality.
- Collaborate with customer support/engineering teams.
Required Skills:
- 5+ years QA/testing (automation/manual).
- API testing, Robot Framework, Postman, JMeter.
- IDP systems, SSO logins, message bus systems.
- SQL/Elasticsearch for troubleshooting.
- Production monitoring and debugging tools.
- QA team leadership.
- AI testing/prompt engineering concepts.
- Platform product testing (identity login, ESB, audit).
Required Education & Certifications:
- Not specified.
Wait, the user said to exclude location, benefits, etc., but I think education is part of what's asked. The job doesn't mention any education requirements, so "Not specified" is acceptable.
Now, check for conciseness, ATS-friendly language. Use keywords like automation testing, QA, API testing, etc. Avoid fluff. Remove any company specifics mentioned in the original, like mentioning SaaS leader or public sector unless needed. The role summary should mention platform products but keep it brief.
Let me verify each section again. The role summary should be a concise summary. The expectations are the personal traits. Key responsibilities are the main duties. Required skills are the technical requirements. Education/certs as stated.
Yes, this seems to fit. Now, check word count. The total should be under 500 words. Since it's a list, it's probably under. Each section is concise.
Final check: No markdown, only the listed sections. Use clear bullet points or