Information Technology · Software Development
Durban University of Technology, 2014–2017. This is the formal software-development foundation represented in the digital CV.
This chronology connects the formal career record with dated technical and project artefacts. It deliberately distinguishes verified employment and delivery claims from archive material that provides context but is not, by itself, treated as proof of authorship.
The earliest preserved technical material reaches back to the systems-software period, while the formal foundation is a National Diploma in Information Technology focused on Software Development at Durban University of Technology.
Durban University of Technology, 2014–2017. This is the formal software-development foundation represented in the digital CV.
The archive preserves a 2013 Systems Software examination paper, giving a dated technical marker near the beginning of the record.
Historical material includes Joomla and external-platform/API documentation. Its presence is useful context, but this site does not treat possession of reference material as proof that Mandiso authored the underlying product.
Deployment notes, PHP and scheduled-processing material appear alongside project folders before the first verified professional software role in the public career timeline.
Historical folders and deployment notes show the transition from coursework and reference material toward running software and project delivery.
PHP cron and developer material reinforce an early focus on server-side behaviour, scheduled work and operational application concerns.
Verified career record: Junior Software Developer building PHP and JavaScript dashboards and scripts that converted operational data into KPI visibility, with contributions to Net Promoter Score and financial-needs-analysis platforms.
Worked on City Lodge CMS and website delivery, loyalty functionality, AutoTrader integration, mall data services and cinema-information APIs, including framework and PHP-version modernisation while protecting live functionality.
Launched the PWC Bikepark website and developed ordering and administration functionality for Dimples at the World of Golf, translating business requirements into practical operational systems.
Preserved costing models and project-information material show the business side of the archive: estimates, project context and operational information that software ultimately has to serve.
The verified career record moves into bespoke platforms across finance, insurance, tourism, recruitment, ticketing, ecommerce and operations, using Laravel, Vue, Nuxt, Inertia, WordPress, PHP, JavaScript and external APIs.
A preserved 2021 C#/.NET application archive contains controllers, services, data, models, repositories and migrations. Later folders capture WebGap client-development work, domain/site planning and batches of domain-design material.
These artefacts strengthen the historical map of technologies and operating contexts. Where authorship or exact project responsibility is not independently established, the public record keeps the wording at “preserved project archive” rather than converting it into an unsupported claim.
Verified record across municipal, government, funding and commercial platforms: analysis, stabilisation, backlog reduction, workflow implementation, acceptance evidence and production continuity.
Role, stage, task-allocation, approval, inspection and invoicing behaviour required code, schema and operational reasoning rather than isolated feature work.
Application windows, controlled invitations, document requirements, role-aware administration, testing and recovery extended the work into governed programme operations.
The current verified role combines architecture, product direction and hands-on delivery across cloud, workflow, ecommerce, legal technology, public platforms and governed AI-enabled business systems.
The recurring pattern across the longer record is consistent: understand the business process, identify the boundaries between people and systems, connect data and services, make the workflow operable, then prove that it works.
Context, boundaries, service design, data, identity, controls and delivery decisions.
APIs, messaging, authenticated services, external channels and resilient hand-offs.
Deployment, observability, support evidence, recovery and production readiness.
Human approvals, security, privacy, auditability and explicit acceptance gates.
Useful questions include “When did Mandiso start in software?”, “What did he do before WebGap?”, “Has he worked with .NET?”, “How did his career lead to solution architecture?” and “What changed between full-stack development and architecture?”
Use the digital CV for the formal employment timeline, case studies for delivery detail and Ask Mandiso to query the approved public record.