Systems Software Engineer [AQ-19038]
for each section. Use - for lists. Use
for prose.
We must not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the equal opportunity statements, the "Aquent is an equal-opportunity employer" lines, the "Check out our awesome benefits: https://aquent.com/talent/talent-benefits" maybe keep as part of benefits? It's a link; but maybe we can keep as part of benefits description. However it's not boilerplate? It's a link to benefits. Could keep but it's not essential. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The equal opportunity lines are boilerplate; remove them. The link to benefits maybe not boilerplate but it's a reference; we could keep but it's not necessary. Safer to keep benefits description without the link.
We need to preserve all substantive information. So we need to include the description paragraphs about the role, responsibilities list, must-have qualifications list, nice-to-have qualifications list, benefits list.
We should not invent or summarize away detail. So we need to keep the specifics.
Let's extract:
Intro paragraphs: "Aquent is proud to partner with a leading technology company that stands at the forefront of innovation, dedicated to shaping the future of computing. This organization is committed to transforming how vulnerabilities are identified and mitigated across the industry, focusing on securing critical hardware ecosystems through cutting-edge AI, compiler technology, and automated fuzzing. Join a pioneering team where your contributions will make a profound impact on the security posture of critical hardware ecosystems, bridging research ideas with production-quality engineering solutions and driving innovation that secures vital systems through advanced analysis technologies. This is an unparalleled opportunity to join a pioneering team and make a profound impact on the security posture of critical hardware ecosystems. In this dynamic engineering role, your expertise will directly contribute to building and advancing a groundbreaking firmware security analysis platform, instrumental in bridging cutting-edge research with production-quality engineering solutions. You’ll work alongside security researchers, compiler engineers, and platform developers, contributing to the long-term technical strategy and evolution of a critical platform. This role offers a unique chance to work across multiple layers of the technology stack, from low-level compiler infrastructure to modern AI-assisted development workflows, making a tangible difference in securing vital hardware ecosystems."
That's the "About the role" maybe. Could be a section.
Then "What You’ll Do" list: many bullet points (actually sentences separated by periods). We need to turn each into
- . The list includes:
- Build and enhance security analysis pipelines, including developing preprocessing pipelines for C/C++ firmware code into Intermediate Representation (IR).
- Implement and maintain IR-based transformations to prepare firmware for off-target analysis and fuzzing.
- Create and improve code-analysis workflows, encompassing call-graph extraction, metadata generation, and static-analysis integrations.
- Design and maintain systems for generating and executing fuzzing campaigns using modern frameworks and AI-assisted techniques.
- Improve crash triage systems for automated identification, deduplication, and analysis of security findings.
- Develop automated mechanisms to classify code semantics and enhance analysis accuracy.
- Build scalable automation combining compiler infrastructure, security tooling, and AI-driven workflows.
- Enhance vulnerability detection pipelines and reduce false positives through improved analysis techniques.
- Improve reporting systems to transform raw security findings into actionable engineering insights.
- Validate analysis approaches across diverse firmware targets and environments.
- Improve system reliability, modularity, test coverage, and CI/CD automation.
- Create developer documentation, onboarding guides, and architectural references.
- Support dependency review, reproducible builds, and general open-source readiness activities.
- Help establish contribution workflows, issue triage practices, and release processes for external contributors.
- Write clean, maintainable, and well-tested code.
- Participate in design reviews and technical architecture discussions.
- Collaborate closely with engineers across security, hardware, and platform teams.
- Contribute to long-term technical strategy and platform evolution.
That's responsibilities.
Then "Must-Have Qualifications" list:
- Bachelor’s degree in Computer Science, Computer Engineering, or a related technical field, or equivalent practical experience.
- Strong professional experience developing software in C/C++.
- Hands-on experience with compiler technologies, IR, or low-level systems programming.
- Experience working with fuzzing frameworks such as libFuzzer, AFL, AFL++, or similar technologies.
- Strong understanding of software security principles, including memory-safety vulnerabilities and root-cause analysis.
- Proficiency with Python for automation and tooling development.
- Experience using Git-based development workflows.
- Demonstrated ability to write well-tested, maintainable, and documented production code.
Then "Nice-to-Have Qualifications" list:
- Experience with firmware, embedded systems, device software, or bare-metal development.
- Knowledge of hardware abstraction layers (HALs), MMIO, emulation, rehosting, or cross-compilation techniques.
- Experience with static-analysis platforms.
- Familiarity with program-analysis concepts such as call graphs, data-flow analysis, or IR transformations.
- Experience integrating AI, machine learning, or large language model technologies into engineering workflows.
- Previous open-source contributor or maintainer experience.
- Experience building CI/CD pipelines and release automation.
- Familiarity with collaborative development platforms.
Then "About Aquent Talent" paragraph: "Aquent Talent connects the best talent in marketing, creative, and design with the world’s biggest brands. Our eligible talent get access to amazing benefits like subsidized health, vision, and dental plans, paid sick leave, and retirement plans with a match. We also offer free online training through Aquent Gymnasium. More information on our awesome benefits!"
Then "Client Description" paragraph: "Join a global technology leader driving innovation and empowering people and organizations worldwide to achieve more. Here, you’ll collaborate with passionate, diverse teams to create impactful solutions that shape the future. The culture prioritizes growth, inclusion, and purpose—where your ideas are valued, and your work drives real change. Wherever your passion lies and wherever your career is headed—you’ll play a role in projects that touch billions of lives. With flexible work options and a supportive environment, you’ll have the tools to thrive both personally and professionally. Be part of something that truly matters."
Then "Why work with AQUENT?" maybe repeats benefits.
We should combine benefits: from Aquent Talent and maybe flexible work options.
We need to avoid duplication. So we can create Benefits section with bullet list: subsidized health, vision, and dental plans; paid sick leave; retirement plans with a match; free online training through Aquent Gymnasium; flexible work options.
We should not include the link or "More information on our awesome benefits!" as it's not substantive.
We should not include EEO statements.
We should not include "Aquent is an equal opportunity employer." lines.
We should not include "Check out our awesome benefits: https://aquent.com/talent/talent-benefits".
We should not include duplicated lines.
Now decide sections: About the role (intro paragraph), Responsibilities (What You'll Do list), Requirements (maybe combine Must-Have and Nice-to-Have? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Must-Have Qualifications and Nice-to-Have Qualifications. Could map Must-Have to Requirements, Nice-to-Have to Qualifications or Skills. But we need to decide.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (intro). Responsibilities (What You'll Do). Requirements (Must-Have Qualifications). Qualifications (Nice-to-Have Qualifications). Skills maybe not explicitly listed; but we could treat Skills as maybe the technical skills like C/C++, Python, Git, etc. However those are already in Must-Have. Could we create Skills section from the Must-Have? But we already used Must-Have for Requirements. Might be better to map Must-Have to Requirements, Nice-to-Have to Qualifications, and maybe Skills could be omitted if no specific skills beyond those. But we need to only include sections when posting has real specific content. If we don't have distinct Skills content, we should omit Skills section. Similarly Pay and Schedule omitted.
Thus we will output:
About the role
...intro paragraph...
Responsibilities
- ... each bullet ...
Requirements
- ... Must-Have Qualifications ...
Qualifications
- ... Nice-to-Have Qualifications ...
Benefits
- ... benefits list ...
We need to ensure we preserve all substantive information. Let's copy the intro paragraph exactly as given, but we may need to trim any boilerplate like "Aquent is proud to partner..." That's substantive. Keep it.
Check for any duplicated lines: The intro repeats "This is an unparalleled opportunity to join a pioneering team and make a profound impact on the security posture of critical hardware ecosystems." It appears earlier also "Join a pioneering team where your contributions will make a profound impact..." and later "This is an unparalleled opportunity..." It's not duplicate exactly but similar. We should keep both as they are substantive? Might be considered duplicated lines? The instruction: remove duplicated lines. If there are exact duplicate sentences, we should remove duplicates. Let's see: The text includes:
- "Join a pioneering team where your contributions will make a profound impact on the security posture of critical hardware ecosystems, bridging research ideas with production-quality engineering solutions and driving innovation that secures vital systems through advanced analysis technologies."
- Later: "This is an unparalleled opportunity to join a pioneering team and make a profound impact on the security posture of critical hardware ecosystems."
These are not exact duplicates but similar. Not sure if we should remove. Probably keep both as they are not exact duplicates. The instruction likely refers to exact duplicate lines like boilerplate repeated. We'll keep.
Now responsibilities list: need to ensure each bullet ends with a period as in original. We'll keep.
Now Must-Have Qualifications list: keep.
Nice-to-Have Qualifications list: keep.
Benefits list: from Aquent Talent: subsidized health, vision, and dental plans; paid sick leave; retirement plans with a match; free online training through Aquent Gymnasium; flexible work options (from Client Description). Also maybe "More information on our awesome benefits!" we omit.
Now output HTML fragment only.
Let's craft.
Be careful to escape any HTML special characters? The text includes apostrophes, etc. It's fine.
We'll produce:
About the role
Aquent is proud to partner with a leading technology company that stands at the forefront of innovation, dedicated to shaping the future of computing. This organization is committed to transforming how vulnerabilities are identified and mitigated across the industry, focusing on securing critical hardware ecosystems through cutting-edge AI, compiler technology, and automated fuzzing. Join a pioneering team where your contributions will make a profound impact on the security posture of critical hardware ecosystems, bridging research ideas with production-quality engineering solutions and driving innovation that secures vital systems through advanced analysis technologies. This is an
for prose. We must not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the equal opportunity statements, the "Aquent is an equal-opportunity employer" lines, the "Check out our awesome benefits: https://aquent.com/talent/talent-benefits" maybe keep as part of benefits? It's a link; but maybe we can keep as part of benefits description. However it's not boilerplate? It's a link to benefits. Could keep but it's not essential. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The equal opportunity lines are boilerplate; remove them. The link to benefits maybe not boilerplate but it's a reference; we could keep but it's not necessary. Safer to keep benefits description without the link. We need to preserve all substantive information. So we need to include the description paragraphs about the role, responsibilities list, must-have qualifications list, nice-to-have qualifications list, benefits list. We should not invent or summarize away detail. So we need to keep the specifics. Let's extract: Intro paragraphs: "Aquent is proud to partner with a leading technology company that stands at the forefront of innovation, dedicated to shaping the future of computing. This organization is committed to transforming how vulnerabilities are identified and mitigated across the industry, focusing on securing critical hardware ecosystems through cutting-edge AI, compiler technology, and automated fuzzing. Join a pioneering team where your contributions will make a profound impact on the security posture of critical hardware ecosystems, bridging research ideas with production-quality engineering solutions and driving innovation that secures vital systems through advanced analysis technologies. This is an unparalleled opportunity to join a pioneering team and make a profound impact on the security posture of critical hardware ecosystems. In this dynamic engineering role, your expertise will directly contribute to building and advancing a groundbreaking firmware security analysis platform, instrumental in bridging cutting-edge research with production-quality engineering solutions. You’ll work alongside security researchers, compiler engineers, and platform developers, contributing to the long-term technical strategy and evolution of a critical platform. This role offers a unique chance to work across multiple layers of the technology stack, from low-level compiler infrastructure to modern AI-assisted development workflows, making a tangible difference in securing vital hardware ecosystems." That's the "About the role" maybe. Could be a section. Then "What You’ll Do" list: many bullet points (actually sentences separated by periods). We need to turn each into
About the role
...intro paragraph...
Responsibilities
- ... each bullet ...
Requirements
- ... Must-Have Qualifications ...
Qualifications
- ... Nice-to-Have Qualifications ...
Benefits
- ... benefits list ...
About the role
Aquent is proud to partner with a leading technology company that stands at the forefront of innovation, dedicated to shaping the future of computing. This organization is committed to transforming how vulnerabilities are identified and mitigated across the industry, focusing on securing critical hardware ecosystems through cutting-edge AI, compiler technology, and automated fuzzing. Join a pioneering team where your contributions will make a profound impact on the security posture of critical hardware ecosystems, bridging research ideas with production-quality engineering solutions and driving innovation that secures vital systems through advanced analysis technologies. This is an