Product Designer at Kredete

About The Role

• We’re looking for a Product Designer who knows how to design products, not just screens.
• You’ll work on complex financial products across consumer, business, and infrastructure experiences. You should be comfortable taking a problem from an early requirement or rough idea through research, flows, interaction design, polished UI, developer handoff, and ultimately a shipped product.
• We care about craft, but great-looking interfaces alone aren’t enough. We’re looking for someone who understands how products work, can make strong decisions, collaborate closely with product and engineering, and demonstrate the impact of what they’ve shipped.

What You'll Do

• Own product design work from problem definition to production.
• Translate product requirements and business goals into clear user flows and product experiences.
• Question requirements when necessary and identify gaps, edge cases, technical constraints, and opportunities before jumping into UI.
• Design complex workflows across mobile and web products.
• Create user flows, wireframes, prototypes, interaction models, and high-fidelity interfaces.
• Think deeply about states beyond the happy path, including loading, empty, error, permission, validation, edge cases, and failure scenarios.
• Work closely with Product Managers and Engineers throughout implementation rather than treating handoff as the end of the design process.
• Participate in design QA and ensure what ships meets the intended experience and quality.
• Contribute to and evolve our design system.
• Use data, research, customer feedback, and product metrics to evaluate design decisions.
• Document important design decisions, behaviours, interactions, and implementation requirements.
• Use AI tools to accelerate research, exploration, prototyping, documentation, and execution where appropriate.
• Take ownership of outcomes and continuously improve products after launch.

Qualifications
Product Thinking

You can look beyond individual screens and understand the complete system.

You Should Be Able To Explain

• What problem you were solving.
• Why the problem mattered.
• How you arrived at your solution.
• What alternatives you considered.
• What constraints influenced the design.
• What you personally owned.
• What eventually shipped.
• What happened after it shipped.