Automation Test Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes: About Niyam IT, Inc. (company description) – maybe that's not a required heading but we could put under "About the role"? Actually "About the role" is a heading for description of role. The posting includes a paragraph about the role: "Niyam is seeking an Automation Test Engineer to join our team in support of our work with a federal client. We offer competitive compensation and benefits. This hybrid role will design, implement, and execute comprehensive testing and evaluation protocols that ensure compliance with system requirements. The ideal candidate will have strong experience in automated testing frameworks, Agile methodologies, and Java development, with the ability to collaborate closely with cross-functional teams to deliver high-quality software and hardware solutions. Candidate must be able to work onsite at client location in Ashburn, VA up to 4 days/week." That's role description. Could be under "About the role". Then "Roles And Responsibilities" list. Then "Requirements". Then "Preferred Skills". Then "What We Offer" (benefits). Also "Flexible Work Hours", "Remote Work", "Career Growth", "Great People", "Great Environment", "Diversity & Inclusion". Those are benefits. Also "We offer competitive compensation and benefits." No specific pay or schedule details besides "up to 4 days/week onsite". That's schedule info: "Candidate must be able to work onsite at client location in Ashburn, VA up to 4 days/week." That's schedule. We can include a Schedule section with that detail. Pay: only "competitive compensation and benefits" no specific numbers, so we should NOT create Pay section because it's not specific. Benefits: we have list of benefits (flexible hours, remote work, career growth, great people, great environment, diversity & inclusion). Those are specific enough to create Benefits section. Qualifications: maybe same as Requirements? The posting has Requirements and Preferred Skills. We could treat Requirements as Requirements section, Preferred Skills as Skills section. Or we could combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Qualifications maybe not needed if covered by Requirements. We'll not create Qualifications if no distinct content. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, application deadline, etc. Also remove "Application Deadline: This will be posted for a minimum of 2 business days..." etc. Also remove "Niyam IT, Inc. is an Equal Opportunity..." etc. We need to preserve all substantive information. So we need to include company description? The "About Niyam IT, Inc." is substantive but not necessarily a heading. Could be placed under About the role? Might be better to include a short paragraph about the company under About the role or maybe a separate "About the company" but not in allowed headings. Since only allowed headings list, we could put company description under About the role as part of role description? But the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely we should stick to those headings only. So we can include company description in a paragraph under About the role or maybe as a separate paragraph before headings? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can have a short paragraph about the company before the headings. That's okay. Thus output: maybe a

about Niyam IT, Inc. then

About the role

with paragraph describing role. Then

Responsibilities

with

