UI/UX Designer

window.notificationMessages = []; Find a Job + + + + Search const TopSearch = { handleSubmit: function (event) { event.preventDefault(); event.stopPropagation();

const form = event.target;

const getValue = (name) => { if (form[name]) { if (form[name].type) { if (["select-one", "text", "hidden"].indexOf(form[name].type) > -1) { return form[name].value; } if (["checkbox", "radio"].indexOf(form[name].type) > -1 && form[name].checked) { return form[name].value; } } else if (form[name].length) { return form[name].value; } }

return ""; };

const experienceLevel = getValue("experience[]") || getValue("experience"); const jobFunction = getValue("job_function[]") || getValue("job_function"); const industry = getValue("industry[]") || getValue("industry"); const location = getValue("location[]") || getValue("location"); const workType = getValue("work_type"); const term = getValue("q"); const sortBy = getValue("sort_by");

// If the logged in user is authenticated // Append authenticated value to make url unique/different to logged out url // same action is happening in SearchFilterViewComposer // line 589 in the multiSearchFilterHref function const authenticated = document.getElementById("authenticated").value; let toUrl = ""; if (industry.trim() && jobFunction.trim()) { const segments = [jobFunction, location, workType].filter((x) => x); toUrl = ${segments.join("/")}?industry=${industry}; } else { const segments = [jobFunction, industry, location, workType].filter((x) => x); toUrl = segments.join("/"); }

if (experienceLevel) { toUrl += ${toUrl.indexOf("?") === -1 ? "?" : "&"}experience=${experienceLevel}; }

if (term.trim()) { toUrl += ${toUrl.indexOf("?") === -1 ? "?" : "&"}q=${encodeURI(term.replace(" ", "+"))}; }

if (sortBy.trim()) { toUrl += ${toUrl.indexOf("?") === -1 ? "?" : "&"}sort=${sortBy}; }

if (authenticated === "true") { toUrl += ${toUrl.indexOf("?") === -1 ? "?" : "&"}authenticated=${Date.now()}; }

const wholeUrl = ${form.getAttribute("action")}/${toUrl.toLocaleLowerCase()}; window.location.assign(wholeUrl.replace(//$/, ""));

return false; }, }; Homepage Engineering & Technology IT & Telecoms Nairobi Contract UI/UX Designer UI/UX Designer Anonymous Employer Engineering & Technology 6 days ago Easy apply New 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 Experience Length: 5 years Language Requirement: English Working Hours: Contract - 9 to 5 Applicant Location: Kenya Job descriptions & 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 experience 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 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 (requirements 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 & Experience
• 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