Principal Software Engineer - CRM

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting: It includes: - Intro: "We anticipate the application window for this opening will close on - 28 Sep 2026 Careers that change lives start here. Medtronic is a global leader..." This is generic intro; maybe we can include as a short paragraph under About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: description of Medtronic, mission, etc. Also "A Day in the Life Principal Software Engineer Careers That Change Lives ..." Might be considered about the role. - Responsibilities: there is a list: "In general, the following responsibilities apply for the Principal Software Engineer role. This includes, but is not limited to:" then bullet list. - Requirements/Qualifications: there is "Qualifications MUST HAVE – MINIMUM REQUIREMENTS TO BE CONSIDERED FOR THIS ROLE..." then list of minimum requirements. Also "Nice to Have" list. - Skills: maybe combine with Requirements? But we can have a Skills section for technical skills desired (list of key technical skills desired). The posting includes "Key technical skills desired include:" then bullet list. Also "Key skills and attributes include:" then bullet list. - Benefits: there is "Benefits & Compensation" section with salary range, benefits list. - Pay: salary range is given; we could put Pay section with salary range. - Schedule: mention "We are working on-site 4 days per week" and "This role will require less than 10% travel". That's schedule info. We need to avoid filler like "commensurate with experience". Not present. We must not repeat job title as heading. So no heading for "Principal Software Engineer". Use sections. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as HTML. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "Physical Job Requirements", "U.S. Work Authorization & Sponsorship", "Recruitment Fraud Alert", maybe those are boilerplate? They are not EEO but maybe considered legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove sections like Physical Job Requirements, U.S. Work Authorization & Sponsorship, Recruitment Fraud Alert. Also maybe the "About Medtronic" duplicate? There's an "About Medtronic" paragraph later; that's substantive? It's similar to earlier intro. Might be considered boilerplate but it's about company. Might keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Medtronic" paragraph is somewhat generic but still about company. Might keep as part of About the role. We also need to drop duplicated lines. There's duplicate "Physical Job Requirements" repeated; we will remove that entirely. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Medtronic is a global leader in healthcare technology with a Mission to alleviate pain, restore health, and extend life. Our 95,000 employees work across more than 150 countries to put patients first — developing innovative medical technologies that improve the lives of 72+ million patients each year. Your unique talents will help shape the future of healthcare while building a career grounded in purpose, growth, and impact. A Day in the Life Principal Software Engineer Careers That Change Lives At Medtronic, we push the limits of what technology can do to make tomorrow better than yesterday, and that makes it an exciting and rewarding place to work. The Device Embedded Systems group in Medtronic’s Electrophysiology Therapies (EPT) operating unit designs, develops, and verifies embedded applications used in implantable medical devices. As a Principal Software Engineer, you will use your strong DevOps and CI/CD expertise to advance the tools and workflows used by the Device Embedded Systems group. You will play a leading role in the group’s transition to GitHub Enterprise, the adoption of GitHub Copilot and AI-assisted development agents, and the delivery of select tools in partnership with a dedicated AWS cloud team. We are looking for a highly motivated, self-starting software engineer who wants to innovate in a fast-paced environment and improve people’s quality of life.

But we need to avoid repeating job title? The phrase "Principal Software Engineer" appears; that's okay as it's not a heading. We could keep that. Next

Responsibilities

• Evaluate, improve, and upgrade our firmware/software development tools and workflows
• Lead migration and adoption efforts for GitHub Enterprise and AI-assisted development tooling (GitHub Copilot and coding agents), in partnership with the AWS cloud team
• Partner with the central AWS cloud team to design, deliver, and support developer tools hosted on AWS
• Train the team on use of new tools and practices
• Troubleshoot and resolve technical and non-technical issues with tools and workflows
• Support legacy tools, including OTS and custom-built solutions
• Work well with a variety of individuals across engineering disciplines
• Influence tools-related decisions and organizational processes
• Apply basic project management skills

Next

Key technical skills desired

maybe we call it Skills? The instruction says use headings like Skills. So we can have

Skills

and include both technical skills and key skills/attributes. But we might split:

Technical Skills

and

Key Skills and Attributes

. However instruction only gave examples; we can use other headings if they reflect content. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. Probably better to use Skills for both technical and key skills. We'll combine. So

Skills

