Frontend Engineer

AI summary

We are looking for a Senior Frontend Engineer to build high-quality user experiences using latest front-end technologies. This is a 12-month contract embedded within a Visa-client joint tech squad in Nairobi. Responsibilities include implementing features for M-Pesa app, integrating payment services, and collaborating with cross-functional teams.

• 6+ years of experience required
• Contract/Secondee engagement for 12 months
• Work on M-Pesa app frontend
• Collaborate with UX/UI designers and backend engineers
• Experience with CYBS (CyberSource) payment integration preferred

Description

Find a Job + + + + Search Frontend Engineer Anonymous Employer Engineering & Technology 2 months ago Easy apply Nairobi Full Time 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 Frontend Engineer to play a critical role in building high-quality, elegant and responsive user experience using the latest front-end technologies. Experience Level: Senior level Experience Length: 6 years Language Requirement: English Working Hours: Full Time - 8 to 5 Applicant Location: Kenya Job descriptions & requirements 1. Role Title & Level Frontend Engineer Senior (6+ years of experience) 2. Engagement Summary · Engagement Type: Contract / Secondment · Squad Context: Embedded within the Visa–client joint Tech Squad; responsible for frontend feature delivery, app UI integration, and push provisioning flows · 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 Frontend Engineer to play a critical role in building high-quality, elegant and responsive user experience using the latest front-end technologies. Embedded within a cross-functional tech squad, this role works in close collaboration with backend engineers, UX/UI designers, and the Scrum Master to deliver high-quality features iteratively within sprint cycles. 4. Key Responsibilities · Implement frontend features and enhancements for push provisioning flows within the M-Pesa app, including wallet provisioning UI, token management screens, and user consent flows. · Integrate CYBS (CyberSource) payment services into the M-Pesa application frontend, implementing required UI components and user flows to specification. · Execute frontend test scripts for acquiring/payment acceptance flows, including UI-level functional tests and end-to-end test scenarios · Collaborate with the UI/UX Designer to translate wireframes, prototypes, and design specifications into pixel-accurate, responsive, and accessible frontend implementations. · Implement analytics and event-tracking instrumentation within the app frontend to support digital lift measurement and data-driven campaign tracking. · Ensure frontend code meets performance standards: app load time, rendering performance, and network efficiency benchmarks defined in the project's performance budget. · Build and maintain frontend unit and integration tests; contribute to automated UI testing frameworks where applicable. · Work with Backend Engineers to agree and consume backend API contracts; surface and resolve API integration issues at the frontend layer. · Support knowledge transfer by producing component documentation, frontend integration guides, and onboarding materials for internal team frontend engineering counterparts. 5. Measurable Outcomes & Deliverables First 30 Days · Development environment configured; app codebase reviewed; understanding existing frontend architecture documented. · First sprint frontend deliverables completed and reviewed (per sprint plan); code merged to agreed branch. · Analytics instrumentation plan produced (in collaboration with Data Scientist): event taxonomy defined, tracking library confirmed. · Frontend technical approach document produced for push provisioning flow implementation. · Device/OS test matrix agreed and documented. Days 31–60 · Push provisioning UI components implemented and validated in sandbox/development environment. · CYBS integration frontend components: at least one payment flow UI built and tested against sandbox backend. · Analytics events implemented and validated for at least two key user journeys (e.g., card provisioning, payment initiation). · Achieve ≥ 70% frontend unit test coverage on all new code delivered to date · Document a component library inventory of reusable frontend components built to date Days 61–90 · Push provisioning frontend flows signed off by UI/UX Designer and Product Owner; functional tests passing across agreed device matrix. · CYBS integration frontend completed and UAT-ready; test script evidence documented. · Full analytics instrumentation live in staging; digital lift tracking validated end-to-end with Data Scientist. · Frontend integration guide produced and handed over to client frontend engineering team. · At least two knowledge transfer sessions delivered to client frontend developers. Ongoing KPIs · Deliver frontend features in line with sprint commitments and agreed designs. · Maintain high UI quality through effective testing and early identification of defects. · Ensure optimal performance and smooth user experience across key customer journeys. · Build frontend components that are accessible, usable, and aligned with agreed standards. · Collaborate effectively with design, backend, an