1. What does a typical day as a Flutter developer at PesaKit look like for you?
A typical day for me as a Flutter developer at PesaKit starts around 8:15 AM with a daily standup alongside the team. During this session, we share progress updates, discuss priorities, and highlight any blockers that might impact our work.
Late mornings are usually dedicated to feature development. I focus on building user-facing screens, such as agent onboarding, KYC workflows, or other key features, using Flutter. Collaboration with backend engineers is a regular part of my routine, especially when integrating APIs and working with dynamic, data-driven flows. Code reviews are a consistent part of my workflow to ensure high-quality code and proper test coverage.
After lunch, my afternoons are typically spent working closely with the QA team to test new features across various Android devices, helping to identify and resolve any issues.
By around 4:00 PM, I shift my focus to final testing, writing documentation, and refining the user interface. I also prepare and deploy builds through our CI/CD pipeline on release days. My day involves a balanced mix of coding, collaboration, and testing to deliver mobile-first financial solutions that meet real-world needs.
2. What is one feature you have built that you are especially proud of and why?
One of the features I’m most proud of building at PesaKit is the dynamic onboarding flow builder for agent registration. Traditionally, onboarding flows, especially KYC processes, are hardcoded, requiring code changes and full app releases for every update. To solve this, I built a flexible, backend-driven system where every aspect of the onboarding flow is defined via JSON configuration.
This includes form fields, validation rules, conditional logic, and UI layout. As a result, the app can dynamically render onboarding steps based on the JSON config, without needing to push a new release.
One major benefit is that product and operations teams can update onboarding steps without involving developers or going through the app store release cycle. For instance, if a client requires an additional document or a new data field, it can be added to the config and go live instantly.
3. What do you enjoy most about working with Flutter?
What I enjoy most about working with Flutter is the ability to build beautiful, consistent, and high-performance cross-platform apps from a single codebase. Flutter gives me full control over every pixel on the screen, which makes it incredibly fun and rewarding to create polished UIs that look and feel native on both Android and iOS.
The hot reload feature is also a big win; it allows for rapid experimentation and instant feedback, which significantly boosts productivity and creativity during development.
4. How do you see your work impacting our agents and users?
Every feature I build is designed to solve real, on-the-ground problems. For example, when I optimize the app to work smoothly in low-connectivity areas or enable offline capabilities, I’m empowering agents to serve their communities even without a stable internet.
I also pay close attention to user experience, because I know that agents often work under pressure with limited time. A clean, responsive UI and a seamless workflow mean they can complete tasks with fewer taps, less confusion, and less training, which translates into better service for end-users.
5. What’s been the toughest challenge you have faced recently, and how did you solve it?
Probably not the toughest challenge I faced, but recently was handling unreliable network conditions for agents using the app in rural areas with poor or intermittent internet connectivity.
The problem wasn’t just that requests failed, it was that users would unknowingly submit forms multiple times, causing duplicate transactions or failed onboarding. It created both data integrity issues and a frustrating user experience.
To solve it, I had to design a system that combined local persistence, retry logic, and clear UI feedback.
6. What is the first thing you do when you start your workday (besides opening your laptop)?
For me, it’s a quick catch with team members on things outside work
7. What is your go-to snack or drink while working?
My go-to drink is coffee.
8. What is the weirdest bug you have ever encountered?
Mmh interesting! One of the weirdest bugs I’ve encountered was when a section of users reported that they couldn’t tap the bottom navigation bar; it was completely unresponsive. At first, it seemed random and hard to reproduce on my development devices, which made it even more puzzling.
After some digging, I discovered that the issue was only happening on certain Android devices with smaller screen resolutions or when the app was running in split-screen or zoomed display mode. In those cases, a hidden or overlapping widget (like a transparent container or an off-screen modal) was unintentionally sitting on top of the bottom nav bar, blocking the touch gestures.
To make matters worse, the bug didn’t show up in any debug logs or crash reports, because technically nothing was “failing.” The UI looked fine, but user input just didn’t register.
9. What do you like to do outside work to unwind or recharge?
I enjoy listening to music, especially hip-hop and soul, watching a good series, or catching up with friends and family.
10. What motivates you to keep pushing, especially on the hard days?
What motivates me, especially on the hard days, is knowing that the work I do has a real impact on people’s lives.
I’m also driven by a personal desire to keep growing as a developer. Hard days often come with the toughest challenges, but also the biggest learning opportunities. Whether I’m debugging an elusive issue or trying to design a more resilient system, I know that pushing through makes me stronger technically and mentally.