• CI/CD pipeline design and implementation, with hands-on expertise in GitHub Actions, reusable workflows, self-hosted runners, and branch/environment protection policies
• Administration of GitHub Enterprise (Cloud or Server), including org and repo configuration, SSO/SCIM, Advanced Security, secret scanning, and Dependabot
• Experience deploying and governing GitHub Copilot and Copilot agent capabilities (Copilot Business/Enterprise, Copilot Extensions, coding agents), including policy, telemetry, and driving developer adoption
• Build, test, and deployment automation for embedded/firmware or comparably complex software environments
• Source control migration and branching strategy development, including experience migrating teams from legacy systems (e.g., SVN) to Git/GitHub
• Working knowledge of AWS services relevant to developer tooling (IAM, S3, EC2/ECS/Lambda, CodeArtifact, Secrets Manager, CloudWatch) and experience collaborating with a separate cloud platform team on shared-responsibility architectures
• Infrastructure-as-code experience (Terraform or CloudFormation) and familiarity with containerized tooling (Docker)
• Monitoring, troubleshooting, and continuous improvement of delivery processes, including DORA-style metrics and pipeline observability
• Strong verbal and written communication skills
• Technical training, mentoring, and coaching experience, including enabling engineers on GitHub Enterprise workflows and responsible use of Copilot/AI coding agents
• Change management and organizational influence, with a track record of driving enterprise-scale tool migrations and rollouts
• Experience driving adoption of DevOps, CI/CD, and AI-assisted development practices across teams
• Ability to influence and align with external partner teams (e.g., a central AWS cloud team) to deliver shared tooling in a regulated, safety-critical environment

Next

Qualifications

maybe include Minimum Requirements and Nice to Have. We can have

Qualifications

• Must have – Minimum requirements: Bachelor’s degree in computer engineering, electrical engineering, computer science, engineering, or a related technical discipline and a minimum of 7 years of work experience, OR an advanced degree in computer engineering, electrical engineering, computer science, engineering, or a related technical discipline with 5 years of work experience.
• Nice to have: Experience developing GitHub Actions workflows, GitHub Enterprise org/repo configuration, and policy/security controls; Experience with GitHub Copilot and/or Copilot agent capabilities (Copilot Business/Enterprise, Extensions, coding agents); Working knowledge of AWS and experience collaborating with a dedicated cloud platform team; Infrastructure-as-code experience with Terraform or CloudFormation; Scripting/automation experience in Python; SVN integration and migration experience; Experience programming in Java and Perl (for legacy tool support); Experience delivering developer tooling in a regulated environment (medical device, aerospace, automotive, or similar).

But we need to preserve all detail; we should not lose any. The Nice to Have list is a series of bullet points; we could keep them as separate

items under a subheading? However we already used Skills for technical skills; Nice to Have is more like additional qualifications. Could put under Qualifications as separate list. We'll do:

Qualifications

• Bachelor’s degree in computer engineering, electrical engineering, computer science, engineering, or a related technical discipline and a minimum of 7 years of work experience, OR an advanced degree in computer engineering, electrical engineering, computer science, engineering, or a related technical discipline with 5 years of work experience.

Nice to have

• Experience developing GitHub Actions workflows, GitHub Enterprise org/repo configuration, and policy/security controls
• Experience with GitHub Copilot and/or Copilot agent capabilities (Copilot Business/Enterprise, Extensions, coding agents)
• Working knowledge of AWS and experience collaborating with a dedicated cloud platform team
• Infrastructure-as-code experience with Terraform or CloudFormation
• Scripting/automation experience in Python
• SVN integration and migration experience
• Experience programming in Java and Perl (for legacy tool support)
• Experience delivering developer tooling in a regulated environment (medical device, aerospace, automotive, or similar)

But the instruction says use headings like Requirements, Qualifications, Skills. Nice to have maybe not a standard heading but we can include as part of Qualifications. However we need to preserve all detail; we can embed Nice to Have as a sublist within Qualifications. Simplify:

Qualifications

• Minimum requirements: Bachelor’s degree in computer engineering, electrical engineering, computer science, engineering, or a related technical discipline and a minimum of 7 years of work experience, OR an advanced degree in computer engineering, electrical engineering, computer science, engineering, or a related technical discipline with 5 years of work experience.
• Nice to have: