Systems Engineer

sweetgreen is on a mission to build healthy communities by connecting people to real food. We passionately believe that real food should be convenient and accessible to everyone, and we are building a company that reflects that belief. Our team is made up of people who care deeply about the guest experience, our partners, and each other.

The Systems Engineer II, New Restaurant Openings is responsible for the technical build out of new and relocated sweetgreen restaurants. The role sits on the NRO team within Technology and works at the intersection of business systems analysis and hands on technical execution: partnering with Store Design, Operations, and third party vendors, translating restaurant requirements into system configuration, then staging, configuring, and validating the restaurant technology stack so that each location opens with technology that works the first time. That stack includes POS and QSR platforms such as PAR Brink, along with payments, loyalty, inventory, Salesforce, and the integrations between them. You will be a technical point of contact at each NRO milestone, and you will help reduce the manual effort in the process over time through scripting, API driven tooling, and templated configuration.

You will:

• Execute the technical build out for assigned new restaurant openings, from requirements through go live and post launch stabilization, working alongside the third party vendors who perform on site installation.
• Configure POS and QSR platforms for each opening, including menus, pricing, tenders, modifiers, and store level settings, and stage back end systems and environments so all platforms are integration-ready before go-live.
• Validate technical readiness at each NRO milestone, including install, punch, turnover, and pre-grand opening, against defined entry and exit criteria, and escalate risk early rather than at the gate.
• Provide on-site and remote support during opening week, troubleshoot configuration, integration, and data flow issues across POS, payments, loyalty, inventory, and reporting, and transition each location cleanly into steady-state IT support.
• Build automation that removes manual steps from the build, including scripting, REST API integrations, and bulk configuration tooling, and execute functional, integration, regression, and user acceptance testing with results captured as repeatable artifacts.
• Gather and document requirements from Restaurant Operations, Finance, Construction, and Development partners, translate them into system configuration, and report readiness and status clearly to technical and non-technical audiences.

Desired traits:

• Detail-driven: you treat configuration accuracy as the product, and you verify rather than assume.