• ... etc. Then

  Requirements

  with
  • ... etc. Then

    Skills

    with preferred skills list. Then

    Benefits

    with list of benefits. Then

    Schedule

    with paragraph about onsite up to 4 days/week. We must not include Pay section. Check for any other specifics: "We offer competitive compensation and benefits." Already covered in benefits? Not specific. We'll not add pay. Now ensure we preserve all substantive information: company description, role description, responsibilities list, requirements list, preferred skills list, benefits list, schedule detail. Let's extract each. Company description: "About Niyam IT, Inc. (Niyam) Niyam IT was founded in 2007 by a group of consultants who shared a unique vision: a technology company steeped in orderly process yet driven by passion and innovation. Over the following decade, we fine-tuned our craft and built an impressive track record of successful outcomes, securing our reputation as the go-to provider of smart, innovative solutions. Today, Niyam is at the forefront of the industry, leading the way in crafting mission-critical technologies for Emergency Preparedness & Response, Natural Resource Management, Law Enforcement & Justice, Health IT, and Global Citizen Services." We can keep that as a paragraph. What We Offer section: list: - Flexible Work Hours: Life doesn’t always fit into a 9-to-5 schedule. We offer flexibility to help you manage your work-life balance effectively. - Remote Work: Niyam understands the value of flexibility. We offer remote work. - Career Growth: Niyam is not just a job; it’s a career journey. We provide a supportive environment for your professional development and offer fully paid opportunities for training and advancement within the company. - Great People: Our people are the blueprint of who Niyam is to the industry and community. - Great Environment: Niyam fosters a great environment where innovation, collaboration, and personal growth thrive. - Diversity & Inclusion: We believe in the strength of diverse perspectives. Your unique ideas are welcomed and celebrated every day at Niyam. Join us in creating a workplace where innovation, diversity, and well-being thrive. We can turn each into
  • items. Role description paragraph: "Niyam is seeking an Automation Test Engineer to join our team in support of our work with a federal client. We offer competitive compensation and benefits. This hybrid role will design, implement, and execute comprehensive testing and evaluation protocols that ensure compliance with system requirements. The ideal candidate will have strong experience in automated testing frameworks, Agile methodologies, and Java development, with the ability to collaborate closely with cross-functional teams to deliver high-quality software and hardware solutions. Candidate must be able to work onsite at client location in Ashburn, VA up to 4 days/week." We could split schedule detail out later but it's okay to keep in role description; but we also have schedule section. To avoid duplication, maybe we keep schedule detail only in schedule section and remove from role description. However we must preserve all substantive information; we can keep it in schedule section and still mention hybrid role etc. Let's adjust: role description paragraph without schedule detail: "Niyam is seeking an Automation Test Engineer to join our team in support of our work with a federal client. We offer competitive compensation and benefits. This hybrid role will design, implement, and execute comprehensive testing and evaluation protocols that ensure compliance with system requirements. The ideal candidate will have strong experience in automated testing frameworks, Agile methodologies, and Java development, with the ability to collaborate closely with cross-functional teams to deliver high-quality software and hardware solutions." Then schedule section: "Candidate must be able to work onsite at client location in Ashburn, VA up to 4 days/week." Now responsibilities list: from "Roles And Responsibilities": - Design, implement, and execute testing protocols to validate system and application requirements. - Develop, maintain, and enhance automated testing scripts and frameworks for application products. - Conduct regression, smoke, and integration testing for IT applications. - Evaluate test cases, document results, and deliver regular progress updates to stakeholders. - Provide expertise to support user requirements for complex software and hardware applications. - Participate in all phases of risk management assessments and development lifecycles. - Collaborate closely with development teams to identify, isolate, and resolve software defects. - Ensure adherence to Agile and QA methodologies throughout the development cycle. - Perform API testing to validate system integrations, data exchange, and service reliability. - Utilize SQL queries to validate data integrity, perform backend testing, and support defect analysis. Now requirements list: from "Requirements": - US Citizen with ability to successfully complete federal background investigation. - Bachelor’s degree in Computer Science, Engineering, or a related field. - Minimum of 5 years of professional experience in software quality assurance. - Strong understanding of Agile and QA methodologies. - Demonstrated expertise in: - Test Automation Tools (e.g., Selenium, WebDriver). - Java development. - API testing tools and methodologies (e.g., Rest-Assured, Postman, REST, SOAP). - SQL backend testing and data validation. - Source control and concurrent workflows (Git preferred). - Proficiency in creating and maintaining automated test frameworks and scripts. - Experience in regression, smoke, and integration testing. - Excellent analytical, problem-solving, and communication skills. - Ability to work collaboratively in cross-functional teams. - Must be local to Ashburn, VA and available to work onsite up to 4 days/week. Note: The last item about local to Ashburn duplicates schedule; we already have schedule section; but we can keep it in requirements as it's a requirement. However to avoid duplication, maybe we keep it only in schedule section and remove from requirements? But the requirement includes "Must be local to Ashburn, VA and available to work onsite up to 4 days/week." That's a requirement. We could keep it in requirements and also schedule section? That would duplicate. Better to keep it in requirements and not have separate schedule section? But schedule section is allowed if we have specific schedule info. The requirement already includes schedule info; we could still have schedule section but we would be duplicating. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. However we can keep schedule section with that detail and also keep it in requirements? That would be duplication but still preserving info. Might be okay but better to avoid duplication by moving schedule detail to schedule section and remove from requirements. However the requirement also includes "Must be local to Ashburn, VA". That's location requirement, not schedule. So we could keep location requirement in requirements and schedule detail in schedule section. The requirement sentence includes both; we can split: "Must be local to Ashburn, VA." and "Available to work onsite up to 4 days/week." We'll separate. Thus requirements list: - US Citizen with ability to successfully complete federal background investigation. - Bachelor’s degree in Computer Science, Engineering, or a related field. - Minimum of 5 years of professional experience in software quality assurance. - Strong understanding of Agile and QA methodologies. - Demonstrated expertise in: - Test Automation Tools (e.g., Selenium, WebDriver). - Java development. - API testing tools and methodologies (e.g., Rest-Assured, Postman, REST, SOAP). - SQL backend testing and data validation. - Source control and concurrent workflows (Git preferred). - Proficiency in creating and maintaining automated test frameworks and scripts. - Experience in regression, smoke, and integration testing. - Excellent analytical, problem-solving, and communication skills. - Ability to work collaboratively in cross-functional teams. - Must be local to Ashburn, VA. Schedule section: "Candidate must be able to work onsite at client location in Ashburn, VA up to 4