Senior Oracle APEX Developer II
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove the "Contact Government Services, LLC is an Equal Opportunity Employer..." and the AI note etc. Also remove the links and email etc? Those might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The email and website might be considered contact info; not explicitly prohibited but could be considered contact info; but they said preserve ALL substantive information; contact info maybe substantive? However they said remove application instructions. The email and website could be considered contact info for more info; but they said "For more information about CGS please visit: https://www.cgsfederal.com or contact:Email: [email protected]" That's maybe not essential but could be considered contact info. However they didn't explicitly say to remove contact info; but they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact info is not those. Might keep? But they also said "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." The email/website could be considered minor metadata; maybe we can drop it. Safer to drop contact info and links as they are not core job description. Also the salary line is at end: "#CJ $149,760 - $216,320 a year". We'll include Pay section.
Now we need to decide sections:
- About the role: paragraph(s) describing role and environment.
- Responsibilities: list of duties (the "Skills and attributes for success" bullet list). Could also include some responsibilities from earlier paragraph? But we will treat that list as responsibilities.
- Qualifications: the bullet list under "Qualifications-". Also maybe include "Ideally, you will also have:" as preferred qualifications; could be part of Qualifications or separate "Preferred Qualifications". But we only have headings: Qualifications, Skills, Benefits, Pay, Schedule. We could put preferred qualifications under Qualifications as additional bullet points, maybe separate with note? But we must not invent headings. Could add a
note "Preferred qualifications:" then list. But better to keep Qualifications section include both required and preferred? Might be okay.
- Skills: maybe we could separate technical skills list? But we already have responsibilities list includes many technical skills. Could create Skills section for technical skills like Oracle APEX, PL/SQL, etc. However we must not create thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine responsibilities and skills into one section? But we have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include.
We have substantive content for About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills (technical skills) but we could merge into Responsibilities. However the responsibilities list already includes many skills; but we could still have a Skills section summarizing technical skills (e.g., Oracle APEX, PL/SQL, JavaScript, etc.) but that would be thin. Better to not include Skills if we can incorporate into Responsibilities.
Requirements: maybe we could treat the qualifications as Requirements. But we have both Qualifications and Requirements headings allowed. The posting has "Qualifications-" section. Could map that to Qualifications. Requirements could be things like "U.S. Citizen", "Ability to obtain and maintain a public trust security clearance", "Experience with secure network programming..." etc. Those are also in qualifications list. So we could just have Qualifications section covering all.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to ensure we don't include empty sections.
Now we need to format.
Let's extract About the role paragraph(s). We'll combine into one
.
Paragraph: "Employment Type: Full-Time, Entry-Mid Level Department: Information Technology CGS is hiring a Senior Oracle APEX Developer to support a range of IT services, including software application support, enterprise infrastructure support, service desk, ITSM, deskside support, workstation engineering and maintenance, telecommunications and mobility engineering services, managed print services, Active Directory services, and video conferencing. The ideal candidate will be personable and articulate and will focus on making sure that the customer’s needs are met quickly and effectively. The successful candidate will be a self-starter who can work with limited supervision. Excellent communication skills are required to effectively interface with customers to understand requirements and mission needs, and then be able to translate them into actions. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities."
We might want to remove "Employment Type: Full-Time, Entry-Mid Level Department: Information Technology" as metadata? Could fold into short
or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could keep that as a short
before About the role? But we already have About the role heading; we could include that sentence as part of About the role paragraph. It's okay.
Now Responsibilities: list items.
We need to extract each bullet from the "Skills and attributes for success-" list.
Let's list them:
- Work at the direction of the program manager to support the full lifecycle development of custom Oracle Applications, primarily using the Oracle APEX toolset.
- Perform advanced use of Oracle APEX 4.0 and above.
- Perform work with Oracle Integrated Development Environments such as Quest Toad and Oracle SQL Developer.
- Design and manipulate web content dynamically using JQuery, Ajax, JavaScript, CSS, and HTML.
- Create dynamic reports within the Oracle APEX environment. Provide support in the advanced use of Oracle Database products version 11 and above.
- Provide support for Oracle database objects – tables, indexes, directories, sequences, triggers, etc.
- Provide support with PL/SQL, Java, Windows PowerShell, and Unix shell scripting with familiarity with built-in PLSQL packages and procedures.
- Provide support with storage, efficient retrieval, and manipulation of unstructured data (BLOBs, CLOBs, JSON, XMLType) in an Oracle environment.
- Integrate and manage BI Publisher templates and web Services.
- Successfully deliver enterprise-level workflow-centric applications.
- Build logical functions and algorithms to automate business processes.
Note some sentences have two clauses separated by period; we keep as one bullet.
Now Qualifications: list from "Qualifications-" bullet list.
Let's extract:
- Bachelor’s degree with 8+ years experience. A High School diploma with additional years of experience and/or relevant certifications may be considered in lieu of a degree.
- U.S. Citizen.
- Ability to obtain and maintain a public trust security clearance.
- Experience with secure network programming in an Oracle environment; use of security certificates, HTTPS callouts, etc.
- Experience with full lifecycle development of custom Oracle Applications, including the Oracle APEX toolset.
- Experience with the use of Oracle Integrated Development Environments such as Quest Toad and Oracle SQL Developer.
- Experience with JQuery, Ajax, JavaScript, CSS, and HTML.
- Experience with PL/SQL, Java, Windows PowerShell, and Unix shell scripting with familiarity with built-in PLSQL packages and procedures.
- Experience with storage, efficient retrieval, and manipulation of unstructured data (BLOBs, CLOBs, JSON, XMLType) in an Oracle environment.
- Experience establishing goals and meeting project plan objectives.
- Must be able to write and maintain system documentation on work products.
- Excellent communication and teamwork skills.
- Agile development experience.
- Customer interface experience.
Then "Ideally, you will also have:" list:
- Experience with Oracle Database products version 11 and above.
- Experience with Oracle Forms and Reports version 10G or higher.
- Experience with Oracle APEX 4.0 and above.
- Experience troubleshooting operational issues.
- Government contracting experience, particularly with the DOJ.
- Current DOJ Clearance.
We could include
for prose. We must not repeat job title as heading. No Job ID. We must preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove the "Contact Government Services, LLC is an Equal Opportunity Employer..." and the AI note etc. Also remove the links and email etc? Those might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The email and website might be considered contact info; not explicitly prohibited but could be considered contact info; but they said preserve ALL substantive information; contact info maybe substantive? However they said remove application instructions. The email and website could be considered contact info for more info; but they said "For more information about CGS please visit: https://www.cgsfederal.com or contact:Email: [email protected]" That's maybe not essential but could be considered contact info. However they didn't explicitly say to remove contact info; but they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact info is not those. Might keep? But they also said "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." The email/website could be considered minor metadata; maybe we can drop it. Safer to drop contact info and links as they are not core job description. Also the salary line is at end: "#CJ $149,760 - $216,320 a year". We'll include Pay section. Now we need to decide sections: - About the role: paragraph(s) describing role and environment. - Responsibilities: list of duties (the "Skills and attributes for success" bullet list). Could also include some responsibilities from earlier paragraph? But we will treat that list as responsibilities. - Qualifications: the bullet list under "Qualifications-". Also maybe include "Ideally, you will also have:" as preferred qualifications; could be part of Qualifications or separate "Preferred Qualifications". But we only have headings: Qualifications, Skills, Benefits, Pay, Schedule. We could put preferred qualifications under Qualifications as additional bullet points, maybe separate with note? But we must not invent headings. Could add a
note "Preferred qualifications:" then list. But better to keep Qualifications section include both required and preferred? Might be okay. - Skills: maybe we could separate technical skills list? But we already have responsibilities list includes many technical skills. Could create Skills section for technical skills like Oracle APEX, PL/SQL, etc. However we must not create thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine responsibilities and skills into one section? But we have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have substantive content for About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills (technical skills) but we could merge into Responsibilities. However the responsibilities list already includes many skills; but we could still have a Skills section summarizing technical skills (e.g., Oracle APEX, PL/SQL, JavaScript, etc.) but that would be thin. Better to not include Skills if we can incorporate into Responsibilities. Requirements: maybe we could treat the qualifications as Requirements. But we have both Qualifications and Requirements headings allowed. The posting has "Qualifications-" section. Could map that to Qualifications. Requirements could be things like "U.S. Citizen", "Ability to obtain and maintain a public trust security clearance", "Experience with secure network programming..." etc. Those are also in qualifications list. So we could just have Qualifications section covering all. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to ensure we don't include empty sections. Now we need to format. Let's extract About the role paragraph(s). We'll combine into one
. Paragraph: "Employment Type: Full-Time, Entry-Mid Level Department: Information Technology CGS is hiring a Senior Oracle APEX Developer to support a range of IT services, including software application support, enterprise infrastructure support, service desk, ITSM, deskside support, workstation engineering and maintenance, telecommunications and mobility engineering services, managed print services, Active Directory services, and video conferencing. The ideal candidate will be personable and articulate and will focus on making sure that the customer’s needs are met quickly and effectively. The successful candidate will be a self-starter who can work with limited supervision. Excellent communication skills are required to effectively interface with customers to understand requirements and mission needs, and then be able to translate them into actions. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities." We might want to remove "Employment Type: Full-Time, Entry-Mid Level Department: Information Technology" as metadata? Could fold into short
or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could keep that as a short
before About the role? But we already have About the role heading; we could include that sentence as part of About the role paragraph. It's okay. Now Responsibilities: list items. We need to extract each bullet from the "Skills and attributes for success-" list. Let's list them: - Work at the direction of the program manager to support the full lifecycle development of custom Oracle Applications, primarily using the Oracle APEX toolset. - Perform advanced use of Oracle APEX 4.0 and above. - Perform work with Oracle Integrated Development Environments such as Quest Toad and Oracle SQL Developer. - Design and manipulate web content dynamically using JQuery, Ajax, JavaScript, CSS, and HTML. - Create dynamic reports within the Oracle APEX environment. Provide support in the advanced use of Oracle Database products version 11 and above. - Provide support for Oracle database objects – tables, indexes, directories, sequences, triggers, etc. - Provide support with PL/SQL, Java, Windows PowerShell, and Unix shell scripting with familiarity with built-in PLSQL packages and procedures. - Provide support with storage, efficient retrieval, and manipulation of unstructured data (BLOBs, CLOBs, JSON, XMLType) in an Oracle environment. - Integrate and manage BI Publisher templates and web Services. - Successfully deliver enterprise-level workflow-centric applications. - Build logical functions and algorithms to automate business processes. Note some sentences have two clauses separated by period; we keep as one bullet. Now Qualifications: list from "Qualifications-" bullet list. Let's extract: - Bachelor’s degree with 8+ years experience. A High School diploma with additional years of experience and/or relevant certifications may be considered in lieu of a degree. - U.S. Citizen. - Ability to obtain and maintain a public trust security clearance. - Experience with secure network programming in an Oracle environment; use of security certificates, HTTPS callouts, etc. - Experience with full lifecycle development of custom Oracle Applications, including the Oracle APEX toolset. - Experience with the use of Oracle Integrated Development Environments such as Quest Toad and Oracle SQL Developer. - Experience with JQuery, Ajax, JavaScript, CSS, and HTML. - Experience with PL/SQL, Java, Windows PowerShell, and Unix shell scripting with familiarity with built-in PLSQL packages and procedures. - Experience with storage, efficient retrieval, and manipulation of unstructured data (BLOBs, CLOBs, JSON, XMLType) in an Oracle environment. - Experience establishing goals and meeting project plan objectives. - Must be able to write and maintain system documentation on work products. - Excellent communication and teamwork skills. - Agile development experience. - Customer interface experience. Then "Ideally, you will also have:" list: - Experience with Oracle Database products version 11 and above. - Experience with Oracle Forms and Reports version 10G or higher. - Experience with Oracle APEX 4.0 and above. - Experience troubleshooting operational issues. - Government contracting experience, particularly with the DOJ. - Current DOJ Clearance. We could include