UI/UX Designer

• UI/UX Designer
• 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 UI/UX Designer to play a critical role in shaping customer-facing experiences delivered under the Visa–client implementation programme.

Experience

• Level:
• Senior level
• Length:
• 5 years
• Language Requirement:
• English
• Working Hours:
• Contract - 8 to 5
• Applicant
• Location:
• Kenya
• Job descriptions &
• design, UI delivery, and design
• governance across all user-facing initiative workstreams
• ·
• 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 UI/UX Designer to play a
• critical role in shaping customerfacing experiences delivered under the
• Visa–client implementation programme. Embedded within a crossfunctional tech squad, the role is
• responsible for designing intuitive, buildready user journeys across push provisioning,
• acquiring/payment flows, and campaignrelated touchpoints within the MPesa ecosystem.
• Working closely with Frontend Engineers and
• client stakeholders, the UI/UX Designer ensures design intent is accurately
• realised through sprintbased delivery, provides UX and branding
• inputs into initiatives such as Tokenisation,
• 4. Key
• ·
• 5–8
• years of UX/UI design experience, with at least 2 years in mobile application
• design for financial services, payments, or fintech.
• ·
• Proven
• ability to design end-to-end user flows for complex, multi-step transaction
• journeys (payment flows, onboarding, authentication) in mobile contexts.
• ·
• Proficiency
• in Figma / Sketch / Adobe XD]for
• high-fidelity UI design, prototyping, and developer handoff.
• ·
• contributing to or maintaining a mobile design system and component library.
• ·
• Solid
• understanding of mobile UX best practices, including gesture navigation,
• accessibility (WCAG), and performance-aware design.
• ·
• Ability
• to conduct or facilitate lightweight usability research (heuristic evaluation,
• prototype testing, user interviews).
• ·
• working in agile/sprint-based delivery environments, including structured
• design handoff and design QA processes.
• ·
• Strong
• communication skills; ability to present and defend design decisions to
• technical and non-technical stakeholders.
• 8.
• designing for M-Pesa, mobile money applications, or comparable
• super-app payment ecosystems.
• ·
• designing for emerging market users, including considerations for
• lower-literacy contexts, low-end devices, or intermittent connectivity.
• ·
• Familiarity
• with tokenization user journeys or digital wallet provisioning flows (Google
• Pay, Apple Pay, or comparable).
• ·
• Knowledge
• of motion design and micro-interaction principles for mobile UX.
• ·
• with A/B testing or multivariate testing frameworks for UI optimization.
• ·
• Familiarity
• with accessibility auditing tools (Axe, Lighthouse, or equivalent).
• ·
• Basic
• understanding of frontend/mobile development constraints (useful for
• design-engineering collaboration).
• 9.
• Tools & Technologies
• ·
• Design
• & prototyping: Figma or equivalent
• ·
• Developer
• handoff: Figma Dev Mode / equivalent]
• ·
• Design
• system management: Figma Styles & Components / equivalent
• ·
• Collaboration:
• Miro / Mural / FigJam
• ·
• Communication:
• Microsoft Teams
• ·
• Issue
• tracking: Jira / Azure DevOps
• ·
• Documentation:
• Confluence / SharePoint]
• 10.
• Contract/Secondment Notes
• ·
• This
• is a contract/secondment engagement. The resource must adhere to all applicable
• brand, confidentiality, and intellectual property obligations of both client
• and Visa, including guidelines for handling user research data.
• ·
• Performance
• will be assessed on a deliverables basis, with formal reviews at 30, 60, and 90
• days against the KPIs and deliverables defined in Section 5.
• ·
• Knowledge
• transfer to client's in-house design team — including design system
• maintenance, usability methodology, and component documentation practices — is
• a standing engagement obligation.
• Log In and Apply
• Important safety tips
• Do not make any payment without confirming with the BrighterMonday Customer Support Team.
• If you think this advert is not genuine, please report it via the Report Job link below.
• Report Job

Requirements

• 1. Role Title & Level
• UI/UX Designer
• Level:
• Intermediate–Senior (5–8 years of relevant experience)
• 2.
• Engagement Summary
• ·
• Engagement
• Type:
• Contract / Secondment
• ·
• Squad
• Context:
• Embedded within the Visa–client joint Tech
• Squad; responsible for user
• alignment, design review/approval).
• ·
• Data
• Scientist (analytics event instrumentation alignment within user journeys).
• ·
• Backend
• Engineers (understanding of technical constraints affecting UX).
• ·
• client
• brand/marketing team (brand compliance, visual identity guidance).
• 7.
• Required Skills &

