OCI Senior Core Infrastructure Engineer - Nashville TN

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse the job description and extract relevant content. Let's identify sections: - About the role: maybe the initial paragraph describing location, relocation, remote work, description of work. Could be "About the role" or "Job Description". We'll use "About the role". - Responsibilities: there is a "Responsibilities" section later: "We’re looking for hands-on engineers...". Also earlier bullet-like sentences about design, develop, troubleshoot, etc. We'll combine. - Requirements / Qualifications: There's "Required Qualifications" and "Preferred Qualifications". Also "Qualifications" earlier: BS/MS, 7 years experience. We'll have a "Qualifications" section maybe split into Required and Preferred? The instruction: use headings for section headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have "Required Qualifications" and "Preferred Qualifications" as subheadings? But only allowed headings are those listed; we could use "Qualifications" for required and maybe "Preferred Qualifications" as a subsection under Qualifications? However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those exact headings. We can have "Qualifications" and inside we can list required and preferred as paragraphs or lists. Could also have "Skills" separate. We need to decide what content goes where. Let's extract: Location: Nashville, TN campus. Relocation allowance available, no remote work. Role description: Design, develop, troubleshoot and debug software programs for databases, applications, tools, networks etc. As a member of the software engineering division, you will take an active role in the definition and evolution of standard practices and procedures. You will be responsible for defining and developing software for tasks associated with the developing, designing and debugging of software applications or operating systems. Work is non-routine and very complex, involving the application of advanced technical/business skills in area of specialization. Leading contributor individually and as a team member, providing direction and mentoring to others. Also later: "The Oracle Cloud Infrastructure (OCI) team can provide you the opportunity to build and operate a suite of massive scale, integrated cloud services..." etc. That's more about team and mission. Also "What is IAM at OCI?" description. Also "Who are we seeking?" bullet-like paragraphs. Also "What are the biggest challenges for the team?" paragraph. Also "Career Level - IC3" appears multiple times. Also "Responsibilities" section: "We’re looking for hands-on engineers with expertise and passion in solving difficult problems in distributed systems and highly available services. As a Senior Software Engineer you will lead the software design and development for major components of this platform. You should be both a rock solid coder and a distributed systems generalist, able to dive deep into any part of the stack and low level systems as well as design broad distributed system interactions. You should have experience operating large cloud services and have good familiarity with operational tools. You should value simplicity and scale, work comfortably in a collaborative, agile environment, and be excited to learn. This role is based in Nashville TN so candidates who do not currently live in the Nashville area will need to relocate" Also "Qualifications Disclaimer:" etc. Then salary range and benefits. We need to extract Benefits: list of medical, dental, vision, disability, life insurance, etc. Also vacation accrual details, holidays, sick leave, parental leave, adoption assistance, ESPP, financial planning, group legal, voluntary benefits. Pay: "US: Hiring Range in USD from: $79,200 - $209,500 per year. May be eligible for bonus and equity." Schedule: Not explicitly mentioned. There's no schedule info like full-time, hours. Could infer full-time but not stated. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay and Benefits because they are stated. Schedule not stated, so we should not include Schedule section. Skills: Could be a section for technical skills like Java, J2EE, OOP, JWT, OAuth2, Okta, PL/SQL, etc. But we might incorporate into Qualifications. However we have a separate "Skills" heading allowed. We could create Skills section listing those specific technologies. But we must not invent or summarize away detail; we must preserve all substantive info. If we create Skills section, we need to ensure we include all skill-related details from the posting. The posting includes many specific skills under Required Qualifications and Preferred Qualifications. We could put them under Qualifications instead. But we have both Qualifications and Skills headings allowed; we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Skills into one Qualifications section, and not create a separate Skills unless there is distinct skill content not covered elsewhere. However the posting does have a list of specific technical skills; we could treat them as part of Qualifications. That seems fine. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not include Requirements heading if we use Qualifications. But we could also include Requirements as separate if we have content. However we have qualifications content; we could put under Qualifications. The instruction lists both Requirements and Qualifications as possible headings; we can choose either. To avoid thin sections, we can have Qualifications covering both required and preferred. Now we need to format with

