Engagements described the way an engineer would describe them.

The problem

A heavy-civil and mining contractor operating across multiple sites needed one system for people, procurement, stock and project accounting — with each site able to run its own operation without fragmenting the data.

The approach

A two-level tenant → organisation model, so a client can hold multiple sites or legal entities under a single tenant. Client-specific rules are handled by extension on a common codebase rather than by forking the product — the discipline that keeps a platform maintainable past its third customer.

What was built

• Node.js, TypeScript and Express service layer
• PostgreSQL accessed through the raw pg driver — no ORM, a deliberate architectural position
• React and Vite front end
• Self-serve signup with trial provisioning
• Ten modules on a shared schema with tenant isolation

The problem

High-stakes examination processing at institutional scale, where a calculation error or an hour of downtime during a live cycle is not recoverable.

The approach

Database architecture and optimisation, enterprise reporting, workflow automation, backend APIs, authentication hardening, and production support across live examination cycles — delivered as part of the engineering team on client platforms in prior roles.

What was built

• ETL pipelines ingesting millions of scanned examination pages
• Stored procedure, view and reporting engineering on SQL Server
• Automated result calculation and anomaly detection
• Authentication and authorisation hardening
• Production issue resolution without interrupting active cycles

The problem

A product suite where every application carried its own authentication — duplicate accounts, inconsistent mechanisms, no central policy enforcement and limited auditability.

The approach

Standards research, architecture, backend API development, database schema and RBAC/permission modelling for a tenant-aware identity platform: session management, JWT with refresh-token lifecycle, claims-based authorisation, MFA evaluation and audit logging.

What was built

• ASP.NET Core Identity implementation
• RBAC with fine-grained permission modelling
• JWT plus refresh-token lifecycle management
• Administrative modules for users, roles and policy
• Authentication event audit logging

The problem

Wholly manual operations — inventory, customer records, billing, quotations and sales history kept on paper. No accurate stock position and no reporting capability.

The approach

A single-handed engagement covering requirements gathering, solution and database design, development, testing, deployment, user training and post-deployment support. Early-career work, and the clearest precedent for how the practice operates today.

What was built

• Customer and product catalogue management
• Inventory management with stock position reporting
• Billing, invoicing and quotations
• Sales and purchase records
• User authentication and operational reporting