OCTO Web Developer Master

Washington, United States | Posted on 06/06/2026

• Design, develop, and maintain Drupal-based websites supporting DC.gov and District agency platforms.
• Build and customize Drupal modules, themes, content types, taxonomies, and views per agency requirements.
• Perform Drupal core and contributed module updates, security patches, and version migrations (e.g., Drupal 7 to Drupal 10/11).
• Integrate Drupal sites with enterprise systems, APIs, and third‑party services.
• Ensure deliverables comply with Section 508, WCAG 2.1 AA, and District web standards.
• Apply web security best practices consistent with OCTO and federal cybersecurity guidelines.
• Collaborate with OCTO project managers, UX designers, content strategists, and agency stakeholders.
• Produce technical documentation, code comments, and operational runbooks.
• Provide Tier 3 production support and participate in deployment activities, including occasional after‑hours work.

• HTML & Markup: Strong command of semantic HTML5: sectioning elements, headings hierarchy, lists, tables, and forms.
• Solid grasp of web accessibility (WCAG 2.1 AA): ARIA roles and attributes, keyboard navigation, focus management, alt text, and accessible form labeling.
• Familiarity with structured data and SEO markup: meta tags, Open Graph, Twitter cards, and Schema.org/JSON‑LD.
• Understanding how Drupal renders markup through Twig and ability to produce clean, valid output via template overrides.
• CSS & Styling: Deep working knowledge of modern CSS layout:
  Flexbox and CSS Grid, with sound judgment about when to use each.
• Proficiency with responsive design: media queries, fluid typography, container queries, and mobile‑first methodology.
• Command of cascade, specificity, and inheritance, with ability to debug specificity conflicts.
• Comfort with CSS custom properties, modern color/spacing tokens, and maintainable theming patterns.

• Strong SCSS/SASS skills: nesting, mixins, functions, partials, disciplined file architecture.
• Consistent CSS methodology such as BEM and understanding how it maps onto Drupal’s class conventions.
• Familiarity with CSS transitions, transforms, animations with attention to performance and reduced‑motion preferences.
• Strong DOM manipulation and event handling, event delegation, performance‑conscious listeners.
• Fluency with Fetch API and asynchronous data handling, JSON parsing, error handling.
• Understanding how to attach and scope JS correctly through the Libraries API rather than inline scripts.
• Awareness of frontend performance: defer/async loading, minimizing reflows, debouncing/throttling, avoid render‑blocking scripts.
• Experience with a build/tooling pipeline (Webpack, Vite, Gulp) and linting/formatting (ESLint, Prettier, Stylelint).
• Exposure to modern framework (React/Vue) for decoupled or partially decoupled Drupal frontends.
• Hands‑on experience with Domain Access module, Domain Config module, cache contexts/invalidation, domain‑aware menu/block/pathauto strategies.
• Familiarity with CI/CD pipelines (BLT, Git Hub Actions, Acquia Pipelines).
• Hands‑on Acquia Cloud experience: environments, Cloud Hooks, code/database/files workflow, Acquia CLI.
• Comfort with multi‑database configuration and routing.
• Experience building and consuming REST APIs: JSON:
  
  API, REST module, custom REST resources.
• Experience with common third‑party integrations: analytics, marketing automation.

• Fluency with Drupal 9/10/11 admin UI: content types, fields, vocabularies, view modes, form/display modes, blocks, menus, URL aliases, redirects.
• Solid command of Configuration Management workflows: config export/import, , .
• Strong grasp of user access control: roles, permissions, content moderation workflows, custom workflow states/transitions.
• Demonstrated expertise with Views: complex queries, contextual filters, relationships, exposed filters/sorts, output rewriting, REST exports.
• Experience administering Media Library, image styles, responsive image styles, crop/focal‑point strategies.
• Clear mental model of what belongs in config vs. content vs. state vs. settings.php.

• Strong Twig skills: template…