Software Development Engineer, Sponsored Products and Brands
Amazon · Seattle, WA · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements (Basic Qualifications), Skills? The posting includes Preferred Qualifications, Benefits, Pay (salary ranges), maybe Schedule not present. We must only include sections when there is real specific content. So we need sections: About the role (the description paragraph before responsibilities), Responsibilities (list), Basic Qualifications (list), Preferred Qualifications (list), Benefits (list), Pay (list of salary ranges). Also maybe "About The Team" could be part of About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can choose appropriate headings. We need to avoid repeating job title. Also we should not include Job ID etc. Remove boilerplate like EEO, accommodations, etc. Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract content:
Description paragraph: "Redefine how ads become a personalized, inspiring part of the customer journey — applying Generative AI and Large Language Models to transform advertising experiences across Amazon's shopping surfaces at massive scale. This is a rare opportunity to shape the next chapter of advertising engineering on one of the highest-impact teams in Amazon Ads. The Off-Search team within Sponsored Products and Brands (SPB) builds delightful ad experiences across surfaces beyond Search — product detail pages, the homepage, and store-in-store pages. We deliver highly personalized, context-aware advertising that adapts to individual shopper preferences, scales across diverse page types, and integrates seamlessly with organic recommendations. We operate full stack — from backend ads-retail edge services, ad retrieval, and ad auctions to shopper-facing experiences — all designed to deliver meaningful value. You'll build hyper-scale online systems, offline data pipelines, and ML infrastructure to transform core areas like ad retrieval, ad allocation, whole-page relevance, and differentiated recommendations."
That's the intro.
Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph (maybe could be part of responsibilities? It's more description but we can treat as part of About the role? Might be redundant. We could include it in About the role or separate? The instruction: include a section only when posting has real specific content. The "A day in the life" is substantive but maybe we can merge into About the role or Responsibilities. Safer to include as part of About the role? But we already have About the role from description. Could add that paragraph there.
Then "About The Team" paragraph.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then benefits paragraph: "Amazon is an equal opportunity employer..." that's boilerplate to remove. Then Los Angeles County applicants specifics (maybe not needed). Then "Our inclusive culture..." etc. Then accommodation link. Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location salary ranges: USA, CA, Palo Alto - 165,200.00 - 223,600.00 USD annually; USA, NY, New York - 158,100.00 - 213,800.00 USD annually; USA, WA, SEATTLE - 143,700.00 - 194,400.00 USD annually.
Company - Amazon.com Services LLC.
We need to output sections: About the role (maybe combine description + A day in the life + About The Team?), Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay.
We should not include Requirements (maybe same as Basic Qualifications). Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can choose appropriate headings. We need to avoid repeating job title. Also we should not include Job ID etc. Remove boilerplate like EEO, accommodations, etc. Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract content:
Description paragraph: "Redefine how ads become a personalized, inspiring part of the customer journey — applying Generative AI and Large Language Models to transform advertising experiences across Amazon's shopping surfaces at massive scale. This is a rare opportunity to shape the next chapter of advertising engineering on one of the highest-impact teams in Amazon Ads. The Off-Search team within Sponsored Products and Brands (SPB) builds delightful ad experiences across surfaces beyond Search — product detail pages, the homepage, and store-in-store pages. We deliver highly personalized, context-aware advertising that adapts to individual shopper preferences, scales across diverse page types, and integrates seamlessly with organic recommendations. We operate full stack — from backend ads-retail edge services, ad retrieval, and ad auctions to shopper-facing experiences — all designed to deliver meaningful value. You'll build hyper-scale online systems, offline data pipelines, and ML infrastructure to transform core areas like ad retrieval, ad allocation, whole-page relevance, and differentiated recommendations."
That's the intro.
Then "Key job responsibilities" list bullet points.
Then "A day in the life" paragraph (maybe could be part of responsibilities? It's more description but we can treat as part of About the role? Might be redundant. We could include it in About the role or separate? The instruction: include a section only when posting has real specific content. The "A day in the life" is substantive but maybe we can merge into About the role or Responsibilities. Safer to include as part of About the role? But we already have About the role from description. Could add that paragraph there.
Then "About The Team" paragraph.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then benefits paragraph: "Amazon is an equal opportunity employer..." that's boilerplate to remove. Then Los Angeles County applicants specifics (maybe not needed). Then "Our inclusive culture..." etc. Then accommodation link. Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location salary ranges: USA, CA, Palo Alto - 165,200.00 - 223,600.00 USD annually; USA, NY, New York - 158,100.00 - 213,800.00 USD annually; USA, WA, SEATTLE - 143,700.00 - 194,400.00 USD annually.
Company - Amazon.com Services LLC.
We need to output sections: About the role (maybe combine description + A day in the life + About The Team?), Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay.
We should not include Requirements (maybe same as Basic Qualifications). Use for each section.
We need to use - for any list of duties/requirements/benefits. For Benefits we have a paragraph describing benefits; we could turn into list items.
We must not repeat job title. No markdown.
Let's craft.
Section About the role: combine the initial description paragraph, plus "A day in the life" paragraph, plus "About The Team" paragraph? Might be too much but okay.
Better: About the role: initial description + A day in the life. About The Team could be separate section "About the Team" but not in given examples; but we could still use heading "About the Team". The instruction gave examples but not limited to those; we can use any heading as long as it's
. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not exclusive. Safer to stick to those headings. So we could put About the role covering all narrative content. Responsibilities list. Requirements (or Qualifications) for Basic Qualifications. Preferred Qualifications could be under Qualifications? Might be separate "Qualifications" heading with sub? But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (basic) and Qualifications (preferred) maybe. Or we could combine both under Qualifications with subheadings? But they want only headings, not subheadings. Could have two sections: Requirements (basic) and Qualifications (preferred). Benefits section. Pay section.
Let's do that.
Now extract lists.
Responsibilities bullet points:
- Apply Generative AI (GenAI) and Large Language Models (LLMs) to deliver more relevant, personalized ad and shopping experiences across Amazon surfaces
- Design, develop, and operate large-scale distributed systems for Sponsored Products and Brands advertising
- Build and optimize data pipelines and services that improve ad retrieval, allocation, whole-page relevance, and differentiated recommendations
- Design globally scalable solutions that evolve in the right long-term direction while delivering iterative value to customers
- Collaborate with applied scientists, product managers, and engineers to define and deliver customer-focused solutions end to end
- Write high-quality, maintainable code and participate in design and code reviews
- Drive operational excellence through monitoring, automation, and continuous improvement
Basic Qualifications list:
- 3+ years of non-internship professional software development experience
- 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
- Experience programming with at least one software programming language
- Experience in computer science fundamentals, including data structures, algorithms, and object-oriented design.
- Experience building and operating scalable distributed systems or services.
Preferred Qualifications list:
- Bachelor's degree in Computer Science, Engineering, Mathematics, or a related field
- 5+ years of software development experience
- Hands-on experience applying Generative AI (GenAI) or Large Language Model (LLM) to real-world problems at scale.
- Experience in building machine learning systems, recommendation engines, or large-scale data pipelines.
- Experience with AWS services or other cloud platforms.
- Strong track record of delivering complex projects end-to-end.
Benefits: from paragraph: health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave.
We could list each as separate
- . Also mention sign-on payments and RSUs? That's part of compensation not benefits. But we could include in Pay section.
Pay: location salary ranges list.
We also have mention: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation detail; could be included in Pay section as note.
Thus Pay section could include:
- Base salary range:
- Palo Alto, CA: $165,200 - $223,600 USD annually
- New York, NY: $158,100 - $213,800 USD annually
- Seattle, WA: $143,700 - $194,400 USD annually
- Total compensation includes sign-on payments and RSUs.
We should not include boilerplate like EEO, accommodations, etc.
Now craft HTML.
We'll output:
About the role
... combined paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
- ...
...
Make sure no extra text.
Now compose the About the role paragraph: combine description, A day in the life, About The Team.
Description paragraph: "Redefine how ads become a personalized, inspiring part of the customer journey — applying Generative AI and Large Language Models to transform advertising experiences across Amazon's shopping surfaces at massive scale. This is a rare opportunity to shape the next chapter of advertising engineering on one of the highest-impact teams in Amazon Ads. The Off-Search team within Sponsored Products and Brands (SPB) builds delightful ad experiences across surfaces beyond Search — product detail pages, the homepage, and store-in-store pages. We deliver highly personalized, context-aware advertising that adapts to individual shopper preferences, scales across diverse page types, and integrates seamlessly with organic recommendations. We operate full stack — from backend ads-retail edge services, ad retrieval, and ad auctions to shopper-facing experiences — all designed to deliver meaningful value. You'll build hyper-scale online systems, offline data pipelines, and ML infrastructure to transform core areas like ad retrieval, ad allocation, whole-page relevance, and differentiated recommendations."
A day in the life paragraph: "You'll help build hyper-scale online systems, offline data pipelines, and machine learning infrastructure — leveraging GenAI and LLMs to transform how ads are retrieved, allocated, and experienced. You'll have the opportunity to redesign how ads contribute to a personalized, relevant, and inspirational shopping experience, with the customer value proposition at the forefront."
About The Team paragraph: "The Sponsored Products and Brands team at Amazon Ads is re-imagining the advertising landscape through industry leading generative AI technologies, revolutionizing how millions of customers discover products and engage with brands across Amazon.com and beyond. We are at the forefront of re-inventing advertising experiences, bridging human creativity with artificial intelligence to transform every aspect of the advertising lifecycle from ad creation and optimization to performance analysis and customer insights. We are a passionate group of innovators dedicated to developing responsible and intelligent AI technologies that balance the needs of advertisers, enhance the shopping experience, and strengthen the marketplace. If you're energized by solving complex challenges and pushing the boundaries of what's possible with AI, join us in shaping the future of advertising."
Combine them into maybe two paragraphs? Could be one big paragraph but better to split into multiple tags. The instruction: use
for prose. So we can have multiple
under About the role.
Thus:
About the role
Redefine how ads become a personalized, inspiring part of the customer journey — applying Generative AI and Large Language Models to transform advertising experiences across
- for any list of duties/requirements/benefits. For Benefits we have a paragraph describing benefits; we could turn into list items.
We must not repeat job title. No markdown.
Let's craft.
Section About the role: combine the initial description paragraph, plus "A day in the life" paragraph, plus "About The Team" paragraph? Might be too much but okay.
Better: About the role: initial description + A day in the life. About The Team could be separate section "About the Team" but not in given examples; but we could still use heading "About the Team". The instruction gave examples but not limited to those; we can use any heading as long as it's
. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not exclusive. Safer to stick to those headings. So we could put About the role covering all narrative content. Responsibilities list. Requirements (or Qualifications) for Basic Qualifications. Preferred Qualifications could be under Qualifications? Might be separate "Qualifications" heading with sub? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (basic) and Qualifications (preferred) maybe. Or we could combine both under Qualifications with subheadings? But they want only headings, not subheadings. Could have two sections: Requirements (basic) and Qualifications (preferred). Benefits section. Pay section. Let's do that. Now extract lists. Responsibilities bullet points: - Apply Generative AI (GenAI) and Large Language Models (LLMs) to deliver more relevant, personalized ad and shopping experiences across Amazon surfaces - Design, develop, and operate large-scale distributed systems for Sponsored Products and Brands advertising - Build and optimize data pipelines and services that improve ad retrieval, allocation, whole-page relevance, and differentiated recommendations - Design globally scalable solutions that evolve in the right long-term direction while delivering iterative value to customers - Collaborate with applied scientists, product managers, and engineers to define and deliver customer-focused solutions end to end - Write high-quality, maintainable code and participate in design and code reviews - Drive operational excellence through monitoring, automation, and continuous improvement Basic Qualifications list: - 3+ years of non-internship professional software development experience - 2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience - Experience programming with at least one software programming language - Experience in computer science fundamentals, including data structures, algorithms, and object-oriented design. - Experience building and operating scalable distributed systems or services. Preferred Qualifications list: - Bachelor's degree in Computer Science, Engineering, Mathematics, or a related field - 5+ years of software development experience - Hands-on experience applying Generative AI (GenAI) or Large Language Model (LLM) to real-world problems at scale. - Experience in building machine learning systems, recommendation engines, or large-scale data pipelines. - Experience with AWS services or other cloud platforms. - Strong track record of delivering complex projects end-to-end. Benefits: from paragraph: health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. We could list each as separate
- . Also mention sign-on payments and RSUs? That's part of compensation not benefits. But we could include in Pay section.
Pay: location salary ranges list.
We also have mention: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation detail; could be included in Pay section as note.
Thus Pay section could include:
- Base salary range:
- Palo Alto, CA: $165,200 - $223,600 USD annually
- New York, NY: $158,100 - $213,800 USD annually
- Seattle, WA: $143,700 - $194,400 USD annually
- Total compensation includes sign-on payments and RSUs.
We should not include boilerplate like EEO, accommodations, etc.
Now craft HTML.
We'll output:
About the role
... combined paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
- ... ...
tags. The instruction: use
for prose. So we can have multiple
under About the role. Thus:
About the role
Redefine how ads become a personalized, inspiring part of the customer journey — applying Generative AI and Large Language Models to transform advertising experiences across