Mookh sells event tickets and creator products across East Africa. I joined as a frontend engineer working on speed and defects, and now lead the frontend.
What I did as an engineer
The product had grown faster than its frontend. Components had accumulated responsibilities, rendering was doing more work than it needed to, and the same defects kept returning because fixes stopped at the symptom.
- Optimised component rendering across the product, cutting work the browser was repeating on every update.
- Split oversized components into composable units, so a change lands in one place instead of four.
- Traced reported defects to root cause rather than patching the screen where they surfaced.
What I do as lead
The job changed from writing the most code to deciding what good looks like and making it repeatable.
- Set the frontend direction and the standards the rest of the work is reviewed against.
- Own the architecture decisions: state boundaries, component boundaries, and performance budgets that hold.
- Review code and mentor engineers, arguing about the reasoning behind a change rather than only its output.
What the role is really about
A ticketing platform is judged in the minutes around an on-sale, when traffic spikes and every slow render costs a sale. Most of leading here is protecting that: agreeing what the frontend is allowed to cost, and holding the line in review when a feature wants to spend more.