Development Operations Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. The posting includes: - About The Role: description (first paragraph after "About The Role"). - Responsibilities: "A Typical Day Will Include..." list of duties. - Requirements: "This Role Is a Fit for You If..." list of qualifications/requirements. - Bonus Points: additional qualifications/experience. - Skills: maybe combine? The posting mentions skills like Python, Bash, CI/CD, Docker, Kubernetes, Helm, GitOps, ArgoCD, Ansible, AI tools, etc. Could be part of Requirements or Skills. - Benefits: "What We Offer..." list of benefits. - Pay: "The annual base salary range for this position is $105,000 - $115,000. In addition, this role is eligible for an annual target bonus & a comprehensive benefits package." - Schedule: Not mentioned. So we should not include Schedule section. Also need to include maybe Qualifications? The "Bonus Points" could be considered Qualifications or additional qualifications. We could have a Qualifications section for required qualifications (the "Fit for You If...") and maybe a separate Skills section for technical skills? But the instruction: prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use headings for those specific names if content exists. We have content for About the role, Responsibilities, Requirements (Fit for You If...), Qualifications (Bonus Points?), Benefits, Pay. Skills maybe not needed separately if covered in Requirements. But we could still include Skills if we have explicit skill list. The posting includes skill list in the Fit for You If... (scripting, CI/CD, containers, etc.) and Bonus Points (cloud, monitoring, etc.). Could treat Skills as separate but might be thin. Better to combine Requirements and Qualifications into one section? But they said use headings for those specific names if content exists. We could have both Requirements and Qualifications sections, each with content. That's okay. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like duplicated lines (the repeated Bullhorn core purpose paragraph appears twice; we should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate repeated paragraphs. The repeated paragraph appears twice: "Bullhorn's core purpose is to create an incredible customer experience..." and later again near end. We should keep only one instance. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's a "Compensation And Transparency Statement" which is legal but includes salary range info; we need to keep salary range but maybe discard the statement? The instruction: remove legal/EEO/equal-opportunity/scam-warning boilerplate. The compensation transparency statement is legal but includes salary range; we need to keep the salary range info. We could keep the salary range sentence and discard the rest of the statement. Similarly "What We Offer..." is benefits; keep. We need to output only HTML fragment, no markdown fences. Let's craft sections:

About the role

As a DevOps Engineer at Bullhorn, you'll be building the tools and systems that facilitate large-scale software releases safely and effectively. This includes all pipelines for building, packaging, deploying, and validating software delivery. You will help the team take code changes safely and quickly from a developer's machine all the way to production. We're a release-engineering and platform team: we build and maintain the systems that enable engineering teams to deploy with confidence. We relentlessly automate manual toil from the software delivery lifecycle. This is a hands-on building role. You'll write automations, own our deploy and CI/CD tooling, containerize and modernize our environments, and partner directly with engineering teams to remove the friction that slows them down.

Maybe also include the first paragraph about Bullhorn core purpose? That's not about the role; it's general company info. Should we include? The instruction: Preserve ALL substantive information; do not invent or summarize away detail. The core purpose paragraph is substantive but not specific to role. However the instruction about sections: we only output sections for role-specific content. The core purpose could be placed in a

