Senior Oracle EBS Manufacturing Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No boilerplate. Remove EEO etc. Must preserve all substantive info. Let's parse posting: First paragraph: "Edgewater is seeking a Senior Oracle EBS Manufacturing Developer to support a major national laboratory. The role involves configuring, developing, testing, and deploying solutions with Oracle E-Business Suite (EBS) Discrete and/or Process Manufacturing Modules, including Inventory, BOM, MRP, Cost Management, WIP, ASCP, and Quality. The candidate will also resolve Tier 2 incident tickets related to Oracle EBS manufacturing modules, support the implementation of a new Oracle Manufacturing solution for manufacturing facility, and conduct feasibility studies and requirements gathering. Additionally, responsibility extends to assisting with the integration of third-party tools such as FactoryWorks, Primavera P6, and Windchill PDMLink with Oracle EBS." That's about the role. Then "Responsibilities" heading appears in posting: "Responsibilities Collaborate with team members to investigate, plan, gather requirements, design, develop, test, document, analyze problems, and support software systems and applications. Support the design of software tools and subsystems that support reuse and domain analysis Assisting Applications Engineers and Programmers in interpreting software requirements and design specifications coding, integrating, and testing software components to ensure they meet project objectives. Analyze functional business applications and design specifications across various areas, including finance, accounting, personnel, manpower, logistics, and contracts. Develop block diagrams and logic flow charts, translating detailed designs into computer software, testing, debugging, and refining software to produce high-quality products. Prepare comprehensive documentation and enhance software to improve efficiency while providing technical direction to programmers to ensure project deadlines are met. Experience in information system design, including application programming on large-scale database management systems and the development of complex software to satisfy design objectives." That's a block of responsibilities. Then "Qualifications" heading: "Qualifications BS in relevant discipline plus minimum 7 years or more years of directly related experience that demonstrates the knowledge, skills, and ability to perform the duties of the job. Candidate must be able to obtain and maintain a DOE Q Clearance US Citizenship is required Preferred candidate would reside in the Albuquerque area" Then "Required Skills:" list. Then "Desired:" list. Then "About Us:" paragraph about company. We need to decide sections: About the role (we have content). Responsibilities (we have content). Requirements? The posting has "Qualifications" and "Required Skills" and "Desired". Could combine into Requirements and Skills sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications? They list both as possible headings. But we should avoid duplication. Probably we can have "Qualifications" for education/clearance etc., and "Skills" for required/desired skills. "Requirements" maybe could be used for mandatory requirements like clearance, citizenship, location? But we already have qualifications. Let's follow typical: Qualifications (education, experience, clearance, citizenship, location). Skills (technical skills). Requirements maybe not needed if we already have qualifications. But we could include Requirements for mandatory items like DOE Q Clearance, US Citizenship, location preference. However qualifications already covers that. To avoid thin sections, we can combine qualifications and requirements into one "Qualifications" section. And have "Skills" section for required/desired skills. We also need Benefits, Pay, Schedule: posting does not mention any. So we omit those sections. We must not include boilerplate like About Us? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed as boilerplate but it's company description. Might be considered boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Us paragraph is substantive about company but not about the job. Might be considered not needed? Usually they'd want to keep it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us is not those. It's not prohibited. However they said "Prefer a few substantive sections over many thin ones." Including About Us could be a section but we don't have a heading for it in list. Could we add a section "About the company"? Not in allowed headings list. Probably we should omit About Us to keep focus on job. The instruction didn't forbid it but they gave list of headings to use; we could add other headings but 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 but not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add About Us. Thus output sections: About the role, Responsibilities, Qualifications, Skills. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Use

for prose,

