5in5

5in5

Professional contributions in my current employment to a business-lending platform, spanning loan applications, customer self-service, operational administration and backend integrations.

Client work

Professional contributions through my current employment at 5in5. The platform is company-owned; this case study describes my work within the existing product and team.

Overview

5in5 is a company-owned business-lending platform serving customer application and loan-management journeys alongside operational backoffice workflows. I contribute through my current employment as a Senior .NET Developer and Team Lead.

The engineering work spans an established ASP.NET Core backend, SQL Server data handling and Angular customer and administration applications. This case study focuses on my contributions and preserves the distinction between team-owned product delivery and individual responsibility.

My contribution

Senior .NET developer and team lead — current employment

Professional .NET backend development and technical leadership

Angular customer and backoffice workflow contributions

Loan-application lifecycle and customer self-service changes

Integration and validation work within the existing platform

Compatibility and regression checks for established business behaviour

Key features

Loan application journeys

Customer-facing application workflow contributions

Customer self-service

Account and loan-management interfaces

Backoffice workflows

Operational administration over backend-owned rules

Documents and payments

Integration with supported platform processes

Lifecycle consistency

Handling of repeated and re-entered application flows

Typed client integration

Angular interfaces with shared API contracts

Case study

Context

A business-lending platform must support both the customer journey and the operational work behind it. At 5in5, those surfaces include credit applications, account and loan information, documents, payments and backoffice administration. A change to one part of the lifecycle can affect several interfaces and integrations.

My role

I work at 5in5 as a Senior .NET Developer and Team Lead in my current employment. My contribution covers software development and technical coordination within an existing company platform. Product ownership and wider team delivery remain attributed to 5in5.

Contribution focus

My work involves backend business flows and Angular frontoffice and backoffice journeys. Areas include application lifecycle consistency, customer data and contact changes, loan-related self-service and operational interfaces. Work is grounded in existing backend rules rather than rebuilding those rules independently in each client.

Technical approach

The platform includes ASP.NET Core services, SQL Server persistence and Angular applications. Established components and integrations are maintained alongside newer Angular client work. Existing API contracts and status models guide implementation so that interface improvements preserve the behaviour on which operational users already rely.

Where workflows depend on identity, bank information or payment-provider responses, the backend remains the authoritative boundary. Customer-facing interfaces present the supported next action and validation feedback without exposing internal administrative controls.

Engineering challenges

An established lending system requires careful treatment of repeated requests, application re-entry and the relationship between historical records and live workflows. Tracing the current execution path, preserving existing records and adding targeted guards is preferable to silently changing business meaning across the platform.

Outcome and boundaries

The contribution is ongoing work on customer and operational journeys within the lending platform. The work is delivered within the existing company platform and its established product and operational teams.