Original listing text, shown exactly as published by the company.
What you will do
- Act as a product designer within a cross-functional full-stack product team, contributing to team-level outcomes
and shared KPIs
- Lead the design process in discovery: from problem framing and task clarification to hypotheses, concepts,
validation, and delivery
- Translate complex business processes into scalable UX solutions for a Web SaaS CRM platform
- Design interfaces for multi-step workflows, admin panels, configuration flows, tables, roles, permissions, and
operational scenarios
- Think beyond a single use case or client request and design solutions that can work across different companies,
industries, and business models
- Build abstractions from specific business cases and turn them into reusable, flexible product patterns
- Challenge requirements and product assumptions by asking “what if” questions: what happens if there are 10
options, 100 scenarios, different user roles, or another business process
- Conduct user research, stakeholder interviews, contextual inquiries, and workflow analysis to uncover user needs,
business logic, constraints, and friction points
- Develop hypotheses and validate them through prototypes, usability testing, analytics, and iterative feedback
- Collaborate closely with engineers to understand technical constraints, implementation logic, APIs, frontend
limitations, and system dependencies
- Prepare clear design documentation that helps engineers understand not only how the interface should look, but
why it should work this way
- Apply existing design system components and patterns; contribute to the growth of Kyivstar’s corporate design
system when existing solutions are insufficient
- Use product analytics and qualitative feedback to evaluate the impact of design decisions and improve usability,
efficiency, and scalability
- Provide design QA during implementation to ensure that delivery matches both visual quality and product intent
- Optionally use AI-based tools, prototyping tools, low-code/no-code, or vibe-coding approaches to explore ideas,
structure tasks, validate assumptions, or speed up design workflows
Qualifications and experience needed
- Product design experience: 4+ years as a Product Designer, UX Designer, or similar role, preferably in SaaS, B2B,
B2B2C, CRM, support tools, communication platforms, or complex operational products
- Discovery maturity: ability to work with ambiguous problems, frame tasks, identify constraints, form hypotheses,
and shape product direction before moving into UI execution
- Systems thinking: ability to see a product as a system of roles, workflows, scenarios, permissions, configurations,
and business rules — not just as a set of screens
- Conceptual thinking: ability to move from a specific client request to a more abstract, scalable solution, and then
translate it back into a concrete interface
- Complex interface design: strong experience designing admin panels, dashboards, tables, multi-step flows,
configuration interfaces, role-based experiences, or workflow-heavy products
B2B / SaaS mindset: understanding of how products work for different companies, teams, roles, and business
processes; ability to design for more than one customer context
- Technical understanding: solid understanding of how frontend development works, including responsive layouts,
components, constraints, and modern web interface logic; basic knowledge of HTML/CSS concepts such as flexbox
is a plus
- Collaboration with engineers: ability to discuss trade-offs, implementation complexity, technical limitations, and
product feasibility with developers
- Research and analytics: experience with qualitative and quantitative methods, including user interviews, usability
testing, workflow analysis, product analytics, and feedback synthesis
- Argumentation: ability to clearly explain and defend design decisions, compare alternatives, describe
consequences, and show why a particular solution is appropriate
- Critical thinking: ability to challenge requirements, avoid jumping to the first obvious solution, and consider edge
cases, future scaling, and long-term product impact
- Design systems: hands-on experience using and extending component libraries; familiarity with structured design
systems and Figma libraries
- Tools: strong proficiency in Figma and prototyping tools; ability to present design work clearly to stakeholders and
developers
- Communication: strong collaboration skills, comfort working in Agile/Scrum teams, and ability to communicate
clearly in Ukrainian and English
Nice to have
- Experience with CRM, customer support, contact center, communication, telecom, or enterprise workflow products
- Experience in modern SaaS startups or product companies where designers had broad ownership and direct
influence on product decisions
- Experience with AI-powered SaaS products or AI-based product workflows
- Previous frontend, business analysis, product management, or technical background
- Experience with low-code/no-code tools, vibe coding, AI prototyping, or prompt-based workflows
- Understanding of AI tools beyond surface-level usage: ability to use them critically, structure tasks well, and
recognize their limitations
- Experience designing products with integrations, APIs, automation flows, complex permissions, or multi-role user
models
You may be a good fit if you
- Do not wait for a perfect task description — you help shape the task yourself
- Ask strong “what if” questions before jumping into UI
- Can think about how one feature will work for different companies and business processes
- Are comfortable working with uncertainty, incomplete context, and complex constraints
- Can challenge product and technical stakeholders constructively
- Care about both product value and implementation feasibility
- Think in systems, patterns, scenarios, and long-term scalability
- Can explain not only what should be designed, but why it should work this way
This role may not be the best fit if you
- Prefer working only with fully prepared requirements and detailed specifications
- Focus mostly on visual UI execution without deeper product or UX ownership
- Avoid technical discussions with engineers
- Design only for the immediate task without considering future scalability
- Are uncomfortable challenging assumptions or defending your decisions
- Prefer narrow delivery tasks over Discovery, problem framing, and system-level thinking
es for everyone: annual or quarterly, depending on the role
- Learning opportunities through the company’s library, internal resources, and partner programs
- Health and life insurance…