headings,

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can condense into lists while preserving meaning. However we must not lose any detail. That's tricky: we need to include all specifics like "BS or MS degree or equivalent experience relevant to functional area. 7 years of software engineering or related experience." etc. We can put those as list items. We must not include boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the EEO statement, the accommodation request line, the "Oracle is an Equal Employment Opportunity Employer..." etc. Also remove "Career Level - IC3" duplicated lines? Might be considered metadata; but it's substantive? It's a career level; maybe we can keep it as part of Qualifications or About the role? It's not boilerplate; it's a job level. Could include in Qualifications as a note. But we can also drop if considered minor metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Career level maybe minor metadata; we could fold into a short p or drop. Safer to drop? But it's substantive info about role level. However we can include in a paragraph under About the role or Qualifications. I'd include it as a short p. Also we need to remove the "What is IAM at OCI?" heading? That's content; we can keep as paragraph. We must not include duplicated lines. We'll need to deduplicate. Let's extract all substantive sentences and bullet points. I'll go through the text and note each piece. Original text: "Job Description This position is based in our Nashville, TN campus. Relocation allowance available no remote work Design, develop, troubleshoot and debug software programs for databases, applications, tools, networks etc. As a member of the software engineering division, you will take an active role in the definition and evolution of standard practices and procedures. You will be responsible for defining and developing software for tasks associated with the developing, designing and debugging of software applications or operating systems. Work is non-routine and very complex, involving the application of advanced technical/business skills in area of specialization. Leading contributor individually and as a team member, providing direction and mentoring to others. BS or MS degree or equivalent experience relevant to functional area. 7 years of software engineering or related experience. The Oracle Cloud Infrastructure (OCI) team can provide you the opportunity to build and operate a suite of massive scale, integrated cloud services in a broadly distributed, multi-tenant cloud environment. OCI is committed to providing the best in cloud products that meet the needs of our customers who are tackling some of the world’s biggest challenges. We offer unique opportunities for smart, hands-on engineers with the expertise and passion to solve difficult problems in distributed highly available services and virtualized infrastructure. At every level, our engineers have a significant technical and business impact designing and building innovative new systems to power our customer’s business critical applications. What is IAM at OCI? Identity and Access Management (IAM) allows users to control who has access to their cloud resources. As part of the Cloud Platform organization, the team is responsible for the design and build of core services that are utilized by internal and external customers alike. Who are we seeking? We are looking for engineers with distributed systems experience. You should have experience with the design of major features and launching them into production. You’ve operated high-scale services and understand how to make them more resilient. You work on most projects and tasks independently. You have experience working with services that require data to travel long distances, but have to abide by compliance and regulations. You stay up at night thinking about how to protect the service from upstream dependencies. The ideal candidate will be technically strong and get a lot done – you’ve worked on services that are highly available, scalable, and redundant. You understand that simple systems are easier to operate and troubleshoot. You can balance speed and quality with iteration and incremental improvements. You’ve made life easier for other developers and have motivated your teams to make both process and service improvements with your ability to automate and instrument properly to get the right data. You understand operational excellence and how to instill a culture of being proactive with your teammates. You find anomalies in graphs that didn’t trip any alarms and root cause problems before they become real problems. The person in this role will get a lot done on a daily basis, drive tactical execution of features and projects, and own feature design. What are the biggest challenges for the team? The biggest challenges for the team are reliability and performance. The growth of the business is driving us to improve the ability of our systems to scale out and handle traffic patterns that are several orders of magnitude greater than what we can support today. We understand that software is living and needs investment. The challenge is making the right tradeoffs, communicating those decisions effectively, and crisp execution. We need engineers who can build services that handle millions of requests per second. We need engineers who can figure out how we can survive regional data center outages and protect our customers. We need engineers who can build services that enable us to offer even more options to customers and contribute to the overall growth of Oracle Cloud. Required Qualifications Hands-on experience building and operating end-to-end systems and services.Experience driving security, documentation, and UX reviews; partnering with Product Managers throughout the launch lifecycle.Experience developing service-oriented architectures (SOA) and RESTful web services.Strong expertise in Java, J2EE, and object-oriented programming principles.Experience with JWT, OAuth2, Okta, and other authentication and authorization frameworks.Strong knowledge of Core Java, including concurrency concepts, concurrency patterns, and thread-safe code.Strong Oracle PL/SQL development experience, including complex stored procedures, functions, packages, triggers, and bulk-processing routines for high-volume transactional systems.Proven production database support experience, including SQL performance troubleshooting, locking/deadlocks, connectivity and connection-pool issues, scheduled jobs, and collaboration with DBAs on availability, access, and recovery.Experience with at least one scripting language for automation, proof-of-concept development, or command-line tools. Preferred Qualifications Hands-on experience developing and operating services on public cloud platforms, such as AWS, Azure