Wiki source code of Contract Software Developer
Last modified by Rudi Marais on 2026/03/26 17:30
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | = Contract Software Developer (Microsoft Stack) = |
| 2 | |||
| 3 | **Contract Role – Feature Delivery Only (No Operational Responsibility)** | ||
| 4 | |||
| 5 | == Employment Model & Location == | ||
| 6 | |||
| 7 | |**Field**|**Details**| | ||
| 8 | |Employment Type|Contract| | ||
| 9 | |Engagement Model|Outcome-based feature delivery (delivery against defined acceptance criteria)| | ||
| 10 | |Working Model|Remote or hybrid by agreement (project dependent)| | ||
| 11 | |Client Coverage|Work contributes to platforms servicing South Africa and international clients| | ||
| 12 | |Website|[[ebsphere.com>>url:https://www.ebsphere.com]]| | ||
| 13 | |||
| 14 | == Role Overview == | ||
| 15 | |||
| 16 | This contract role is strictly focused on feature development and delivery. | ||
| 17 | The contractor will work on clearly defined backlog items under the direction of permanent team members. | ||
| 18 | The role is designed for delivery output and does not include operational ownership. | ||
| 19 | |||
| 20 | == Scope of Work (In Scope) == | ||
| 21 | |||
| 22 | * Deliver application features using **C#, ASP.NET** | ||
| 23 | * Implement UI components using **Blazor** | ||
| 24 | * Implement or extend APIs based on provided specifications and patterns | ||
| 25 | * Write clean, testable code aligned to existing architecture | ||
| 26 | * Implement data access and logic using **SQL / T-SQL** where required | ||
| 27 | * Use **Git** and follow PR and branching standards | ||
| 28 | * Collaborate with permanent engineers for handover, code review and refinement | ||
| 29 | * Provide short handover notes for delivered features (e.g., feature behaviour and configuration assumptions) | ||
| 30 | |||
| 31 | == Explicitly Out of Scope == | ||
| 32 | |||
| 33 | * Production support or after-hours incident response | ||
| 34 | * Change control processes or CAB participation | ||
| 35 | * Azure infrastructure administration (SQL MI / VMs) | ||
| 36 | * Azure WAF configuration and rule tuning | ||
| 37 | * Microsoft Defender administration | ||
| 38 | * Microsoft Intune administration | ||
| 39 | * Client interaction or onsite client support | ||
| 40 | * Supporting internal client-facing teams (implementation/service delivery/client success) | ||
| 41 | * Documentation beyond minimal handover notes | ||
| 42 | * Mobile support (Xamarin/MAUI) | ||
| 43 | |||
| 44 | == Required Skills == | ||
| 45 | |||
| 46 | * Strong experience in **C# / ASP.NET** development | ||
| 47 | * Practical **Blazor** experience | ||
| 48 | * Solid **SQL / T-SQL** ability (implementation-level) | ||
| 49 | * Strong **Git** discipline (PR workflow, branch hygiene) | ||
| 50 | * Ability to work effectively in an existing codebase and deliver to acceptance criteria | ||
| 51 | |||
| 52 | == Advantageous == | ||
| 53 | |||
| 54 | * Experience in rules-driven domains (employee benefits, pensions, insurance) | ||
| 55 | * Experience working in database-centric systems (app-in-DB patterns) | ||
| 56 | * Familiarity with Azure-hosted application patterns (consumption-level knowledge) | ||
| 57 | |||
| 58 | == Engagement Success Criteria == | ||
| 59 | |||
| 60 | * Features delivered on time against agreed acceptance criteria | ||
| 61 | * Code quality meets review standards | ||
| 62 | * Clean handover to the permanent team with minimal rework |