Front-End Technical Lead

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real content. The posting includes "Key Responsibilities" with subparts: Technical Leadership & Architecture, Delivery & Engineering Excellence, Team Leadership & Collaboration. Also "Required Qualifications & Experience" and "Preferred Qualifications". There's no explicit About the role, Benefits, Pay, Schedule. So we should include sections: Responsibilities, Requirements (maybe combine Required Qualifications & Experience as Requirements), Qualifications (maybe Preferred Qualifications as Qualifications? Actually they said sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: Responsibilities from Key Responsibilities. Requirements from Required Qualifications & Experience. Qualifications from Preferred Qualifications (or maybe Skills). Skills could be extracted from qualifications but we can just put Skills as a subsection? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to output based on content. We have content for Responsibilities, Requirements, Qualifications (preferred). Possibly Skills could be derived but not explicit separate. Better to output Responsibilities, Requirements, Qualifications. Not output About the role, Benefits, Pay, Schedule because no content. Also we should not repeat job title. Use

• for any list of duties/requirements/benefits. So we need to turn the bullet-like sentences into list items. The responsibilities are paragraphs with multiple sentences; we can split each sentence into
• . But we must preserve ALL substantive information; not invent or summarize away detail. So we need to keep each piece of info. Could keep each sentence as separate
• . Or we could keep paragraphs as

  and inside them use

  for lists? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So if we have a list of duties, we should use

    • . The responsibilities section is essentially a list of duties. So we should output
      • each duty. Similarly for requirements and qualifications. We need to extract each distinct duty sentence. Let's parse responsibilities: Technical Leadership & Architecture - Own the technical vision, architecture, engineering standards, delivery quality, and operational stability of the online ordering application across web, iOS, and Android. - Provide hands-on technical leadership for the shared Angular, Ionic, Capacitor, and TypeScript codebase. - Establish and enforce engineering standards for RxJS, NgRx, HTML5, SCSS, npm, Bootstrap, Axios, responsive design, reusable components, routing, service patterns, and environment configuration. - Design, troubleshoot, and maintain native wrappers and plugins supporting analytics, push notifications, geolocation, permissions, payments, deep linking, authentication, and other platform-specific capabilities. - Partner with the Web Front-End Lead supporting React 18, Gatsby, TypeScript, GraphQL, Apollo Client, SASS, React Testing Library, and Prismic CMS. - Collaborate with the Back-End Technical Lead on Node/Express services, GraphQL APIs, REST APIs, AWS AppSync, and third-party integrations. - Ensure robust and secure integration with Olo, Paytronix, Radar, FreedomPay, Ping Identity, Firebase, Google Analytics, Google Tag Manager, Quantum Metric, and other approved enterprise platforms. - Drive performance optimization, accessibility, security, observability, dependency upgrades, scalability, and technical-debt remediation across front-end channels. - Define and maintain coding standards, reusable component patterns, pull-request controls, unit-test expectations, quality gates, and technical documentation. Delivery & Engineering Excellence - Lead end-to-end front-end delivery for new capabilities, enhancements, defect remediation, and technical-debt initiatives across web and mobile ordering journeys. - Translate business requirements, UX designs, hero flows, acceptance criteria, and non-functional requirements into technical designs, implementation tasks, estimates, and release plans. - Contribute actively to backlog refinement, sprint planning, estimation, design reviews, demonstrations, and release planning. - Lead code reviews, merge approvals, dependency management, front-end design decisions, documentation, and engineering governance. - Define the testing strategy for Jest unit tests, Angular component and service testing, integration testing, UI testing, simulators, physical devices, responsive layouts, native plugins, and regression automation. - Ensure validation of critical customer capabilities, including Apple Pay, push notifications, authentication redirects, geolocation and geofencing, deep links, permissions, analytics events, and QA mobile builds. - Partner with QA and Automation Engineers to embed front-end tests into CI/CD pipelines and improve agreed quality, automation, and coverage measures. - Own remediation of accessibility findings and ensure new and modified components follow applicable WCAG and ADA requirements. - Own technical readiness and execution of iOS and Android releases, including versioning, signing, certificates, provisioning profiles, build configuration, release notes, store compliance, and rollout support. - Support QA application distribution through Firebase App Distribution and production publishing through Apple App Store Connect and Google Play Console. - Maintain iOS, Android, and web build pipelines in Azure DevOps using YAML, approved scripts, CLI tooling, and appropriate quality and release controls. - Provide technical leadership during deployments, hypercare, production monitoring, defect triage, and root-cause analysis. - Use Quantum Metric, Firebase Analytics, Google Analytics, Google Tag Manager, application logs, and approved dashboards to investigate customer-impacting issues, validate analytics events, and identify anomalies. - Partner with DevOps to improve build automation, deployment reliability, observability, alerting, front-end performance, and platform availability. - Drive continuous improvement against agreed delivery, productivity, quality, code coverage, automation, stability, and incident-reduction objectives. Team Leadership & Collaboration - Lead and mentor a distributed team of front-end leads and developers across onshore and offshore locations. - Provide technical direction, coaching, and knowledge sharing to strengthen engineering practices and platform understanding. - Create clear ownership across design, development, review, testing, release, technical documentation, and operational support activities. - Work closely with Product Owners, Digital Leads, UX/Design, Back-End Engineering, QA, Automation, DevOps, Security, and business stakeholders. - Promote constructive technical decision-making, early risk identification, dependency management, and transparent escalation. - Align the front-end team with Agile ceremonies, delivery commitments, release governance, and continuous-improvement practices. Now Required Qualifications & Experience: - 12 years of front-end engineering experience, including technical leadership of enterprise web or mobile applications. - Strong hands-on experience with Angular, Ionic, Capacitor, TypeScript, RxJS, and NgRx. - Demonstrated experience maintaining a shared codebase deployed across web, iOS, and Android. - Working knowledge of Swift, Xcode, Kotlin or Java, Android Studio, and Gradle. - Strong knowledge of responsive web design, mobile UX patterns, component architecture, state management, API integration, performance optimization, and accessibility. - Experience with GraphQL, REST APIs, authentication flows, third-party SDKs, and complex transactional customer journeys. - Experience with Azure DevOps, Git, pull requests, Firebase App Distribution, Apple App Store Connect, and Google Play Console. - Strong communication, technical documentation, stakeholder-management, mentoring, and distributed-team leadership skills. Preferred Qualifications: - Experience in QSR, restaurant ordering, digital commerce, payments, loyalty, geolocation, or other high-volume customer-facing applications. - Experience with Olo, Paytronix, Radar, FreedomPay, Ping Identity, Firebase, Quantum Metric, Google Analytics, or Google Tag Manager. - Working knowledge of React 18, Gatsby, Apollo Client, GraphQL, React Testing Library, SASS, and Prismic CMS. - Awareness of AWS-hosted application patterns, including Lambda, AppSync, ECS, S3, CloudFront, CloudWatch, and Cloudflare integrations. - Experience working in Agile delivery models with geographically distributed engineering, QA, DevOps, Product, and UX teams. We could also have a Skills section: maybe combine some skills from qualifications. But we already have Requirements and Qualifications. The instruction says we can include Skills section if there is real specific content. We could extract skills like "Strong communication, technical documentation, stakeholder-management, mentoring, and distributed-team leadership skills." but that's already in Required Qualifications. Might be redundant. Safer to just output Responsibilities, Requirements, Qualifications. We must not include headings with filler. So output:

        Responsibilities

        ...

        Requirements

        ...

        Qualifications

        ...
        Make sure to preserve all info. No extra text. Let's craft HTML. We need to ensure proper escaping? Not needed. We'll produce:

        Responsibilities

        • Own the technical vision, architecture, engineering standards, delivery quality, and operational stability of the online ordering application across web, iOS, and Android.
        • Provide hands-on technical leadership for the shared Angular, Ionic, Capacitor, and TypeScript codebase.
        • Establish and enforce engineering standards for RxJS, NgRx, HTML5, SCSS, npm, Bootstrap, Axios, responsive design, reusable components, routing, service patterns, and environment configuration.
        • Design, troubleshoot, and maintain native wrappers and plugins supporting analytics, push notifications, geolocation, permissions, payments, deep linking, authentication, and other platform-specific capabilities.
        • Partner with the Web Front-End Lead supporting React 18, Gatsby, TypeScript, GraphQL, Apollo Client, SASS, React Testing Library, and Prismic CMS.
        • Collaborate with the Back-End Technical Lead on Node/Express services, GraphQL APIs, REST APIs, AWS AppSync, and third-party integrations.
        • Ensure robust and secure integration with Olo, Paytronix, Radar, FreedomPay, Ping Identity, Firebase, Google Analytics, Google Tag Manager, Quantum Metric, and other approved enterprise platforms.
        • Drive performance optimization, accessibility, security, observability, dependency upgrades, scalability, and technical-debt remediation across front-end channels.
        • Define and maintain coding standards, reusable component patterns, pull-request controls, unit-test expectations, quality gates, and technical documentation.
        • Lead end-to-end front-end delivery for new capabilities, enhancements, defect remediation, and technical-debt initiatives across web and mobile ordering journeys.
        • Translate business requirements, UX designs, hero flows, acceptance criteria, and non-functional requirements into technical designs, implementation tasks, estimates, and release plans.
        • Contribute actively to backlog refinement, sprint planning, estimation, design reviews, demonstrations, and release planning.
        • Lead code reviews, merge approvals, dependency management, front-end design decisions, documentation, and engineering governance.
        • Define the testing strategy for Jest unit tests, Angular component and service testing, integration testing, UI testing, simulators, physical devices, responsive layouts, native plugins, and regression automation.
        • Ensure validation of critical customer capabilities, including Apple Pay, push notifications, authentication redirects, geolocation and geofencing, deep links, permissions, analytics events, and QA mobile builds.
        • Partner with QA and Automation Engineers to embed front-end tests into CI/CD pipelines and improve agreed quality, automation, and coverage measures.
        • Own remediation of accessibility findings and ensure new and modified components follow applicable WCAG and ADA requirements.
        • Own technical readiness and execution of iOS and Android releases, including versioning, signing, certificates, provisioning profiles, build configuration, release notes, store compliance, and rollout support.
        • Support QA application distribution through Firebase App Distribution and production publishing through Apple App Store