Test Engineer, (Consultant, Engineering & Technical Services)

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Keep substantive info. We need to parse the posting. Key sections: - Intro description: "We are seeking a Test Engineer as part of our Consultant, Engineering & Technical Services career path to ensure the quality and reliability of a large-scale federal enterprise data platform. This opportunity supports a major federal agency's modernization initiative focused on building and operating a secure, cloud-native data platform that enables scalable, governed data services across the agency. The Test Engineer will validate platform functionality, support release readiness, and ensure accessibility compliance across the shared technology foundation that powers data-driven decision-making agency-wide. This is a fully remote role. At Fearless, this Consultant collaborates with cross-functional teams to deliver high-quality, secure, and maintainable systems across all stages of the software and data lifecycle. This role is instrumental in delivering secure, efficient, and scalable solutions that directly impact the success of projects, teams, and organizational goals. This role will possess and/or develop the skills to be able to span the domains of software development, data engineering, infrastructure automation, information assurance, and AI/ML integration at a practical application level of proficiency . This Consultant role will work on projects that allow them to contribute across the entire technology stack—software, infrastructure, data, AI, and security—to ensure quality, speed, and innovation in delivery." That could be "About the role". Also "Fearless Impact" sections maybe part of responsibilities? But we have a separate "Your Responsibilities In This Role" list. Also "Fearless Impact" includes bullet points about impact. Could be part of responsibilities or separate? The instruction: Use headings only when posting has real specific content. We could include "Responsibilities" heading for the list under "Your Responsibilities In This Role". Also maybe "Impact" could be part of responsibilities or maybe we can include as a separate section "Impact". But allowed headings list includes only those specific ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. "Impact" could go under Responsibilities or About the role. Probably better to put under Responsibilities as part of description? But we have a separate list of responsibilities; we could also include the Fearless Impact bullet points under Responsibilities as additional items. "Requirements" heading: includes Work Experience Project Skill and Experience Requirements list (minimum 4 years experience, bachelor's degree, ability to obtain Public Trust clearance, proven experience conducting functional and regression testing, hands-on API testing, experience tracking defects, working knowledge of test automation frameworks, experience within Agile teams). Also "Preferred Experience" could be under Requirements or maybe Skills? The instruction: Use headings only when posting has real specific content. We could have Requirements section containing both required and preferred? Might be okay. But we also have "Fearless Skills And Competencies" list (Analytical Thinking, Synthetic Thinking, etc.) and "Required Level Of Proficiency". That could go under Skills heading. Also "Physical Requirements" could be under Requirements? But Physical Requirements is separate; maybe we could include under Requirements or maybe under a separate section? Not in allowed list; we could fold into Requirements or maybe under Skills? Probably better to put Physical Requirements under Requirements as part of the role's requirements. "Benefits" heading: there is a Benefits section with details (Life at Fearless, benefits list). Also there is a separate "Benefits At Fearless" later with details. We'll combine. "Pay" heading: there is compensation details with salary range and starting pay, bonus eligibility. So include Pay. "Schedule": there is mention of "This is a fully remote role." Also maybe flexible schedules mentioned in benefits. But schedule specifics? Not explicit schedule like hours. Could include "Fully remote" and maybe "Flexible, life-friendly schedules" from benefits. So we can include Schedule section with that info. We must not include headings with filler like "commensurate with experience". Avoid empty sections. We must preserve all substantive info; not invent or summarize away detail. Must not omit substantive info. So we need to include all details from the posting that are substantive, but we can reformat into HTML. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out sections like "We believe in paying people fairly..." maybe that's part of compensation but not boilerplate? It's somewhat generic but still part of compensation description. Might keep as part of Pay section. However "We believe in paying people fairly..." is generic but still part of compensation philosophy; could keep. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The EEO statement is near the bottom: "We’re proud to be an equal opportunity employer..." That should be removed. Also "Reasonable Accommodations" maybe not boilerplate? It's about accommodations; could be considered substantive? Might keep? It's not EEO but it's about accommodations; could keep under Benefits maybe. But it's a statement about process; maybe keep as part of Benefits? Not sure. Safer to keep it as it's substantive about accommodations. However it's more like a policy; but not explicitly prohibited. We'll keep. Also "So, What’s Next?" section about hiring process is application instructions; should be removed. Also "Where You Can Build with Fearless" about states list maybe considered substantive? It's about where they can hire; could be considered part of Benefits or maybe Schedule? Not exactly. Might be considered location eligibility; could be included under About the role? Might be considered substantive. But it's not in allowed headings; we could fold into About the role as a note. However 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." The states list is not minor metadata? It's location eligibility; could be considered minor metadata but still substantive. We could include as a paragraph under About the role. We must output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

We are seeking a Test Engineer as part of our Consultant, Engineering & Technical Services career path to ensure the quality and reliability of a large-scale federal enterprise data platform. This opportunity supports a major federal agency's modernization initiative focused on building and operating a secure, cloud-native data platform that enables scalable, governed data services across the agency. The Test Engineer will validate platform functionality, support release readiness, and ensure accessibility compliance across the shared technology foundation that powers data-driven decision-making agency-wide. This is a fully remote role. At Fearless, this Consultant collaborates with cross-functional teams to deliver high-quality, secure, and maintainable systems across all stages of the software and data lifecycle. This role is instrumental in delivering secure, efficient, and scalable solutions that directly impact the success of projects, teams, and organizational goals. This role will possess and/or develop the skills to be able to span the domains of software development, data engineering, infrastructure automation, information assurance, and AI/ML integration at a practical application level of proficiency. This Consultant role will work on projects that allow them to contribute across the entire technology stack—software, infrastructure, data, AI, and security—to ensure quality, speed, and innovation in delivery. Fearless is licensed to hire talented individuals residing in the following 15 states: Alabama, California, Delaware, District of Columbia, Florida, Georgia, Maryland, New Jersey, New York, North Carolina, Pennsylvania, South Carolina, Tennessee, Texas, and Virginia.

Responsibilities

• Execute functional, regression, and integration testing to validate platform features and data services.
• Perform API testing to verify interfaces between platform components and downstream systems.
• Support release readiness activities by validating deployments and confirming platform stability before go-live.
• Verify accessibility compliance with Section 508 standards across platform interfaces and user-facing tools.
• Validate data pipelines, integrations, and platform services to ensure data accuracy, reliability, and end-to-end functionality.
• Support automated testing and quality gates within CI/CD pipelines to improve release quality and delivery reliability.
• Track, document, and communicate defects using defect management systems to support resolution workflows.
• Develop and maintain automated test scripts to increase test coverage and improve testing efficiency.
• Collaborate with engineering, product, and stakeholder teams to clarify requirements, define acceptance criteria, and ensure quality throughout the software delivery lifecycle.
• Collaborate with cross functional teams; earn the trust of your customer and teammates by delivering world class services.
• Be reliable completing assigned objectives on time.
• Alert your teammates and supervisor immediately when you think a deliverable is at risk.
• Gather intelligence and listen to what your client, other people within the customer’s organization and other contractors say about your project, and report back to your Fearless teammates and supervisor (whether it’s good, bad or just informational).
• Deliver expected outcomes relative to high quality code and maintainable systems.
• Offer and implement innovative solutions that include engineering best practices through new tools, frameworks and methodologies.
• Serve as a trusted advisor in your area of expertise.

Requirements

• Minimum of 4 years of experience in software testing, quality assurance, or related roles.
• Bachelor's degree in Computer Science, Information Technology, Engineering, or related field, or equivalent work experience.
• Ability to obtain and maintain Public Trust clearance.
• Proven experience conducting functional and regression testing across complex software systems.
• Hands-on experience performing API testing and validating integrations between system components.
• Experience tracking and managing defects through resolution using defect management tools.
• Working knowledge of test automation frameworks and scripting to support automated testing workflows.
• Experience working within Agile software delivery teams and participating throughout the software development lifecycle.
• Physical requirements: ability to sit for extended periods while working on a computer or during meetings; must be able to travel occasionally to client sites or company meetings, which may involve driving or flying; ability to communicate effectively via phone, email, and in-person, requiring clear speech, listening, and written communication skills; ability to move within an office environment, including reaching for files, using office equipment, and occasional light lifting (up to 10 pounds).

Maybe also include Preferred Experience under Requirements? Could add as a sublist but we can incorporate as part of Requirements: "Preferred Experience: Experience testing cloud-native platforms or data engineering systems; familiarity with accessibility testing tools and Section 508 validation techniques; experience supporting the federal government, healthcare, or other highly regulated environments." We'll add as separate bullet.

Skills

• Analytical Thinking: The ability to observe and interpret information, break down complex problems into parts, identify patterns/relationships and draw logical conclusions to develop effective solutions.
• Synthetic Thinking: The ability to combine different ideas, information, or concepts to create a new, complex understanding or solution by integrating disparate elements into a new, meaningful whole.
• Adaptability: Comfort with change, flexibility in the face of shifting demands and resilience to setbacks.
• Ownership & Accountability: Committed to taking responsibility for outcomes, ensuring that all commitments are met with a focus on enhancing service delivery.
• Consultative Advising: Identifies and articulates client challenges, scopes projects and aligns recommendations to business