Principal Engineer - UI
American Eagle Outfitters Inc. · Pittsburgh, PA · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Use for headings. Use
for headings. Use - for lists,
for prose. Remove boilerplate.
We need to extract content from job description.
Title: Principal Engineer - UI (but we don't repeat as heading). Reports To: Director of Engineering, Location: Pittsburgh, PA.
We have "About American Eagle" paragraph. That could be "About the role"? Actually "About American Eagle" is company description, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have "Get To Know The Role" paragraph: description of role. That could be "About the role". We'll put that as
About the role
with content.
Then "What You’ll Do" list of duties: that is Responsibilities. We'll put
Responsibilities
with - each bullet.
Then "What You Bring" includes requirements, qualifications, skills. We need to separate into Requirements, Qualifications, Skills maybe. The instruction: prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have extensive list under "What You Bring" with bullet points (though not formatted as bullet list in source but each line starts with bold). We can treat as list.
We could split: Requirements (experience, years), Qualifications (education? none), Skills (technical). But maybe combine into one section "Requirements" covering all. However they ask to use headings like Requirements, Qualifications, Skills. We could create three sections if content distinct.
Let's parse "What You Bring":
- Extensive Technical Leadership: 10+ years of software engineering experience, with 3+ years in a Staff or Principal role leading the architectural direction for high-scale, enterprise-level web platforms.
- Mastery of Modern Web Architectures: Deep expertise in Next.js, React, and Node.js, with a proven ability to design scalable micro-frontend or "island" architectures that support multi-year framework transitions.
- Expertise in Backend-for-Frontend (BFF) Patterns: Proven track record of architecting and implementing BFF layers (via Node.js, GraphQL, or Express) to orchestrate data from multiple downstream microservices and legacy APIs, optimizing payload delivery for web and mobile clients.
- Legacy Modernization Experience: Proven track record of successfully decomposing and migrating complex legacy monoliths (e.g., Ember.js, Backbone, or Angular.js) into modern, high-performance environments without interrupting business operations.
- Design Systems & Storybook Expertise: Significant experience building, documenting, and scaling enterprise Design Systems using Storybook to ensure UI consistency and component reusability across multiple squads.
- Systems Thinking & Governance: Demonstrated experience in building and enforcing global engineering standards, including the creation of enterprise-grade boilerplates, CI/CD pipelines (Bitbucket), and automated quality gates.
- AI-First Mindset: Practical experience leveraging Agentic AI and LLMs (Gemini, Code Assist) to accelerate documentation, perform automated code audits, and improve overall engineering throughput.
- Performance-Driven Mentality: Deep understanding of Web Vitals, SEO optimization, and browser internals, with the ability to use Real User Monitoring (RUM) data to drive architectural decisions.
- Strategic Partner Management: Experience governing the technical output of distributed teams and external vendor partners, ensuring high-quality contributions and adherence to the "Definition of Done."
- Advanced Testing & Observability: Expert knowledge of enterprise testing suites (Playwright) and observability platforms (New Relic, Quantum Metric, OTe) to ensure system reliability during major technical shifts.
Then "Nice To Have" list (optional). Could be under Skills? Might treat as Skills.
We also have "Perks: Why You’ll Love it Here" list: Generous employee discount, Summer Fridays, Casual dress code, Hybrid schedule, FOMO events. That's benefits.
Pay/Benefits Information: includes description of pay determination, benefits list, PTO variable, discretionary bonuses. This is Pay and Benefits info.
Schedule: Job Schedule: Full time (from JOB INFO). Also location Pittsburgh, PA.
We need to include sections only if real specific content. Pay: we have actual starting pay determined by various factors... that's not specific numbers, but it's still content about pay. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they do state pay determination but not specific numbers. Is that considered filler? It says "Actual starting pay is determined by various factors, including but not limited to relevant experience and location." That's somewhat generic but still states something. It's not a specific number, but it's not "commensurate with experience" exactly; it's similar. Might be considered filler. Safer to omit Pay section if no concrete numbers. However they also list benefits details (health care, wellness, 401(k), etc.) which is specific. So Benefits section can be included.
Schedule: they state "Job Schedule: Full time". That's specific enough. So we can include Schedule section with
Full time
.
Now Benefits: we have list of benefits from Pay/Benefits Information plus perks list. We'll combine.
We need to avoid repeating job title. Also we should not include metadata like Job ID, Posting Date etc. We'll drop.
Now structure:
About the role
... from Get To Know The Role paragraph.
Responsibilities
- Drive Architectural Evolution: Lead the multi-year strategy for modernizing our core web platform, currently focused on a large-scale transition from a legacy Ember.js single-page application to a modern, edge-ready Next.js framework.
- Manage Hybrid Technical States: Design and oversee the interoperability layers that allow legacy and modern codebases to coexist seamlessly during transitional periods, ensuring zero impact on the customer experience.
- Own the Web Technical Foundation: Define and maintain the enterprise "Web Boilerplate" and core libraries, ensuring long-term consistency in state management, rendering patterns, and integration with the AEO Design System.
- Lead AI-Augmented Engineering: Pioneer the integration of Agentic AI (Cursor, Gemini, Qodo) into the SDLC to institutionalize institutional logic, automate testing, and accelerate the "Mean Time to Contribution" for distributed teams.
- Establish Technical Governance for Strategic Partners: Serve as the primary technical quality bar for vendor partners, enforcing standardized "Definition of Done" criteria and 100% automated ticket gating.
- Optimize Developer Experience (DX): Architect the local development environments, CI/CD feedback loops, and tooling that empower a global engineering team to ship code with high velocity and zero manual overhead.
- Monitor and Enforce Performance Budgets: Own the long-term roadmap for Core Web Vitals and SEO performance, utilizing Real User Monitoring (RUM) to validate architectural changes against business conversion.
- Collaborate as a Strategic Partner: Work closely with Product and UX leadership to translate a multi-year business vision into scalable, resilient technical roadmaps.
- Champion Internal Opportunities: Influence cross-functional technical direction by driving efficient uses of the web platform in other use cases beyond customer facing AE.com applications
Now Requirements/Qualifications/Skills. We could combine into one section "Requirements" with list of all What You Bring plus Nice To Have as optional skills. But we have headings for Requirements, Qualifications, Skills. Perhaps we can put:
Requirements
Extensive Technical Leadership: 10+ years of software engineering experience, with 3+ years in a Staff or Principal role leading the architectural direction for high-scale, enterprise-level web platforms.
Qualifications
Mastery of Modern Web Architectures: Deep expertise in Next.js, React, and Node.js, with a proven ability to design scalable micro-frontend or "island" architectures that support multi-year framework transitions.
... but that seems many sections.
Better to follow instruction: prefer a few substantive sections over many thin ones. So maybe combine all into one section "Requirements". But they gave examples of headings; we can still use only those we need. So we could have:
Requirements
- Extensive Technical Leadership: 10+ years of software engineering experience, with 3+ years in a Staff or Principal role leading the architectural direction for high-scale, enterprise-level web platforms.
- Mastery of Modern Web Architectures: Deep expertise in Next.js, React, and Node.js, with a proven ability to design scalable micro-frontend or "island" architectures that support multi-year framework transitions.
- Expertise in Backend-for-Frontend (BFF) Patterns: Proven track record of architecting and implementing BFF layers (via Node.js, GraphQL, or Express) to orchestrate data from multiple downstream microservices and legacy APIs, optimizing payload delivery for web and mobile clients.
- Legacy Modernization Experience: Proven track record of successfully decomposing and migrating complex legacy monoliths (e.g., Ember.js, Backbone, or Angular.js) into modern, high-performance environments without interrupting business operations.
- Design Systems & Storybook Expertise: Significant experience building, documenting, and scaling enterprise Design Systems using Storybook to ensure UI consistency and component reusability across multiple squads.
- Systems Thinking & Governance: Demonstrated experience in building and enforcing global engineering standards, including the creation of enterprise-grade boilerplates, CI/CD pipelines (Bitbucket), and automated quality gates.
- AI-First Mindset: Practical experience leveraging Agentic AI and LLMs (Gemini, Code Assist) to accelerate documentation, perform automated code audits, and improve overall engineering throughput.
- Performance-Driven Mentality: Deep understanding of Web Vitals, SEO optimization, and browser internals, with the ability to use Real User Monitoring (RUM) data to drive architectural decisions.
- Strategic Partner Management: Experience governing the technical output of distributed teams and external vendor partners, ensuring high-quality contributions and adherence to the "Definition of Done."
- Advanced Testing & Observability: Expert knowledge of enterprise testing suites (Playwright) and observability platforms (New Relic, Quantum Metric, OTe) to ensure system reliability during major technical shifts.
Then maybe a separate "Nice-to-have Skills" section? Could be under Skills.
We have Nice To Have list: Micro-Frontend (MFE) Orchestration, GraphQL, Event-Driven Architecture, Infrastructure as Code (IaC), Retail/E-commerce Specifics, Web Accessibility (a11y) Specialist, Experience with Optimizely experimentation platform, Experience with Google Tag Manager for 3rd-party integration management, including SGTM, Familiarity with native app development (iOS/Android) for cross-platform alignment, Enjoy wearing jeans to work every day (not just AE jeans :-)). The last is a fun note but still content.
We could put under Skills
with list.
Now Benefits: combine perks and benefits.
Benefits list from Pay/Benefits Information: health care benefits (medical, vision, dental); wellness benefits; 401(k) retirement benefits; life and disability insurance; employee stock purchase program; paid time off; paid sick leave; parental leave and benefits; discretionary bonuses and other incentives.
for prose. Remove boilerplate. We need to extract content from job description. Title: Principal Engineer - UI (but we don't repeat as heading). Reports To: Director of Engineering, Location: Pittsburgh, PA. We have "About American Eagle" paragraph. That could be "About the role"? Actually "About American Eagle" is company description, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have "Get To Know The Role" paragraph: description of role. That could be "About the role". We'll put that as
About the role
withcontent. Then "What You’ll Do" list of duties: that is Responsibilities. We'll put
Responsibilities
with- each bullet.
Then "What You Bring" includes requirements, qualifications, skills. We need to separate into Requirements, Qualifications, Skills maybe. The instruction: prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have extensive list under "What You Bring" with bullet points (though not formatted as bullet list in source but each line starts with bold). We can treat as list.
We could split: Requirements (experience, years), Qualifications (education? none), Skills (technical). But maybe combine into one section "Requirements" covering all. However they ask to use headings like Requirements, Qualifications, Skills. We could create three sections if content distinct.
Let's parse "What You Bring":
- Extensive Technical Leadership: 10+ years of software engineering experience, with 3+ years in a Staff or Principal role leading the architectural direction for high-scale, enterprise-level web platforms.
- Mastery of Modern Web Architectures: Deep expertise in Next.js, React, and Node.js, with a proven ability to design scalable micro-frontend or "island" architectures that support multi-year framework transitions.
- Expertise in Backend-for-Frontend (BFF) Patterns: Proven track record of architecting and implementing BFF layers (via Node.js, GraphQL, or Express) to orchestrate data from multiple downstream microservices and legacy APIs, optimizing payload delivery for web and mobile clients.
- Legacy Modernization Experience: Proven track record of successfully decomposing and migrating complex legacy monoliths (e.g., Ember.js, Backbone, or Angular.js) into modern, high-performance environments without interrupting business operations.
- Design Systems & Storybook Expertise: Significant experience building, documenting, and scaling enterprise Design Systems using Storybook to ensure UI consistency and component reusability across multiple squads.
- Systems Thinking & Governance: Demonstrated experience in building and enforcing global engineering standards, including the creation of enterprise-grade boilerplates, CI/CD pipelines (Bitbucket), and automated quality gates.
- AI-First Mindset: Practical experience leveraging Agentic AI and LLMs (Gemini, Code Assist) to accelerate documentation, perform automated code audits, and improve overall engineering throughput.
- Performance-Driven Mentality: Deep understanding of Web Vitals, SEO optimization, and browser internals, with the ability to use Real User Monitoring (RUM) data to drive architectural decisions.
- Strategic Partner Management: Experience governing the technical output of distributed teams and external vendor partners, ensuring high-quality contributions and adherence to the "Definition of Done."
- Advanced Testing & Observability: Expert knowledge of enterprise testing suites (Playwright) and observability platforms (New Relic, Quantum Metric, OTe) to ensure system reliability during major technical shifts.
Then "Nice To Have" list (optional). Could be under Skills? Might treat as Skills.
We also have "Perks: Why You’ll Love it Here" list: Generous employee discount, Summer Fridays, Casual dress code, Hybrid schedule, FOMO events. That's benefits.
Pay/Benefits Information: includes description of pay determination, benefits list, PTO variable, discretionary bonuses. This is Pay and Benefits info.
Schedule: Job Schedule: Full time (from JOB INFO). Also location Pittsburgh, PA.
We need to include sections only if real specific content. Pay: we have actual starting pay determined by various factors... that's not specific numbers, but it's still content about pay. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they do state pay determination but not specific numbers. Is that considered filler? It says "Actual starting pay is determined by various factors, including but not limited to relevant experience and location." That's somewhat generic but still states something. It's not a specific number, but it's not "commensurate with experience" exactly; it's similar. Might be considered filler. Safer to omit Pay section if no concrete numbers. However they also list benefits details (health care, wellness, 401(k), etc.) which is specific. So Benefits section can be included.
Schedule: they state "Job Schedule: Full time". That's specific enough. So we can include Schedule section with
Full time
. Now Benefits: we have list of benefits from Pay/Benefits Information plus perks list. We'll combine. We need to avoid repeating job title. Also we should not include metadata like Job ID, Posting Date etc. We'll drop. Now structure:About the role
... from Get To Know The Role paragraph.
Responsibilities
- Drive Architectural Evolution: Lead the multi-year strategy for modernizing our core web platform, currently focused on a large-scale transition from a legacy Ember.js single-page application to a modern, edge-ready Next.js framework.
- Manage Hybrid Technical States: Design and oversee the interoperability layers that allow legacy and modern codebases to coexist seamlessly during transitional periods, ensuring zero impact on the customer experience.
- Own the Web Technical Foundation: Define and maintain the enterprise "Web Boilerplate" and core libraries, ensuring long-term consistency in state management, rendering patterns, and integration with the AEO Design System.
- Lead AI-Augmented Engineering: Pioneer the integration of Agentic AI (Cursor, Gemini, Qodo) into the SDLC to institutionalize institutional logic, automate testing, and accelerate the "Mean Time to Contribution" for distributed teams.
- Establish Technical Governance for Strategic Partners: Serve as the primary technical quality bar for vendor partners, enforcing standardized "Definition of Done" criteria and 100% automated ticket gating.
- Optimize Developer Experience (DX): Architect the local development environments, CI/CD feedback loops, and tooling that empower a global engineering team to ship code with high velocity and zero manual overhead.
- Monitor and Enforce Performance Budgets: Own the long-term roadmap for Core Web Vitals and SEO performance, utilizing Real User Monitoring (RUM) to validate architectural changes against business conversion.
- Collaborate as a Strategic Partner: Work closely with Product and UX leadership to translate a multi-year business vision into scalable, resilient technical roadmaps.
- Champion Internal Opportunities: Influence cross-functional technical direction by driving efficient uses of the web platform in other use cases beyond customer facing AE.com applications
Requirements
Extensive Technical Leadership: 10+ years of software engineering experience, with 3+ years in a Staff or Principal role leading the architectural direction for high-scale, enterprise-level web platforms.
Qualifications
Mastery of Modern Web Architectures: Deep expertise in Next.js, React, and Node.js, with a proven ability to design scalable micro-frontend or "island" architectures that support multi-year framework transitions.
... but that seems many sections. Better to follow instruction: prefer a few substantive sections over many thin ones. So maybe combine all into one section "Requirements". But they gave examples of headings; we can still use only those we need. So we could have:Requirements
- Extensive Technical Leadership: 10+ years of software engineering experience, with 3+ years in a Staff or Principal role leading the architectural direction for high-scale, enterprise-level web platforms.
- Mastery of Modern Web Architectures: Deep expertise in Next.js, React, and Node.js, with a proven ability to design scalable micro-frontend or "island" architectures that support multi-year framework transitions.
- Expertise in Backend-for-Frontend (BFF) Patterns: Proven track record of architecting and implementing BFF layers (via Node.js, GraphQL, or Express) to orchestrate data from multiple downstream microservices and legacy APIs, optimizing payload delivery for web and mobile clients.
- Legacy Modernization Experience: Proven track record of successfully decomposing and migrating complex legacy monoliths (e.g., Ember.js, Backbone, or Angular.js) into modern, high-performance environments without interrupting business operations.
- Design Systems & Storybook Expertise: Significant experience building, documenting, and scaling enterprise Design Systems using Storybook to ensure UI consistency and component reusability across multiple squads.
- Systems Thinking & Governance: Demonstrated experience in building and enforcing global engineering standards, including the creation of enterprise-grade boilerplates, CI/CD pipelines (Bitbucket), and automated quality gates.
- AI-First Mindset: Practical experience leveraging Agentic AI and LLMs (Gemini, Code Assist) to accelerate documentation, perform automated code audits, and improve overall engineering throughput.
- Performance-Driven Mentality: Deep understanding of Web Vitals, SEO optimization, and browser internals, with the ability to use Real User Monitoring (RUM) data to drive architectural decisions.
- Strategic Partner Management: Experience governing the technical output of distributed teams and external vendor partners, ensuring high-quality contributions and adherence to the "Definition of Done."
- Advanced Testing & Observability: Expert knowledge of enterprise testing suites (Playwright) and observability platforms (New Relic, Quantum Metric, OTe) to ensure system reliability during major technical shifts.
Skills
with list. Now Benefits: combine perks and benefits. Benefits list from Pay/Benefits Information: health care benefits (medical, vision, dental); wellness benefits; 401(k) retirement benefits; life and disability insurance; employee stock purchase program; paid time off; paid sick leave; parental leave and benefits; discretionary bonuses and other incentives.