Drupal Frontend Engineer, (Consultant, Engineering & Technical Services)
Fearless · Baltimore, MD · 4 wk ago
RemoteRemoteInformation Technology$96k–$133k/yrFull-time
We need to output HTML fragment with sections: headings for sections like 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 as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role: description of role, collaboration, etc. The first paragraph(s) about Fearless, role description.
- Responsibilities: list of duties under "Your Responsibilities In This Role" bullet points.
- Requirements / Qualifications: maybe combine? The posting has "Work Experience Project Skill and Experience Requirements" list, also "Fearless Skills And Competencies" (these are more like competencies). Also "Preferred Experience". Also "Required Level Of Proficiency". Also "Physical Requirements". Also "Place Of Performance & Travel Requirements". Also "Mandatory technical assessment". Also "Ability to obtain and maintain Public Trust clearance". Also "CMS residency requirements". Also "Drupal.org username required". Also "5+ years of web development experience" etc.
We need to decide sections: Could have "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we must only include sections with real content.
We have Pay: salary range given. So include Pay section.
Benefits: there is a Benefits section describing benefits. So include Benefits.
Schedule: maybe not explicit schedule; only mention flexible, life-friendly schedules, remote primarily, occasional travel. Could include Schedule? The posting mentions flexible schedules, remote primarily, occasional travel. That could be considered schedule info. But we need to see if we should create a Schedule section only if posting actually states them. It does mention flexible schedules, remote primarily, occasional travel. So we could include Schedule.
But we must avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
for sections like 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 as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role: description of role, collaboration, etc. The first paragraph(s) about Fearless, role description.
- Responsibilities: list of duties under "Your Responsibilities In This Role" bullet points.
- Requirements / Qualifications: maybe combine? The posting has "Work Experience Project Skill and Experience Requirements" list, also "Fearless Skills And Competencies" (these are more like competencies). Also "Preferred Experience". Also "Required Level Of Proficiency". Also "Physical Requirements". Also "Place Of Performance & Travel Requirements". Also "Mandatory technical assessment". Also "Ability to obtain and maintain Public Trust clearance". Also "CMS residency requirements". Also "Drupal.org username required". Also "5+ years of web development experience" etc.
We need to decide sections: Could have "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we must only include sections with real content.
We have Pay: salary range given. So include Pay section.
Benefits: there is a Benefits section describing benefits. So include Benefits.
Schedule: maybe not explicit schedule; only mention flexible, life-friendly schedules, remote primarily, occasional travel. Could include Schedule? The posting mentions flexible schedules, remote primarily, occasional travel. That could be considered schedule info. But we need to see if we should create a Schedule section only if posting actually states them. It does mention flexible schedules, remote primarily, occasional travel. So we could include Schedule.
But we must avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- 5+ years of web development experience ...
tags. We need to avoid repeating job title as heading. Already not. We must not include boilerplate like EEO etc. We'll omit. Now produce HTML. Structure:
About the role
At Fearless, the Consultant, Engineering & Technical Services collaborates with cross-functional Agile teams to architect, implement, and maintain modern, high-performing digital experiences for a federal health care platform serving approximately 11 million monthly users. Leveraging advanced Drupal frontend expertise—including component-based architecture and modular design system implementation—this role optimizes public access to critical health care services while bridging technical execution and user-centered delivery. As a subject-matter expert, the successful candidate works independently to establish and uphold team standards for quality, performance, and WCAG accessibility. This position requires candidates to obtain and maintain a federal Public Trust clearance and satisfy all CMS residency requirements. This Consultant collaborates with cross-functional teams to deliver high-quality, secure, and maintainable systems across all stages of the software and data lifecycle. This role is instrumental in delivering secure, efficient, and scalable solutions that directly impact the success of projects, teams, and organizational goals. This role will possess and/or develop the skills to be able to span the domains of software development, data engineering, infrastructure automation, information assurance, and AI/ML integration at a practical application level of proficiency. This Consultant role will work on projects that allow them to contribute across the entire technology stack—software, infrastructure, data, AI, and security—to ensure quality, speed, and innovation in delivery.
That seems to capture all. Now ResponsibilitiesResponsibilities
- with each bullet.
Now Requirements