About
I care about what software makes possible.
My work starts with the organisation, its people and the problem in front of them. From there, I help shape requirements into systems and software that can be put to use.
How I think about technology
Software is part of a larger system.
A useful solution depends on understanding how people work, what information they need and how decisions move through an organisation. The interface and the code matter, but so do the requirements, workflows and boundaries that give them purpose.
I bring that perspective to digital payments, academic verification, planning tools, institutional websites and data APIs: understand the context, make the system legible, then build toward the need.
Approach
Understand → Design → Build → Deliver
- 01
Understand
Requirements, user needs, operating context and the problem a system must solve.
- 02
Design
Information architecture, workflows, domain concepts and system boundaries.
- 03
Build
Web interfaces, backend services, APIs and the data structures that connect them.
- 04
Deliver
A usable system with clear behavior, considered security and practical operations.
Technical capabilities
Tools in service of the system.
- Product & systems
- Requirements analysis · Workflow design · Information architecture
- Backend & APIs
- API design · Django · Laravel · Python · PHP
- Data
- Relational data · PostgreSQL · MySQL · Redis
- Frontend
- React · Next.js · TypeScript · Responsive interfaces
Experience
Evidence through the work.
The available profile material does not include verified employer histories or dates. These projects show the range of system contexts represented here.
Education
Formal education details are not included in the profile information available for this portfolio.