Just Eat EPOS Integration
Problem Space
Re-architect a platform from student prototypes to a layered design, after spending time with restaurant operators to understand the EPOS workflows the system actually needed to fit. Migrate from ASP.NET WebForms to MVC 3. Internationalise for 2 new European markets. Build an automated deployment pipeline. Reverse-engineer EPOS printers for restaurant order acceptance. One of the first 20 technical hires.
Architecture & Patterns
- Re-architecture from student prototypes to layered design
- Migration from ASP.NET WebForms to MVC 3
- Internationalisation for 2 new European markets
- Automated deployment pipeline (Ruby + Jenkins)
- EPOS printer reverse engineering for restaurant order acceptance
Tools & Stack
ASP.NET MVC 3, Ruby, Jenkins, SQL Server, EPOS hardware, WebForms, IIS
Business Outcomes
- Successful re-architecture from student prototypes to production-grade layered design
- Platform internationalised for 2 new European markets
- Automated deployment pipeline reduced release friction
- EPOS printer integration enabled direct restaurant order acceptance
- One of the first 20 technical hires at Just Eat
Reusable Narrative Snippets
As one of the first 20 technical hires at Just Eat, re-architected the platform from student prototypes to a layered design, migrating from ASP.NET WebForms to MVC 3 and internationalising for 2 new European markets.
Built an automated deployment pipeline with Ruby and Jenkins, and reverse-engineered EPOS printers for direct restaurant order acceptance.
Source Notes
- Derived from role responsibilities and achievements in
config/madu_profile.json; reconciled with JobVia export (madu_alikor_export.json). - Confidence: high