Front End Engineer II, Amazon Leo
- list? The benefits are described in prose; we could keep as
with the list. But rule: Use
- for any list of duties/requirements/benefits. So we should turn benefits into a list.
Similarly responsibilities: list.
Qualifications: Basic Qualifications and Preferred Qualifications could be combined into Requirements section? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements (maybe combine basic and preferred) or separate Qualifications and Skills. But we need to decide.
We have Basic Qualifications (2+ years experience, 1+ years CS fundamentals, experience using JS frameworks such as angular and react). Preferred Qualifications: agile experience, experience with common front-end technologies such as HTML, CSS, JS, TypeScript, Node.
We could put Requirements section with Basic Qualifications as required, and maybe Skills section with Preferred Qualifications? Or combine.
Better: Use Requirements for basic qualifications, Skills for preferred qualifications (or technologies). But we need to follow instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include multiple of those as appropriate. We need to avoid empty sections. Thus we can have:
About the role
with description paragraph.Responsibilities
with- list from "Key job responsibilities" plus maybe day in the life? But day in the life is narrative; could be included in About the role or separate? Probably keep as part of About the role.
We have "A day in the life" narrative; could be included in About the role as extra paragraph.
Requirements
with basic qualifications list.Skills
with preferred qualifications list (or maybe technologies). Could also include "Experience using JavaScript frameworks such as angular and react" as skill. But we already have that in basic qualifications. Might duplicate. Let's think: Basic qualifications includes experience using JS frameworks such as angular and react. Preferred qualifications includes agile experience, experience with common front-end technologies such as HTML, CSS, JS, TypeScript, Node. We could put Requirements: basic qualifications (2+ years experience, 1+ years CS fundamentals, experience using JS frameworks such as angular and react). Skills: preferred qualifications (agile experience, experience with HTML, CSS, JS, TypeScript, Node). That seems fine.Benefits
with list.Pay
with salary range and mention sign-on payments and RSUs. We should not include Schedule. We also need to include location? Not required as heading; could be included in About the role paragraph or maybe as a short p. The location is "USA, WA, Redmond". Could be included in About the role. We also need to include Export Control Requirement (citizenship). That's substantive; maybe include in Requirements or a separate note? Could be part of Requirements as a bullet. We should preserve all substantive info: export control requirement. Thus in Requirements we can add bullet: "Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum." Now we need to remove boilerplate: equal opportunity employer, disability accommodation, etc. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; maybe we keep as part of benefits? It's a reference; but it's not substantive detail about benefits; it's a pointer. Might be considered boilerplate? It's not EEO but it's a link. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is not substantive detail about benefits; it's a reference. Could be omitted? It's not required to keep. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not exactly those; it's a reference to benefits page. Might be considered navigation? It's a URL. I'd say we can keep it as part of benefits paragraph, but it's not a list item. However we are converting benefits to list; we could add a list item "Learn more about our benefits: https://amazon.jobs/en/benefits". That seems okay. But we need to preserve ALL substantive information; the link is substantive? It's a pointer to more info; but it's not a benefit itself. Might be okay to keep. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:About the role
Amazon Leo is building a global e-commerce experience for Internet Service Provider (ISP) customers, and we need a Front End Engineer II to help us do it. You will work with React and Next.js to design, build, and ship features that serve customers worldwide. Many of these experiences are built from zero-to-one, so you will regularly move from ambiguous problem to working product. You will own the full software development lifecycle, collaborating with product, marketing, business, and backend engineering partners to deliver accessible, performant interfaces. If you enjoy working with AI-driven development workflows, picking up new frameworks quickly, and turning complex requirements into clean user experiences, this is the role for you. Export Control Requirement: Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum. The team is based in Redmond, WA, USA.
But we already have About The Team paragraph; we could incorporate that. Better: About the role includes description of role and maybe team. We have "About The Team" paragraph: "We are part of the Leo Commerce engineering organization at Amazon, building the e-commerce experience for a global ISP customer base. Our team works closely with backend commerce services, product, marketing, and business partners to launch new experiences from scratch. We are scaling the team and investing in AI-based development and operational workflows to meet the growing needs of our customers. If you are looking for a place where you can grow your expertise by tackling new problems regularly alongside an inclusive group of engineers, we would be glad to have you." We could include that in About the role or separate section "About the team". But headings list includes About the role only; not About the team. Could incorporate into About the role. Thus About the role paragraph will be long; maybe split into twoelements? The rule: use
for prose. So we can have multiple
under the heading. Thus:
About the role
Amazon Leo is building a global e-commerce experience for Internet Service Provider (ISP) customers, and we need a Front End Engineer II to help us do it. You will work with React and Next.js to design, build, and ship features that serve customers worldwide. Many of these experiences are built from zero-to-one, so you will regularly move from ambiguous problem to working product. You will own the full software development lifecycle, collaborating with product, marketing, business, and backend engineering partners to deliver accessible, performant interfaces. If you enjoy working with AI-driven development workflows, picking up new frameworks quickly, and turning complex requirements into clean user experiences, this is the role for you.
Export Control Requirement: Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum.
About the team: We are part of the Leo Commerce engineering organization at Amazon, building the e-commerce experience for a global ISP customer base. Our team works closely with backend commerce services, product, marketing, and business partners to launch new experiences from scratch. We are scaling the team and investing in AI-based development and operational workflows to meet the growing needs of our customers. If you are looking for a place where you can grow your expertise by tackling new problems regularly alongside an inclusive group of engineers, we would be glad to have you. The team is based in Redmond, WA, USA.
Now Responsibilities:Responsibilities
- Design and build front-end features for the Amazon Leo e-commerce platform using React and Next.js, taking projects from concept through deployment and ongoing operation.
- Collaborate with product managers, UX designers, marketing, and backend commerce service teams to translate customer and business needs into accessible, scalable solutions that work across devices and browsers.
- Leverage agentic development workflows and generative AI tools to accelerate feature delivery, and identify opportunities to improve infrastructure using AWS native services.
- Participate actively in code reviews, providing constructive feedback to teammates while coaching others on front-end best practices, UI design patterns, and maintainable coding standards.
- Write clear documentation for your team's software and train new team members on how it is constructed, tested, and operated.
- list from "Key job responsibilities" plus maybe day in the life? But day in the life is narrative; could be included in About the role or separate? Probably keep as part of About the role.
We have "A day in the life" narrative; could be included in About the role as extra paragraph.
- for any list of duties/requirements/benefits. So we should turn benefits into a list.
Similarly responsibilities: list.
Qualifications: Basic Qualifications and Preferred Qualifications could be combined into Requirements section? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements (maybe combine basic and preferred) or separate Qualifications and Skills. But we need to decide.
We have Basic Qualifications (2+ years experience, 1+ years CS fundamentals, experience using JS frameworks such as angular and react). Preferred Qualifications: agile experience, experience with common front-end technologies such as HTML, CSS, JS, TypeScript, Node.
We could put Requirements section with Basic Qualifications as required, and maybe Skills section with Preferred Qualifications? Or combine.
Better: Use Requirements for basic qualifications, Skills for preferred qualifications (or technologies). But we need to follow instruction: "Use