Principal Database Administrator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills? The posting includes "About The Role", "Your Responsibilities Will Include", "Required Qualifications", "Preferred Qualifications". Also includes "Work model, sponsorship, relocation" which is metadata; we can fold into a short

maybe under a generic section? The instruction: "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." So we can include a short

for work model, sponsorship, relocation. Also we have salary info: Minimum Salary: $102100 Maximum Salary: $194000. Also note about compensation etc. The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD') and never create Pay/Schedule/Benefits sections unless the posting actually states them." We have salary specifics, so we can include a Pay section with the salary range. Benefits? Not explicitly listed besides mention of core and optional employee benefits but not details. So we should not create Benefits section because no specific benefits listed. Schedule? Work model is hybrid requiring at least three days per week; that's schedule info. So we can include a Schedule section with that detail. However we need to check if we should create a Schedule section: The posting says "Work model, sponsorship, relocation: ... This role follows a hybrid work model requiring employees to be in our local office at least three days per week." That's schedule info. So we can include a Schedule section with that. Also we could include a short paragraph for sponsorship/relocation metadata. We must not include boilerplate like EEO, equal-opportunity, scam-warning, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the content from About The Role, Responsibilities, Required Qualifications, Preferred Qualifications, Pay (salary range), Schedule (hybrid model), maybe a short note about sponsorship/relocation. We should not include "Requisition ID: 635220" as heading; we can fold into a short

