Backend Engineer

AI summary

Senior Backend Engineer role for a 12-month contract in Nairobi, Kenya. The engineer will work within a joint Visa-client tech squad on backend development for tokenisation, Visa Direct, CYBS integration, and push provisioning. Requires 6+ years of experience and proficiency in English.

• Senior level (6+ years experience) contract role
• Embedded in Visa-client joint Tech Squad
• Work on tokenisation, Visa Direct, CYBS, and M-Pesa
• 12-month engagement with agile sprints

Description

Find a Job + + + + Search Backend Engineer Anonymous Employer Engineering & Technology 2 months ago Easy apply Nairobi Contract IT & Telecoms Confidential Share link Share on WhatsApp Share on LinkedIn Share on Facebook Share on Twitter Share via SMS Job summary We are looking for a Senior Backend Engineer to play a critical role in building solutions. Experience Level: Senior level Experience Length: 6 years Language Requirement: English Working Hours: Contract - 8 to 5 Applicant Location: Kenya Job descriptions & requirements 1. Role Title & Level Backend Engineer Level: Senior (6+ years of experience) 2. Engagement Summary · Engagement Type: Contract / Secondment · Squad Context: Embedded within the Visa–client joint Tech Squad; responsible for backend development, host changes, operational processes, and integration support across all initiatives · Expected Duration: [12 months] · Primary Location: [Nairobi, Kenya] — Expectation of days in the office will be confirmed by your Hiring Manager · Sprint Cadence: Fortnightly agile sprints · Reporting Line: [Reports to Technical Program Manager, TPM] 3. Role Purpose We are looking for a Senior Backend Engineer to play a critical role in building solutions. The engineer will take responsibility for backend domains or major features and drive them end-to-end from design through delivery. You will be a valued member of a collaborative team, working closely with crossfunctional stakeholders to translate business requirements into robust technical solutions. 4. Key Responsibilities · Design and implement backend changes required for Tokenisation, including token service enrollment flows, host system changes, and operational backend processes. · Develop and integrate CYBS (CyberSource) service backend components into the M-Pesa payment stack, following agreed integration architecture. · Implement backend support for push provisioning app enhancements, including secure token storage, provisioning state management, and notification services. Supporting Responsibilities · Build and maintain logging, monitoring, and alerting infrastructure for all initiative-specific backend services, ensuring operational visibility pre- and post-production launch. · Execute and support backend functional testing, including integration tests, regression suites, and performance benchmarking; log and remediate defects to agreed SLAs. · Collaborate with team on end-to-end integration design, ensuring backend services expose well-formed, documented APIs. · Support knowledge transfer by co-authoring technical runbooks, system design documentation, and onboarding guides for client engineering counterparts. 5. Measurable Outcomes & Deliverables First 30 Days · Development environment fully configured; access to relevant codebases, repositories, and sandbox environments confirmed. · Map all backend service dependencies across Tokenisation, Visa Direct, CYBS, and push provisioning into a shared dependency register. · Attend all Scrum ceremonies and contribute to sprint planning with estimated, clearly scoped backend tasks · Logging and monitoring baseline agreed; instrumentation plan drafted. Days 31–60 · Tokenization host changes implemented and validated in sandbox; functional test cases passing. · Visa Direct backend configuration and transaction processing components built and tested in sandbox. · CYBS backend integration components developed; unit and integration test coverage on new code. · Monitoring and alerting hooks operational for at least one initiative; alert thresholds configured. Days 61–90 · Tokenization backend changes promoted to certification environment; all functional and regression test cases passing. · Visa Direct backend production-ready: transaction quality checks passing, health check endpoints operational. · CYBS integration backend components deployed to UAT / staging environment; test script execution completed. · Backend architecture decision record (ADR) produced for at least one significant design choice during the engagement. · Technical runbook produced for all backend components delivered; client engineers onboarded to operate and maintain systems. Ongoing KPIs · Deliver backend features reliably in line with sprint commitments and agreed scope. · Maintain high code quality through strong testing practices and low defect escape. · Respond effectively to critical backend issues and support stable production operations. · Contribute to the reliability, observability, and continuous improvement of backend services. · Transfer knowledge to client engineers through documentation, pairing, and shared delivery practices. 6. Stakeholders & Ways of Working Agile Ceremonies: All sprint ceremonies; leads or contributes to technical refinement of backend stories; participates in daily stand-ups. Reporting Cadence: · Sprint-level: backend delivery status reported at sprint review. · Ad-hoc: technical blockers escalated to API Integration Engineer or Scrum Master within 4