In planning & operations
From Amazon audit to Regional Workforce Lead — a continuous arc through data, ops, and leadership.
Regional Workforce Lead Forecasting & Analytics Automation Champ
I lead workforce planning across multi-country operations — turning forecasts, schedules, and real-time signals into service-level stability.
Numbers behind the work. Countries, accounts, years, skills — each one earned.
In planning & operations
From Amazon audit to Regional Workforce Lead — a continuous arc through data, ops, and leadership.
Countries, in parallel
End-to-end workforce planning across multi-country BPO operations — each with its own SLA grammar.
Accounts under planning
Forecasts, schedules, resource allocation — tuned to each client's SLA and seasonal rhythm.
Specialised skills, daily
Python, SQL, VBA, Power BI, ML, Lean Six Sigma — a stack chosen to make operations measurable.
Remote · 1y 8mo
Audited large datasets for Amazon's Egypt launch. Learned what data integrity looks like at scale — the foundation everything else was built on.
Cairo · 11mo
Pivoted into BPO operations. Resolved complex customer issues with analytical rigour — the first lessons in how front-line work shapes the metrics planners later optimise.
Cairo · 9mo
Owned real-time ops and SLA adherence. Led the team end-to-end — performance, development, scheduling. Where dashboards became decisions, in minutes.
Cairo · 2y 2mo
Led capacity planning across two countries and six+ accounts. Built Python forecasting models that folded ML into the planning cycle. Owned the full scheduling stack.
Cairo · ongoing
Promoted to lead workforce management across the region. Multi-site, multi-country scope. Where the discipline of planning meets the breadth of regional leadership.
I don't just schedule shifts. I model the system that makes the shifts possible — the demand patterns, the agent skills, the seasonal noise, the SLA cliffs. Then I build the forecasts, the automations, and the dashboards that let the whole operation run a step ahead, instead of a step behind.
Real-time fires happen because something upstream wasn't modelled right. I start every problem with the demand-supply structure beneath it.
If a planner runs the same query every Monday, that query becomes a Python or VBA job. Time saved on plumbing is time spent on judgement.
Forecasts that flatter no one. Dashboards that show the gap, not hide it. Lean Six Sigma discipline applied to the data itself.
Capacity for two national markets, six+ accounts, in one cohesive model. Resource allocation tuned per account SLA, seasonality, and skill mix. The model isn't perfect — it's transparent enough that the ops floor can tell me where it's wrong, and why.
Forecasting models in Python — regression and statistical methods stitched together for planning that doesn't surprise anyone in week three. Outputs feed directly into the schedule engine, replacing what used to be week-long spreadsheets.
As Senior RTM I owned SLA adherence in the moment. But the lasting work was turning that minute-by-minute knowledge into structural insights for the planning layer. Bottlenecks identified at real-time speed inform capacity assumptions at planning speed.
Open to conversations about workforce planning, forecasting at scale, BPO operations, or anywhere data, scheduling, and Lean discipline meet.
Start a conversation