Senior Software Engineer / Technical Lead
I am a Pretoria-based engineer with 10+ years in mobile development, deep cross-platform experience, and a mechanical engineering background that still shapes how I reason about systems, trade-offs, reliability, and delivery.
My strongest work sits at the intersection of product-minded mobile engineering and technical leadership: turning ambiguous business needs into reliable apps, helping teams make better architecture decisions, and keeping delivery honest without losing sight of craft.
I have worked across fintech, healthcare, and industrial environments, moving from mechanical engineering in mining into software. That path made me pragmatic. I care about first principles, failure modes, maintainability, and the operating context around the code as much as the implementation itself: databases, APIs, release paths, support loops, team process, and the production realities that determine whether software keeps earning trust after launch.
Digital banking
Building modern banking experiences where security, performance, accessibility, and release discipline matter. I focus on resilient app architecture, clear module boundaries, data contracts, production readiness, and collaboration across product, design, QA, backend, platform, and support teams.
Healthcare platform
Led mobile development for healthcare benefit access, helping turn complex service journeys into usable mobile workflows. The work covered React Native, cloud-backed architecture, data-driven integrations, scale, delivery coordination, production support, and long-term maintainability.
Product build
Built a conversational survey product that makes data collection feel more human. It has been a useful playground for product thinking, conversational UI, React, cloud architecture, and shipping outside the comfort of a larger team.
Engineering transition
My early engineering work in mining trained me to think in constraints: load, failure, inspection, risk, and operating conditions. I bring that same discipline to app architecture, debugging, performance, and team decision-making.
I like teams that move with clarity: small decisions made well, architecture that explains itself, and enough technical discipline that product speed does not turn into future drag.
I reach for Clean Architecture, BLoC, modular boundaries, and typed contracts when they make change safer, testing clearer, and onboarding easier.
I care about predictable releases, review quality, pragmatic estimates, useful rituals, incident follow-through, and making risks visible early enough to do something about them.
I help engineers grow by making expectations explicit: readable code, thoughtful trade-offs, ownership, good debugging habits, and calm technical communication.
Flutter, Dart, React Native, TypeScript, platform integration, performance tuning, offline-aware flows, design-system implementation, CI/CD, and app-store release discipline.
Clean Architecture, BLoC, layered app design, testable state management, API contracts, observability, security considerations, and practical cloud-backed mobile patterns.
Firebase, AWS Lambda, API Gateway, authentication, serverless workflows, analytics, feature rollout patterns, and the glue needed to move from prototype to production.
Relational modelling, document data, Redis-style caching, schema evolution, migrations, sync and offline concerns, query performance, API boundaries, and the trade-offs that show up when products grow.
Discovery, estimation, technical design, pull-request standards, QA coordination, CI/CD, mobile app release and deployment management, monitoring, incident response, and production support rhythms.
Mechanical engineering gave me a useful bias: understand the system before changing it. Mining made that concrete, because real environments punish assumptions. Software has different materials, but the same engineering instincts matter: model the forces, know the tolerances, design for maintenance, and respect what happens in production.