DirectJobHub
Jobs · Information Technology · Tennessee

Senior Core Infrastructure Engineer - OCI Product Catalog (Nashville-TN)

Oracle · Nashville, TN · 3 wk ago
Information Technology$79k–$210k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the job description. First, location line: "Location: Nashville, TN — onsite 5 days/week. Relocation assistance is available; this is not a remote position." This is location info; could be part of About the role? Probably we can include location in About the role paragraph. We need to avoid repeating job title as heading. The job title is Senior Core Infrastructure Engineer (IC3). Not to be used as heading. We need sections: About the role (maybe includes description of team, role overview). Responsibilities (list). Requirements (maybe qualifications). Qualifications (maybe separate). Skills (must-have). Benefits (list). Pay (range). Schedule (maybe onsite 5 days/week). Also maybe include relocation assistance. We must not include sections with filler like "commensurate with experience". Not present. We need to extract content. Let's extract: About the role: The OCI Product Catalog team builds platform services that define and manage OCI products and their associated metadata, including integrations with SKUs, metering, limits, product availability, and lifecycle management. The team is building a centralized product model and automation platform that enables OCI service teams to onboard, deploy, and manage products consistently across cloud environments while providing centralized control over product availability. We are looking for a Senior Core Infrastructure Engineer (IC3) with strong full-stack development experience to help design, build, and operate OCI Product Catalog. This is a hands-on engineering role spanning distributed backend services, APIs, automation, and web-based operator experiences. The engineer will own features end to end, from technical design and implementation through testing, deployment, observability, and production operation. Also location: Nashville, TN — onsite 5 days/week. Relocation assistance is available; this is not a remote position. We can include location and relocation in About the role paragraph. Responsibilities: The "Key Responsibilities" section with sub-bullets. We need to list them as
  • . The content includes many bullet points under categories: System Design & Architecture - System Scalability, System Reliability Design, System Reliability Performance, Correctness / Availability, Operational Troubleshooting & Incident Management, Compliance & Security, Automation & Change Management. We need to preserve all substantive info. So we can flatten them into list items, each bullet as a line. Might be long but okay. We should not include headings like "System Design & Architecture - System Scalability:" as separate headings; we just include as list items. We need to extract each bullet: Under System Design & Architecture - System Scalability: - Implements and contributes to the development for components of distributed systems that support horizontal and vertical scaling including leveraging distributed state management tools. - Optimizes code and/or systems for large-scale data processing in large-scale systems. - Implements scalability requirements for assigned components and reviews implementation of team members. - Leverages components of data plane platforms to handle large-scale data retrieval, storage, and processing. - Implements performance and load testing. System Design & Architecture - System Reliability Design: - Collaborates with team to build fault-tolerant components capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms. - Applies recovery oriented computing principles to design components that effectively handle service disruptions. - Implements retry mechanisms, circuit breakers, and timeouts to help handle network unreliability. System Design & Architecture - System Reliability Performance: - Implements tests and alarm configurations to proactively detect and address issues/failures. - Supports efforts to recover from failures by drafting and executing runbooks and operational procedures. - Builds and customizes dashboards, telemetry systems, and alerting mechanisms to monitor component health. System Design & Architecture - Correctness / Availability: - Designs and implements functional requirements and testing for assigned features within an existing system. - Implements tests scenarios (e.g., fault-injection, brown-out) to evaluate system correctness. - Implements standard data replication and synchronization techniques to maintain data integrity and availability. Operational Troubleshooting & Incident Management: - Diagnoses, debugs, and resolves issues in system components to support ongoing operation. - Implements basic strategies to prevent interruptions, ensuring no maintenance windows are required for customers and users when resolving issues. - Designs and implements automation scripts and tooling used to troubleshoot operational issues. - Participates in operational support rotations, assisting in incident responses and root cause investigations. Compliance & Security: - Applies advanced security measures to protect data and applications in multi-tenant environments, including encryption and access controls. - Implements remediation plans to continuously improve security. - Collaborates with the team to ensure cloud infrastructure complies with relevant industry standards and regulations and that documentation is up-to-date Automation & Change Management: - Maintains automation scripts and tools (e.g., Infrastructure as Code (IaC)) for managing cloud infrastructure. - Adheres to change management plans for patching, updating, and rolling back applications. Now Requirements: The "Qualifications" section includes a disclaimer about US based roles etc. But we need to separate Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Qualifications" section in the posting (with disclaimer). Also "MUST-HAVE SKILLS:" list. Also there is a "Qualifications" disclaimer and then "Range and benefit information..." etc. So we need to map. We have: Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements. Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $79,200 - $209,500 per year. May be eligible for bonus and equity. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity. Oracle US offers a comprehensive benefits package which includes the following: [list]. Then later: "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; we should remove. Also "As part of Oracle's onboarding process..." about biometric verification; that's maybe not boilerplate? It's about onboarding requirement; could be considered part of Qualifications? Might be considered procedural; but it's not EEO. Might be considered part of Qualifications? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The biometric verification is not exactly EEO but could be considered legal/onboarding requirement; not sure. Safer to keep? It's not application instruction; it's about onboarding. Might be considered part of Qualifications? I'd keep it as part of Qualifications maybe. But we need to separate Requirements vs Qualifications. The posting has "Qualifications" heading with disclaimer and then salary/benefits. There's also "MUST-HAVE SKILLS:" which could be Skills section. There's no explicit "Requirements" heading but we can infer requirements from the MUST-HAVE SKILLS and maybe from the description. However we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide what goes into Requirements vs Qualifications vs Skills. We have: - MUST-HAVE SKILLS: list of skills (Strong Java or comparable OOP experience, Backend service and API development experience, Distributed systems fundamentals, Experience designing and delivering production-quality software, Full-stack development experience, including modern web UI development, Strong debugging and problem-solving skills, Understanding of testing, observability, reliability, and operational readiness, Ability to independently own features from design through production.) That's clearly skills. Qualifications: The disclaimer about US based roles, immunization, drug testing, plus maybe the biometric verification requirement. Also maybe the location/onsite requirement? But location is separate. Requirements: Could be the experience expectations like "Strong full-stack development experience", "hands-on engineering role", etc. But those are already in About the role. Might be better to put Requirements as the list of mandatory qualifications (like years of experience, education). Not present. The posting does not have explicit requirements like degree, years. So maybe we skip Requirements section if no specific content. But we need to avoid empty sections. Thus we could have sections: About the role, Responsibilities, Skills, Benefits, Pay, Schedule. Possibly Qualifications (if we have content like disclaimer and biometric). But the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include Qualifications if we have content. What content qualifies for Qualifications? The disclaimer about US based roles, immunization/occupational health mandates, drug testing requirements. Also the biometric verification requirement. Also maybe the statement about "Range and benefit information provided in this posting are specific to the stated locations only US:" but that's more about Pay/Benefits. Thus we can put Qualifications: includes the disclaimer and the biometric verification note. But we also have "MUST-HAVE SKILLS:" which is Skills. Now Benefits: list of benefits from Oracle US offers a comprehensive benefits package which includes the following: Medical, dental, and vision insurance, including expert medical opinion Short term disability and long term disability Life insurance and AD&D Supplemental life insurance (Employee/Spouse/Child) Health care and dependent care Flexible Spending Accounts Pre-tax commuter and parking benefits 401(k) Savings and Investment Plan with company match Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation. 11 paid holidays Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours. Paid parental leave Adoption assistance Employee Stock Purchase Plan Financial planning and group legal Voluntary benefits including auto, homeowner and pet insurance We need to put that as
    • items. Pay: Hiring Range in USD from: $79,200 - $209,500 per year. May be eligible for bonus and equity. Schedule: Location says onsite 5 days/week. Also relocation assistance available; not remote. So schedule: onsite 5 days/week. We should not duplicate location in About the role? We can include location in About the role paragraph. Now we need to output only HTML fragment, no markdown fences. Let's craft:

      About the role

      The OCI Product Catalog team builds platform services that define and manage OCI products and their associated metadata, including integrations with SKUs, metering, limits, product availability, and lifecycle management. The team is building a centralized product model and automation platform that enables OCI service teams to onboard, deploy, and manage products consistently across cloud environments while providing centralized control over product availability. We are looking for a Senior Core Infrastructure Engineer (IC3) with strong full-stack development experience to help design, build, and operate

Similar jobs