Automation Engineer with Security Clearance
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists,
for prose
3. Do NOT repeat job title as heading (page already shows it)
4. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
8. Never create Pay/Schedule/Benefits sections unless posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- Company description: "About Niyam IT (Niyam)" - this is company background
- "What We Offer:" - benefits/perks list
- Role description: "Niyam is seeking a highly motivated, hands-on Automation Engineer..." - this is about the role
- "Roles and Responsibilities:" - list of duties
- "Requirements:" - list of requirements
- "Preferred Skills:" - list of preferred skills
- "Why Join Niyam" - more benefits/culture info
- Application Deadline and EEO statement - boilerplate to remove
Sections I should create:
1. About the role (or similar) - for the role description paragraph
2. Responsibilities - for the roles and responsibilities list
3. Requirements - for the requirements list
4. Preferred Skills - for preferred skills list
5. Benefits - for "What We Offer" and "Why Join Niyam" (these are benefits/perks)
The posting mentions "competitive compensation and benefits" but no specific pay details, so no Pay section.
Schedule: mentions "onsite at client location in Ashburn, VA up to 4 days/week" - this is a schedule detail, but it's also in requirements. Could include in a Schedule section or fold into requirements. The rules say only create Schedule section if posting actually states them. It does state onsite requirement. But it's also a requirement. I'll include it in Requirements list and maybe mention in About the role.
The "What We Offer" and "Why Join Niyam" are benefits. I'll combine into a Benefits section.
The company background "About Niyam IT" could be an "About the Company" section, but the rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" isn't listed. But "About the role" is. The company description is not about the role. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But they say "Prefer a few substantive sections over many thin ones." I think I should include company background as it's substantive. But the heading "About the Company" isn't in the list. Could use "About the Role" for the role description paragraph, and maybe "Company Overview" for the company description. However, the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Automation Engineer". The company description is separate.
I'll include:
- About the Role (for the paragraph describing the role)
- Responsibilities
- Requirements
- Preferred Skills
- Benefits (combining What We Offer and Why Join Niyam)
I'll omit the company background "About Niyam IT" as it's more marketing, but it's substantive. The rules say "Preserve ALL substantive information". The company background is substantive. But the allowed headings don't include "About the Company". I could fold it into a paragraph before sections? But the output should be HTML fragment with sections. The rules say "include a section ONLY when the posting has real, specific content for it". The company background is real content. I'll create a section "Company Overview" using h3. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use "Company Overview".
But the user might expect only those headings. However, the example says "e.g." meaning for example. I think it's okay.
Let me structure:
Company Overview
...company description...
About the Role
...role description paragraph...
Responsibilities
- ...
Requirements
- ...
Preferred Skills
- ...
Benefits
- ...
Note: The "What We Offer" list includes: Flexible Work Hours, Remote Work, Career Growth, Great People, Great Environment, Diversity & Inclusion. The "Why Join Niyam" includes: Award-Winning Culture, Meaningful Mission Impact, Drive Innovation, Accelerate Your Career, Collaborative, People-First Environment. I'll combine into one Benefits list.
Also, the requirement "Must be available to work onsite in Ashburn, VA up to 4 days/week" is a schedule requirement. I'll keep in Requirements.
The posting says "Candidate must be able to work onsite at client location in Ashburn, VA up to 4 days/week." That's in the role description paragraph. I'll keep it there and also in requirements.
Now, I need to remove boilerplate: "Application Deadline: ...", "Niyam IT, Inc. is an Equal Opportunity ("EEO") Employer. All qualified applicants will receive consideration without regard to ..." - remove.
Also remove "Join us in creating a workplace where innovation, diversity, and well-being thrive. Your journey at Niyam awaits. Apply today!" - that's application instruction/marketing.
Now, write HTML.
Let me extract content precisely.
Company Overview paragraph: "Niyam 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. For nearly two decades, we have served the U.S. Federal government delivering mission-critical IT solutions across Emergency Preparedness and Response, Civilian Agency Services, and Law Enforcement and Public Safety. Niyam is CMMI DEV Level 3 accredited and ISO certified (ISO 9001:2015, ISO/IEC 20000-1, ISO/IEC 27001), and holds an active CMMC Level 2 certification. We are proud to be recognized as a Best Places to Work by The Washington Post (2025) and USA Today (2026)."
About the Role: "Niyam is seeking a highly motivated, hands-on Automation Engineer to join our team in support of our work with a federal client. We offer competitive compensation and benefits. The ideal candidate will be responsible for developing and maintaining automated testing solutions that help ensure the quality, reliability, and performance of our applications. This role offers an excellent opportunity for both early-career and experienced professionals who are eager to learn, contribute, and grow in a collaborative environment. Candidate must be able to work onsite at client location in Ashburn, VA up to 4 days/week."
Responsibilities list (8 items):
1. Design, implement, and execute testing protocols to validate system and application requirements.
2. Develop, maintain, and enhance automated testing scripts and frameworks for application products.
3. Conduct regression, smoke, and integration testing for IT applications.
4. Evaluate test cases, document results, and deliver regular progress updates to stakeholders.
5. Provide expertise to support user requirements for complex software and hardware applications.
6. Participate in all phases of risk management assessments and development lifecycles.
7. Collaborate closely with development teams to identify, isolate, and resolve software defects.
8. Ensure adherence to Agile and QA methodologies throughout the development cycle.
9. Perform API testing to validate system integrations, data exchange, and service reliability.
10. Utilize SQL queries to validate data integrity, perform backend testing, and support defect analysis.
Wait, there are 10 bullet points? Let's count: The text shows bullet points but in the raw text it's lines. I'll treat each line as a list item.
Requirements list (15 items):
1. US Citizen with ability to successfully complete federal background investigation.
2. Bachelor's degree in Computer Science, Engineering, or a related technical field.
3. Must be available to work onsite in Ashburn, VA up to 4 days/week.
4. Minimum of 5 years of professional experience designing, developing, and maintaining Java-based automation solutions.
5. Minimum of 3 years of professional software development experience with expertise in Java, JavaScript, object-oriented and functional programming (OOP/FP) principles, and shell scripting.
6. Minimum of 2 years of hands-on experience designing and maintaining Selenium-based testing frameworks.
7. Excellent verbal and written communication skills.
8. Strong analytical and problem-solving abilities.
9. Fast learner with the ability to adapt to new technologies and evolving project requirements.
10. Self-motivated team player with a proactive mindset and commitment to delivering high-quality results.
11. Desire to learn, grow, and contribute to the organization's mission.
12. Ability to work effectively within an Agile/Scrum environment, including participation in iterative development cycles.
13. Ability to thrive in a collaborative, high-performing team environment.
Preferred Skills list (4 items):
1. Experience developing applications or test automation solutions using Java.
2. Experience with Selenium or other automated testing frameworks.
3. Exposure to automated testing, quality assurance, CI/CD pipelines, or DevOps practices.
4. Familiarity with test strategy development, test case design, and application troubleshooting.
Benefits list (combining What We Offer and Why Join Niyam):
What We Offer:
- 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.
Why Join Niyam:
- Award-Winning Culture: Proudly recognized by The Washington Post as a Top Workplace for two consecutive years and named to the Inc. 5000 list of America's Fastest-Growing Private Companies for four consecutive years, reflecting our commitment to employee engagement, growth, and excellence.
- Meaningful Mission Impact: Join an SBA-certified HUBZone small business trusted by federal agencies including FEMA, CBP, NOAA, DOJ, TSA, and others to deliver innovative solutions that support critical national missions.
- Drive Innovation: Play a key role in shaping the future of Niyam's proprietary technology accelerators
for prose 3. Do NOT repeat job title as heading (page already shows it) 4. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Company description: "About Niyam IT (Niyam)" - this is company background - "What We Offer:" - benefits/perks list - Role description: "Niyam is seeking a highly motivated, hands-on Automation Engineer..." - this is about the role - "Roles and Responsibilities:" - list of duties - "Requirements:" - list of requirements - "Preferred Skills:" - list of preferred skills - "Why Join Niyam" - more benefits/culture info - Application Deadline and EEO statement - boilerplate to remove Sections I should create: 1. About the role (or similar) - for the role description paragraph 2. Responsibilities - for the roles and responsibilities list 3. Requirements - for the requirements list 4. Preferred Skills - for preferred skills list 5. Benefits - for "What We Offer" and "Why Join Niyam" (these are benefits/perks) The posting mentions "competitive compensation and benefits" but no specific pay details, so no Pay section. Schedule: mentions "onsite at client location in Ashburn, VA up to 4 days/week" - this is a schedule detail, but it's also in requirements. Could include in a Schedule section or fold into requirements. The rules say only create Schedule section if posting actually states them. It does state onsite requirement. But it's also a requirement. I'll include it in Requirements list and maybe mention in About the role. The "What We Offer" and "Why Join Niyam" are benefits. I'll combine into a Benefits section. The company background "About Niyam IT" could be an "About the Company" section, but the rules only list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" isn't listed. But "About the role" is. The company description is not about the role. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But they say "Prefer a few substantive sections over many thin ones." I think I should include company background as it's substantive. But the heading "About the Company" isn't in the list. Could use "About the Role" for the role description paragraph, and maybe "Company Overview" for the company description. However, the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Automation Engineer". The company description is separate.
I'll include:
- About the Role (for the paragraph describing the role)
- Responsibilities
- Requirements
- Preferred Skills
- Benefits (combining What We Offer and Why Join Niyam)
I'll omit the company background "About Niyam IT" as it's more marketing, but it's substantive. The rules say "Preserve ALL substantive information". The company background is substantive. But the allowed headings don't include "About the Company". I could fold it into a paragraph before sections? But the output should be HTML fragment with sections. The rules say "include a section ONLY when the posting has real, specific content for it". The company background is real content. I'll create a section "Company Overview" using h3. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use "Company Overview".
But the user might expect only those headings. However, the example says "e.g." meaning for example. I think it's okay.
Let me structure:
Company Overview
Company Overview
...company description...
About the Role
...role description paragraph...
Responsibilities
- ...
Requirements
- ...
Preferred Skills
- ...
Benefits
- ...