Lead Drupal Architect/Developer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate like EEO, navigation, etc. Include sections only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule only if posting actually states them. Here we have Salary: $135-165k DoE (Depends on Experience). That's pay info. So we can include Pay section with that salary range. Schedule: Terms: Full-time. That's schedule info. So we can include Schedule section with Full-time. Benefits: there is a benefits paragraph later. So include Benefits section.
We also need About the role? The description includes Position Description paragraph. Could be About the role. We'll put that as About the role.
Responsibilities: list many bullet points. We'll put under Responsibilities.
Requirements: list bullet points. We'll put under Requirements.
Qualifications? The posting includes Requirements and Desired Experience; maybe we treat Requirements as qualifications. But we have separate sections: Requirements, Qualifications, Skills. We need to decide based on content. The posting has "Requirements" list and "Desired Experience" list. Could map Requirements to Requirements section, Desired Experience to Qualifications or Skills. But we must not create sections with filler. We have substantive content for both. Could create Requirements section for the mandatory requirements, and Qualifications section for desired experience. Skills maybe not needed separately; we could embed skills within Requirements/Qualifications. But we need to follow instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one Requirements section? But they are distinct. However we can include both as separate sections if they have content. Let's see: Requirements list includes citizenship, 7+ years, etc. Desired Experience list includes federal agencies, accessibility, AWS GovCloud, AI chatbot, etc. Those are desired, not required. Could treat as Qualifications. So we will have Requirements and Qualifications sections.
Skills: maybe not needed; we could omit if no explicit skills list separate. The responsibilities and requirements already cover skills. So we omit Skills section to avoid thin.
Thus sections: About the role (position description paragraph), Responsibilities (list), Requirements (list), Qualifications (list), Benefits (list), Pay (salary), Schedule (full-time). Ensure we use
for each heading.
We need to strip boilerplate: The initial paragraph about Revolutional delivering tech solutions etc is part of company overview; could be considered About the role? Actually it's generic company description; but we can include it as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The company overview is substantive but not specific to role. However we might include it in About the role section as context. It's okay.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc; remove that. Also remove the "Here At Revolutional We Are Pleased..." paragraph about recognitions and benefits? Actually benefits are there; we need to keep benefits. The recognition paragraph is also substantive but maybe not required; but we can keep as part of About the role? It's about company culture; could be included but not required. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that recognition paragraph as well, maybe under About the role or a separate section like Company Overview. But we only have headings for specific categories; we could put it under About the role as part of description. However About the role heading is for role description; but we can still include extra info there. It's okay.
We must not include the EEO statement etc.
Now craft HTML.
We'll need to convert bullet lists to - . Ensure we preserve all bullet points.
Let's extract About the role content: The first paragraph: "Revolutional delivers advanced technology solutions and mission support to federal agencies across civilian, health, and national security environments. We apply modern capabilities, including AI/ML, cloud, cybersecurity, and IT modernization to solve complex challenges, enable faster and more secure operations, and drive measurable mission outcomes. We are redefining how federal technology gets built and delivered by operating with a product mindset, prioritizing speed, ownership, and execution over bureaucracy."
Then Position Description paragraph: "We are seeking an experienced Drupal Architect/Developer to design, develop, secure, and deploy the Drupal 11 CMS backend for a public-facing federal agency website. The role will work closely with the AWS Cloud Architect, frontend developers, security team, content administrators, and agency stakeholders to deliver a secure, scalable, accessible, and maintainable Drupal platform integrated with a modern React/Next.js frontend in AWS GovCloud. The Drupal Architect will help define the hosting and deployment architecture, establish secure connections among Drupal, databases, storage, caching, search, APIs, and the frontend, and implement infrastructure and application configuration through approved DevSecOps processes. The ideal candidate has significant prior experience deploying Drupal 11 in a regulated cloud environment, preferably AWS GovCloud, supporting the federal ATO activities."
Then the recognition paragraph: "Here At Revolutional We Are Pleased To Have Been Repeatedly Recognized For Our Outstanding Work Culture, The Innovative Work We Do, And The Employees On Our Team Who Make a Difference Each Day. Some Of These Recognitions Include Recognized as a Top 20 "Best Place to Work in Virginia"Recipient of Department of Labor's HireVets Gold MedallionGreat Place to Work Certification for five years runningA Virginia Chamber of Commerce Fantastic 50 companyA Northern Virginia Technology Council Tech 100 company Inc. 5000 list of fastest growing companies for eleven yearsTwo-time SBA SBIR Tibbett's Award winnerVirginia Values Veterans (V3) Certification We recognize that every bit of our success is the result of our teams of hard-working, motivated, and innovative professionals who are proud to call themselves part of the Revolutional family!"
We could combine all three into About the role section as prose (
). Might be long but okay.
Now Responsibilities list: many bullet points starting with "Design and implement..." etc. We'll need to capture each line as
- . Ensure we keep the exact wording.
Let's copy responsibilities bullet points from the posting:
- Design and implement the Drupal 11 CMS architecture for a high-availability, public-facing website.
- Configure Drupal content types, taxonomies, workflows, roles, permissions, moderation, publishing, and editorial features.
- Develop custom Drupal modules, services, plugins, event subscribers, and integrations.
- Configure and secure Drupal JSON:API, GraphQL, or other APIs used by the React/Next.js frontend.
- Define backup, recovery, logging, monitoring, scaling, and disaster-recovery requirements.
- Identify and remediate application and infrastructure security risks.
- Provide technical information and evidence required for the ATO process.
- Coordinate deployment, testing, release management, and production support.
- Collaborate with the AWS Cloud Architect on deployment architecture, networking, storage, databases, caching, logging, monitoring, backups, and disaster recovery.
- Deploy and operate Drupal in AWS GovCloud using approved services and containerized or automated deployment patterns.
- Integrate Drupal with PostgreSQL, object storage, caching services, search platforms, CDN services, and external APIs.
- Ensure that unpublished, restricted, and administrative content is not exposed through APIs, search indexes, caches, or frontend applications.
- Implement secure Drupal administration, authentication, authorization, session management, and administrative access controls.
- Review and manage Drupal modules, Composer dependencies, PHP libraries, and third-party integrations.
- Establish Drupal coding standards, development practices, branching strategies, and release procedures.
- Support CI/CD pipelines, automated testing, code reviews, vulnerability remediation, and controlled production releases.
- Optimize Drupal performance, caching, database queries, API responses, and media delivery.
- Support content migration, data modeling, integration testing, performance testing, and production readiness activities.
- Develop technical documentation, deployment procedures, configuration guides, data-flow diagrams, and operational runbooks.
- Support security assessments, vulnerability remediation, ATO documentation, and continuous-monitoring activities.
- Troubleshoot application, integration, performance, deployment, and production issues.
- Mentor Drupal developers and promote maintainable, reusable, and secure solutions.
Now Requirements list:
- U.S. Citizenship and ability to obtain and maintain a Federal Public Trust clearance.
- 7+ years of Drupal development experience, including architecture and production deployments.
- Demonstrated experience with Drupal 9, 10, or 11; direct Drupal 11 experience in AWS cloud environment is strongly preferred.
- Strong experience with PHP, Symfony, Composer, Twig, Drupal APIs, configuration management, and custom module development.
- Experience designing Drupal content models, taxonomies, editorial workflows, permissions, and moderation processes.
- Experience with decoupled or headless Drupal implementations.
- Experience integrating Drupal with React, Next.js, JSON:API, GraphQL, or similar frontend technologies.
- Experience with integrating with AWS managed database service (RDS/PostgreSQL or MySQL) and database backed React applications.
- Experience deploying Drupal using containers, automated pipelines, or infrastructure-as-code environments.
- Working knowledge of AWS managed cloud services and cloud deployment concepts.
- Experience with Drupal security updates, dependency management, secure configuration, access control, and vulnerability remediation.
- Experience with automated testing, code review, version control, and CI/CD practices.
- Experience supporting public-facing, high-traffic, or mission-critical websites.
- Ability to create technical documentation and communicate effectively with technical and nontechnical stakeholders.
Now Qualifications (Desired Experience) list:
- Experience supporting federal agencies, government contractors, FedRAMP environments, or ATO activities.
- Experience with accessibility requirements, including Section 508 and WCAG.
- Prior experience deploying Drupal in AWS GovCloud or another regulated cloud environment.
- Experience integrating Drupal with Amazon Bedrock and AI-enabled chatbot/search.
- Experience with AWS services such as ECS/Fargate, Aurora or PostgreSQL, S3, CloudFront, ElastiCache, OpenSearch, WAF, and Secrets Manager.
- Experience with automated Drupal security and quality tools.
- Acquia, Drupal or relevant professional certifications.
Now Benefits paragraph: "In addition to competitive compensation, a family-focused culture, and a dynamic, productive work environment, we offer all full-time employees a variety of benefits including, but not limited to Traditional and HSA- eligible medical insurance plans 100% employer-paid dental and vision insurance options 100% employer-sponsored STD, LTD, and life insurance5% 401(k) company matchingFlexible-schedules and teleworking optionsPaid holidays and PTO Accrual PlansPaid Parental LeaveProfessional development and career growth opportunities Team and company-wide events, recognition, and appreciation-- and so much more!"
We need to format as list? It's a prose sentence with benefits separated by spaces. Could convert to list items for clarity. But instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into list items. Let's split by benefits mentioned:
- Traditional and HSA-eligible medical insurance plans
- 100% employer-paid dental and vision insurance options
- 100% employer-sponsored STD, LTD, and life insurance
- 5% 401(k) company matching
- Flexible-schedules and teleworking options
- Paid holidays and PTO Accrual Plans
- Paid Parental Leave
- Professional development and career growth opportunities
- Team and company-wide events, recognition, and appreciation
We'll keep as list.
Pay: Salary: $135-165k DoE. We'll put in
maybe.
Schedule:
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate like EEO, navigation, etc. Include sections only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule only if posting actually states them. Here we have Salary: $135-165k DoE (Depends on Experience). That's pay info. So we can include Pay section with that salary range. Schedule: Terms: Full-time. That's schedule info. So we can include Schedule section with Full-time. Benefits: there is a benefits paragraph later. So include Benefits section. We also need About the role? The description includes Position Description paragraph. Could be About the role. We'll put that as About the role. Responsibilities: list many bullet points. We'll put under Responsibilities. Requirements: list bullet points. We'll put under Requirements. Qualifications? The posting includes Requirements and Desired Experience; maybe we treat Requirements as qualifications. But we have separate sections: Requirements, Qualifications, Skills. We need to decide based on content. The posting has "Requirements" list and "Desired Experience" list. Could map Requirements to Requirements section, Desired Experience to Qualifications or Skills. But we must not create sections with filler. We have substantive content for both. Could create Requirements section for the mandatory requirements, and Qualifications section for desired experience. Skills maybe not needed separately; we could embed skills within Requirements/Qualifications. But we need to follow instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one Requirements section? But they are distinct. However we can include both as separate sections if they have content. Let's see: Requirements list includes citizenship, 7+ years, etc. Desired Experience list includes federal agencies, accessibility, AWS GovCloud, AI chatbot, etc. Those are desired, not required. Could treat as Qualifications. So we will have Requirements and Qualifications sections. Skills: maybe not needed; we could omit if no explicit skills list separate. The responsibilities and requirements already cover skills. So we omit Skills section to avoid thin. Thus sections: About the role (position description paragraph), Responsibilities (list), Requirements (list), Qualifications (list), Benefits (list), Pay (salary), Schedule (full-time). Ensure we use
for each heading.
We need to strip boilerplate: The initial paragraph about Revolutional delivering tech solutions etc is part of company overview; could be considered About the role? Actually it's generic company description; but we can include it as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The company overview is substantive but not specific to role. However we might include it in About the role section as context. It's okay.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc; remove that. Also remove the "Here At Revolutional We Are Pleased..." paragraph about recognitions and benefits? Actually benefits are there; we need to keep benefits. The recognition paragraph is also substantive but maybe not required; but we can keep as part of About the role? It's about company culture; could be included but not required. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that recognition paragraph as well, maybe under About the role or a separate section like Company Overview. But we only have headings for specific categories; we could put it under About the role as part of description. However About the role heading is for role description; but we can still include extra info there. It's okay.
We must not include the EEO statement etc.
Now craft HTML.
We'll need to convert bullet lists to - . Ensure we preserve all bullet points.
Let's extract About the role content: The first paragraph: "Revolutional delivers advanced technology solutions and mission support to federal agencies across civilian, health, and national security environments. We apply modern capabilities, including AI/ML, cloud, cybersecurity, and IT modernization to solve complex challenges, enable faster and more secure operations, and drive measurable mission outcomes. We are redefining how federal technology gets built and delivered by operating with a product mindset, prioritizing speed, ownership, and execution over bureaucracy."
Then Position Description paragraph: "We are seeking an experienced Drupal Architect/Developer to design, develop, secure, and deploy the Drupal 11 CMS backend for a public-facing federal agency website. The role will work closely with the AWS Cloud Architect, frontend developers, security team, content administrators, and agency stakeholders to deliver a secure, scalable, accessible, and maintainable Drupal platform integrated with a modern React/Next.js frontend in AWS GovCloud. The Drupal Architect will help define the hosting and deployment architecture, establish secure connections among Drupal, databases, storage, caching, search, APIs, and the frontend, and implement infrastructure and application configuration through approved DevSecOps processes. The ideal candidate has significant prior experience deploying Drupal 11 in a regulated cloud environment, preferably AWS GovCloud, supporting the federal ATO activities."
Then the recognition paragraph: "Here At Revolutional We Are Pleased To Have Been Repeatedly Recognized For Our Outstanding Work Culture, The Innovative Work We Do, And The Employees On Our Team Who Make a Difference Each Day. Some Of These Recognitions Include Recognized as a Top 20 "Best Place to Work in Virginia"Recipient of Department of Labor's HireVets Gold MedallionGreat Place to Work Certification for five years runningA Virginia Chamber of Commerce Fantastic 50 companyA Northern Virginia Technology Council Tech 100 company Inc. 5000 list of fastest growing companies for eleven yearsTwo-time SBA SBIR Tibbett's Award winnerVirginia Values Veterans (V3) Certification We recognize that every bit of our success is the result of our teams of hard-working, motivated, and innovative professionals who are proud to call themselves part of the Revolutional family!"
We could combine all three into About the role section as prose (
). Might be long but okay.
Now Responsibilities list: many bullet points starting with "Design and implement..." etc. We'll need to capture each line as
- . Ensure we keep the exact wording.
Let's copy responsibilities bullet points from the posting:
- Design and implement the Drupal 11 CMS architecture for a high-availability, public-facing website.
- Configure Drupal content types, taxonomies, workflows, roles, permissions, moderation, publishing, and editorial features.
- Develop custom Drupal modules, services, plugins, event subscribers, and integrations.
- Configure and secure Drupal JSON:API, GraphQL, or other APIs used by the React/Next.js frontend.
- Define backup, recovery, logging, monitoring, scaling, and disaster-recovery requirements.
- Identify and remediate application and infrastructure security risks.
- Provide technical information and evidence required for the ATO process.
- Coordinate deployment, testing, release management, and production support.
- Collaborate with the AWS Cloud Architect on deployment architecture, networking, storage, databases, caching, logging, monitoring, backups, and disaster recovery.
- Deploy and operate Drupal in AWS GovCloud using approved services and containerized or automated deployment patterns.
- Integrate Drupal with PostgreSQL, object storage, caching services, search platforms, CDN services, and external APIs.
- Ensure that unpublished, restricted, and administrative content is not exposed through APIs, search indexes, caches, or frontend applications.
- Implement secure Drupal administration, authentication, authorization, session management, and administrative access controls.
- Review and manage Drupal modules, Composer dependencies, PHP libraries, and third-party integrations.
- Establish Drupal coding standards, development practices, branching strategies, and release procedures.
- Support CI/CD pipelines, automated testing, code reviews, vulnerability remediation, and controlled production releases.
- Optimize Drupal performance, caching, database queries, API responses, and media delivery.
- Support content migration, data modeling, integration testing, performance testing, and production readiness activities.
- Develop technical documentation, deployment procedures, configuration guides, data-flow diagrams, and operational runbooks.
- Support security assessments, vulnerability remediation, ATO documentation, and continuous-monitoring activities.
- Troubleshoot application, integration, performance, deployment, and production issues.
- Mentor Drupal developers and promote maintainable, reusable, and secure solutions.
Now Requirements list:
- U.S. Citizenship and ability to obtain and maintain a Federal Public Trust clearance.
- 7+ years of Drupal development experience, including architecture and production deployments.
- Demonstrated experience with Drupal 9, 10, or 11; direct Drupal 11 experience in AWS cloud environment is strongly preferred.
- Strong experience with PHP, Symfony, Composer, Twig, Drupal APIs, configuration management, and custom module development.
- Experience designing Drupal content models, taxonomies, editorial workflows, permissions, and moderation processes.
- Experience with decoupled or headless Drupal implementations.
- Experience integrating Drupal with React, Next.js, JSON:API, GraphQL, or similar frontend technologies.
- Experience with integrating with AWS managed database service (RDS/PostgreSQL or MySQL) and database backed React applications.
- Experience deploying Drupal using containers, automated pipelines, or infrastructure-as-code environments.
- Working knowledge of AWS managed cloud services and cloud deployment concepts.
- Experience with Drupal security updates, dependency management, secure configuration, access control, and vulnerability remediation.
- Experience with automated testing, code review, version control, and CI/CD practices.
- Experience supporting public-facing, high-traffic, or mission-critical websites.
- Ability to create technical documentation and communicate effectively with technical and nontechnical stakeholders.
Now Qualifications (Desired Experience) list:
- Experience supporting federal agencies, government contractors, FedRAMP environments, or ATO activities.
- Experience with accessibility requirements, including Section 508 and WCAG.
- Prior experience deploying Drupal in AWS GovCloud or another regulated cloud environment.
- Experience integrating Drupal with Amazon Bedrock and AI-enabled chatbot/search.
- Experience with AWS services such as ECS/Fargate, Aurora or PostgreSQL, S3, CloudFront, ElastiCache, OpenSearch, WAF, and Secrets Manager.
- Experience with automated Drupal security and quality tools.
- Acquia, Drupal or relevant professional certifications.
Now Benefits paragraph: "In addition to competitive compensation, a family-focused culture, and a dynamic, productive work environment, we offer all full-time employees a variety of benefits including, but not limited to Traditional and HSA- eligible medical insurance plans 100% employer-paid dental and vision insurance options 100% employer-sponsored STD, LTD, and life insurance5% 401(k) company matchingFlexible-schedules and teleworking optionsPaid holidays and PTO Accrual PlansPaid Parental LeaveProfessional development and career growth opportunities Team and company-wide events, recognition, and appreciation-- and so much more!"
We need to format as list? It's a prose sentence with benefits separated by spaces. Could convert to list items for clarity. But instruction: Use
- for any list of duties/requirements/benefits. So we should turn benefits into list items. Let's split by benefits mentioned:
- Traditional and HSA-eligible medical insurance plans
- 100% employer-paid dental and vision insurance options
- 100% employer-sponsored STD, LTD, and life insurance
- 5% 401(k) company matching
- Flexible-schedules and teleworking options
- Paid holidays and PTO Accrual Plans
- Paid Parental Leave
- Professional development and career growth opportunities
- Team and company-wide events, recognition, and appreciation
We'll keep as list.
Pay: Salary: $135-165k DoE. We'll put in
maybe.
Schedule:
). Might be long but okay. Now Responsibilities list: many bullet points starting with "Design and implement..." etc. We'll need to capture each line as
- for any list of duties/requirements/benefits. So we should turn benefits into list items. Let's split by benefits mentioned:
- Traditional and HSA-eligible medical insurance plans
- 100% employer-paid dental and vision insurance options
- 100% employer-sponsored STD, LTD, and life insurance
- 5% 401(k) company matching
- Flexible-schedules and teleworking options
- Paid holidays and PTO Accrual Plans
- Paid Parental Leave
- Professional development and career growth opportunities
- Team and company-wide events, recognition, and appreciation
We'll keep as list.
Pay: Salary: $135-165k DoE. We'll put in
maybe. Schedule: