Job Summary
BACKGROUND Standard Bank Offshore requires a Senior Integration Developer to support both Change‑the‑Bank and Run‑the‑Bank activities within the Integration and Automation environment. The resource will operate within Agile delivery teams and will be responsible for design, development, deployment, and production support. 1.1 Change‑the‑Bank Design and develop integration solutions, APIs, and workflows Enhance existing systems and interfaces Contribute to solution architecture and technical design 1.2 Run‑the‑Bank Production support and incident resolution Monitoring and optimisation of solutions Continuous improvement of system stability and performance 2. SCOPE OF SERVICES The Supplier agrees to provide the Services in accordance with the Agreement and this Service Request, as more particularly set out below. Services 2.1 Solution Design Produce High-Level Design (HLD) and Low-Level Design (LLD) documentation Create UML diagrams using Draw.io or equivalent Define integration patterns and architecture designs 2.2 Development & Engineering Develop integration solutions using C# /.NET and API-based architecture Implement integration patterns (event-driven, asynchronous, messaging) Ensure adherence to coding standards and secure development practices 2.3 DevOps & Deployment Build and maintain CI/CD pipelines using Azure DevOps Manage source code using Git-based workflows Support automated deployment across environments 2.4 Agile Delivery Participate in: Programme Increment (PI) Planning Sprint planning Backlog refinement Daily stand-ups and retrospectives Contribute to estimation, planning, and delivery commitments 2.5 Production Support & Incident Management Support L1/L2 support engineers in resolving incidents Provide L3 escalation support Perform root cause analysis (RCA) Resolve incidents in line with agreed SLAs 3. Deliverables 3.1 Design Deliverables High-Level Design (HLD) documents Low-Level Design (LLD) documents UML diagrams (sequence, flow, component) 3.2 Development Deliverables Working integration components (APIs, workflows, interfaces) Source code maintained in repositories Unit and integration test coverage 3.3 DevOps Deliverables CI/CD pipelines and deployment automation Environment and configuration scripts Deployment documentation 3.4 Support Deliverables Incident resolution within SLA Root cause analysis documentation Knowledge transfer to support teams 3.5 Documentation Deliverables Technical documentation (e.g. Confluence) Runbooks and operational guides Release notes 4. Acceptance Criteria 4.1 Functional Acceptance Solution meets defined business and technical requirements 4.2 Quality Standards Code adheres to engineering and security standards Adequate test coverage is provided No critical or high-severity defects in production Work delivered within agreed estimates and sprint commitments 4.3 Design & Documentation Design artefacts are complete and aligned with architecture standards Documentation supports operational use and audit requirements 4.4 DevOps & Deployment Successful automated deployment via CI/CD pipelines No unauthorised manual intervention required 4.5 Support Readiness Solutions are fully monitorable and supportable Runbooks and support documentation completed Knowledge transfer completed 5. Service Level Agreements (SLA) 5.1 Incident Response & Resolution Priority Response Time Resolution Target P1 (Critical) < 1 hour Within 4 hours P2 (High) < 2 hours Within 1 business day P3 (Medium) < 4 hours Within 2–3 business days P4 (Low) < 1 business day As agreed 5.2 Support Expectations Active support for L1/L2 escalation Ownership of L3 root cause resolution Participation in incident reviews and problem management 5.3 Performance Measures % of incidents resolved within SLA Delivery against sprint commitments Defect leakage into production 5.4 Governance & Delivery KPIs % of work correctl
Key Responsibilities
. Delivery Governance & Ways of Working 6.1 Agile Participation Participation in PI Planning and sprint ceremonies Contribution to capacity planning 6.2 Work Management (Jira) All work must be tracked in Jira Work items must be accurate and up to date No off-system work permitted 6.3 Engineering Standards Adherence to Standard Bank coding standards and engineering practices Compliance with architecture, security, and governance requirements 6.4 Governance & Compliance Adherence to Standard Bank governance policies and regulatory requirements 6.5 Mandatory Compliance Training Completion within required timeframes No compliance breaches permitted 6.6 Work Estimation & Delivery Accuracy All work must be accurately estimated Delivery aligned to estimates wherever reasonably achievable Risks must be proactively raised Deviations must be documented and updated in Jira 6.7 Service Reviews Service review meetings with account manager Frequency to be agreed (maximum monthly) 7. Commercial & Administrative Requirements 7.1 Timesheets Timesheets must: Detail hours worked and activities Align to Jira work items Be submitted and approved 7.2 Billing Billing based on approved timesheets only No payment for: Unapproved hours Work not tracked in agreed systems 7.3 Performance Alignment Engagement continuation and payment subject to: SLA adherence Delivery quality Compliance with governance 8. Skills Requirements 8.1 Essential Skills Integration and API development C# / .NET Core UML-based design (Draw.io or equivalent) Azure DevOps and Git CI/CD practices Agile/Scrum delivery Production support and SLA-based incident resolution 8.2 Preferred Skills Azure services (Function Apps, Logic Apps, Service Bus, Storage, App Insights, Log Analytics) Jira and Confluence Power Platform Infrastructure as Code (Terraform / ARM) SFTP standards 8.3 Desirable Skills Containers / Kubernetes Messaging platforms Financial services / regulated environment experience 9. Legal, Commercial & Risk Safeguards 9.1 Intellectual Property (IP Ownership) All deliverables, code, documentation, and artefacts are the sole property of Standard Bank No reuse without prior written consent 9.2 Resource Replacement Standard Bank may request resource replacement at any time Supplier must provide a suitably qualified replacement 9.3 Termination & Notice Either party may terminate with three (3) months’ written notice During the notice period: Full service delivery and SLA obligations remain in force Knowledge transfer must be completed Standard Bank may terminate immediately for: Breach of contract SLA underperformance Compliance violations Poor delivery or conduct 9.4 Acceptance & Sign-Off All work must be formally accepted Acceptance linked to: Jira completion Deliverable validation Timesheet approval 9.5 Billing Traceability All billable work must be: Linked to Jira work items Accepted deliverables 9.6 Subcontracting No subcontracting without written approval Supplier remains liable 9.7 Knowledge Transfer & Exit Full handover required on termination Documentation and artefacts must be delivered Transition support must be provided 9.8 Confidentiality & Data Protection Full compliance with data security policies Protection of confidential and production data GDPR and regulatory alignment 9.9 Dispute Resolution & Escalation Defined escalation path: Delivery Team → Tech Lead → Account Manager → Procurement All disputes formally documented 9.10 Audit Rights Standard Bank may audit: Deliverables Jira records Timesheets Code and deployments 9.11 Risk & Delay Notification Supplier must proactively notify delivery risks Failure to do so constitutes non-performance 9.12 Performance Improvement Standard Bank may enforce a performance improvement plan Continued failure may result in termination 10. Period of Engagement The period of engagement will be 12 months from the agreed contract start date, subject to the terms and conditio