Sr Platform Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Why Mayo Clinic" intro, then Benefits Highlights, Responsibilities, Qualifications, Exemption Status, Compensation Detail, Benefits Eligible, Schedule, etc. We must not repeat job title as heading. Use

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. We have content for Benefits, Responsibilities, Qualifications, Pay (Compensation Detail), Schedule. Possibly also "About the role" could be the introductory paragraph about Mayo Clinic and why work there. That seems appropriate. "Requirements" maybe same as Qualifications? We can combine? But we need separate headings if content exists. The posting has "Qualifications" section with bullet list. Also "Exemption Status" etc but those are minor metadata; we can fold into short

or drop. We should not create sections for Exemption Status, etc. Also "Benefits Eligible Yes" is part of benefits but we already have Benefits section. We must use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, E-Verify, etc. Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content: Intro: "Why Mayo Clinic Mayo Clinic is top-ranked in more specialties than any other care provider according to U.S. News & World Report. As we work together to put the needs of the patient first, we are also dedicated to our employees, investing in competitive compensation and comprehensive benefit plans – to take care of you and your family, now and in the future. And with continuing education and advancement opportunities at every turn, you can build a long, successful career with Mayo Clinic." That's prose for About the role. Benefits Highlights: list: - Medical: Multiple plan options. - Dental: Delta Dental or reimbursement account for flexible coverage. - Vision: Affordable plan with national network. - Pre-Tax Savings: HSA and FSAs for eligible expenses. - Retirement: Competitive retirement package to secure your future. Also "Benefits Eligible Yes" maybe note. We'll put Benefits section with

  • each. Responsibilities: many bullet points under "The position will be responsible for the following essential functions:" then list. We'll capture each as
  • . Need to preserve all. Let's list responsibilities from text: - Contribute to the design, development, and deployment of reusable platform foundations using established well-architected and secure-by-default principles. - Design, develop, and maintain platform services and integration capabilities that enable the secure and efficient exchange of healthcare data between systems and applications. - Collaborate with engineering, product, design, architecture, and other partner teams to clarify requirements, review technical specifications, and develop maintainable solutions. - Build robust and scalable services using one or more languages and frameworks such as Java, TypeScript, Go, or .NET while maintaining appropriate standards for data integrity, security, reliability, and healthcare compliance. - Develop and maintain applications and shared user-interface capabilities using React/Next.js to provide reliable, fluent user interfaces for healthcare professionals and patients. - Build and maintain integrations with healthcare systems, APIs, and data sources, applying reusable patterns where appropriate to promote consistency and reduce bespoke implementations. - Partner with cloud architects and platform engineers to deploy and operate healthcare solutions on Google Cloud Platform (GCP) using established cloud and infrastructure patterns. - Use established DevOps practices, CI/CD pipelines, and deployment tooling to automate delivery and ensure high availability and performance of healthcare applications. - Collaborate with data engineers to provide platform capabilities that support the secure movement, validation, monitoring, and use of healthcare data. - Stay informed about technologies and practices relevant to platform engineering, healthcare interoperability, frontend development, and cloud operations, and contribute to the team’s evaluation of their practical value. - Work with product, solutions, and implementation teams to identify recurring application and integration needs and translate them into reusable platform tools, patterns, and documentation. - Partners with the solutions and implementation/support team to design, develop and deploy management and support tooling for all aspects of the platform’s operations. This may include things like quality monitoring tools, system action audit logs, and application telemetry. - Contribute to meeting established service-level objectives and agreements by implementing monitoring, alerting, reliability improvements, and follow-up actions for services owned by the team. - Contribute to the execution of the Mayo Clinic Platform technical roadmap and provide technical input based on implementation experience, operational learning, and the needs of teams using the platform. - Collaborate with product partners to follow established Software Development Life Cycle and Product Development Life Cycle processes, helping keep technical delivery aligned with product goals and organizational requirements. Also note: "The above statements describe the general nature and level of work only. They are not an exhaustive list of all required responsibilities, duties, and skills. Other duties may be added or assigned." That's boilerplate; we should remove? It's generic but maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This sentence is generic but not exactly those categories; but it's a disclaimer about responsibilities. Might be considered boilerplate? It's not EEO etc. Might keep? Safer to keep? The instruction says remove boilerplate, duplicated lines, and application instructions. This is a generic disclaimer; could be considered boilerplate. I'd remove it to keep only substantive responsibilities. Qualifications: list: - Bachelors degree in a relevant information technology field or a minimum 7 years of direct full-stack engineering with increasing complexity. - 3-5 years working in diverse environments utilizing Agile principles of software development. - Proven experience as a Full Stack Engineer with a strong emphasis on healthcare interoperability. - Proficiency in Java and/or .NET for backend development, including API / service design and implementation. - Expertise in Javascript with a focus on React and react frameworks (e.g. NextJS) for building responsive and intuitive front-end applications. - Hands-on experience with Google Cloud Platform (GCP) (or equivalent) services and cloud-native application development. - Familiarity with healthcare interoperability standards such as HL7, FHIR and OMOP. - Strong problem-solving skills and the ability to work in a collaborative, cross-functional team environment. - Experience with DevOps practices, CI/CD pipelines, and containerization technologies (e.g., Docker, Kubernetes) is a plus. - Knowledge of healthcare data security and compliance requirements, including HIPAA, is highly desirable. - Excellent communication skills and the ability to convey complex technical concepts to non-technical stakeholders. - A proactive and self-driven mindset with a passion for staying up-to-date with emerging technologies and industry best practices. - Experience with Interoperability standards such as HL7, FHIR and OMOP. (duplicate) - Experience with solutions integration/delivery in a healthcare setting. We have duplicate line about HL7 etc; we should deduplicate. Pay: Compensation Detail: "$127,900 - $185,500 / year". Also maybe "Exemption Status Exempt" but we can fold into short

    or drop. We'll include Pay section with that salary range. Schedule: "Schedule Full Time Hours/Pay Period 80 Schedule Details Monday - Friday 10%+ travel may be required". Also "Benefits Eligible Yes". We'll include Schedule section with that info. We should not include "Exemption Status Exempt", "Vacancy is not eligible for sponsorship", etc. Those are minor metadata; we can drop or fold into short p. Probably drop. Now construct HTML:

    About the role

    Why Mayo Clinic Mayo Clinic is top-ranked in more specialties than any other care provider according to U.S. News & World Report. As we work together to put the needs of the patient first, we are also dedicated to our employees, investing in competitive compensation and comprehensive benefit plans – to take care of you and your family, now and in the future. And with continuing education and advancement opportunities at every turn, you can build a long, successful career with Mayo Clinic.

    Benefits

    • Medical: Multiple plan options.
    • Dental: Delta Dental or reimbursement account for flexible coverage.
    • Vision: Affordable plan with national network.
    • Pre-Tax Savings: HSA and FSAs for eligible expenses.
    • Retirement: Competitive retirement package to secure your future.

    Responsibilities

    • Contribute to the design, development, and deployment of reusable platform foundations using established well-architected and secure-by-default principles.
    • Design, develop, and maintain platform services and integration capabilities that enable the secure and efficient exchange of healthcare data between systems and applications.
    • Collaborate with engineering, product, design, architecture, and other partner teams to clarify requirements, review technical specifications, and develop maintainable solutions.
    • Build robust and scalable services using one or more languages and frameworks such as Java, TypeScript, Go, or .NET while maintaining appropriate standards for data integrity, security, reliability, and healthcare compliance.
    • Develop and maintain applications and shared user-interface capabilities using React/Next.js to provide reliable, fluent user interfaces for healthcare professionals and patients.
    • Build and maintain integrations with healthcare systems, APIs, and data sources, applying reusable patterns where appropriate to promote consistency and reduce bespoke implementations.
    • Partner with cloud architects and platform engineers to deploy and operate healthcare solutions on Google Cloud Platform (GCP) using established cloud and infrastructure patterns.
    • Use established DevOps practices, CI/CD pipelines, and deployment tooling to automate delivery and ensure high availability and performance of healthcare applications.
    • Collaborate with data engineers to provide platform capabilities that support the secure movement, validation, monitoring, and use of healthcare data.
    • Stay informed about technologies and practices relevant to platform engineering, healthcare interoperability, frontend development, and cloud operations, and contribute to the team’s evaluation of their practical value.
    • Work with product, solutions, and implementation teams to identify recurring application and integration needs and translate them into reusable platform tools, patterns, and documentation.
    • Partners with the solutions and implementation/support team to design, develop and deploy management and support tooling for all aspects of the platform’s operations. This may include things like quality monitoring tools, system action audit logs, and application telemetry.
    • Contribute to meeting established service-level objectives and agreements by implementing monitoring, alerting, reliability improvements, and follow-up actions for services owned by the team.
    • Contribute to the execution of the Mayo Clinic Platform technical roadmap and provide technical input based on implementation experience, operational learning, and the needs of teams using the platform.
    • Collaborate with product partners to follow established Software Development Life Cycle and Product Development Life Cycle processes, helping keep technical delivery aligned with product goals and organizational requirements.

    Qualifications

    • Bachelors degree in a relevant information technology field or a minimum 7 years of direct full-stack engineering with increasing complexity.
    • 3-5 years working in diverse environments utilizing Agile principles of software development.
    • Proven experience as a Full Stack Engineer with a strong emphasis on healthcare interoperability.
    • Proficiency in Java and/or .NET for backend development, including API / service design and implementation.
    • Expertise in Javascript with a focus on React and react frameworks (e.g. NextJS) for building responsive and intuitive front-end applications.
    • Hands-on experience with Google Cloud Platform (GCP) (or equivalent) services and cloud-native application development.
    • Familiarity