Senior Developer

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. The posting includes purpose, day consists of, you'll be successful with (qualifications), key responsibilities, required qualifications, preferred qualifications, working conditions, benefits & rewards, benefits & rewards, EEO etc. We need to strip boilerplate: EEO, legal, etc. Also remove duplicated lines. We need to preserve substantive info. We need to decide sections: About the role (purpose and day consists of). Responsibilities (key responsibilities). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications? Actually they said use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: Requirements = required qualifications; Qualifications = preferred qualifications; Skills = maybe combine required/preferred skills? Could also list skills from responsibilities. But we need to avoid filler sections. We have Benefits & Rewards content: bonus opportunities, 401k, ESPP, referral bonus, medical/dental/vision/life insurance, paid vacation, sick time, paid holidays, personal holiday, paid volunteer time off. That's substantive. So Benefits section. Pay: not mentioned. So we should NOT include Pay heading. Schedule: not mentioned (no schedule info). So omit. We also have Working Conditions (travel & environment) and Physical/Sensory Requirements. Those could go under maybe "Working Conditions" but not in allowed headings. Could we put under "Requirements"? Not appropriate. Perhaps we can omit because not in allowed headings? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those for section headings, but does not forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. Working conditions maybe not needed; we could drop as not fitting. However we need to preserve ALL substantive information; cannot drop details like travel may be required, noise level, physical requirements. If we cannot put them under allowed headings, maybe we can incorporate them into a generic

without heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but suggests we should use those for sections. It might be okay to have other headings but they'd be non-standard. Safer to stick to those headings and embed other info within appropriate sections (e.g., Responsibilities could include travel? Not really). Could add a "Working Conditions" paragraph under Responsibilities? Might be odd. Maybe we can treat "Working Conditions" as part of "Requirements" or "Qualifications"? Not ideal. Given instruction: "Prefer a few substantive sections over many thin ones." So we could combine working conditions into a section like "About the role" or "Responsibilities". But better to create a section "Working Conditions" not in list? Might violate. Let's read again: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can use other headings as long as they are

. Probably acceptable. But to be safe, we can include a section "Working Conditions" as

. The instruction didn't forbid other headings. It just gave examples. So we can include. Similarly, we might include "Preferred Qualifications" as Qualifications heading. We need to avoid boilerplate: EEO, legal, etc. Also remove duplicated lines. Let's extract substantive content: Purpose: "Behind every seamless customer experience, scalable application, and high-performing engineering team is infrastructure built to perform under pressure. As our Senior Developer, you'll play a critical role in designing, automating, and optimizing the cloud platforms that keep our business moving. You'll partner closely with engineering teams to improve reliability, accelerate deployments, strengthen security, and create systems that scale alongside a rapidly growing organization. If you're energized by solving complex technical challenges and building environments that empower others to do their best work, we'd love to meet you." Your Day Consists Of: list of bullet-like sentences (no actual bullet formatting). We'll convert to

