Drupal 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. Let's parse. The posting includes: - Employment Type: Full-Time - Department: Developer - CGS is seeking a Drupal Developer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. - CGS brings motivated... (description) - Skills And Attributes For Success: list of items (site building, administration, maintenance of Drupal sites; develop custom Drupal themes and modules; work closely with users; work within Agile methodology; learn new technologies; help back-end and front-end developers work together) - Qualifications: list (Bachelor’s Degree in Computer Science or related field; 3+ years of Drupal experience; 3+ in Drupal 8/9; 5+ years of experience with PHP, MySQL, HTML, JQuery; 3+ years of experience with Drupal content modeling and site governance; 5+ years of experience with CSS, Sass, and USWDS; 3+ years of experience with OEL, REHL, and CentOS; Experience with Apache; Experience with Google Analytics; Experience with Azure DevOps/Agile Methodology; Experience with REST/SOAP APIs; Experience with CI/CD; Experience with Drush/Composer; Ideally, You Will Also Have Experience with Government software development policies and procedures; Client-facing communication experience; Federal Agency issued security clearance) - Our Commitment: paragraph about CGS values, etc. - Benefits: list: Health, Dental, and Vision; Life Insurance; 401k; Flexible Spending Account (Health, Dependent Care, and Commuter); Paid Time Off and Observance of State/Federal Holidays - Pay: "#CJ$109,685.33 - $148,858.66 a year" (looks like a pay range). So we have Pay. - Schedule: Not explicitly mentioned. Only "Employment Type: Full-Time". That implies schedule maybe full-time but not specific hours. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have. Pay we have. Schedule we do not have explicit schedule (like hours, shift). So we should not include Schedule section. Also we need About the role section: we have description of role: "CGS is seeking a Drupal Developer to join our team supporting a wide-ranging technical support initiative for a large Federal agency." plus maybe some description about mission. Could be considered About the role. We'll include. Responsibilities: The "Skills And Attributes For Success" list seems like responsibilities/duties. We'll treat as Responsibilities. Requirements: Could be qualifications? Usually Requirements separate from Qualifications. But we have Qualifications list. We could treat Qualifications as Requirements. However we have both Qualifications 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 if content distinct. The posting has "Qualifications" list. It also has "Skills And Attributes For Success". That could be Skills. So we can map: - About the role: description paragraph. - Responsibilities: maybe not explicitly separate; but we could treat the Skills And Attributes as Responsibilities? Actually they are skills needed for success, could be considered Skills. But we also have a separate Skills heading allowed. Let's decide: Use Responsibilities for core duties (maybe from description: supporting technical support initiative, etc.) but we don't have explicit duty list. Could combine. Better: Use Responsibilities for the list of duties (site building, administration, etc.) and Skills for technical qualifications list (the longer list). But the list under Skills And Attributes For Success includes both duties and skills. However we can split: Responsibilities: site building, administration, maintenance; develop custom themes/modules; work closely with users; work within Agile; learn new tech; help back-end and front-end developers work together. That's 6 items. Skills: the longer list of technical experience: Drupal experience, PHP, MySQL, etc., plus others. Qualifications: Bachelor's degree, etc. Actually the qualifications list includes education and years experience; but many of those overlap with skills. However we can still have Qualifications for education and baseline requirements (Bachelor's degree, 3+ years Drupal, etc.) and Skills for specific tech stack. But we must not repeat info. We need to preserve all substantive information. So we need to include all items somewhere. Let's extract items: From Skills And Attributes For Success: - Site building, administration, and maintenance of Drupal sites - Develop custom Drupal themes and modules - Work closely with the users to understand their requirements - Work within the Agile methodology helping Sprint teams - Learn new technologies or off-the-shelf software quickly - Help back-end and front-end developers work with one another From Qualifications list: - Bachelor’s Degree in Computer Science or related field - 3+ years of Drupal experience - 3+ in Drupal 8/9 - 5+ years of experience with PHP, MySQL, HTML, JQuery - 3+ years of experience with Drupal content modeling and site governance - 5+ years of experience with CSS, Sass, and USWDS - 3+ years of experience with OEL, REHL, and CentOS - Experience with Apache - Experience with Google Analytics - Experience with Azure DevOps/Agile Methodology - Experience with REST/SOAP APIs - Experience with CI/CD - Experience with Drush/Composer - Ideally, You Will Also Have Experience with Government software development policies and procedures - Client-facing communication experience - Federal Agency issued security clearance From Benefits: - Health, Dental, and Vision - Life Insurance - 401k - Flexible Spending Account (Health, Dependent Care, and Commuter) - Paid Time Off and Observance of State/Federal Holidays Pay: #CJ$109,685.33 - $148,858.66 a year About the role: The introductory paragraph: "CGS is seeking a Drupal Developer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. 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 could also include the "Our Commitment" paragraph as part of About the role or maybe as separate section? Not in headings list. Could incorporate into About the role. We must not include boilerplate like EEO, contact info, application instructions, AI notice, etc. Remove those. Thus final HTML:

