Case Studies

Context: TrustCircle needed more than screens. The platform required lending rules, user roles, loan workflows, payment handling, audit-friendly data and an admin view that made operational sense.

My role: I translated lending requirements into system architecture, data models, workflow logic and business rules before building the Node.js backend, React frontend and PostgreSQL schema.

Outcome: The platform was deployed live on AWS with PayFast ITN handling, JWT authentication, role-based access control and an admin analytics dashboard.

• 350+ automated tests with a 100% pass rate
• AWS Elastic Beanstalk, RDS, S3, CloudFront and Route 53
• Redis, BullMQ, SSL/TLS, bcrypt and JWT used in the delivery

Context: A live multi-tenant PHP/Laravel platform had security, workflow, data and architecture risks that were affecting confidence in the system.

My role: I worked through the platform without a prepared audit framework, mapped the flows, identified code-level and workflow-level risks, documented expected business rules and classified findings by severity.

Outcome: The development team received its first structured remediation roadmap, written in language both technical and non-technical stakeholders could act on.

• 100+ critical architecture, security, logic and data-integrity issues identified
• SQL injection exposure, RBAC gaps and cross-tenant leakage flagged
• Corrected workflows proposed for onboarding, documents and job acceptance

Context: Connect needed structured review across user journeys, document handling, recruitment workflow rules and expected system behaviour.

My role: I tested the platform end to end, checked whether the workflows matched business expectations, documented issues with reproduction context and translated unclear behaviour into actionable requirements.

Outcome: The work gave the team clearer QA evidence, cleaner acceptance logic and a more practical view of where the platform needed workflow refinement.

• Reviewed candidate, recruiter and process-flow behaviour
• Documented defects, unclear states and workflow mismatches
• Translated business expectations into technical review notes
• Supported clearer handoff between analysis, QA and development

Context: Job seekers and recruitment teams need cleaner ways to manage profile information, role fit, application flow and candidate visibility without losing the human context behind each applicant.

My role: I treated JobBot as a systems problem: understand the recruitment journey, identify repeated manual steps, structure candidate information and connect the workflow to a practical user-facing experience.

Outcome: The project shows my interest in building tools that reduce job-search friction while keeping the process useful for recruiters, candidates and delivery teams.

• Framed the product around recruitment workflow and user decision points
• Connected automation thinking with candidate profile quality and role-fit logic
• Applied systems analysis to a real employment platform context
• Strengthens my portfolio across AI, UX, process design and software delivery

Context: A cybersecurity project required practical research into threat hunting concepts, including hypothesis-driven hunting, IOCs vs TTPs, telemetry mapping, MITRE ATT&CK and the Cyber Kill Chain.

My role: I led the work and completed the core analysis and written deliverable. The public version is sanitized: names, class details and the original PDF are not published.

Outcome: I produced a structured explanation of how proactive hunting turns attacker behaviour into testable questions, maps those questions to telemetry and reduces reliance on short-lived indicators.

• Compared IOC-based detection with TTP-focused hunting
• Mapped telemetry sources including Windows Event Logs, DNS logs, proxy logs, EDR process trees and cloud audit logs
• Built example hunt logic for MITRE ATT&CK T1078: Valid Accounts
• Critiqued the Cyber Kill Chain and connected it to behaviour-based hunting

Context: Mobile connectivity affected users, branches and ATMs nationwide. Repeated escalations showed that the process itself needed attention, not only individual ticket handling.

My role: I administered 500+ 3G, 4G and LTE SIM cards, diagnosed issues through service-provider portals and Cisco ISE, maintained the master database and helped identify the recurring escalation pattern.

Outcome: I co-authored revised SOPs with my manager. Escalations dropped noticeably within the first month because the corrected process gave teams clearer steps and ownership.

• 500+ SIM assets administered across users, branches and ATMs
• 3-day SLA environment with ticketing, billing and asset verification
• Collaborated with Service Desk, Networking, IT Support, ATM Engineers and vendors through ticket handoffs and escalations

Internal evidence cannot be shared publicly because this work was completed in a banking environment where operational documents, screenshots and process details remain confidential.

Context: Weekly and monthly task reporting needed a cleaner way to capture time, status, users and output without repeatedly rebuilding reports by hand.

My role: I designed the SharePoint list structure, connected Power Automate flows and built Power BI dashboards with drill-down views by employee, task and reporting period.

Outcome: Reporting became export-ready, repeatable and easier for management to review without chasing manual updates.

• Live dashboards for weekly and monthly views
• Automated outputs for Excel and PDF reporting
• KPI tracking by employee, task and status
• Handled individual task records and department-level information with confidentiality in mind

Task-reporting evidence cannot be shared publicly because it contains individual staff task records and internal department information across Admin, HR, IT, Operations and other business areas. This is company-only information and should remain private.