In this role, you will serve as the leader of a strong team of engineers responsible for the increasingly complex set of APIs that power digital ordering at Chick-fil-A. The position requires a critical thinker, a problem solver, and a decisive leader. We are looking for a thoughtful software engineer who values and takes pride in maintainable and extensible software. We need you to apply the technical experience you have gained in software development to the design, development, delivery, and operation of complex and highly critical technical products in a fun and fast-paced environment. You will not be responsible for HR management of your team, which will allow you to be able to oversee the technical aspects of your team’s growth and delivery while also contributing individually.
This specific engineer will serve on Chick-fil-A's Loyalty Core services team. It is one of several DevOps pods responsible for core web services used by our Chick-fil-A Mobile app and in-restaurant digital technology. Chick-fil-A has experienced tremendous growth in our digital customer engagement through Chick-fil-A App ordering and in-restaurant scans over the past several years. A significant portion of Chick-fil-A's sales now include digital engagement. This allows us to better know our customers and care for them personally. This team delivers functionality specifically related to customer engagement and loyalty, which includes membership status, rewards, and customer communications. The team partners closely with other engineering teams and is responsible for services used by both the consumer facing and in-restaurant digital systems. This team will build exciting and stable features that help will enable Chick-fil-A to better engage and reward our customers while powering the promise of our brand through digital channels.
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.