• for lists. We need to avoid repeating job title as heading. Already not. We need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now craft HTML. First, About the role: combine first paragraph. Paragraph: "Edgewater is seeking a Senior Oracle EBS Manufacturing Developer to support a major national laboratory. The role involves configuring, developing, testing, and deploying solutions with Oracle E-Business Suite (EBS) Discrete and/or Process Manufacturing Modules, including Inventory, BOM, MRP, Cost Management, WIP, ASCP, and Quality. The candidate will also resolve Tier 2 incident tickets related to Oracle EBS manufacturing modules, support the implementation of a new Oracle Manufacturing solution for manufacturing facility, and conduct feasibility studies and requirements gathering. Additionally, responsibility extends to assisting with the integration of third-party tools such as FactoryWorks, Primavera P6, and Windchill PDMLink with Oracle EBS." Make that a

  . Responsibilities: we have a block. Need to break into list items? The instruction: Use

  • for any list of duties/requirements/benefits. The responsibilities block is a paragraph with many sentences; could be turned into list items for each duty. But we could keep as

    if not a list. However it's a list of duties; better to make

    • . Let's split sentences: - Collaborate with team members to investigate, plan, gather requirements, design, develop, test, document, analyze problems, and support software systems and applications. - Support the design of software tools and subsystems that support reuse and domain analysis. - Assisting Applications Engineers and Programmers in interpreting software requirements and design specifications coding, integrating, and testing software components to ensure they meet project objectives. - Analyze functional business applications and design specifications across various areas, including finance, accounting, personnel, manpower, logistics, and contracts. - Develop block diagrams and logic flow charts, translating detailed designs into computer software, testing, debugging, and refining software to produce high-quality products. - Prepare comprehensive documentation and enhance software to improve efficiency while providing technical direction to programmers to ensure project deadlines are met. - Experience in information system design, including application programming on large-scale database management systems and the development of complex software to satisfy design objectives. Note some sentences have grammar issues but we preserve as is. Now Qualifications: content: "BS in relevant discipline plus minimum 7 years or more years of directly related experience that demonstrates the knowledge, skills, and ability to perform the duties of the job. Candidate must be able to obtain and maintain a DOE Q Clearance US Citizenship is required Preferred candidate would reside in the Albuquerque area" We can make a

      with that text. Could also split into list but it's fine. Now Skills: we have Required Skills list and Desired list. We'll combine into a

      • maybe separate headings? But we only have Skills section. Could include both required and desired as list items, maybe mark with (Required) or (Desired). But we must preserve all detail. Let's list each item. Required Skills: - Experience with Oracle E-Business Suite (EBS) Discrete and/or Process Manufacturing Modules - Understanding of EBS Inventory-to-Cost-Accounting and Plan-to-Produce processes - Experience with the EBS modules Inventory, WIP, BOM, Routing, and Cost Management - Familiarity with manufacturing costing and accounting distributions - Strong SQL, for troubleshooting and reporting - Strong PL/SQL, for process automation and interfaces/integrations - Familiarity with EBS concurrent processing, open interfaces, and APIs - Experience troubleshooting transaction, costing, and accounting issues Desired: - APEX experience - Reporting tools (Oracle Reports, Power BI, SSRS) - EBS Forms personalization and customization - Experience with related Oracle modules: Engineering, Quality, Material Requirements Planning, Subledger Accounting We'll put all as list items, maybe prefix with [Required] or [Desired] but that adds info not originally there; better to keep as is and maybe separate with a comment? But we cannot add extra info not in posting. We could just list them all; the distinction is lost but still all content present. However we could keep two subheadings inside Skills section using

        ? Not allowed; only h3 for section headings. Could use

        to note "Required Skills:" then list, then

        "Desired:" then list. That preserves the distinction without adding new info. Use

        for the labels, then

        • for each list. Thus Skills section:

          Required Skills:

          ...

          Desired:

          ...
          Now ensure we don't include any boilerplate like "About Us". Also remove duplicated lines. There's no duplication. Now output HTML fragment. Let's craft:

          About the role

          Edgewater is seeking a Senior Oracle EBS Manufacturing Developer to support a major national laboratory. The role involves configuring, developing, testing, and deploying solutions with Oracle E-Business Suite (EBS) Discrete and/or Process Manufacturing Modules, including Inventory, BOM, MRP, Cost Management, WIP, ASCP, and Quality. The candidate will also resolve Tier 2 incident tickets related to Oracle EBS manufacturing modules, support the implementation of a new Oracle Manufacturing solution for manufacturing facility, and conduct feasibility studies and requirements gathering. Additionally, responsibility extends to assisting with the integration of third-party tools such as FactoryWorks, Primavera P6, and Windchill PDMLink with Oracle EBS.

          Responsibilities

          • Collaborate with team members to investigate, plan, gather requirements, design, develop, test, document, analyze problems, and support software systems and applications.
          • Support the design of software tools and subsystems that support reuse and domain analysis.
          • Assisting Applications Engineers and Programmers in interpreting software requirements and design specifications coding, integrating, and testing software components to ensure they meet project objectives.
          • Analyze functional business applications and design specifications across various areas, including finance, accounting, personnel, manpower, logistics, and contracts.
          • Develop block diagrams and logic flow charts, translating detailed designs into computer software, testing, debugging, and refining software to produce high-quality products.
          • Prepare comprehensive documentation and enhance software to improve efficiency while providing technical direction to programmers to ensure project deadlines are met.
          • Experience in information system design, including application programming on large-scale database management systems and the development of complex software to satisfy design objectives.