Lead Full-Stack Developer

We need to output HTML fragment with sections only when posting has real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Job Family Software Development & Support Travel Required Up to 10% Clearance Required Ability to Obtain Public Trust Then "What You Will Do" is responsibilities. Then "What You Will Need" is requirements/qualifications/skills. Then "What Would Be Nice To Have" is nice-to-have (maybe skills). Then "What We Offer" includes benefits. Also "About Guidehouse" is boilerplate (EEO etc) to remove. We need sections: About the role? The posting doesn't have an explicit "About the role" section; but we could include a short paragraph summarizing role? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not create About the role if no explicit content. However we could treat the initial sentences before "What You Will Do" as about the role? It includes Job Family, Travel Required, Clearance Required, Ability to Obtain Public Trust. That's metadata about the role. Could be considered "About the role". But we need to decide if that's substantive enough. It includes travel, clearance, public trust. That's specific. So we could create an About the role section with that info. Responsibilities: from "What You Will Do" bullet-like sentences (though not bullet). We'll need to convert to

• for any list of duties/requirements/benefits. The responsibilities are multiple sentences; we can split each sentence into a list item. Requirements: from "What You Will Need". That includes education, experience, etc. We'll list as list items. Skills: maybe combine technical skills from requirements and nice-to-have? The instruction: Use sections for Skills if posting has real specific content. We have skills listed: Expert proficiency in Python and JavaScript, Django experience preferred, etc. Also nice-to-have includes certifications, etc. Could create Skills section covering both required and nice-to-have? But we already have Requirements section for qualifications; Skills could be separate for technical skills. However we must not create thin sections. Perhaps combine Requirements and Skills into one? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have no explicit Pay or Schedule info. So we should NOT include Pay or Schedule sections. Benefits: we have "What We Offer" with benefits list. So include Benefits section. Qualifications: maybe same as Requirements? Could combine. But we have both Requirements and Qualifications headings available. We could put education/experience under Requirements, and technical skills under Skills. Or we could put all under Requirements and skip Skills. But we have nice-to-have separate; maybe Skills for technical skills, Qualifications for education/experience. Let's decide. We need to preserve all substantive info. So we must include education, experience, leadership, AWS experience, etc. Also technical skills (Python, JavaScript, Django, etc). Also nice-to-have (certifications, other tools). Also benefits. Thus we can have: - About the role: includes Job Family, Travel Required Up to 10%, Clearance Required Ability to Obtain Public Trust. - Responsibilities: list from "What You Will Do". - Requirements: education and experience requirements (Bachelor's degree or equivalent, years of experience, leadership, AWS experience, etc). Could also include citizenship, clearance, public trust? But those already in About the role maybe. - Skills: technical skills required (proficiency in Python/JavaScript, Django, Vue.js, microservices, API design, containerization, CI/CD, AWS SAM, patterns, Agile, communication, etc). Also nice-to-have could be separate but we could include under Skills as "Nice-to-have" items. - Benefits: list from "What We Offer". We should not include Qualifications if we already have Requirements and Skills; but we could include Qualifications as education/experience and keep Requirements for something else? Actually typical: Requirements = mandatory, Qualifications = preferred. But we have both mandatory and nice-to-have. Could map Requirements = mandatory, Qualifications = nice-to-have. But we also have Skills separate. Might be redundant. Better to follow typical: About the role, Responsibilities, Requirements (mandatory), Qualifications (preferred), Benefits. Skills maybe not needed if we incorporate into Requirements/Qualifications. But the instruction says we can use Skills section if posting has real specific content. It does have specific technical skills. So we could include Skills. Thus we have sections: About the role, Responsibilities, Requirements, Skills, Benefits. We must not include Pay or Schedule. Now we need to format. We must not repeat job title as heading. No markdown. We need to output only HTML fragment. Let's extract content precisely. About the role: - Job Family: Software Development & Support - Travel Required: Up to 10% - Clearance Required: Ability to Obtain Public Trust We could phrase as sentences. Responsibilities: from "What You Will Do". Let's copy sentences: 1. Work closely with clients, leaders, solution architects, and technical and functional leads across Guidehouse teams and market segments to support client projects, growth initiatives, and capability development. 2. Serve as a key member of the modernization team, leading and mentoring full-stack development teams while providing technical guidance and architectural oversight for innovative solution prototypes using cloud architectures and modern software technologies. 3. Lead solution architecture and hands-on full-stack engineering for scalable, secure distributed systems using modern programming technologies, AWS-native services, microservices architecture, containerization, and API-first design patterns. 4. Collaborate with user experience designers, platform engineers, product owners, solution architects, business analysts, and full-stack development teams to design, build, test, and deploy high-value, operationally resilient software products on AWS that meet functional and non-functional requirements. 5. Define application architecture standards, design patterns, and development best practices across teams; establish architectural roadmaps for complex modernization projects; and ensure alignment with AWS Well-Architected Framework principles. 6. Lead technical decision-making, oversee implementation of complex distributed systems, and provide escalation support for challenging technical issues while managing timelines, resource allocation, and technical deliverables across multiple concurrent initiatives. 7. Guide proof-of-concept development and technical demonstrations to validate solution strategies, and lead solution architecture efforts for RFPs, technical proposals, and thought leadership initiatives. That's 7 items. Requirements (mandatory): from "What You Will Need". Let's parse: - A Bachelor’s degree ; Additional four(4) years of experience is required in lieu of degree. - Minimum of six (6) years of relevant full-stack application development experience, including at least four (4) years in leadership or architecture roles. - Minimum of five (5) years of experience developing, building, or modernizing applications on AWS. - Experience leading teams and implementing frontend and backend services for cloud-native software products and solutions using technologies such as Python, JavaScript, Django, and Vue.js. - Expert proficiency in Python and JavaScript, with proven experience leading teams of five or more developers. - Django experience is preferred; experience with Flask, FastAPI, Falcon, or SQLAlchemy may be considered as an alternative. - Vue.js experience is preferred; experience with React, Svelte, or Angular version 1.6 or higher may be considered as an alternative. - Proven ability to work independently while leading, mentoring, collaborating with, and supporting team members to solve complex technical problems across multiple concurrent projects. - Proven ability to architect software products and solution prototypes, establish technical standards, validate solution strategies, and explain the tradeoffs of complex design alternatives to technical and non-technical stakeholders. - Experience with microservices architecture, API design patterns, containerization using Docker or Kubernetes, serverless computing, and modern CI/CD practices for enterprise-scale applications. - Familiarity with the AWS Serverless Application Model (SAM) and proven design patterns, such as Model-View-Controller, Circuit Breaker, and Event-Driven patterns, is required. Candidates must also be able to design and build cloud-based software products that align with AWS Well-Architected Framework principles. - This hands-on cloud software architecture and engineering leadership role requires the ability to design, build, deploy, and architect custom AWS cloud applications while leading technical teams. - Proven ability to design, build, test, and deploy software products and solutions on AWS, with demonstrated success in client-facing roles and stakeholder management. - In-depth understanding of Agile and Scaled Agile practices, with extensive experience planning and implementing software products in agile environments while leading development teams. - Excellent written and verbal communication skills, with the ability to understand customer requirements, engineer solutions, and present complex technical concepts to executive stakeholders. - Candidates must be legally authorized to work in the United States without the need for employer sponsorship. Due to the nature of this role and associated government clearance requirements, candidates must be U.S. citizens or lawful permanent residents (Green Card holders) to be eligible for consideration. - Must be able to OBTAIN and MAINTAIN a Federal or DoD "PUBLIC TRUST"; candidates must obtain approved adjudication of their PUBLIC TRUST prior to onboarding with Guidehouse. Candidates with an ACTIVE PUBLIC TRUST or SUITABILITY are preferred. Note: Some of these are preferences (Django experience preferred, Vue.js preferred). But we can keep them in Requirements or Skills. We'll treat them as Requirements (some are preferred). But we could move preferred to Skills or Qualifications. Skills: technical skills: proficiency in Python/JavaScript, Django, Vue.js, Flask, FastAPI, Falcon, SQLAlchemy, React, Svelte, Angular, microservices, API design, Docker, Kubernetes, serverless, CI/CD, AWS SAM, MVC, Circuit Breaker, Event-Driven, AWS Well-Architected, Agile, communication, etc. Also nice-to-have: AWS Certified Solutions Architect – Professional, AWS Certified Developer – Associate, experience with Flask, Docker, Amazon EKS/Kubernetes, AWS Step Functions, Amazon EventBridge, AWS Lambda, Amazon API Gateway, Elasticsearch, caching frameworks, Redis, Memcached, Amazon RDS for PostgreSQL, MongoDB, experience supporting solution architecture for technical proposal volumes, white papers, RFPs/RFIs, thought leadership initiatives, experience with advanced monitoring and observability tools, performance tuning, capacity planning, proficiency delivering cloud-based software products using modern CI/CD pipeline tools, collaborating with dev, ops, security, contributions to open-source, technical publications, thought leadership. We could put all these under Skills, separating required vs nice-to-have maybe not needed. Benefits: from "What We Offer". List: - Medical, Rx, Dental & Vision Insurance - Personal and Family Sick Time & Company Paid Holidays - Parental Leave - 401(k) Retirement Plan - Group Term Life and Travel Assistance - Voluntary Life and AD&D Insurance - Health Savings Account, Health Care & Dependent Care Flexible Spending Accounts - Transit and Parking Commuter Benefits - Short-Term & Long-Term Disability - Tuition Reimbursement, Personal Development, Certifications & Learning Opportunities - Employee Referral Program - Corporate Sponsored Events & Community Outreach - Care.com annual membership - Employee Assistance Program - Supplemental Benefits via Corestream (Critical Care, Hospital Indemnity, Accident Insurance, Legal Assistance and ID theft protection, etc.) - Position may be eligible for a discretionary variable incentive bonus We should not include boilerplate about Guidehouse (EEO etc). So omit that. Now produce HTML. Structure:

  About the role

  Job Family: Software Development & Support. Travel Required: Up to 10%. Clearance Required: Ability to Obtain Public Trust.

  Responsibilities

  • ...
  ...