The Digerati

Contract C#/.NET developer · Singapore

C#/.NET developer in Singapore, available now

Most C#/.NET roles are not green fields. They are living platforms with a team already around them, and that is the shape of my .NET work too. I spent four years as the client-side engineer on a Cayman Islands group’s web estate: one ASP.NET Core and Umbraco codebase serving around ten consumer brands, delivered together with an agency team, where I was the second-busiest contributor across the life of the repository. Before that I led the C#/.NET API behind a South-East Asian telehealth platform on Azure. I am comfortable being embedded, working to someone else’s conventions, and measuring my contribution in what the team shipped.

  • Four years embedded client-side on a 17-project .NET and Umbraco platform, alongside an agency team
  • .NET 8, ASP.NET Core MVC and Umbraco 13 in production across roughly ten brand sites
  • Led the C#/.NET API behind a telehealth platform on Azure, running the client relationship directly
See selected work

Availability and engagement

Straight answers to the things recruiters screen on first.

Available now Singapore, on-site or hybrid Full-time contract engagements Fixed-scope projects Day rate on request

C#/.NET

What I actually do with C#/.NET.

ASP.NET Core & Umbraco

MVC controllers, view components and generated content models on Umbraco 13: one codebase, around ten public sites, each with its own brand.

Azure platforms

Day-to-day delivery on Azure: AI Search indexes, Functions, Front Door and multi-environment pipelines with slot swaps.

SEO in .NET

Server-side schema.org structured data, sitemap generation rebuilt around the content tree, and CMS-managed redirects replacing hand-kept rewrite maps.

New brand builds

Consumer sites stood up end to end inside an existing platform: pattern library, templates, controllers and content models.

Search & listings

Job and content search against Azure AI Search, including a job-listings library created from scratch and caching where query cost demands it.

Production care

Site-down 500s diagnosed and fixed under pressure, no-store caching on protected pages, and forms wired to the CRM with per-form overrides.

Worked examples

Three problems and how they were solved.

All three from inside client teams, described within what NDAs allow. Ask me to go deeper in conversation.

Ten brands, one codebase, four years

A Cayman Islands group runs its consumer web estate (corporate, retail, real estate, hospitality) as one ASP.NET Core and Umbraco codebase with a shared pattern-library system. I worked on it client-side for four years alongside the delivering agency: onboarding new brands, rebuilding an existing site’s front-end library, and standing up a new consumer site end to end, from pattern library and templates to controllers and content models. The platform crossed from .NET Framework to .NET 8 and Umbraco 7 to 13 in that time, and my job included keeping my areas working through each move. Embedded work is its own skill: you inherit conventions, you negotiate rather than dictate, and your value shows up in the team’s output more than your own.

The SEO plumbing nobody else wanted

On a multi-brand estate, search visibility is engineering. I originated the structured-data subsystem: LocalBusiness, Organisation, Article, FAQ and breadcrumb markup generated server-side from CMS fields, with conditional validation so half-filled content cannot emit broken schema. I rebuilt sitemap generation around the published content tree, and replaced hand-maintained IIS rewrite maps with redirects managed in the CMS, so marketing could move pages without a deploy. None of this is glamorous, which is exactly why it was available to own, and it is the same layer this site takes seriously, for the same reason.

Leading the API behind a telehealth product

A South-East Asian telemedicine provider needed its established mobile product on the web. I led the C#/.NET API work behind the new web platform, hosted on Azure and fronted by Azure API Management, and ran the client relationship directly on a fortnightly review cycle. Health products concentrate the things .NET is genuinely good at: a typed contract between teams, authentication that cannot be casual, and an API surface that has to stay stable while the product moves. It is also the engagement that taught me the most about being the technical point of contact rather than just the implementer.

FAQ

C#/.NET contracting in Singapore: common questions

Are you available for C#/.NET contract work in Singapore?

Yes. Available now for full-time contract engagements, on-site or hybrid in Singapore. .NET roles are usually team roles, and that is the shape of work I am best at: joining an existing codebase and its conventions rather than arriving with my own. Fixed-scope .NET work can also run through The Digerati.

What is your day rate?

Day rate on request. Engagement length, on-site expectation and scope move it. Tell me the shape of the role and you will get a number, not a range.

How current is your .NET?

The platform I worked on through August 2024 runs .NET 8, ASP.NET Core MVC and Umbraco 13, with Entity Framework Core and SQL Server behind it. I watched it climb there from .NET Framework and Umbraco 7, which is its own education in what upgrades really cost. Since then my daily work has been Python and Next.js, so I would call my .NET current but not sole, and I would rather say that than have you find out.

Do you know Umbraco?

Well: versions 7 through 13, including Forms with custom workflow types, generated content models and multi-site configuration from one instance. If you run a different CMS, or a plain ASP.NET Core service with no CMS at all, the patterns transfer; the CMS was never the hard part.

Can you work alongside our agency or existing team?

That was my seat for four years: the client-side engineer working with an agency delivery team, second-busiest contributor on the repository without ever being the loudest voice in it. I know how that relationship goes wrong (unclear ownership, review queues nobody drains, us-and-them testing) and what keeps it healthy. If you have both an internal team and an agency, I am comfortable being the bridge.

What about Azure?

My .NET platforms have lived on it: Azure AI Search behind site and listings search, Functions for background work, Front Door in front, and multi-environment pipelines with slot swaps carrying every release. I work fluently within an Azure estate, and I say plainly when a piece of it, infrastructure design for instance, is better owned by a specialist.