SENIOR DEVELOPER | C# / .NET / Azure / Kubernetes | REMOTE - SOUTH AFRICA, R1.6m – R1.8m

There are Senior Developer roles where you inherit a backlog. And then there are roles where you get to influence how an entire technology platform evolves.

I’m recruiting a SENIOR DEVELOPER (C# / .NET / Azure / Kubernetes) for an established INTERNATIONAL WEALTH MANAGEMENT BUSINESS operating across the UK and South Africa.

Offering R1.6m – R1.8m this role is 100% REMOTE (but you MUST be based in SOUTH AFRICA).

This is a business with genuine scale, significant assets under custody and a sophisticated technology platform sitting at the heart of how private clients, wealth managers and financial intermediaries invest, trade, report and manage money internationally.

Technology here isn’t an internal support function. It is part of the product.

And that makes this a particularly interesting opportunity for a strong BACKEND ENGINEER who wants more than another feature-development role.

THE OPPORTUNITY:

You’ll join a growing engineering team building and evolving secure, highly available financial applications using C#, modern .NET and Azure.

The role is deliberately broad.

You’ll still be deeply hands-on with engineering, but you’ll also move upstream into:

• architecture and system design
• technical decision-making
• cloud infrastructure
• Kubernetes and container orchestration
• CI/CD and automated deployment
• infrastructure-as-code
• engineering standards and code quality

In other words, you won’t simply be handed architecture and asked to implement it. You’ll help shape it.

And, this is where I think the role becomes particularly compelling.

You’ll have the opportunity to work on the engineering challenges that emerge when software sits underneath a real-world international financial platform:

BUILDING FOR SCALE AND RESILIENCE: Design backend services that need to remain performant, secure and dependable as transaction volumes, integrations and users grow.

MODERNISING ARCHITECTURE: Help make decisions around microservices, APIs, asynchronous processing and how existing systems should evolve rather than simply maintaining what already exists.

OWNING SOFTWARE ALL THE WAY INTO PRODUCTION: Work beyond application code into containers, Kubernetes, Azure infrastructure, CI/CD and automated deployment.

SOLVING DISTRIBUTED-SYSTEM PROBLEMS: Work with APIs, messaging, asynchronous workloads and services where reliability, observability and failure handling genuinely matter.

ENGINEERING WITHIN A HIGH-TRUST ENVIRONMENT: Financial systems introduce interesting technical constraints around security, data integrity, auditability and operational risk. You’ll learn to engineer elegant solutions without ignoring those realities.

INFLUENCING ENGINEERING PRACTICE: As a senior member of the team, you’ll help improve design patterns, code reviews, development standards and technical decision-making across the wider engineering function.

That breadth is difficult to acquire in roles where Developers are separated from architecture, cloud and production infrastructure.

Here, you’ll get exposure to all of it.

TECHNICALLY, I’m looking for someone strong in:

• C# / .NET Core / .NET 6+
• Backend and API development
• RESTful services
• Microservices
• Asynchronous programming
• Microsoft Azure
• Kubernetes
• Containers
• CI/CD
• Infrastructure-as-code
• Automated deployment

Experience with RabbitMQ, SQL Server, financial services or secure software engineering would be useful, but isn’t necessarily the defining factor.

WHO I THINK WILL ENJOY THIS ROLE:

Probably someone with 8+ years in software engineering who still loves writing code, but increasingly wants to understand and influence the bigger engineering picture.

Someone who asks:

Why was the system designed this way?

What happens when this service fails?

How do we make this easier to deploy?

How will this behave at scale?

Is there a better architectural approach?

If you want to remain purely an application developer, this probably isn’t the role.

If you want to become the kind of engineer who can comfortably move between code, architecture, cloud and production systems, it could be an excellent next step.