Software Engineer Ii, Supply Chain Order Management

Chick-fil-A restaurants come in many shapes and sizes, all of them delivering thousands of meals a day to happy customers. Have you ever wondered how varying sizes of restaurants, including mall fronts, can keep an abundant of stock items to serve all their customers? The answer is the order management system that allows operators to place orders with ease allowing them to replenish their stock items through various distributors. One of the components of the Order Management system consist of the front-end UI (Signal) which is handled by the front-end team. Signal UI is tightly coupled with the ordering process to help operators ease their burden of ordering supplies for their restaurant.

The Chick-fil-A Software Engineer II position, for Supply Chain Order Management, will allow you to grow in a fast-paced dynamic environment, solving high-impact problems using cutting-edge technologies. In this role, you will have oversight in core order management platform as well as adding new features to support operators in the supply ordering process. As the Software Engineer II for supply chain software products, you will be working on complex features while also learning new technologies and patterns. You will be working with product owners to strategically plan out new requirements, as well as working towards agile best practices and standards. The team is leveraging cloud-based technologies to create enterprise services and APIs for our Operator-facing ordering platforms and analytics.

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.

This role is based in Atlanta, Georgia. If a candidate meets our relocation policy guidelines, Chick-fil-A does offer relocation.

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.