Senior Application Software Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the job description. Key sections: - About the role: The first paragraph(s) describing role: "We are seeking a versatile Software Engineer to contribute across platform engineering, cloud infrastructure, distributed systems, application development, integration services, and healthcare workflow solutions. This role bridges the gap between foundational cloud platforms and customer-facing healthcare applications, providing opportunities to work throughout the software development lifecycle. The ideal candidate is passionate about building reliable platforms, developing innovative applications, solving complex technical challenges, and delivering solutions that directly impact healthcare providers, patients, payers, and public health organizations." We can put that under

About the role

with

. - Responsibilities: The section titled "Responsibilities" then "RESPONSIBILITIES" then bullet list. We'll extract bullet points. List items: - Design, develop, test, and maintain scalable software solutions and cloud-native services. - Build and support healthcare applications, APIs, integrations, and platform capabilities. - Develop reliable, secure, and highly available systems running on Oracle Cloud Infrastructure (OCI). - Collaborate with product managers, architects, engineers, and operational teams to deliver customer-focused solutions. - Participate in system design, code reviews, troubleshooting, performance optimization, and operational excellence initiatives. - Contribute to automation, observability, security, and continuous delivery practices. - Support modernization efforts leveraging cloud technologies, healthcare interoperability standards, and AI-driven capabilities. We'll output