• . You'll Be Successful With: list of qualifications (5+ years experience, Terraform, Azure, APIM, troubleshooting, Dynatrace, CI/CD, collaborative mindset, mentor). We'll treat as Required Qualifications. Key Responsibilities: list. Required Qualifications: list (Bachelor's degree, 5+ years experience, Terraform, Azure, APIM, ActiveMQ, Dynatrace, Git, troubleshooting, CI/CD). Preferred Qualifications: list (containerization, security best practices, Agile/Scrum, scripting Python/Bash/PowerShell). Working Conditions (travel & environment): Travel may be required including air and car travel; noise level quiet to moderate. Physical/Sensory Requirements: Sedentary Work – Ability to exert 10 - 20 pounds of force occasionally, and/or negligible amount of force frequently to lift, carry, push, pull or otherwise move objects. Sedentary work involves sitting most of the time, but may involve walking or standing for brief periods of time. Benefits & Rewards: list. EEO etc: remove. We need to avoid repeating job title as heading (the page already shows it). So no heading for Senior Developer. We need to not put Job ID/requisition numbers as headings (none present). Now produce HTML fragment. We'll structure:

  About the role

  purpose paragraph

  Your Day Consists Of

  maybe we treat as Responsibilities? But we have separate Responsibilities section. Could combine day-consists-of into Responsibilities. But we have Key Responsibilities separate. Might be redundant. Better to have a section "Responsibilities" that includes both day-consists-of and key responsibilities. However the instruction says use headings like Responsibilities. So we can make a Responsibilities section that includes the day-consists-of bullets and key responsibilities bullets. Thus:

  Responsibilities

  • Designing and implementing Infrastructure as Code solutions using Terraform to create scalable, secure, and repeatable cloud environments.
  • Building, configuring, and optimizing Azure-based infrastructure that supports critical business applications.
  • Managing Azure API Management (APIM) services to enable reliable and secure integrations across platforms.
  • Monitoring system health and performance using Dynatrace, proactively identifying opportunities to improve reliability and user experience.
  • Leading root-cause analysis and resolution efforts for complex application, infrastructure, and cloud-related issues.
  • Partnering with software engineering teams to enhance CI/CD pipelines, automate deployments, and improve development velocity.
  • Develop and manage Azure-based solutions, including deployment, configuration, and optimization of cloud resources.
  • Configure and maintain Azure API Management (APIM) services to enable secure, reliable API integrations.
  • Administer and support messaging systems, including ActiveMQ, ensuring high availability and performance.
  • Monitor system performance and application health using Dynatrace; proactively identify and resolve issues.
  • Lead troubleshooting efforts for complex system, application, and infrastructure issues across environments.
  • Collaborate with development teams to integrate CI/CD pipelines using Bitbucket, Git, or similar version control systems.
  • Implement best practices for code versioning, branching strategies, and deployment automation.
  • Ensure system reliability, security, and compliance through continuous improvement and automation.
  • Mentor junior team members and contribute to DevOps best practices and standards.
  But we have duplicates: some items appear both in day-consists-of and key responsibilities. We should deduplicate. Let's merge unique items. List unique responsibilities: - Designing and implementing Infrastructure as Code solutions using Terraform to create scalable, secure, and repeatable cloud environments. - Building, configuring, and optimizing Azure-based infrastructure that supports critical business applications. - Managing Azure API Management (APIM) services to enable reliable and secure integrations across platforms. - Monitoring system health and performance using Dynatrace, proactively identifying opportunities to improve reliability and user experience. - Leading root-cause analysis and resolution efforts for complex application, infrastructure, and cloud-related issues. - Partnering with software engineering teams to enhance CI/CD pipelines, automate deployments, and improve development velocity. - Administer and support messaging systems, including ActiveMQ, ensuring high availability and performance. - Develop and manage Azure-based solutions, including deployment, configuration, and optimization of cloud resources. (similar to building/configuring/optimizing Azure-based infrastructure; maybe duplicate) - Configure and maintain Azure API Management (APIM) services to enable secure, reliable API integrations. (similar to managing APIM) - Monitor system performance and application health using Dynatrace; proactively identify and resolve issues. (similar to monitoring) - Lead troubleshooting efforts for complex system, application, and infrastructure issues across environments. (similar to leading root-cause analysis) - Collaborate with development teams to integrate CI/CD pipelines using Bitbucket, Git, or similar version control systems. (similar to partnering with software engineering teams to enhance CI/CD) - Implement best practices for code versioning, branching strategies, and deployment automation. - Ensure system reliability, security, and compliance through continuous improvement and automation. - Mentor junior team members and contribute to DevOps best practices and standards. We can consolidate to avoid near-duplicates. Let's produce a concise list: - Design and implement Infrastructure as Code using Terraform for scalable, secure, repeatable cloud environments. - Build, configure, and optimize Azure infrastructure supporting critical business applications. - Manage Azure API Management (APIM) services for secure, reliable API integrations. - Monitor system health and performance with Dynatrace, identifying improvements to reliability and user experience. - Lead root‑cause analysis and resolution of complex application, infrastructure, and cloud issues. - Partner with engineering teams to enhance CI/CD pipelines, automate deployments, and boost development velocity. - Administer and support messaging systems (e.g., ActiveMQ) ensuring high availability and performance. - Implement code versioning, branching, and deployment automation best practices. - Ensure system reliability, security, and compliance via continuous improvement and automation. - Mentor junior team members and promote DevOps best practices. That covers. Now Requirements section: Required Qualifications. List: - Bachelor’s degree in Computer Science, Engineering, or related field (or equivalent experience). - 5+ years of experience in DevOps, cloud engineering, or related roles. - Strong hands‑on experience with Terraform for infrastructure as code. - Proven experience working with Microsoft Azure services. - Experience with Azure API Management (APIM). - Solid understanding of messaging systems such as ActiveMQ. - Experience with Dynatrace or similar monitoring and observability tools. - Proficiency with Git‑based version control systems such as Bitbucket or GitHub. - Strong troubleshooting and problem‑solving skills across distributed systems. - Familiarity with CI/CD pipelines and automation tools. We can combine similar items. Now Qualifications section: Preferred Qualifications. List: - Experience with containerization technologies such as Docker and Kubernetes. - Knowledge of security best practices in cloud environments. - Experience working in Agile or Scrum environments. - Scripting experience in languages such as Python, Bash, or PowerShell. Now Benefits section: Benefits & Rewards. List: - Bonus opportunities and career advancement opportunities at every level. - Programs that help you reach your financial goals: 401(k) with company match, Employee Stock Purchase Plan, and Referral Bonus Program. - Medical, Dental,