Senior Software Engineer

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to preserve all substantive info, remove boilerplate like EEO, legal, navigation, cookie, application instructions, duplicated lines. We need to parse the posting. Key parts: - "Why This Role Matters" paragraph: could be considered "About the role". Use

About the role

then

with that paragraph. - "Key Responsibilities": list bullet points. Use

Responsibilities

then

• each. - "Required Qualifications": bullet list. Use

  Qualifications

  maybe "Required Qualifications". Could also be "Requirements". The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Required Qualifications and Preferred Qualifications. Could combine into Qualifications section with required and preferred? But we need to preserve all info. Could have

  Required Qualifications

  but heading must be from allowed list? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use "Required Qualifications" as heading? Probably better to stick to allowed ones: maybe "Qualifications" for required, and maybe "Preferred Qualifications" as a subsection? But we can't create new headings not in list? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, not strict. However to be safe, we can use "Required Qualifications" and "Preferred Qualifications" as headings; they are still section headings. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid others. So we can use those. We also have "Preferred Qualifications": list. We have "Required Experience and Education:" with multiple options. That could be part of Qualifications or maybe "Requirements". We'll include under Qualifications. We have "You use modern AI tools with judgment:" sentence. Could be part of Qualifications or maybe a separate "Skills"? Could be a skill. We'll include under Qualifications maybe as a bullet. We have "Salary Range (CO): $100,000 USD - $155,000 USD". That's Pay. So we need a Pay section with that info. We have "Clearance Requirement: This position may require an active TS/SCI Clearance. Current clearance holders are strongly encouraged to apply. If you don't currently hold one, Bluestaq will sponsor eligible candidates through the clearance process based on program needs." That's maybe a requirement but not in list; we could include under Qualifications or a separate section like "Clearance". But not in allowed list; maybe we can include under Qualifications as a bullet. We have "Relocation: Relocation assistance is available for full-time positions." That's a Benefit? Could be under Benefits. We have "About Bluestaq" paragraph: could be "About the role"? Actually "About Bluestaq" is company description. Could be under "About the role" or maybe a separate "About the company". But we already used About the role for the why this role matters. Could combine? Better to have About the role (why role matters) and maybe a separate "About Bluestaq" but not in list. Could put under About the role as additional paragraph. We have "What We Offer:" list of benefits. That's Benefits section. We have EEO boilerplate etc to remove. We have "Applications will be accepted for 60 days..." that's application instruction, remove. We need to output only HTML fragment. Let's structure:

  About the role

  Why This Role Matters Senior Software Engineers are the technical anchors of our teams. You'll be the go-to person for a domain or service, ensuring that what we ship is not only functional but well-designed, tested, and sustainable. Your work will directly impact mission readiness, and your mentorship will shape the next generation of engineers at Bluestaq. You'll balance hands-on delivery with technical leadership, raising the bar for code quality and system design.

  Then Responsibilities.

  Responsibilities

  • Own features and modules that span multiple components/services and require coordination with other teams or roles
  • Design and implement non-trivial features with clear tradeoffs (performance, readability, complexity, security)
  • Write solid tests (unit, integration, basic end-to-end) and help improve test coverage and reliability
  • Identify and address code smells, refactoring opportunities, and tech debt in your area
  • Understand core architecture patterns in use (microservices, event-driven, SPA, component-based UI) and work within them effectively
  • Operate independently within your product area: scope work, make reasonable design decisions, and proactively raise risks
  • Act as an escalation point for junior engineers when debugging issues or clarifying designs
  • Mentor others via pairing, feedback, and sharing context, not just fixing things yourself
  • Lead medium-sized features from idea → design → implementation → production → follow-up
  • Debug complex issues that span multiple components or services, including production incidents
  • Make incremental improvements to architecture, patterns, and tooling in your domain
  Note: The bullet "Mentor others via pairing, feedback, and sharing context, not just fixing things yourself" we need to keep. Now Qualifications. We have Required Qualifications bullet list, then Required Experience and Education, then Preferred Qualifications bullet list, then AI tools sentence, clearance, relocation maybe. We could split into Required Qualifications and Preferred Qualifications sections. Let's do:

  Required Qualifications

  • Strong proficiency in multiple programming languages and frameworks
  • Proven ability to design and deliver complex features across the full stack
  • Deep understanding of software architecture patterns and design principles
  • Experience with automated testing strategies and test-driven development
  • Track record of mentoring junior engineers and improving team practices
  • Strong debugging and problem-solving skills across distributed systems
  • Experience with cloud platforms, containerization, and modern deployment practices
  • Excellent communication skills and ability to explain technical concepts clearly
  Then maybe a

  Required Experience and Education

  but not in list; but we could incorporate into Qualifications. However we need to preserve that info. Could add a

  after Required Qualifications: "Required Experience and Education: PhD in Computer Science, Engineering, or a related field and 0+ years of software engineering or related experience, OR Master's degree in Computer Science, Engineering, or a related field and 2+ years of software engineering or related experience, OR Bachelor's degree in Computer Science, Engineering, or a related field and 4+ years of software engineering or related experience, OR Associate degree in a related field and 6+ years of software engineering or related experience, OR High School Diploma/GED and 8+ years of software engineering or related experience." Then Preferred Qualifications.

  Preferred Qualifications

  • Experience with microservices architectures and distributed systems
  • Familiarity with event-driven architectures and asynchronous processing
  • Background in performance optimization and scalability
  • Experience working on government, defense, or mission-critical systems
  • Knowledge of security best practices and secure coding standards
  • Contributions to open-source projects or technical communities
  • Experience with observability tools and practices (logging, metrics, tracing)
  • Familiarity with customer-facing environments, including Technical Exchange Meetings (TEMs) or similar collaborative forums with stakeholders
  Then maybe a

  Additional Qualifications

  for AI tools, clearance, relocation. But we could incorporate into Qualifications as bullet list. Let's add a

  Additional Qualifications

  but not in allowed list; maybe better to put under Qualifications as extra bullets. But we have to avoid filler. We'll include them as bullets under a

  Additional Qualifications

  maybe okay. Alternatively we could add a

  Skills

  for AI tools, clearance, relocation? Not ideal. Given the instruction to prefer few substantive sections over many thin ones, maybe we combine Required Qualifications, Required Experience and Education, Preferred Qualifications, AI tools, clearance, relocation into a single Qualifications section with subheadings? But we cannot use subheadings besides

  . Could use

  with bold? Not allowed? We can use inside

  . But we need to preserve info. Simplify: We'll have

  Qualifications

  and inside we will have

  for required qualifications list? But we need lists. Could do multiple

  inside same section with headings? Not allowed to add extra headings? Could use

  Required Qualifications:

  then
  . That's okay. Thus:

  Qualifications

  Required Qualifications:

  ...

  Required Experience and Education:

  PhD in Computer Science, Engineering, or a related field and 0+ years of software engineering or related experience, OR Master's degree in Computer Science, Engineering, or a related field and 2+ years of software engineering or related experience, OR Bachelor's degree in Computer Science, Engineering, or a related field and 4+ years of software engineering or related experience, OR Associate degree in a related field and 6+ years of software engineering or related experience, OR High School Diploma/GED and 8+ years of software engineering or related experience.

  Preferred Qualifications:

  ...

  Additional qualifications:

  • You use modern AI tools with judgment: integrating them into workflows where they're impactful, reviewing their outputs, and handling proprietary or sensitive data responsibly.
  • Clearance Requirement: This position may require an active TS/SCI Clearance. Current clearance holders are strongly encouraged to apply. If you don't currently hold one, Bluestaq will sponsor eligible candidates through the clearance process based on program needs.
  • Relocation: Relocation assistance is available for full-time positions.
  That preserves all. Now Benefits section. We have "What We Offer:" list. We need to capture each benefit: - 100% employer-paid health, dental, and vision for you and your dependents - 10% total 401(k) contribution from day one, no vesting period — Bluestaq contributes 4% automatically and matches 100% of the next 6% - Every role is eligible for an annual performance bonus - $200,000 employer-paid life insurance, plus short- and long-term disability coverage - $5,000 annual professional development budget per employee - 20 days PTO, plus 8 paid holidays - Pet insurance, onsite gym, and flexible schedule We'll put in
  . Now Pay section: Salary Range (CO): $100,000 USD - $155,000 USD. We'll do

  Pay

  <