• each. - Qualifications: There's a "Qualifications" heading with Minimum Qualifications and Preferred Qualifications. Also later "Qualifications Disclaimer". We need to include substantive qualifications. The "Qualifications" section includes Minimum and Preferred. We'll combine maybe under

  Qualifications

  with
  for each? Could separate Minimum and Preferred as subheadings? But only allowed headings are the listed ones; we can still use

  for prose and

  for lists. We could have a

  Qualifications

  then

  Minimum Qualifications:

  then
  etc. Or we could embed in prose. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. So we can have a Qualifications section with lists for minimum and preferred. We must not include filler like "commensurate with experience". Not present. We need to extract Minimum Qualifications bullet list: - 3+ years of experience in software engineering, application development, platform engineering, or related technical roles within a fast-paced technology environment. - Bachelor's degree in Computer Science, Engineering, related field or equivalent years of relevant experience - Experience developing enterprise software applications or cloud platforms. - Strong programming and software design skills. - Experience with OCI, AWS, Azure, or Google Cloud. - Experience with distributed systems, APIs, and cloud technologies. - Knowledge of software development lifecycle and engineering best practices. Preferred Qualifications bullet list: - Experience with healthcare technology or regulated industries. - Familiarity with healthcare interoperability standards. - Experience building large-scale SaaS platforms. - Knowledge of AI, machine learning, or data engineering solutions. - Strong problem-solving and communication skills. Also there is a "Technologies and Areas of Focus" section which could be considered Skills. We'll put under Skills. Skills: list of technologies: - Oracle Cloud Infrastructure (OCI) - Cloud-native architectures - Distributed systems and microservices - Kubernetes and container technologies - Java, Python, Go, JavaScript, or related languages - REST APIs and event-driven systems - CI/CD and DevOps tooling - Infrastructure automation - Observability and monitoring platforms - Healthcare interoperability standards (FHIR, HL7, SMART on FHIR) - Artificial Intelligence and Machine Learning platforms - Large-scale healthcare data management - Cross-Functional Leadership (maybe not a skill but we can include) - Partner with engineering, product, security, operations, and customer teams. - Drive engineering excellence through best practices, mentoring, and technical leadership. - Participate in roadmap planning and technology modernization efforts. - Contribute to innovation initiatives focused on AI, cloud, healthcare interoperability, and next-generation healthcare experiences. But many of those are more responsibilities/leadership. However we can treat as Skills. We also have "Current and Future Initiatives" which is descriptive about Oracle Health initiatives. Could be part of About the role or maybe a separate section? Not in allowed headings; we could incorporate into About the role as prose. We have Pay: "US: Hiring Range in USD from: $87,000 - $187,000 per year. May be eligible for bonus and equity." Also mention Oracle maintains broad salary ranges etc. That's substantive. So we need a Pay section. We have Benefits: a long list of benefits. So Benefits section. Schedule: Not mentioned explicitly. There's no schedule info. So we should not create Schedule section. Requirements: Not separate; qualifications cover. Could we have Requirements section? The posting doesn't have a separate "Requirements" heading besides Qualifications. We could skip Requirements. We must not create sections with filler. So include About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Check if any other sections like "About Us" could be About the role? Already have About the role. The "About Us" is boilerplate about Oracle; could be considered About the role? Might be considered fluff but it's substantive about company. However instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" paragraph about Oracle's mission might be considered boilerplate? It's not EEO but it's generic marketing. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Us is substantive about company mission. Could include under About the role? Might be better to include as a separate section? Not allowed headings besides those. Could incorporate into About the role as additional paragraph. But we must not repeat job title as heading. Already fine. We must not put Job ID/requisition numbers as headings; none present. We must drop duplicated lines: there is a repeated "Qualifications" heading later with disclaimer; we should not duplicate. We must drop the "Qualifications Disclaimer" paragraph about immunization etc. That's likely boilerplate (legal). Should remove. We must drop the "Range and benefit information provided in this posting are specific to the stated locations only" etc. That's part of Pay/Benefits but we already captured range and benefits. The sentence about Oracle maintains broad salary ranges etc is part of Pay; we can keep as prose. We must drop the "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instruction; remove. We must drop "Career Level - IC3" maybe not needed; could be metadata but not a heading; we could drop as minor metadata. We must drop "About Us" maybe keep as part of About the role? It's not duplicated; it's substantive about Oracle. I'd keep as a paragraph under About the role. We must drop EEO statement at end; remove. Now craft HTML. Structure:

    About the role

    We are seeking a versatile Software Engineer to contribute across platform engineering, cloud infrastructure, distributed systems, application development, integration services, and healthcare workflow solutions. This role bridges the gap between foundational cloud platforms and customer-facing healthcare applications, providing opportunities to work throughout the software development lifecycle. The ideal candidate is passionate about building reliable platforms, developing innovative applications, solving complex technical challenges, and delivering solutions that directly impact healthcare providers, patients, payers, and public health organizations.

    Only Oracle brings together the data, infrastructure, applications, and expertise to power everything from industry innovations to life-saving care. And with AI embedded across our products and services, we help customers turn that promise into a better future for all. Discover your potential at a company leading the way in AI and cloud solutions that impact billions of lives. True innovation starts when everyone is empowered to contribute. That’s why we’re committed to growing a workforce that promotes opportunities for all with competitive benefits that support our people with flexible medical, life insurance, and retirement options. We also encourage employees to give back to their communities through our volunteer programs. We’re committed to including people with disabilities at all stages of the employment process. If you require accessibility assistance or accommodation for a disability at any point, let us know by emailing accommodation-request_mb@oracle.com or by calling 1-888-404-2494 in the United States.

    But note the accommodation request line might be considered contact info; it's not boilerplate? It's about accommodation; could be considered EEO/legal? Might be okay to keep? It's not EEO but it's about accommodation. Might be considered part of company policy; but it's not strictly required. Might be safe to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Accommodation request is related to disability accommodation; could be considered EEO. Safer to remove that sentence. Also the sentence about Oracle bringing together data etc is generic marketing but not EEO; we can keep. We'll keep the first paragraph about Oracle's mission; maybe we can keep it. Now Responsibilities:

    Responsibilities

    • Design, develop, test, and maintain scalable software solutions and cloud-native services.
    • Build and support healthcare applications, APIs, integrations, and platform capabilities.
    • Develop reliable, secure, and highly available systems running on Oracle Cloud Infrastructure (OCI).
    • Collaborate with product managers, architects, engineers, and operational teams to deliver customer-focused solutions.
    • Participate in system design, code reviews, troubleshooting, performance optimization, and operational excellence initiatives.
    • Contribute to automation, observability, security, and continuous delivery practices.
    • Support modernization efforts leveraging cloud technologies, healthcare interoperability standards, and AI-driven capabilities.
    Qualifications: We need to separate Minimum and Preferred maybe as

    Minimum Qualifications:

    then
    etc. Or we could combine into one list with headings inside

    . Use

    for prose. Let's do:

    Qualifications

    Minimum Qualifications:

    • 3+ years of experience in software engineering, application development, platform engineering, or related technical roles within a fast-paced technology environment.
    • Bachelor's degree in Computer Science, Engineering, related field or equivalent years of relevant experience
    • Experience developing enterprise software applications or cloud platforms.
    • Strong programming and software design skills.
    • Experience with OCI, AWS, Azure, or Google Cloud.
    • Experience with distributed systems, APIs, and cloud technologies.
    • Knowledge of software development lifecycle and engineering best practices.

    Preferred Qualifications:

    • Experience with healthcare technology or regulated industries.
    • Familiarity with healthcare interoperability standards.
    • Experience building large-scale SaaS platforms.
    • Knowledge of AI, machine learning, or data engineering solutions.
    • Strong problem-solving and communication skills.
    Skills:

    Skills

    • Oracle Cloud Infrastructure (OCI)