Contract Software Developer

Last modified by Rudi Marais on 2026/03/26 17:30

Contract Software Developer (Microsoft Stack)

Contract Role – Feature Delivery Only (No Operational Responsibility)

Employment Model & Location

FieldDetails 
Employment TypeContract 
Engagement ModelOutcome-based feature delivery (delivery against defined acceptance criteria) 
Working ModelRemote or hybrid by agreement (project dependent) 
Client CoverageWork contributes to platforms servicing South Africa and international clients 
Websiteebsphere.com 

Role Overview

This contract role is strictly focused on feature development and delivery.
The contractor will work on clearly defined backlog items under the direction of permanent team members.
The role is designed for delivery output and does not include operational ownership.

Scope of Work (In Scope)

  • Deliver application features using C#, ASP.NET
  • Implement UI components using Blazor
  • Implement or extend APIs based on provided specifications and patterns
  • Write clean, testable code aligned to existing architecture
  • Implement data access and logic using SQL / T-SQL where required
  • Use Git and follow PR and branching standards
  • Collaborate with permanent engineers for handover, code review and refinement
  • Provide short handover notes for delivered features (e.g., feature behaviour and configuration assumptions)

Explicitly Out of Scope

  • Production support or after-hours incident response
  • Change control processes or CAB participation
  • Azure infrastructure administration (SQL MI / VMs)
  • Azure WAF configuration and rule tuning
  • Microsoft Defender administration
  • Microsoft Intune administration
  • Client interaction or onsite client support
  • Supporting internal client-facing teams (implementation/service delivery/client success)
  • Documentation beyond minimal handover notes
  • Mobile support (Xamarin/MAUI)

Required Skills

  • Strong experience in C# / ASP.NET development
  • Practical Blazor experience
  • Solid SQL / T-SQL ability (implementation-level)
  • Strong Git discipline (PR workflow, branch hygiene)
  • Ability to work effectively in an existing codebase and deliver to acceptance criteria

Advantageous

  • Experience in rules-driven domains (employee benefits, pensions, insurance)
  • Experience working in database-centric systems (app-in-DB patterns)
  • Familiarity with Azure-hosted application patterns (consumption-level knowledge)

Engagement Success Criteria

  • Features delivered on time against agreed acceptance criteria
  • Code quality meets review standards
  • Clean handover to the permanent team with minimal rework
Tags:
    

Need help?

If you need help with XWiki you can contact: