Lead Agentic Software Engineer
About the role
with paragraphs. Then "Essential Functions Here’s the work you’ll do:" followed by bullet list of duties. That's responsibilities. SoResponsibilities
with- each duty.
Then after that: "This job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the employee. Duties, responsibilities and activities may change, or new ones may be assigned at any time." That's boilerplate, can be removed.
Then: "This role is a good fit for someone with these qualifications, experience and skills:" then list of Required Qualifications (bullets). Then "Preferred Qualifications:" list. Then "Supervisory Responsibilities: This position may supervise one or more employees." Then "Work environment and physical requirements: Prolonged periods sitting at a desk and working on a computer. Travel: Travel is minimal. Occasional local travel to client sites in the Washington, DC metropolitan area may be required." Then "Additional Information The base salary range of $120,700.00 to $193,100.00 represents the low and high of the company’s pay range for this position. The budgeted starting salary is in the lower half of the base salary range. Individual compensation will vary based on experience, skills, qualifications, internal equity, and business needs. Full-time employees are eligible for comprehensive health and wellness benefits, 401(k) employer contributions and matching, and other benefits." Then EEO etc.
We need sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Required Qualifications and Preferred Qualifications. Could combine into Qualifications section (maybe separate Required and Preferred?). But instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and include both required and preferred as list items, maybe differentiate? Could also have Requirements heading for required qualifications, and Skills heading for skills? But we have both qualifications and skills overlapping. Let's interpret:
- Requirements: maybe the mandatory qualifications (education, experience).
- Qualifications: maybe preferred qualifications?
- Skills: maybe technical skills list.
But we have a lot of detail; we can split as:
Requirements: Bachelor’s degree ... seven or more years building and shipping production web applications and platforms. Deep experience delivering and maintaining sites or applications on one or more enterprise content management platforms ... Strong full-stack experience with modern JavaScript frameworks (React, TypeScript), API design, and both relational and NoSQL databases. Hands-on experience engineering e-commerce solutions ... Production experience building with large language models ... Experience designing and implementing automated testing ... Clear technical communication ... U.S. citizenship, with the ability to obtain and maintain a U.S. government suitability or clearance determination if required for a project assignment.
That's required qualifications.
Qualifications (preferred): Experience with cloud AI services such as Google Vertex AI, Azure AI, or Amazon Bedrock. Experience delivering software in federal, state, or nonprofit environments, including work subject to security review, authority to operate (ATO) processes, or Section 508 compliance. Familiarity with the Model Context Protocol (MCP), vector databases, and agent evaluation or observability tooling. Experience with headless and decoupled architectures, including headless CMS platforms and front-end frameworks such as Next.js. Experience with DevOps practices and infrastructure as code, such as Terraform, Docker, and GitHub Actions. Depth in one or more enterprise commerce or experience platforms at scale — such as Adobe Commerce (Magento), Shopify Plus, Salesforce Commerce Cloud, or Adobe Experience Manager — and familiarity with PCI DSS and secure handling of payment data. Experience contributing to proposals, technical scoping, or estimates, and presenting technical work to clients.
Skills: maybe we could extract from responsibilities? But responsibilities already cover duties. Could also list technical skills like: architecting agentic systems, model/framework selection, tool and function calling, multi-step orchestration, context and memory, retrieval-augmented generation, guardrails, designing full-stack web apps, etc. But that seems redundant with responsibilities. Perhaps we can omit Skills section if not distinct. However instructions: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section, or we could have Requirements and Qualifications (preferred) and maybe Skills not needed. But we need to follow allowed headings; we can omit sections if no real specific content. So we can have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's six sections.
Now Benefits: "Full-time employees are eligible for comprehensive health and wellness benefits, 401(k) employer contributions and matching, and other benefits." Also earlier: "We offer competitive salaries, a comprehensive benefits package, a dynamic hybrid work environment, a vibrant workplace and growth opportunities in a variety of specialty areas." That's also benefits. So we can include that.
Pay: base salary range $120,700 to $193,100. Also note budgeted starting salary in lower half. So we can include that.
Schedule: "This is a hybrid role, requiring at least two days per week on site at Reingold’s headquarters in Alexandria, VA." Also maybe mention full-time, exempt. So schedule: full-time, hybrid (minimum 2 days onsite). Also travel minimal occasional local travel.
We should not include boilerplate like EEO, accommodation, drug policy, etc.
Now produce HTML fragment: use
for each section heading. Use
- for any list of duties/requirements/benefits. Use
for prose. We need to ensure we don't repeat job title. Not include Job ID. Let's craft. About the role: combine company description? The initial paragraph about Reingold could be included as part of About the role? Might be better to include a brief about Reingold as part of About the role. But we have a lot of role description already. We'll include both: a short paragraph about Reingold (the first paragraph) then the role details. But the first paragraph is about Reingold company, not role. However it's still substantive. We'll include it. Now Responsibilities: list each duty from "Essential Functions Here’s the work you’ll do:" bullet points. Let's extract them: - Bring AI agents and automation into client products, delivery pipelines, and internal operations — architecting agentic systems end to end: model and framework selection (e.g., Anthropic, OpenAI), tool and function calling, multi-step orchestration, context and memory, retrieval-augmented generation with embeddings and vector stores, and guardrails and fallback behavior — choosing approaches based on accuracy, latency, and cost. - Design, build, and ship production web applications, platforms, and integrations for client programs — architecting the full stack across modern JavaScript frameworks (React, TypeScript), server-side services, and relational and NoSQL data stores. - Define and run evaluations of agent behavior — task success, tool-call correctness, regression, reliability, and cost — and iterate on production systems based on measured results, holding the work to a real production bar rather than demos. - Establish responsible-AI and data-governance practices for public-sector and regulated work: secure handling of client data, human-in-the-loop review, and safeguards against hallucination, prompt injection, data leakage, and inappropriate disclosure. - Lead architecture and development on enterprise content management platforms — traditional and headless alike, including WordPress, Umbraco/.NET, Adobe Experience Manager, and comparable systems — and integrate them with AI services, third-party APIs, and client data. - Design and build e-commerce solutions on platforms such as Adobe Commerce, Shopify, or WooCommerce: storefront, catalog and order management, checkout and payment integration, and connections to fulfillment, CRM, and analytics. - Deploy and operate applications on a major cloud platform: CI/CD pipelines, containerized or serverless services, monitoring, and cost management. - Own quality on your work: build automated end-to-end, regression, and API test suites (for example with Playwright or Cypress) with CI quality gates, and implement automated accessibility testing against Section 508 and WCAG 2.1 AA (for example with axe or WAVE), leading remediation — applying AI-assisted techniques such as test generation, visual regression, and defect triage where they help. - Evaluate emerging AI platforms, models, and tools — including agentic coding tools such as Claude Code, Cursor, and GitHub Copilot — recommend adoption based on testing in real Reingold workflows, and build reusable components and internal tooling that teams can apply across engagements. - Partner with strategists, designers, account teams, and clients to turn business goals into technical requirements and explain tradeoffs to non-technical audiences — providing technical direction and code review on projects, acting as technical lead when we’re building agentic tooling for a client, and mentoring developers and sharing what you learn across the agency. That's 10 items. Now Requirements (required qualifications): list: - Bachelor’s degree in computer science, software engineering, information systems, or a related field, or equivalent professional experience, with seven or more years building and shipping production web applications and platforms. - Deep experience delivering and maintaining sites or applications on one or more enterprise content management platforms — for example WordPress, Umbraco/.NET, Adobe Experience Manager, or a headless CMS — with a track record of picking up unfamiliar platforms quickly. - Strong full-stack experience with modern JavaScript frameworks (React, TypeScript), API design, and both relational and NoSQL databases. - Hands-on experience engineering e-commerce solutions, including storefront, checkout and payment integration, catalog or order management, and reporting. - Production experience building with large language models — API integration, prompt engineering, retrieval-augmented generation, and agent or workflow automation — deployed to real users, not just prototypes. - Experience designing and implementing automated testing, including end-to-end or regression suites in CI pipelines. - Clear technical communication, in writing and in person, with both technical and non-technical audiences. - U.S. citizenship, with the ability to obtain and maintain a U.S. government suitability or clearance
- for any list of duties/requirements/benefits. Use