Job description

Who Are We❓

We Are Foodics! a leading restaurant management ecosystem and payment tech provider. Founded in 2014 with headquarter in Riyadh and offices across 5 countries, including UAE, Egypt, Jordan and Kuwait. We are currently serving customers and partners in over 35 different countries worldwide. Our innovative products have successfully processed over 6 billion (yes, billion with a B) orders so far! making Foodics one of the most rapidly evolving SaaS companies to ever emerge from the MENA region. Also Foodics has achieved three rounds of funding, with the latest raising $170 million in the largest SaaS funding round in MENA, boosting its innovation capabilities to better serve business owners.

The Job in a Nutshell

Foodics powers thousands of restaurants across the region — point of sale, payments, inventory, and the operational backbone underneath. We're building our own ERP platform: the system of record that sits under everything a merchant runs on Foodics.

This is an unusual EM role, so we'll be blunt about it. Today the team has three engineers and there is no team to manage. You will spend most of your time writing code — building the core platform and its integrations into inventory, payments and the POS, shoulder to shoulder with the other engineers.

What you're really being hired for is the second act. As the product matures into a real line of business at Foodics, you're the person who builds the team around it — hiring, structure, process, the whole thing. We want that team built by someone who wrote the first version of the system, not someone who inherited it.

If you're looking to step away from the keyboard, this isn't the role. If you want to build something from zero and then build the team that owns it, it is.

What Will You Do❓

• Write production code as a core contributor, not as a manager who occasionally picks up a ticket
• Own significant parts of the system end to end: core modules, the transactional foundation, regulatory compliance, integration surface
• Make the architectural calls that determine whether this platform survives five years and be accountable for them
• Set the engineering bar by example: code review standards, testing discipline, how we use AI tooling and where we don't trust it
• Work directly with the PM and our domain experts to turn business requirements into a system
• Own hiring: define the roles, run the loop, make the calls
• Grow the engineers already here into people who can run pieces of this independently
• Introduce process at the point it's needed and not before
• Carry the product through its handover into the core business, with the team intact