Senior Generative AI Engineer - AWS
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: equal opportunity etc. Also remove navigation/cookie etc. Not present.
We need to preserve all substantive information. So we need to include the description paragraphs, responsibilities bullet list, minimum requirements bullet list, desired skills bullet list, benefits bullet list.
We need to format as HTML fragment.
Let's extract content.
About the role: "Quevera is seeking a highly experienced Senior Generative AI Engineer – AWS with an active TS/SCI clearance with Polygraph to support a Generative AI optimization engagement for a large-scale enterprise customer in Herndon, Virginia and Springfield, Virginia. This role focuses on enterprise-scale Generative AI optimization and modernization using AWS cloud architecture and GenAI technologies. You will work embedded with customer Scrum teams to design and implement intelligent model routing and orchestration, conversation-context solutions, and scalable GenAI capabilities for production environments."
We can put that in a
.
Responsibilities: list items:
- Design and implement intelligent model-routing logic using ML-based classification to route requests to appropriate LLMs based on conversational context, task complexity, and performance requirements.
- Build and maintain orchestration layers using AWS Bedrock, LangChain, or custom frameworks to support multi-model workflows.
- Train, evaluate, and iterate on classification models using evaluation frameworks and feedback loops.
- Architect conversation-context analysis, retrieval, and embedding strategies to interpret user intent across multi-turn interactions.
- Develop prompt-engineering standards and context-window management techniques supporting intent classification and routing.
- Architect enterprise-scale GenAI solutions with high availability, performance optimization, and cost management.
- Apply GenAI platform practices including observability, model evaluation, guardrails, responsible AI controls, and versioning.
- Design and maintain data extraction and transformation pipelines supporting model training, evaluation, and enterprise application integration.
- Engage with customer stakeholders and technical counterparts to gather requirements, validate solutions, and participate in Agile/Scrum ceremonies.
- Collaborate with the Engagement Manager to track progress and risks and produce technical documentation, architecture diagrams, and handoff artifacts.
Minimum Requirements (list):
- Active TS/SCI clearance with Polygraph required.
- Five (5) or more years of software development and cloud architecture experience.
- Two (2) or more years of hands-on AWS experience with production workloads.
- Two (2) or more years of experience with Generative AI technologies and LLM deployment.
- Proven track record of enterprise-scale architecture design and implementation.
- Experience with NatSec customers.
- Deep understanding of GenAI foundation models and deployment patterns.
- Strong programming skills in Python and infrastructure-as-code tools.
- Experience with vector databases and semantic search technologies.
- Expert-level knowledge of AWS services, including Amazon Bedrock, OpenSearch Service, CloudWatch, ECS/EKS, and RDS/DynamoDB.
- Strong understanding of security automation and compliance frameworks.
- Ability to work independently and drive initiatives with minimal oversight.
- Strong problem-solving and analytical thinking capabilities.
- Experience leading technical discussions and influencing architecture decisions.
- Ability to work in ambiguous, fast-paced environments with a focus on delivering measurable customer outcomes.
- Must be able to obtain and maintain Springfield, VA customer accounts.
- Must be able to travel onsite periodically for meetings and ceremonies.
Desired Skills (list):
- Ability to contribute to complex technical challenges and prototype innovative solutions.
- Ability to effectively transfer knowledge to customer teams.
- Ability to balance strategic thinking with hands-on implementation.
- Ability to deliver enterprise-grade solutions under tight timelines.
Benefits (list):
- 100% employer-paid medical coverage (optional plan)
- Competitive options for Medical, Dental and Vision insurance
- Employer-paid short-term and long-term disability coverage
- Employer-paid life insurance
- $5,000 annually for education, training, certifications, and professional development
- Career advancement through our structured iQTouch Program
- Up to 6% 401(k) match
- Additional 4% profit-sharing contribution, at company discretion
Also there is a paragraph about Award-Winning Culture: "Quevera was recognized as a Top Workplace in the Washington, DC/Baltimore region for 2025, marking our fifth consecutive year receiving this distinction based on employee feedback." And "At Quevera, we believe exceptional people deserve exceptional opportunities. We're more than just a workplace—we're a team of innovators, problem-solvers, and industry experts committed to delivering mission-critical solutions while fostering professional growth, collaboration, and technical excellence."
We could include that as part of About the role or maybe a separate section like "About Quevera". But the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but better to stick to those. The "Award-Winning Culture" and the closing paragraph could be considered part of Benefits or About the role? Might be better to incorporate into About the role or maybe a separate "About Quevera" but not required. Since we need to preserve all substantive information, we need to include that text somewhere. Could add a
after Benefits or within Benefits? Probably better to add a separate section like "About Quevera" but not in the list. However instruction says "Prefer a few substantive sections over many thin ones." Could combine the culture paragraph into Benefits or About the role. The About the role currently is about the role; we could extend it to include the culture paragraph as part of About Quevera but maybe better to add a separate section "About Quevera" but not in the prescribed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe, we could incorporate the culture paragraph into Benefits section as an extra bullet? But it's not a benefit. Could add a
after Benefits without a heading? That would be stray text. Better to add a section "About Quevera" with
About Quevera
. The instruction didn't forbid that; it just gave examples. I think it's acceptable.
But we must not repeat the job title as a heading. That's fine.
We must not include Pay or Schedule sections because not present.
We must not include boilerplate like EEO etc. Remove that.
Thus final HTML:
About the role
Quevera is seeking a highly experienced Senior Generative AI Engineer – AWS with an active TS/SCI clearance with Polygraph to support a Generative AI optimization engagement for a large-scale enterprise customer in Herndon, Virginia and Springfield, Virginia. This role focuses on enterprise-scale Generative AI optimization and modernization using AWS cloud architecture and GenAI technologies. You will work embedded with customer Scrum teams to design and implement intelligent model routing and orchestration, conversation-context solutions, and scalable GenAI capabilities for production environments.
Responsibilities
- Design and implement intelligent model-routing logic using ML-based classification to route requests to appropriate LLMs based on conversational context, task complexity, and performance requirements.
- Build and maintain orchestration layers using AWS Bedrock, LangChain, or custom frameworks to support multi-model workflows.
- Train, evaluate, and iterate on classification models using evaluation frameworks and feedback loops.
- Architect conversation-context analysis, retrieval, and embedding strategies to interpret user intent across multi-turn interactions.
- Develop prompt-engineering standards and context-window management techniques supporting intent classification and routing.
- Architect enterprise-scale GenAI solutions with high availability, performance optimization, and cost management.
- Apply GenAI platform practices including observability, model evaluation, guardrails, responsible AI controls, and versioning.
- Design and maintain data extraction and transformation pipelines supporting model training, evaluation, and enterprise application integration.
- Engage with customer stakeholders and technical counterparts to gather requirements, validate solutions, and participate in Agile/Scrum ceremonies.
- Collaborate with the Engagement Manager to track progress and risks and produce technical documentation, architecture diagrams, and handoff artifacts.
Requirements
- Active TS/SCI clearance with Polygraph required.
- Five (5) or more years of software development and cloud architecture experience.
- Two (2) or more years of hands-on AWS experience with production workloads.
- Two (2) or more years of experience with Generative AI technologies and LLM deployment.
- Proven track record of enterprise-scale architecture design and implementation.
- Experience with NatSec customers.
- Deep understanding of GenAI foundation models and deployment patterns.
- Strong programming skills in Python and infrastructure-as-code tools.
- Experience with vector databases and semantic search technologies.
- Expert-level knowledge of AWS services, including Amazon Bedrock, OpenSearch Service, CloudWatch, ECS/EKS, and RDS/DynamoDB.
- Strong understanding of security automation and compliance frameworks.
- Ability to work independently and drive initiatives with minimal oversight.
- Strong problem-solving and analytical thinking capabilities.
- Experience leading technical discussions and influencing architecture decisions.
- Ability to work in ambiguous, fast-paced environments with a focus on delivering measurable customer outcomes.
- Must be able to obtain and maintain Springfield, VA customer accounts.
- Must be able to travel onsite periodically for meetings and ceremonies.
Skills
- Ability to contribute to complex technical challenges and prototype innovative solutions.
- Ability to effectively transfer knowledge to customer teams.
- Ability to balance strategic thinking with hands-on implementation.
- Ability to deliver enterprise-grade solutions under tight timelines.
Benefits
- 100% employer-paid medical coverage (optional plan)
- Competitive options for Medical, Dental and Vision insurance
- Employer-paid short-term and long-term disability coverage
- Employer-paid life insurance
- $5,000 annually for education, training, certifications, and professional development
- Career advancement through our structured iQTouch Program
- Up to 6% 401(k) match
- Additional 4% profit-sharing contribution, at company discretion
About Quevera
Quevera was recognized as a Top Workplace in the Washington, DC/Baltimore region for 2025, marking our fifth consecutive year receiving this distinction based on employee feedback. At Quevera, we believe exceptional people deserve exceptional opportunities. We're more than just a workplace—we're a team of innovators, problem-solvers, and industry experts committed to delivering mission-critical solutions while fostering professional growth, collaboration, and technical excellence.
Check we didn't include Pay or Schedule. Good.
We need to output only HTML fragment, no markdown fences.
Let's
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: equal opportunity etc. Also remove navigation/cookie etc. Not present. We need to preserve all substantive information. So we need to include the description paragraphs, responsibilities bullet list, minimum requirements bullet list, desired skills bullet list, benefits bullet list. We need to format as HTML fragment. Let's extract content. About the role: "Quevera is seeking a highly experienced Senior Generative AI Engineer – AWS with an active TS/SCI clearance with Polygraph to support a Generative AI optimization engagement for a large-scale enterprise customer in Herndon, Virginia and Springfield, Virginia. This role focuses on enterprise-scale Generative AI optimization and modernization using AWS cloud architecture and GenAI technologies. You will work embedded with customer Scrum teams to design and implement intelligent model routing and orchestration, conversation-context solutions, and scalable GenAI capabilities for production environments." We can put that in a
. Responsibilities: list items: - Design and implement intelligent model-routing logic using ML-based classification to route requests to appropriate LLMs based on conversational context, task complexity, and performance requirements. - Build and maintain orchestration layers using AWS Bedrock, LangChain, or custom frameworks to support multi-model workflows. - Train, evaluate, and iterate on classification models using evaluation frameworks and feedback loops. - Architect conversation-context analysis, retrieval, and embedding strategies to interpret user intent across multi-turn interactions. - Develop prompt-engineering standards and context-window management techniques supporting intent classification and routing. - Architect enterprise-scale GenAI solutions with high availability, performance optimization, and cost management. - Apply GenAI platform practices including observability, model evaluation, guardrails, responsible AI controls, and versioning. - Design and maintain data extraction and transformation pipelines supporting model training, evaluation, and enterprise application integration. - Engage with customer stakeholders and technical counterparts to gather requirements, validate solutions, and participate in Agile/Scrum ceremonies. - Collaborate with the Engagement Manager to track progress and risks and produce technical documentation, architecture diagrams, and handoff artifacts. Minimum Requirements (list): - Active TS/SCI clearance with Polygraph required. - Five (5) or more years of software development and cloud architecture experience. - Two (2) or more years of hands-on AWS experience with production workloads. - Two (2) or more years of experience with Generative AI technologies and LLM deployment. - Proven track record of enterprise-scale architecture design and implementation. - Experience with NatSec customers. - Deep understanding of GenAI foundation models and deployment patterns. - Strong programming skills in Python and infrastructure-as-code tools. - Experience with vector databases and semantic search technologies. - Expert-level knowledge of AWS services, including Amazon Bedrock, OpenSearch Service, CloudWatch, ECS/EKS, and RDS/DynamoDB. - Strong understanding of security automation and compliance frameworks. - Ability to work independently and drive initiatives with minimal oversight. - Strong problem-solving and analytical thinking capabilities. - Experience leading technical discussions and influencing architecture decisions. - Ability to work in ambiguous, fast-paced environments with a focus on delivering measurable customer outcomes. - Must be able to obtain and maintain Springfield, VA customer accounts. - Must be able to travel onsite periodically for meetings and ceremonies. Desired Skills (list): - Ability to contribute to complex technical challenges and prototype innovative solutions. - Ability to effectively transfer knowledge to customer teams. - Ability to balance strategic thinking with hands-on implementation. - Ability to deliver enterprise-grade solutions under tight timelines. Benefits (list): - 100% employer-paid medical coverage (optional plan) - Competitive options for Medical, Dental and Vision insurance - Employer-paid short-term and long-term disability coverage - Employer-paid life insurance - $5,000 annually for education, training, certifications, and professional development - Career advancement through our structured iQTouch Program - Up to 6% 401(k) match - Additional 4% profit-sharing contribution, at company discretion Also there is a paragraph about Award-Winning Culture: "Quevera was recognized as a Top Workplace in the Washington, DC/Baltimore region for 2025, marking our fifth consecutive year receiving this distinction based on employee feedback." And "At Quevera, we believe exceptional people deserve exceptional opportunities. We're more than just a workplace—we're a team of innovators, problem-solvers, and industry experts committed to delivering mission-critical solutions while fostering professional growth, collaboration, and technical excellence." We could include that as part of About the role or maybe a separate section like "About Quevera". But the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but better to stick to those. The "Award-Winning Culture" and the closing paragraph could be considered part of Benefits or About the role? Might be better to incorporate into About the role or maybe a separate "About Quevera" but not required. Since we need to preserve all substantive information, we need to include that text somewhere. Could add a
after Benefits or within Benefits? Probably better to add a separate section like "About Quevera" but not in the list. However instruction says "Prefer a few substantive sections over many thin ones." Could combine the culture paragraph into Benefits or About the role. The About the role currently is about the role; we could extend it to include the culture paragraph as part of About Quevera but maybe better to add a separate section "About Quevera" but not in the prescribed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe, we could incorporate the culture paragraph into Benefits section as an extra bullet? But it's not a benefit. Could add a
after Benefits without a heading? That would be stray text. Better to add a section "About Quevera" with
About Quevera
. The instruction didn't forbid that; it just gave examples. I think it's acceptable. But we must not repeat the job title as a heading. That's fine. We must not include Pay or Schedule sections because not present. We must not include boilerplate like EEO etc. Remove that. Thus final HTML:About the role
Quevera is seeking a highly experienced Senior Generative AI Engineer – AWS with an active TS/SCI clearance with Polygraph to support a Generative AI optimization engagement for a large-scale enterprise customer in Herndon, Virginia and Springfield, Virginia. This role focuses on enterprise-scale Generative AI optimization and modernization using AWS cloud architecture and GenAI technologies. You will work embedded with customer Scrum teams to design and implement intelligent model routing and orchestration, conversation-context solutions, and scalable GenAI capabilities for production environments.
Responsibilities
- Design and implement intelligent model-routing logic using ML-based classification to route requests to appropriate LLMs based on conversational context, task complexity, and performance requirements.
- Build and maintain orchestration layers using AWS Bedrock, LangChain, or custom frameworks to support multi-model workflows.
- Train, evaluate, and iterate on classification models using evaluation frameworks and feedback loops.
- Architect conversation-context analysis, retrieval, and embedding strategies to interpret user intent across multi-turn interactions.
- Develop prompt-engineering standards and context-window management techniques supporting intent classification and routing.
- Architect enterprise-scale GenAI solutions with high availability, performance optimization, and cost management.
- Apply GenAI platform practices including observability, model evaluation, guardrails, responsible AI controls, and versioning.
- Design and maintain data extraction and transformation pipelines supporting model training, evaluation, and enterprise application integration.
- Engage with customer stakeholders and technical counterparts to gather requirements, validate solutions, and participate in Agile/Scrum ceremonies.
- Collaborate with the Engagement Manager to track progress and risks and produce technical documentation, architecture diagrams, and handoff artifacts.
Requirements
- Active TS/SCI clearance with Polygraph required.
- Five (5) or more years of software development and cloud architecture experience.
- Two (2) or more years of hands-on AWS experience with production workloads.
- Two (2) or more years of experience with Generative AI technologies and LLM deployment.
- Proven track record of enterprise-scale architecture design and implementation.
- Experience with NatSec customers.
- Deep understanding of GenAI foundation models and deployment patterns.
- Strong programming skills in Python and infrastructure-as-code tools.
- Experience with vector databases and semantic search technologies.
- Expert-level knowledge of AWS services, including Amazon Bedrock, OpenSearch Service, CloudWatch, ECS/EKS, and RDS/DynamoDB.
- Strong understanding of security automation and compliance frameworks.
- Ability to work independently and drive initiatives with minimal oversight.
- Strong problem-solving and analytical thinking capabilities.
- Experience leading technical discussions and influencing architecture decisions.
- Ability to work in ambiguous, fast-paced environments with a focus on delivering measurable customer outcomes.
- Must be able to obtain and maintain Springfield, VA customer accounts.
- Must be able to travel onsite periodically for meetings and ceremonies.
Skills
- Ability to contribute to complex technical challenges and prototype innovative solutions.
- Ability to effectively transfer knowledge to customer teams.
- Ability to balance strategic thinking with hands-on implementation.
- Ability to deliver enterprise-grade solutions under tight timelines.
Benefits
- 100% employer-paid medical coverage (optional plan)
- Competitive options for Medical, Dental and Vision insurance
- Employer-paid short-term and long-term disability coverage
- Employer-paid life insurance
- $5,000 annually for education, training, certifications, and professional development
- Career advancement through our structured iQTouch Program
- Up to 6% 401(k) match
- Additional 4% profit-sharing contribution, at company discretion
About Quevera
Quevera was recognized as a Top Workplace in the Washington, DC/Baltimore region for 2025, marking our fifth consecutive year receiving this distinction based on employee feedback. At Quevera, we believe exceptional people deserve exceptional opportunities. We're more than just a workplace—we're a team of innovators, problem-solvers, and industry experts committed to delivering mission-critical solutions while fostering professional growth, collaboration, and technical excellence.
Check we didn't include Pay or Schedule. Good. We need to output only HTML fragment, no markdown fences. Let's