Lead Software Engineer, React
Delivering consistent, high-quality user experiences across our internal front-end applications is key to enabling Chick-fil-A’s continued growth. We are looking for a Lead Software Engineer to help us build and evolve our internal React component library and design system, which increasingly serves as a foundation for front-end development across Digital Transformation and Technology. This is a high-impact role for someone who is passionate about front-end engineering, cares deeply about developer experience, and is eager to mentor and lead a team of engineers.
You’ll help shape the technical vision for our component ecosystem, collaborate across engineering and design disciplines, and ensure the experiences we deliver are consistent, accessible, and delightful for the internal teams who depend on them.
This role will live within our Digital Transformation and Technology (DTT) department and work closely with an Agile team including other software engineers, product owners, scrum masters, UX designers, quality engineers, and platform engineers. This role requires deep expertise in React and front-end engineering, as well as a strong understanding of design system principles. In this role, you can expect to build deep technical expertise around component architecture, design-to-code workflows, and scalable front-end patterns that serve internal development teams across the organization.
As the Lead Software Engineer, you will work to deliver the design, architecture, and continued evolution of our internal design system and component library to directly improve the front-end development velocity and consistency across our internal applications, including the following outcomes:
Our Flexible Future model offers a healthy mix of working in person and virtually, strengthening key elements of the Chick-fil-A culture by fostering collaboration and community.
Note - Working in a DevOps model, this opportunity includes both building and running solutions that could require off hours support. This support is shared amongst the team members to cover weekends and weeknights. The goal is to design for failure and, using cloud-native infrastructure patterns, automate responses to possible issues so they can be worked during normal hours.