before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside sections. But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we can include a brief intro paragraph about company culture before sections. That's substantive and not duplicated after dedup. Let's include one paragraph summarizing Bullhorn's core purpose and culture (deduplicated). Then sections. Now Responsibilities: list from "A Typical Day Will Include..." each bullet. We need to convert to

  • . Ensure we keep all bullet points. List: - Designing, building, and maintaining deploy and release pipelines, and the automation that reduces manual intervention during releases - Building and improving our internal release tooling — for example, automating script packaging and DBA approvals, code + script deploys, and release-finishing workflows - Advancing our CI/CD GitOps process: authoring reusable GitLab CI templates, Helm charts, and ArgoCD applications so teams can self-serve their own build and deploy pipelines - Containerizing and modernizing our QA and lower environments (Kubernetes, Helm, Ansible) to bring them closer to production parity - Modernizing build tools across the org to ensure we’re using the latest and greatest technology across all teams. - Attending daily team stand-ups and collaborating with a distributed, cross-functional team across US and UK time zones - Troubleshooting deployment and infrastructure issues, and partnering with engineering teams to resolve environment-specific problems - Leveraging AI tools (Claude Code, Claude Cowork, and similar) as a core part of how you work — writing unit tests and automation, accelerating investigation and refactoring, and finding new ways to eliminate toil - Writing clean, well-tested automation and scripts (Python, Bash) and following solid engineering practices for the tools we own - Contributing to documentation, runbooks, and developer enablement so knowledge is shared and not siloed - Mentoring teammates, driving conversations about priorities and process, and independently owning complex, cross-cutting initiatives - Working within a positive, energizing, collaborative team environment Now Requirements: "This Role Is a Fit for You If..." list. List: - You want to be an integral part of an innovative, high-performance engineering team - You thrive in a fast-paced, agile environment with frequent software releases - You're an automation-first thinker — if you do something more than twice, your instinct is to automate it - You can work through complex problems independently while knowing when to pull others in and help less experienced teammates do the same - You're comfortable scripting and building tooling in Python and Bash/shell - You have hands-on experience with CI/CD systems — GitLab CI/CD and/or Jenkins — including building and maintaining pipelines - You're experienced with containers and orchestration: Docker, Kubernetes, and Helm - You're comfortable building full-stack automation tooling — scripting and backend work in Python, and frontend/UI work in JavaScript (our internal tools have both a Python backend and a web frontend) - You've worked with GitOps and/or infrastructure-as-code and configuration management (ArgoCD, Ansible, or similar) - You're comfortable with Git-based workflows and modern versioning practices - You see AI tooling as a force multiplier and are eager to use it to raise your own and the team's output - You care about reliability, security, and developer experience, and you communicate clearly with the engineering teams you support - You're comfortable challenging and being challenged by your teammates Now Qualifications: Bonus Points list. List: - Bachelor's degree in Computer Science or a similar field, or relevant work experience - Experience with cloud infrastructure (AWS), including services like RDS - Experience with deployment tooling such as Octopus Deploy, and with artifact repositories (Nexus, Artifactory) - Experience with monitoring and observability stacks (Prometheus, Grafana, Backstage, Rancher, or ELK) - Familiarity with SQL Server and collaborating with DBA teams on script and schema deployments - Exposure to secure SDLC / compliance considerations (SOC), and building change management into pipelines - Experience modernizing or migrating legacy systems (e.g., ColdFusion, legacy build jobs) toward modern, containerized workflows - Comfort working across geographically distributed teams and time zones Now Benefits: "What We Offer..." list. List: - Benefits eligibility effective DAY ONE including Medical, Dental, Vision, 401(k), 401(k) Match, and more - Unlimited Planned Paid Time Off - Global Mental Health Support - On-Demand Learning & Development - Quarterly paid volunteer days - Lucrative Employee Referral Program (eligible for prior to your first day) - Company-wide mentor program Now Pay: we have salary range sentence plus mention of annual target bonus & comprehensive benefits package. We'll include that. We should not include Schedule. Now we need to ensure we removed duplicated lines: The repeated Bullhorn core purpose paragraph appears twice; we keep one. Also there is a duplicated line: "Bullhorn's core purpose is to create an incredible customer experience, and the organization has a sharp focus on delivering very high quality products and services to its customers." appears again later near end; we removed duplicate. Also there is a duplicated line: "The company culture is shaped by five Core Values: Ownership, Energy, Speed & Agility, Service, and Being Human." appears twice? Actually appears in first paragraph and later again near end. We need to deduplicate that as well. Let's check: The first paragraph includes that sentence. Later near end: "Bullhorn's core purpose is to create an incredible customer experience, and the organization has a sharp focus on delivering very high quality products and services to its customers. The company culture is shaped by five Core Values: Ownership, Energy, Speed & Agility, Service, and Being Human. Each value, and its underlying definition, serves as a behavioral guide for employees as they interact with customers and fellow coworkers and is an embedded way of operating across our organization. We are a people-first culture where everyone’s contribution is valued and respected. We're looking for smart, forward-thinking individuals who aren't afraid to challenge the status quo and bring fresh perspectives to the table. If you're someone who thrives in a casual, yet fast-paced and agile environment, we'd love to have you join us." Thus we have duplication of the core purpose sentence and the company culture sentence. We'll keep only one occurrence of each. We'll craft an intro paragraph that includes both deduplicated statements plus maybe the rest of that paragraph (the part about people-first culture, looking for smart individuals). That is substantive and not duplicated elsewhere. So we can combine: "Bullhorn's core purpose is to create an incredible customer experience, and the organization has a sharp focus on delivering very high quality products and services to its customers. The company culture is shaped by five Core Values: Ownership, Energy, Speed & Agility, Service, and Being Human. Each value, and its underlying definition, serves as a behavioral guide for employees as they interact with customers and fellow coworkers and is an