Sr. Software Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove EEO statements, scam warning, etc. Keep substantive info.
We need to parse content:
- Intro about McKesson: "McKesson is an impact-driven, Fortune 10 company..." This is about company, could be "About the role" or maybe "About McKesson"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview under "About the role". Probably appropriate.
- Then description of Shared Capabilities team and role: "The Shared Capabilities team builds and operates the core APIs..." That's role description, could be part of About the role.
- Then "What You'll Do" with subheadings: Core Engineering Responsibilities, Technical Leadership Responsibilities, AI-Assisted Development. Those are responsibilities. So we can put under Responsibilities
and list items.
- Then "Priority will be given to candidates who reside in the Columbus, OH Metropolitan area. We are unable to provide sponsorship for this role presently or in the future." That's location/eligibility; could be part of Requirements or Qualifications? Might be under Requirements.
- Then "Minimum Qualifications" with bullet list: Degree or equivalent and typically requires 7+ years of relevant experience. Education Bachelor's degree... Critical Skills list. That's qualifications/requirements. We can put under Requirements
or Qualifications
. The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Probably combine: Requirements for mandatory, Qualifications for preferred? But we have both Minimum Qualifications and Preferred Qualifications. So we can have Requirements for minimum qualifications, and Qualifications for preferred qualifications. Or we could use Skills for critical skills. But we have a separate Skills heading. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: company intro + team description.
- Responsibilities: What You'll Do (core engineering, technical leadership, AI-assisted development).
- Requirements: Minimum Qualifications (degree, 7+ years, education, critical skills list). Could also include location and sponsorship? Might be separate but we can include under Requirements.
- Qualifications: Preferred Qualifications list.
- Skills: Technical Capabilities list (strong understanding of API design, problem-solving, etc.) Could also include critical skills but we already used them under Requirements. Might be redundant but we can still include Technical Capabilities under Skills.
- Benefits: The posting mentions "We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards." Then details about base pay range, bonus, long-term incentive, benefits link. So we have Pay and Benefits. Benefits section: mention competitive compensation package, total rewards, annual bonus, long-term incentive opportunities, link to benefits. We can include that.
- Pay: Base Pay Range $131,000 - $218,300.
- Schedule: Not mentioned. So we omit Schedule.
We must not include placeholder text like "commensurate with experience". Not present.
We must not include boilerplate: EEO, scam warning, etc. Remove those paragraphs.
Also remove duplicated lines.
Now produce HTML fragment with headings and - for lists,
for prose.
We need to preserve all substantive information. Let's extract specifics.
About the role prose:
- "McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care. What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you."
- Then role description: "The Shared Capabilities team builds and operates the core APIs, event standards, and integration services that power product development across CoverMyMeds. These services connect directly to critical business data and serve as foundational building blocks used by engineering teams throughout the organization. As a Senior Software Engineer, you will design, build, and operate production-grade APIs and event-driven services while helping establish the engineering standards that other teams follow. In addition to hands-on software development, you will serve as a technical resource for the organization by reviewing solution designs, mentoring engineers, and providing guidance on architectural decisions and implementation approaches. This is a highly collaborative, backend-focused engineering role with minimal frontend development. Success requires strong technical depth, sound engineering judgment, and the ability to influence teams through expertise rather than authority."
Combine into About the role paragraph(s). Could be multiple
tags.
Responsibilities: list items from What You'll Do.
Core Engineering Responsibilities:
- Design, build, and operate scalable, production-grade APIs used across CoverMyMeds.
- Develop and maintain services built using TypeScript, Node.js, and Python.
- Build and support Kafka-based event-driven integrations and services.
- Design and maintain relational database schemas using PostgreSQL.
- Develop and maintain infrastructure as code using Terraform and related tooling.
- Build and enhance CI/CD pipelines using GitHub Actions and automated deployment processes.
- Build migration tools and assist engineering teams in adopting new platform capabilities.
- Troubleshoot and resolve production issues across services owned by the Shared Capabilities team.
- Participate in an on-call rotation supporting services owned by the team.
Technical Leadership Responsibilities:
- Perform technical feasibility reviews and provide actionable feedback on proposed solutions.
- Partner with engineering teams to establish and maintain API and event-design standards.
- Mentor engineers through code reviews, technical discussions, and collaborative problem solving.
- Act as a technical resource for teammates and partner engineering groups.
- Identify opportunities to improve engineering quality, maintainability, reliability, and scalability.
- Help drive adoption of modern engineering practices and development tooling.
- Collaborate with teams early in the design process to prevent costly architectural divergence.
AI-Assisted Development:
- Utilize AI-assisted development tools to improve engineering productivity and delivery speed.
- Contribute to the continuous improvement of team development workflows and engineering practices.
- Apply sound engineering judgment when validating AI-generated solutions and recommendations.
We can combine all into a single
list, or separate subheadings? The instruction says use - for any list of duties/requirements/benefits. It doesn't forbid subheadings inside list? Probably better to keep as a flat list. Could also group with
but not allowed. We'll just list all items.
Requirements: Minimum Qualifications.
- Degree or equivalent and typically requires 7+ years of relevant experience.
- Education: Bachelor's degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience.
- Critical Skills:
- 5+ years of professional software development experience.
- Demonstrated experience designing, building, and operating production APIs.
- Experience developing backend services using TypeScript/Node.js and Python.
- Experience working with Kafka or similar event-streaming platforms.
- Experience designing and maintaining relational database schemas using PostgreSQL or similar technologies.
- Experience implementing infrastructure as code using Terraform or comparable tooling.
- Experience working with modern CI/CD platforms such as GitHub Actions.
- Experience supporting production systems and resolving operational issues.
- Experience participating in technical design discussions and code reviews.
We could flatten: each bullet as
- . Might be long but okay.
Qualifications: Preferred Qualifications.
- Experience with Azure services, including API Management and Service Bus.
- Experience with Helm and Kubernetes-based deployment environments.
- Experience modernizing applications built with Ruby on Rails or Elixir.
- Experience working in SOX, ITGC, or other regulated software-delivery environments.
- Experience developing platform services, shared engineering capabilities, or internal developer platforms.
- Experience mentoring engineers and influencing technical decisions across teams.
- Experience using AI-assisted software-development tools such as Claude or similar technologies.
Also location and sponsorship: "Priority will be given to candidates who reside in the Columbus, OH Metropolitan area. We are unable to provide sponsorship for this role presently or in the future." Could be under Requirements or Qualifications. Probably under Requirements as it's a requirement. We'll add as bullets.
Skills: Technical Capabilities.
- Strong understanding of API design principles, including versioning and backward compatibility.
- Strong problem-solving and analytical skills.
- Ability to evaluate technical approaches and provide constructive engineering feedback.
- Ability to communicate technical concepts and tradeoffs to technical and non-technical audiences.
- Demonstrated ability to learn new technologies and apply them effectively in a production environment.
Benefits: "We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards. This is determined by several factors, including performance, experience and skills, equity, regular job market evaluations, and geographical markets. The pay range shown below is aligned with McKesson's pay philosophy, and pay will always be compliant with any applicable regulations. In addition to base pay, other compensation, such as an annual bonus or long-term incentive opportunities may be offered. For more information regarding benefits at McKesson, please click here."
We should keep the sentence about benefits link but not the actual link? It says "please click here." We can keep as prose.
Pay: "Our Base Pay Range for this position $131,000 - $218,300"
We need to output only HTML fragment, no markdown fences.
Let's craft.
Structure:
About the role
...company intro...
...role description...
Responsibilities
- ...items...
...
Requirements
- Degree or equivalent and typically requires 7+ years of relevant experience.
- Education: Bachelor's degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience.
- 5+ years of professional software development experience.
- Demonstrated experience designing, building, and operating production APIs.
- Experience developing backend services using TypeScript/Node.js and Python.
- Experience working with Kafka or similar event-streaming platforms.
- Experience designing and maintaining relational database schemas using PostgreSQL or similar technologies.
- Experience implementing infrastructure as code using Terraform or comparable tooling.
- Experience working with modern CI/CD platforms such as GitHub Actions.
- Experience supporting production systems and resolving operational issues.
- Experience participating in technical design discussions and code reviews.
- Priority will be given to candidates who reside in the Columbus, OH Metropolitan area.
- We are unable to provide sponsorship for this role presently or in the future.
Qualifications
- Experience with Azure services, including API Management and Service Bus.
- Experience with Helm and Kubernetes-based deployment environments.
- Experience modernizing applications built with Ruby on Rails or Elixir.
- Experience working in SOX, ITGC, or other regulated software-delivery environments.
- Experience developing platform services, shared engineering capabilities, or internal developer platforms.
- Experience mentoring engineers and influencing technical decisions across teams.
- Experience using AI-assisted software-development tools
- for lists,
for prose. We need to preserve all substantive information. Let's extract specifics. About the role prose: - "McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care. What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you." - Then role description: "The Shared Capabilities team builds and operates the core APIs, event standards, and integration services that power product development across CoverMyMeds. These services connect directly to critical business data and serve as foundational building blocks used by engineering teams throughout the organization. As a Senior Software Engineer, you will design, build, and operate production-grade APIs and event-driven services while helping establish the engineering standards that other teams follow. In addition to hands-on software development, you will serve as a technical resource for the organization by reviewing solution designs, mentoring engineers, and providing guidance on architectural decisions and implementation approaches. This is a highly collaborative, backend-focused engineering role with minimal frontend development. Success requires strong technical depth, sound engineering judgment, and the ability to influence teams through expertise rather than authority." Combine into About the role paragraph(s). Could be multiple
tags. Responsibilities: list items from What You'll Do. Core Engineering Responsibilities: - Design, build, and operate scalable, production-grade APIs used across CoverMyMeds. - Develop and maintain services built using TypeScript, Node.js, and Python. - Build and support Kafka-based event-driven integrations and services. - Design and maintain relational database schemas using PostgreSQL. - Develop and maintain infrastructure as code using Terraform and related tooling. - Build and enhance CI/CD pipelines using GitHub Actions and automated deployment processes. - Build migration tools and assist engineering teams in adopting new platform capabilities. - Troubleshoot and resolve production issues across services owned by the Shared Capabilities team. - Participate in an on-call rotation supporting services owned by the team. Technical Leadership Responsibilities: - Perform technical feasibility reviews and provide actionable feedback on proposed solutions. - Partner with engineering teams to establish and maintain API and event-design standards. - Mentor engineers through code reviews, technical discussions, and collaborative problem solving. - Act as a technical resource for teammates and partner engineering groups. - Identify opportunities to improve engineering quality, maintainability, reliability, and scalability. - Help drive adoption of modern engineering practices and development tooling. - Collaborate with teams early in the design process to prevent costly architectural divergence. AI-Assisted Development: - Utilize AI-assisted development tools to improve engineering productivity and delivery speed. - Contribute to the continuous improvement of team development workflows and engineering practices. - Apply sound engineering judgment when validating AI-generated solutions and recommendations. We can combine all into a single
- list, or separate subheadings? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid subheadings inside list? Probably better to keep as a flat list. Could also group with
but not allowed. We'll just list all items. Requirements: Minimum Qualifications. - Degree or equivalent and typically requires 7+ years of relevant experience. - Education: Bachelor's degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience. - Critical Skills: - 5+ years of professional software development experience. - Demonstrated experience designing, building, and operating production APIs. - Experience developing backend services using TypeScript/Node.js and Python. - Experience working with Kafka or similar event-streaming platforms. - Experience designing and maintaining relational database schemas using PostgreSQL or similar technologies. - Experience implementing infrastructure as code using Terraform or comparable tooling. - Experience working with modern CI/CD platforms such as GitHub Actions. - Experience supporting production systems and resolving operational issues. - Experience participating in technical design discussions and code reviews. We could flatten: each bullet as
- . Might be long but okay.
Qualifications: Preferred Qualifications.
- Experience with Azure services, including API Management and Service Bus.
- Experience with Helm and Kubernetes-based deployment environments.
- Experience modernizing applications built with Ruby on Rails or Elixir.
- Experience working in SOX, ITGC, or other regulated software-delivery environments.
- Experience developing platform services, shared engineering capabilities, or internal developer platforms.
- Experience mentoring engineers and influencing technical decisions across teams.
- Experience using AI-assisted software-development tools such as Claude or similar technologies.
Also location and sponsorship: "Priority will be given to candidates who reside in the Columbus, OH Metropolitan area. We are unable to provide sponsorship for this role presently or in the future." Could be under Requirements or Qualifications. Probably under Requirements as it's a requirement. We'll add as bullets.
Skills: Technical Capabilities.
- Strong understanding of API design principles, including versioning and backward compatibility.
- Strong problem-solving and analytical skills.
- Ability to evaluate technical approaches and provide constructive engineering feedback.
- Ability to communicate technical concepts and tradeoffs to technical and non-technical audiences.
- Demonstrated ability to learn new technologies and apply them effectively in a production environment.
Benefits: "We are proud to offer a competitive compensation package at McKesson as part of our Total Rewards. This is determined by several factors, including performance, experience and skills, equity, regular job market evaluations, and geographical markets. The pay range shown below is aligned with McKesson's pay philosophy, and pay will always be compliant with any applicable regulations. In addition to base pay, other compensation, such as an annual bonus or long-term incentive opportunities may be offered. For more information regarding benefits at McKesson, please click here."
We should keep the sentence about benefits link but not the actual link? It says "please click here." We can keep as prose.
Pay: "Our Base Pay Range for this position $131,000 - $218,300"
We need to output only HTML fragment, no markdown fences.
Let's craft.
Structure:
About the role
...company intro...
...role description...
Responsibilities
- ...items... ...
Requirements
- Degree or equivalent and typically requires 7+ years of relevant experience.
- Education: Bachelor's degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience.
- 5+ years of professional software development experience.
- Demonstrated experience designing, building, and operating production APIs.
- Experience developing backend services using TypeScript/Node.js and Python.
- Experience working with Kafka or similar event-streaming platforms.
- Experience designing and maintaining relational database schemas using PostgreSQL or similar technologies.
- Experience implementing infrastructure as code using Terraform or comparable tooling.
- Experience working with modern CI/CD platforms such as GitHub Actions.
- Experience supporting production systems and resolving operational issues.
- Experience participating in technical design discussions and code reviews.
- Priority will be given to candidates who reside in the Columbus, OH Metropolitan area.
- We are unable to provide sponsorship for this role presently or in the future.
Qualifications
- Experience with Azure services, including API Management and Service Bus.
- Experience with Helm and Kubernetes-based deployment environments.
- Experience modernizing applications built with Ruby on Rails or Elixir.
- Experience working in SOX, ITGC, or other regulated software-delivery environments.
- Experience developing platform services, shared engineering capabilities, or internal developer platforms.
- Experience mentoring engineers and influencing technical decisions across teams.
- Experience using AI-assisted software-development tools
- for any list of duties/requirements/benefits. It doesn't forbid subheadings inside list? Probably better to keep as a flat list. Could also group with