maybe at top or bottom. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content is list vs prose. The responsibilities are a list of bullet-like sentences each starting with a verb. We can put them in

  • . Similarly Required Qualifications and Preferred Qualifications can be lists. The About The Role is prose paragraphs; we can put in

    . Pay: we can put in

    or maybe

    but it's just two numbers; better

    . Schedule: we can put in

    describing hybrid model. We also need to include a short paragraph for sponsorship/relocation: "Boston Scientific will not offer sponsorship or take over sponsorship of an employment visa for this position at this time. Relocation assistance is not available for this position at this time." Could be in a

    under maybe a "Notes" section? But we shouldn't create a section unless real specific content. Could just include that as a

    after Schedule or before. We must not include the boilerplate about EEO, etc. Also remove the lines about "Additional Location(s): US-MN-Arden Hills Diversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance". That's fluff; we can drop. Also remove the lines about "At Boston Scientific, we’ll give you the opportunity..." that's generic marketing; but it's part of the posting? It's before About The Role. It's somewhat generic but still substantive? It's about culture. Might be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The opening paragraph about opportunity is not exactly boilerplate but could be considered generic marketing. However it's not duplicated. Might be okay to keep as part of About the Role? But we already have an About The Role section later. The opening paragraph is more about company culture; we could incorporate into About the Role paragraph. But we must preserve ALL substantive information; we could include it as part of About the Role. Better to keep the substantive content: The paragraph starting "At Boston Scientific, we’ll give you the opportunity..." and the next sentence about Glassdoor etc. Actually the "About The Role" section starts after that. So we could combine. Let's extract: - Intro: "Additional Location(s): US-MN-Arden Hills Diversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance At Boston Scientific, we’ll give you the opportunity to harness all that’s within you by working in teams of diverse and high-performing employees, tackling some of the most important health industry challenges. With access to the latest tools, information and training, we’ll help you in advancing your skills and career. Here, you’ll be supported in progressing – whatever your ambitions." - Then: "Boston Scientific was recognized as a Glassdoor Best Place to Work in 2026, ranking No. 15 on the Top 100 list, reflecting the culture our employees experience every day." - Then "About The Role" paragraph: "The Principal Database Administrator - LATITUDE IT Operations will serve as a strategic technical leader and hands-on database administrator responsible for the reliability, performance, security and evolution of the database platforms supporting LATITUDE, Boston Scientific's Remote Patient Monitoring system. Oracle Database administration is the primary focus of this role, supporting existing enterprise infrastructure and business-critical production environments. PostgreSQL on AWS RDS is a key strategic capability supporting the team's future-state architecture, modernization and migration roadmap. This role combines deep Oracle expertise with the ability to shape the strategic transition toward future-state architecture, including PostgreSQL on AWS RDS. The Principal Database Administrator will troubleshoot complex production issues, lead root-cause analysis, improve database performance and resiliency, and establish sustainable operational standards. Strong Unix/Linux and scripting capabilities are essential for automating database build, deployment, maintenance and support activities. The role will also help advance AI-enabled transformation by evaluating emerging capabilities that can improve database architecture, observability, automation, performance analysis and operational efficiency while maintaining appropriate security, reliability and governance." - Then "Work model, sponsorship, relocation:" paragraph. - Then "Your Responsibilities Will Include" list. - Then "Required Qualifications" list. - Then "Preferred Qualifications" list. - Then "Requisition ID: 635220" plus salary info. - Then compensation paragraph. - Then boilerplate about MA lie detector test, etc. That's legal; we should remove. - Then company description paragraphs about transforming lives, etc. That's marketing; could be considered boilerplate? Might be okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed; but it's generic marketing. Might be considered boilerplate? Not sure. Safer to remove it as it's not substantive to the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about the company but not about the role. Might be considered filler. I'd remove it to keep focused. - Also remove the lines about "Boston Scientific continues to evaluate its policies..." etc. That's legal/boilerplate. - Remove the prohibited substance test paragraph? That's about role being safety-sensitive and requiring test. That's substantive info about the role (requirement). Should we keep? It's a requirement: "This role is deemed safety-sensitive and, as such, candidates will be subject to a prohibited substance test as a requirement." That's a specific requirement. So we should keep that as part of Requirements or maybe a note. - Also the MA lie detector test line is legal; remove. - Also the lines about "Please be advised that certain US based positions..." about COVID vaccination; that's location-specific requirement; could be considered substantive. But it's a conditional requirement; we could keep as note. But we need to decide: The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The vaccination line is not EEO; it's a requirement. Might keep. But we also have to avoid duplication. Given the complexity, I'll produce a concise HTML with sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Pay, Schedule, Notes (maybe for sponsorship/relocation, substance test, vaccination). However the instruction says prefer few substantive sections over many thin ones. So maybe combine notes into a short

    after Schedule. We could have sections: About the role, Responsibilities, Qualifications (combining required and preferred?), Pay, Schedule. But we need to preserve required vs preferred distinction. Could have two subsections under Qualifications: Required and Preferred as

    ? But only

    allowed for section headings. We could use

    for Required Qualifications and another

    for Preferred Qualifications. That's okay; they are substantive. Thus sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Pay, Schedule, Additional Notes (maybe not needed if we fold sponsorship/relocation and substance test into a

    under Schedule or after). But we need to avoid creating a section with filler. Additional Notes would have content; okay. Let's draft:

    About the role

    ... (combined intro and About The Role paragraph)

    Responsibilities

    • Provide expert-level administration and operational support for Oracle Database environments supporting existing LATITUDE infrastructure and business-critical production systems.
    • Own the Oracle database lifecycle, including installation, configuration, upgrades, patching, maintenance, backup and recovery, security, high availability and disaster recovery.
    • Monitor and optimize Oracle database health, capacity, storage, availability, SQL performance and resource utilization; proactively identify risks and implement sustainable improvements.
    • Troubleshoot complex production database incidents and performance issues, perform root-cause analysis and drive issues through resolution.
    • Provide hands-on PostgreSQL administration for AWS RDS and contribute to the architecture, operational readiness and support model for PostgreSQL as a strategic future-state platform.
    • Lead and support database modernization initiatives, including assessment, planning, testing and execution of Oracle-to-PostgreSQL migrations, where appropriate.
    • Develop Unix/Linux-based scripts and automation using Shell/Bash, Python or comparable technologies to support database builds, deployments, configuration, patching, monitoring, maintenance, backup and recovery, and other repeatable infrastructure operations.
    • Apply AWS database services, monitoring, automation and infrastructure-as-code practices to improve observability, reliability, repeatability and operational efficiency for PostgreSQL RDS environments.
    • Evaluate and responsibly apply AI-enabled database and infrastructure capabilities to enhance performance analysis, anomaly detection, operational automation, capacity planning and architectural decision-making while aligning with enterprise security and governance practices.
    • Partner with application, infrastructure, cloud and engineering teams on database architecture, releases, capacity planning, troubleshooting and operational readiness.
    • Develop and maintain database documentation, support procedures, runbooks and technical standards while providing technical direction and mentoring team members in database operations and modernization practices.

    Required Qualifications

    • Bachelor's or master's degree in computer science, information systems, engineering or a related technical field, or equivalent relevant experience.
    • Minimum of 8 years' experience in progressive database administration supporting enterprise and production database environments.
    • Deep hands-on Oracle Database administration expertise supporting enterprise, business-critical production environments, including installation, configuration, upgrades, patch