Lead Gen AI Full Stack Engineer – eCommerce
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to not repeat job title as heading.
We need to not put Job ID/requisition numbers as headings.
We need to include a section only when posting has real, specific content for it.
We need to prefer few substantive sections over many thin ones.
Thus we can combine some sections: maybe "About the role" includes role summary and responsibilities. "Requirements" includes qualifications and skills. "Benefits" includes company benefits. "Pay" includes pay range. "Schedule" includes hybrid schedule.
We need to avoid filler like "commensurate with experience" etc. Not present.
Let's extract content.
Role Summary paragraph:
"Join our eCommerce Team as a Lead Gen AI Full Stack Engineer, owning the full stack end-to-end to design and ship production GenAI products on AWS that transform how engineering, operations, and business teams work —while improving eCommerce products and user experience for millions of customers. You’ll build intelligent, real-time experiences by engineering the full stack — modern UIs, high-throughput backend services, RAG systems, and autonomous AI agents — on AWS with Claude, Bedrock, and the modern LLM ecosystem. Success requires rapidly understanding complex distributed systems, debugging across the stack, and shipping from prototype to production. This is a Hybrid position located at our Frisco, TX. You will be required to be on-site 2 to 3 days a week on a as needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time."
That's a paragraph.
Then "About The Role" bullet points:
- Collaborate with business and engineering stakeholders to translate requirements into technical specifications and execute end-to-end delivery
- Engineer the full stack: modern frontends and backend services for our eCommerce platform serving millions of customers, leveraging databases to deliver scalable, high-performance experiences
- Work closely with senior leadership to drive architecture decisions and technical direction for GenAI initiatives — developing solutions that improve organizational productivity and customer experience
- Design and ship production LLM products — conversational chatbots, AI summarization, operational copilots powered by RAG pipelines (vector search, reranking), and autonomous AI agents with tool orchestration and safety guardrails
That's responsibilities.
Then "About You" bullet points:
- 9+ years of full-stack engineering with proven product ownership and large-scale production experience; 2+years shipping production LLM applications with measurable business impact (eCommerce domain experience is a plus)
- Expert across modern full-stack: TypeScript, Node.js (NestJS), React 18, Next.js, Python (FastAPI),SQL/NoSQL databases, and big data ecosystem (Spark, Hadoop, Kafka, data lakes)
- Strong cloud and infrastructure experience: distributed systems (microservices, event-driven architecture, API design), cloud-native AWS delivery with hands-on experience in Lambda, ECS/EKS, API Gateway, DynamoDB, RDS, S3, CloudWatch, SQS/SNS, and CI/CD pipelines
- Deep GenAI experience: Claude, OpenAI, AWS Bedrock, LangGraph, RAG systems (vector search, reranking), prompt engineering, and evaluation — with hands-on use of AI coding tools (Claude Code, Cursor, GitHub Copilot) to ship at high velocity
- Strong observability expertise — uses metrics, logs, and traces to understand complex distributed systems, identify bottlenecks, surface insights, and resolve production issues across the full stack
That's qualifications/skills.
Then "Company Overview" paragraph:
"McAfee is a leader in personal security for consumers. Focused on protecting people, not just devices, McAfee consumer solutions adapt to users’ needs in an always online world, empowering them to live securely through integrated, intuitive solutions that protects their families and communities with the right security at the right moment."
That's company overview; maybe not needed as a section unless we have a specific heading like "About the company". Not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we may omit company overview or incorporate into About the role? Probably we can omit as not required.
Then "Company Benefits And Perks" bullet list:
- We work hard to embrace diversity and inclusion and encourage everyone at McAfee to bring their authentic selves to work every day.
- We offer a variety of social programs, flexible work hours and family-friendly benefits to all of our employees.
- Bonus Program
- 401k Retirement
- Medical, Dental, Vision, Basic Life, Short Term Disability and Long-Term Disability Coverage
- Paid Parental Leave
- Support and Community Involvement
- 14 Paid Company Holidays
- Unlimited Paid Time Off for Exempt Employees
- 96 Hours of Sick Time and 120 Hours of Vacation for Non-Exempt Employees Accrued Each Year
- We're serious about our commitment to diversity which is why McAfee prohibits discrimination based on race, color, religion, gender, national origin, age, disability, veteran status, marital status, pregnancy, gender expression or identity, sexual orientation or any other legally protected status.
We need to remove EEO boilerplate? The last bullet about diversity is EEO statement; we should remove that as boilerplate. Also maybe the first bullet about diversity is also boilerplate? It's about diversity and inclusion; could be considered boilerplate but it's part of benefits? Might be okay to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove any EEO statements. The first bullet about diversity and inclusion could be considered EEO? It's about diversity and inclusion; might be considered EEO. Safer to remove it. Also the last bullet definitely EEO. So we keep the rest.
Thus benefits list:
- We offer a variety of social programs, flexible work hours and family-friendly benefits to all of our employees.
- Bonus Program
- 401k Retirement
- Medical, Dental, Vision, Basic Life, Short Term Disability and Long-Term Disability Coverage
- Paid Parental Leave
- Support and Community Involvement
- 14 Paid Company Holidays
- Unlimited Paid Time Off for Exempt Employees
- 96 Hours of Sick Time and 120 Hours of Vacation for Non-Exempt Employees Accrued Each Year
We could also keep "We work hard to embrace diversity..."? Probably remove.
Now Pay Range: "The anticipated compensation for this position is USD $135,910.00/Yr. - USD $223,285.00/Yr. depending on experience and qualifications."
Schedule: we have hybrid schedule info in role summary; we could extract that into a Schedule section.
We need to avoid duplication: The role summary already includes hybrid schedule; we could keep that in About the role or Schedule. Since we have a Schedule heading allowed, we can put schedule details there.
Thus we need to produce sections:
- About the role: maybe combine role summary paragraph and responsibilities bullet list? Or we could have About the role (role summary) and Responsibilities separate. But we prefer few substantive sections. Could combine role summary and responsibilities under About the role? But the instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings if they have content. But we prefer few substantive sections over many thin ones. However we have distinct content for each: About the role (role summary), Responsibilities (bullet list), Requirements/Qualifications/Skills (maybe combine), Benefits, Pay, Schedule.
We could combine Requirements, Qualifications, Skills into one section called "Requirements" (or "Qualifications") but we have both. The instruction list includes those as possible headings; we can choose to use only those with real content. We have qualifications and skills content; we could put them under "Requirements" (or "Qualifications") as a single section. Let's decide: Use "Requirements" heading and put the About You bullet list there (which includes years of experience, tech stack, cloud, GenAI, observability). That covers qualifications and skills.
Thus sections:
- About the role (role summary paragraph)
- Responsibilities (bullet list from About The Role)
- Requirements (bullet list from About You)
- Benefits (bullet list from Company Benefits And Perks, cleaned)
- Pay (paragraph with pay range)
- Schedule (paragraph with hybrid schedule details)
We need to ensure we don't repeat content. The role summary paragraph includes schedule info; we will move schedule info to Schedule section and remove from About the role paragraph to avoid duplication. So we need to edit the role summary paragraph to exclude the schedule sentences.
Original role summary paragraph includes: "This is a Hybrid position located at our Frisco, TX. You will be required to be on-site 2 to 3 days a week on a as needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time."
We'll remove those sentences from About the role paragraph.
Thus About the role paragraph becomes:
"Join our eCommerce Team as a Lead Gen AI Full Stack Engineer, owning the full stack end-to-end to design and ship production GenAI products on AWS that transform how engineering, operations, and business teams work —while improving eCommerce products and user experience for millions of customers. You’ll build intelligent, real-time experiences by engineering the full stack — modern UIs, high-throughput backend services, RAG systems, and autonomous AI agents — on AWS with Claude, Bedrock, and the modern LLM ecosystem. Success requires rapidly understanding complex distributed systems, debugging across the stack, and shipping from prototype to production."
Now Schedule section will contain the hybrid schedule details.
Now we need to output HTML fragment only, no markdown fences.
Let's craft:
About the role
Join our eCommerce Team as a Lead Gen AI Full Stack Engineer, owning the full stack end-to-end to design and ship production GenAI products on AWS that transform how engineering, operations, and business teams work —while improving eCommerce products and user experience for millions of customers. You’ll build intelligent, real-time experiences by engineering the full stack — modern UIs, high-throughput backend services, RAG systems, and autonomous AI agents — on AWS with Claude, Bedrock, and the modern LLM ecosystem. Success requires rapidly understanding complex distributed systems, debugging across the stack, and shipping from prototype to production.
Responsibilities
- Collaborate with business and engineering stakeholders to translate requirements into
for prose. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings. We need to include a section only when posting has real, specific content for it. We need to prefer few substantive sections over many thin ones. Thus we can combine some sections: maybe "About the role" includes role summary and responsibilities. "Requirements" includes qualifications and skills. "Benefits" includes company benefits. "Pay" includes pay range. "Schedule" includes hybrid schedule. We need to avoid filler like "commensurate with experience" etc. Not present. Let's extract content. Role Summary paragraph: "Join our eCommerce Team as a Lead Gen AI Full Stack Engineer, owning the full stack end-to-end to design and ship production GenAI products on AWS that transform how engineering, operations, and business teams work —while improving eCommerce products and user experience for millions of customers. You’ll build intelligent, real-time experiences by engineering the full stack — modern UIs, high-throughput backend services, RAG systems, and autonomous AI agents — on AWS with Claude, Bedrock, and the modern LLM ecosystem. Success requires rapidly understanding complex distributed systems, debugging across the stack, and shipping from prototype to production. This is a Hybrid position located at our Frisco, TX. You will be required to be on-site 2 to 3 days a week on a as needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time." That's a paragraph. Then "About The Role" bullet points: - Collaborate with business and engineering stakeholders to translate requirements into technical specifications and execute end-to-end delivery - Engineer the full stack: modern frontends and backend services for our eCommerce platform serving millions of customers, leveraging databases to deliver scalable, high-performance experiences - Work closely with senior leadership to drive architecture decisions and technical direction for GenAI initiatives — developing solutions that improve organizational productivity and customer experience - Design and ship production LLM products — conversational chatbots, AI summarization, operational copilots powered by RAG pipelines (vector search, reranking), and autonomous AI agents with tool orchestration and safety guardrails That's responsibilities. Then "About You" bullet points: - 9+ years of full-stack engineering with proven product ownership and large-scale production experience; 2+years shipping production LLM applications with measurable business impact (eCommerce domain experience is a plus) - Expert across modern full-stack: TypeScript, Node.js (NestJS), React 18, Next.js, Python (FastAPI),SQL/NoSQL databases, and big data ecosystem (Spark, Hadoop, Kafka, data lakes) - Strong cloud and infrastructure experience: distributed systems (microservices, event-driven architecture, API design), cloud-native AWS delivery with hands-on experience in Lambda, ECS/EKS, API Gateway, DynamoDB, RDS, S3, CloudWatch, SQS/SNS, and CI/CD pipelines - Deep GenAI experience: Claude, OpenAI, AWS Bedrock, LangGraph, RAG systems (vector search, reranking), prompt engineering, and evaluation — with hands-on use of AI coding tools (Claude Code, Cursor, GitHub Copilot) to ship at high velocity - Strong observability expertise — uses metrics, logs, and traces to understand complex distributed systems, identify bottlenecks, surface insights, and resolve production issues across the full stack That's qualifications/skills. Then "Company Overview" paragraph: "McAfee is a leader in personal security for consumers. Focused on protecting people, not just devices, McAfee consumer solutions adapt to users’ needs in an always online world, empowering them to live securely through integrated, intuitive solutions that protects their families and communities with the right security at the right moment." That's company overview; maybe not needed as a section unless we have a specific heading like "About the company". Not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we may omit company overview or incorporate into About the role? Probably we can omit as not required. Then "Company Benefits And Perks" bullet list: - We work hard to embrace diversity and inclusion and encourage everyone at McAfee to bring their authentic selves to work every day. - We offer a variety of social programs, flexible work hours and family-friendly benefits to all of our employees. - Bonus Program - 401k Retirement - Medical, Dental, Vision, Basic Life, Short Term Disability and Long-Term Disability Coverage - Paid Parental Leave - Support and Community Involvement - 14 Paid Company Holidays - Unlimited Paid Time Off for Exempt Employees - 96 Hours of Sick Time and 120 Hours of Vacation for Non-Exempt Employees Accrued Each Year - We're serious about our commitment to diversity which is why McAfee prohibits discrimination based on race, color, religion, gender, national origin, age, disability, veteran status, marital status, pregnancy, gender expression or identity, sexual orientation or any other legally protected status. We need to remove EEO boilerplate? The last bullet about diversity is EEO statement; we should remove that as boilerplate. Also maybe the first bullet about diversity is also boilerplate? It's about diversity and inclusion; could be considered boilerplate but it's part of benefits? Might be okay to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove any EEO statements. The first bullet about diversity and inclusion could be considered EEO? It's about diversity and inclusion; might be considered EEO. Safer to remove it. Also the last bullet definitely EEO. So we keep the rest. Thus benefits list: - We offer a variety of social programs, flexible work hours and family-friendly benefits to all of our employees. - Bonus Program - 401k Retirement - Medical, Dental, Vision, Basic Life, Short Term Disability and Long-Term Disability Coverage - Paid Parental Leave - Support and Community Involvement - 14 Paid Company Holidays - Unlimited Paid Time Off for Exempt Employees - 96 Hours of Sick Time and 120 Hours of Vacation for Non-Exempt Employees Accrued Each Year We could also keep "We work hard to embrace diversity..."? Probably remove. Now Pay Range: "The anticipated compensation for this position is USD $135,910.00/Yr. - USD $223,285.00/Yr. depending on experience and qualifications." Schedule: we have hybrid schedule info in role summary; we could extract that into a Schedule section. We need to avoid duplication: The role summary already includes hybrid schedule; we could keep that in About the role or Schedule. Since we have a Schedule heading allowed, we can put schedule details there. Thus we need to produce sections: - About the role: maybe combine role summary paragraph and responsibilities bullet list? Or we could have About the role (role summary) and Responsibilities separate. But we prefer few substantive sections. Could combine role summary and responsibilities under About the role? But the instructions say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple headings if they have content. But we prefer few substantive sections over many thin ones. However we have distinct content for each: About the role (role summary), Responsibilities (bullet list), Requirements/Qualifications/Skills (maybe combine), Benefits, Pay, Schedule.
We could combine Requirements, Qualifications, Skills into one section called "Requirements" (or "Qualifications") but we have both. The instruction list includes those as possible headings; we can choose to use only those with real content. We have qualifications and skills content; we could put them under "Requirements" (or "Qualifications") as a single section. Let's decide: Use "Requirements" heading and put the About You bullet list there (which includes years of experience, tech stack, cloud, GenAI, observability). That covers qualifications and skills.
Thus sections:
- About the role (role summary paragraph)
- Responsibilities (bullet list from About The Role)
- Requirements (bullet list from About You)
- Benefits (bullet list from Company Benefits And Perks, cleaned)
- Pay (paragraph with pay range)
- Schedule (paragraph with hybrid schedule details)
We need to ensure we don't repeat content. The role summary paragraph includes schedule info; we will move schedule info to Schedule section and remove from About the role paragraph to avoid duplication. So we need to edit the role summary paragraph to exclude the schedule sentences.
Original role summary paragraph includes: "This is a Hybrid position located at our Frisco, TX. You will be required to be on-site 2 to 3 days a week on a as needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time."
We'll remove those sentences from About the role paragraph.
Thus About the role paragraph becomes:
"Join our eCommerce Team as a Lead Gen AI Full Stack Engineer, owning the full stack end-to-end to design and ship production GenAI products on AWS that transform how engineering, operations, and business teams work —while improving eCommerce products and user experience for millions of customers. You’ll build intelligent, real-time experiences by engineering the full stack — modern UIs, high-throughput backend services, RAG systems, and autonomous AI agents — on AWS with Claude, Bedrock, and the modern LLM ecosystem. Success requires rapidly understanding complex distributed systems, debugging across the stack, and shipping from prototype to production."
Now Schedule section will contain the hybrid schedule details.
Now we need to output HTML fragment only, no markdown fences.
Let's craft:
About the role
Join our eCommerce Team as a Lead Gen AI Full Stack Engineer, owning the full stack end-to-end to design and ship production GenAI products on AWS that transform how engineering, operations, and business teams work —while improving eCommerce products and user experience for millions of customers. You’ll build intelligent, real-time experiences by engineering the full stack — modern UIs, high-throughput backend services, RAG systems, and autonomous AI agents — on AWS with Claude, Bedrock, and the modern LLM ecosystem. Success requires rapidly understanding complex distributed systems, debugging across the stack, and shipping from prototype to production.
Responsibilities
- Collaborate with business and engineering stakeholders to translate requirements into