Responsibilities

• ·
• Own
• endtoend UX delivery for squad features, covering
• user flows, information architecture, wireframes, prototypes, highfidelity UI, and design QA.
• ·
• Design
• payment and provisioning experiences across push provisioning, CYBS/acquiring
• payment flows, and campaignrelated touchpoints within the MPesa app.
• ·
• Design
• user-facing messaging, iconography, consent flows, and visual brand compliance
• elements for Tokenization initiatives, delivered as annotated design
• specifications.
• ·
• Maintain
• and evolve the MPesa
• design system, ensuring components are reusable, documented, and aligned to
• established standards.
• ·
• Partner
• with Frontend Engineers during sprint delivery, validating build feasibility,
• reviewing implementations, and tracking design defects.
• ·
• Enable
• analyticsready
• journeys by collaborating with Data Scientists to ensure key user interactions
• are identifiable and measurable.
• ·
• Validate
• usability through lightweight testing, incorporating findings into design
• refinements ahead of development.
• ·
• Produce
• handoffready
• design artefacts, including annotated designs and specifications for efficient
• engineering delivery.
• ·
• Support
• propositionspecific
• journeys, including Diaspora consumer onboarding and feature flows.
• ·
• Deliver
• knowledge transfer to client designers, covering design methods, tooling,
• component usage, and usability practices
• 5. Measurable Outcomes & Deliverables
• First 30 Days
• ·
• Current
• M-Pesa app design system and component library reviewed; gaps and inconsistencies
• documented.
• ·
• UX
• audit of existing payment flows (where relevant to squad workstreams)
• completed; priority usability issues identified.
• ·
• Push
• provisioning flow: wireframes and user journey map produced and reviewed with
• Product Owner and Frontend Engineer.
• ·
• Design
• tools and collaboration environment configured; design file structure agreed
• with Frontend Engineer.
• Days 31–60
• ·
• Push
• provisioning flow: high-fidelity UI designs completed, reviewed, and approved
• by stakeholders; handed off to Frontend Engineer.
• ·
• CYBS
• Acquiring payment UI components: wireframes and high-fidelity designs produced
• and reviewed.
• ·
• At
• least one usability test or expert review conducted on a key flow; findings
• documented and design iterations applied.
• ·
• Component
• documentation produced for all new UI components delivered to date; added to
• design system.
• ·
• Design
• QA process established: at least one round of design QA completed for
• implemented features.
• Days 61–90
• ·
• CYBS
• Acquiring UI components implemented, and design QA completed; zero critical
• design defects in staging build.
• ·
• Push
• provisioning flows implementation reviewed and signed off by Designer; live in
• UAT / staging.
• ·
• Diaspora
• UX inputs delivered (if applicable): flow designs or UX recommendations for
• diaspora-specific features produced.
• ·
• Design
• system contribution complete: all new components documented, named
• consistently, and added to shared library.
• ·
• Knowledge
• transfer: design playbook (v1) produced for client design team, covering
• component library, design methodology, and usability testing approach. At least
• two sessions delivered.
• Ongoing KPIs
• ·
• Deliver
• timely, buildready
• UX designs that support sprintbased engineering delivery.
• ·
• Ensure
• highquality
• user experiences through thorough design QA and early identification of usability
• issues.
• ·
• Maintain
• consistency and scalability by contributing to and evolving the MPesa design system and component library.
• ·
• Work
• closely with engineers and data teams to enable accurate implementation and
• analyticsready
• user journeys.
• ·
• Transfer
• design capability to client teams through documentation, shared practices, and
• handson
• collaboration.
• 6. Stakeholders & Ways of Working
• Agile Ceremonies:
• All sprint ceremonies; leads design-specific story
• refinement (user stories for UX/UI tasks); participates in daily stand-ups;
• presents designs at sprint review.
• Reporting Cadence:
• ·
• Sprint-level:
• design delivery status at sprint review.
• ·
• Ad-hoc:
• design blockers (e.g., missing brand guidance, stakeholder unavailability for
• review) escalated to TPM within 24 hours.
• Cross-Functional Touchpoints:
• ·
• Frontend
• Engineers (design handoff, implementation QA, component specification).
• ·
• Product
• Owners / client Product team (

Preferred Qualifications

• / Nice-to-Have Skills
• ·
• Direct