- Company Name
- Central Point Partners
- Job Title
- Technical Oracle EBS Developer
- Job Description
-
<think>
Okay, so the user wants me to normalize a job description into a concise mini-job profile for job matching. Let me start by understanding the requirements. They specified that I need to exclude company details, location, benefits, and fluff. The output should only include Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, and Required Education & Certifications. It needs to be factual, concise, ATS-friendly, and globally neutral. Also, the summary should be in English, translating if needed. Max 500 words.
First, I'll parse the original job description. The job title is "Technical Oracle EBS Developer". The job description mentions that it's a contract-to-hire position, only for GC and USC candidates, located in Detroit metro area, hybrid work 4 days remote. The manager is looking for a senior developer with specific versions of Oracle EBS, PL/SQL, Shell Scripting, etc.
For the Role Summary, I should highlight the role's purpose without the company specifics. Maybe something like providing technical support and developing systems with Oracle EBS. The expectations might be the candidate's experience and skills.
Key Responsibilities: They mention analyzing, designing, developing systems, technical support, knowledge of tools, industry trends, training, project leadership. Need to condense these into bullet points without fluff.
Required Skills: PL/SQL, Shell Scripting, Oracle EBS versions R12 and above, SQL Loader, BI Publisher, XML, Unix shell scripting, Oracle Apex. Also, skills like analytical, troubleshooting, communication.
Preferred Qualifications: OAF, J-Developer, REST APIs, web services, integrations with SAAS (like Salesforce), Google Cloud, interpersonal skills, multi-platform experience, balancing development and support roles, project experience in business segments.
Education: Bachelor's degree or equivalent experience.
I need to make sure that all the key points from the job description are covered without mentioning the company name, location specifics beyond Detroit metro, and avoid benefits or contract terms like C2C. Also, ensure that it's ATS-friendly, meaning using standard terms that applicant tracking systems can pick up.
Let me structure each section. The Role Summary should be a short paragraph. Expectations can be bullet points with experience and location. Key Responsibilities in bullet points. Required Skills as bullet points. Education as a bullet. Preferred Qualifications as another section but marked as preferred.
Check for any fluff. The original mentions things like hybrid work, 4 days remote, but we can remove company details like that. Wait, the user said to exclude location, so even though the original restricts to Detroit, the user wants that excluded. Wait, no: "Only candidates who are local to Michigan (Detroit Suburb) will be considered." But the instructions say to exclude location. Hmm. The user says "Exclude company details, location, benefits, or fluff." So location must be excluded. So even the Detroit restriction isn't mentioned.
Wait, but the user says "Exclude company details, location..." So even if the job requires you to be local, I shouldn't include that in the summary. So the Expectations under the Role Summary may need to avoid that. Interesting. The user's instruction is to exclude location. So the manager's note about location is not included.
Similarly, the contract-to-hire and GC/USC are part of the original job description, but as per instructions, those are considered company details or fluff? The user says to exclude such details. So that info isn't part of the mini-profile.
So the Role Summary is focused on the role itself. The Expectations are the experience and skills required. Let me start drafting each section.
Job Title: Technical Oracle EBS Developer
Role Summary: Provide technical support and expertise in Oracle EBS systems, focusing on financial applications and related technologies. Lead system analysis, design, and development to meet user requirements while maintaining industry knowledge and training resources.
Expectations: Minimum 5 years of experience with Oracle EBS Financials (3+ years in technical roles), in-depth technical knowledge of Oracle EBS R12, PL/SQL, Unix shell scripting, SQL Loader, BI Publisher, XML. Bachelor's degree or equivalent experience required.
Key Responsibilities:
- Develop and maintain Oracle EBS systems based on user specifications.
- Solve technical issues related to hardware and software.
- Utilize technical tools for development and support.
- Stay current with industry trends relevant to client needs.
- Provide technical guidance to junior staff as needed.
- Lead projects and fulfill additional assigned duties.
Required Skills:
- Strong PL/SQL and SQL knowledge.
- Proficiency in Unix shell scripting.
- Experience with Oracle EBS R12 (12.0.x) or newer versions.
- Technical skills in SQL Loader, workflow, BI Publisher, XML.
- Oracle Apex development experience.
- Analytical problem-solving and communication skills.
Required Education & Certifications:
- Bachelor's degree in a relevant field. 5+ years related experience (or 4 additional years as substitute).
Preferred Qualifications:
- OAF and J-Developer experience.
- Familiarity with REST APIs, web services, event-driven development.
- Integration expertise between Oracle EBS and SaaS platforms (e.g., Salesforce).
- Knowledge in Google Cloud environments.
- Strong interpersonal and multi-platform teamwork abilities.
- Experience balancing development and support roles across business segments.
Wait, let me check if I included all required elements. The original required: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. Preferred Qualifications were in the job description, but the user didn't mention including them. Wait, the instruction says "Provide a concise summary for job matching. Max 500 words." But the user's output instructions include Required Skills and Required Education, but maybe preferred qualifications can be listed under their own section. However, the output template includes Required Skills and Required Education, but not a "Preferred" section. Wait, the user says "Required Skills, Required Education & Certifications" – so preferred qualifications might go under another section. But the example user provided in their query (the sample input) includes "Preferred Qualifications" as part of the output. Wait, looking at the user's example input:
The user's example (the one they provided) includes a "Basic Qualifications" and "Preferred Qualifications". However, their output should follow the structure: Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
So perhaps in the output, the preferred qualifications don't need to be included unless specified. Wait, the user's instruction says "Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So the preferred qualifications are part of the job description but are not in the output structure. Therefore, the user wants to exclude them. However, the sample input from the user has a long list of preferred qualifications, and perhaps in the mini-job profile, these should be omitted. Wait, but perhaps the user wants a "Required Skills" and "Required Education" and the preferred ones as part of the Key Responsibilities? Or no. Wait, the user's instruction says to exclude fluff. The preferred qualifications might be considered as "fluff," but since they are part of the job description, maybe they should still be included. Also, the user wants a concise summary for job matching, which typically includes all the necessary criteria, required and preferred. But the output structure as per the user's instruction does not have a "Preferred Qualifications" section. So perhaps the user wants to include them in the relevant sections. For example, some of the preferred items might be moved to Required Skills, but since the job description says "preferred," maybe they should be listed under another section. But the user's output structure doesn't have that. Hmm. Maybe it's better to include only the required parts. But that's not accurate because job seekers need to know the preferred qualifications. However, the user might be okay with including the preferred ones if they can be categorized under the existing sections.
Looking back at the user's own example, they have:
In their sample input, the output includes:
Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
In the original job description, the preferred qualifications are things like OAF, J-Developer, REST API, etc. But the user wants the output to include only the required sections. However, for job matching, it's better to include preferred qualifications as part of the skills or responsibilities.
Wait, the user says: "Provide a concise summary for job matching. Max 500 words."
Since the output is for job matching, it might be valuable to include preferred qualifications to help with better matching. But the user's instruction says to output only the specified sections. However, the instruction says "Provide a concise summary for job matching." So perhaps the preferred qualifications should be included, but in where?
Looking back at the user's example structure: the output includes Required Skills and Required Education. The preferred qualifications in the sample input (like knowledge of Google Cloud) are part of the preferred section. But in the output, they are to be omitted because the user's output structure doesn't mention including them and since they are preferred, not required.
But the user says "Required Skills" should be included. So only the skills that are required should be in that section. The preferred ones can be omitted, but maybe in the Key Responsibilities or other sections. However, since the user's output structure doesn't have a place for preferred qualifications, they should be excluded as per the instruction: "Exclude... fluff."
So the final output should only have the required sections. Therefore, the preferred qualifications (like OAF, J-Developer, REST APIs, etc.) are part of the original job description but are not included