About the role

CGS is seeking a Drupal Developer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. 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.

Responsibilities

• Site building, administration, and maintenance of Drupal sites
• Develop custom Drupal themes and modules
• Work closely with the users to understand their requirements
• Work within the Agile methodology helping Sprint teams
• Learn new technologies or off-the-shelf software quickly
• Help back-end and front-end developers work with one another

Skills

• 3+ years of Drupal experience
• 3+ years experience with Drupal 8/9
• 5+ years of experience with PHP, MySQL, HTML, JQuery
• 3+ years of experience with Drupal content modeling and site governance
• 5+ years of experience with CSS, Sass, and USWDS
• 3+ years of experience with OEL, REHL, and CentOS
• Experience with Apache
• Experience with Google Analytics
• Experience with Azure DevOps/Agile Methodology
• Experience with REST/SOAP APIs
• Experience with CI/CD
• Experience with Drush/Composer
• Experience with Government software development policies and procedures (ideal)
• Client-facing communication experience
• Federal Agency issued security clearance

Qualifications

• Bachelor’s Degree in Computer Science or related field

But we have duplicated years of experience etc. Already in Skills. Could move education to Qualifications and keep years experience in Skills. That seems okay. But we also have "3+ years of Drupal experience" and "3+ in Drupal 8/9" etc. Those are skills/experience. So we put them in Skills. Qualifications only education. Alternatively we could have Qualifications include education + baseline years (like 3+ Drupal etc.) and Skills be specific tech. But we need to avoid duplication. Let's decide: Qualifications: Bachelor's degree. Skills: all experience lists. That covers all. Check if any other qualifications like "Ideally, You Will Also Have Experience with Government software development policies and procedures" is ideal, not required. We'll keep in Skills as optional. Now Benefits section:

Benefits

• Health, Dental, and Vision
• Life Insurance
• 401k
• Flexible Spending Account (Health, Dependent Care, and Commuter)
• Paid Time Off and Observance of State/Federal Holidays

Pay section:

Pay

$109,685.33 - $148,858.66 per year

We need to strip the "#CJ$" prefix. Keep just numbers. Now ensure no empty sections. We have About the role, Responsibilities, Skills, Qualifications, Benefits, Pay. No Schedule. Check for any leftover info: Department: Developer, Employment Type: Full-Time. Not included anywhere. Should we include them? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Employment type and department are minor metadata. Could fold into a short

maybe under About the role or at top. But we already have About the role paragraph; we could add a sentence: "This is a full-time position in the Developer department." However we must not invent info; we can include it as it's present. Let's add a short paragraph after About the role maybe as part of same section? Could add a

after the About the role paragraph: "This is a full-time position in the Developer department." That preserves info. Alternatively we could add a

before sections: "Employment Type: Full-Time. Department: Developer." But better to integrate. Let's adjust About the role paragraph to include that sentence. Thus final HTML:

About the role

CGS is seeking a Drupal Developer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. 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,