Oracle Fusion ERP Developer (Senior Principal Applications Analyst)

We need to output HTML fragment with sections: About the role? The description includes "Job Description" then paragraphs. We need to extract sections: About the role (maybe from first paragraph?), Responsibilities, Qualifications, Benefits, Pay, Schedule. Also maybe "About Us" but not required. We must only include sections with real specific content. Avoid filler like "commensurate with experience". We have Pay: salary range given. Schedule: "Work schedule will be 4/10s Monday through Thursday (subject to change)." Benefits: described in About Us paragraph: "MSTS offers our full-time employees highly competitive salaries and benefits packages including medical, dental, and vision; both a pension and a 401k; paid time off and 96 hours of paid holidays; relocation (if located more than 75 miles from work location); tuition assistance and reimbursement; and more." That's specific enough. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. Do not put Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all responsibilities as list items. Qualifications as list? The qualifications section includes many bullet-like sentences; we can format as

  • . Must preserve all details. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also "MSTS is an Equal Opportunity Employer..." etc. Also "MSTS maintains a substance abuse policy..." maybe keep? It's part of qualifications? It's about pre-placement physical exam, drug screen, etc. That's substantive? It's about requirements. Might keep as part of qualifications or responsibilities? It's more like a requirement. We'll keep as part of qualifications maybe as a list item. We need to avoid duplication: there are duplicated sentences about ability to multi-task etc. We should keep only one instance? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines: we should not repeat duplicated lines? It says remove duplicated lines. So we should deduplicate. So we need to identify duplicate sentences and keep only one occurrence. Let's extract sections. First paragraph: "We are looking to hire an Oracle Fusion ERP Developer (Senior Principal Applications Analyst) at our North Las Vegas office. The Oracle Fusion ERP Developer will be responsible for business process analysis, design, development, configuration, implementation and technical support of the Oracle Fusion procurement functions including procurement bolt-on applications. This position will also provide some support for financial and project accounting functions. This position does not manage staff. The position reports to the Enterprise Application Solutions manager. The position requires strong technical experience supporting Oracle Fusion Procurement functions, reports, and Apex applications." That's about the role. We'll put under

    About the role

    with

    containing that paragraph (maybe split into multiple sentences but we can keep as one

    ). Next: Responsibilities section: list of key responsibilities. We'll create

    Responsibilities

    then
    • each. List them: - Prepare test plans and test data; execute tests, analyze results, and correct code to ensure compliance with specifications and business requirements. - Provide advanced Tier 2/3 application support, performing root cause analysis and resolving complex technical issues. - Administer enterprise applications by supporting users, translating business requirements into enhancements, configuring and testing changes, and maintaining application security and permissions. - Provide backend support for enterprise server environments hosting multiple applications, including coordination with infrastructure teams. - Work extensively with SQL Server and Oracle databases to support application functionality, reporting, performance, backup, and data integrity. - Manage SSL certificates and ensure secure application communications. - Identify, report, and perform or assist in the remediation of cybersecurity threats and vulnerabilities affecting applications and servers. - Serve as a liaison between IT and business support teams, ensuring clear communication and alignment on priorities and solutions. - Lead complex projects involving other IT teams, departments, vendors, or consultants. - Provide technical guidance, coaching, and mentoring to less experienced staff. - Use tools such as Azure DevOps, IIS, and ServiceNow to manage development, deployments, incidents, and operational work. - Develop and maintain technical documentation and contribute to application standards and best practices. - Perform other duties assigned by Management. Check for duplicates: none. Qualifications: We need to list qualifications. Let's extract: - Due to the nature of our work, US Citizenship is required for all positions. - Bachelor’s degree in a computer related field or equivalent computer-related experience with at least 12 years of relevant, progressively responsible experience. - 12 Years of experience in the solution design, implementation, and ongoing support of Oracle EBS and Oracle Fusion Applications and Integrations. - 5 Years of experience in both Application development and Integration using Oracle APEX. - 5 Years of Technical Expertise Encompassing Fusion APIs, FBDI, ADF DI Loads, BIP and OTBI Reports. - Strong knowledge and experience in Oracle Fusion modules and other Oracle Fusion products with significant experience in Procurement modules. - Understanding basic Oracle Fusion architecture such as Oracle naming and setup conventions, file system layout, server architecture, etc. - Must have experience in Procurement Services, iSupplier, Procurement Contracts, Procurement Sourcing. - Skilled in ESS Jobs, Flex Fields (DFF, EFF, KFF), Lookups, Value sets, and Fusion Apps functional setup manager configurations. - Oracle EBS 12.1.3 developer background is a plus. - Oracle Fusion cloud developer background with expert skill in: Procurement Supplier Portal Financials and Project Management modules experience is a plus - Oracle SQL BIP and OTBI reports including data modules - PL/SQL Fusion APIs and FBDI - APEX experience is a plus - Oracle Integration Cloud (OIC) is a plus - Oracle Analytics Cloud (OAC) is a plus - Oracle Business Process Module is a plus - Java experience is a plus - Experience using My Oracle Support, OTN and other Oracle-provided support resources. - Command of a broad range of the most advanced technical principles, concepts, and theories in a broad range of disciplines in software development. - Must possess excellent customer service skills. - Knowledge of application security, permissions, SSL certificates, and vulnerability management. - Strong analytical, troubleshooting, testing, and problem-solving skills. - Ability to multi-task and maintain organization in a fast-paced, changing environment. - Ability to work independently while supporting multiple applications and priorities. - Ability to accept responsibility in new areas and have the level of technical and analytical skills that will provide successful outcomes to those assignments. - Ability to accept multiple responsibilities and manage work to ensure deadlines and milestones are met. - Ability, aptitude and desire to continually learn about new tools and technology and have the ability to evaluate the best solution for stated problems. - Ability to deliver quality, maintainable solutions. - Ability to use a systems engineering approach when implementing new solutions or modifying existing solutions. - Ability to use standard office equipment, mobile devices, and security-related hardware or software. - Ability to understand and comply with policies, procedures, laws, and regulations while maintaining strict confidentiality. - Ability to communicate effectively in English, both verbally and in writing, including preparing clear technical documentation and reports. - Ability to meet the physical requirements necessary to safely and effectively perform assigned duties. - The primary work location will be at the North Las Vegas facility on Losee Road. - Work schedule will be 4/10s Monday through Thursday (subject to change). - Pre-placement physical examination, which includes a drug screen, is required. - MSTS maintains a substance abuse policy that includes random drug testing. - Must possess a valid driver’s license. - Ability to obtain a HSPD-12 Personal Identity Verification credential under the Department of Energy Order 206.2, ‘ Identity, Credential, and Access Management ,’ and Supplemental Directive NNSA SD 206.2, ‘ Implementation of Personal Identity Verification for Uncleared Contractors ’. - Annual salary range for this position is: $142,438.40 - $220,771.20. - Starting salary is determined based on the position market value, the individual candidate education and experience and internal equity. - MSTS offers our full-time employees highly competitive salaries and benefits packages including medical, dental, and vision; both a pension and a 401k; paid time off and 96 hours of paid holidays; relocation (if located more than 75 miles from work location); tuition assistance and reimbursement; and more. We need to separate Pay, Schedule, Benefits sections. So we should extract those specifics. Pay: salary range and starting salary determination. Schedule: work schedule 4/10s Monday through Thursday (subject to change). Benefits: the paragraph about benefits. We also have location: primary work location at North Las Vegas facility on Losee Road. Could be part of About the role or maybe a separate section? Not required heading; we can include in About the role paragraph. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does. We need to avoid filler like "commensurate with experience". Not present. Now we need to deduplicate: there are duplicate sentences about ability to multi-task etc. We see "Ability to multi-task and maintain organization in a fast-paced, changing environment." appears twice. We'll keep only one. Also "Ability to accept multiple responsibilities and manage work to ensure deadlines and milestones are met." appears once. Also "Ability to work independently while supporting multiple applications and priorities." appears once. Now we need to format Qualifications as list items (
      • ) but we might want to split into logical groups? The instruction: Use
        • for any list of duties/requirements/benefits. So qualifications is a list of requirements; we can use
          • . However there are many items; we can keep them as list. We also need to include About Us? Not required as a heading; but we could include as

            About Us

            if we want to keep that info. The instruction: "include a section ONLY when the posting has real, specific content for it". About Us has specific content. Should we include? It's not one of the prescribed headings but we could still use

            About Us

            . The list of headings given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About Us but we could still include if we want. However they said "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." Including About Us may be okay but could be considered thin? It's a paragraph about mission. Might be okay to include. However the instruction also says "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." About Us is not minor metadata; it's substantive. I'd include it as a section. But we must ensure we don't create sections with filler. About Us paragraph is substantive. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule, About Us (maybe). Could also include Skills? Not needed. We need to ensure we don't include duplicated lines. Let's check qualifications list for duplicates: I see "Ability to multi-task and maintain organization in a fast-paced, changing environment." appears twice; we will keep one. Also "Ability to accept multiple responsibilities and manage work to ensure deadlines and milestones are met." appears once. Now we