Senior UI/UX Designer

Splixon; Kolkata District; On-site; INR 900,000 - 1,200,000; Full time

Job summary

Splixon Technologies Pvt. Ltd. in Kolkata is seeking a Product Designer to own end-to-end interface design for an explanation-focused product. You will translate goals into defined features, design score dashboards, and craft clear UX copy across screens.

You will prototype with low and high fidelity, define motion and transitions, ensure accessibility, and document states for engineers to build without back-and-forth questions. This role requires strong Figma skills and handoff discipline.

Qualifications

• Experience designing data-dense analytical interfaces.
• Strong Figma proficiency and design system knowledge.
• Excellent UX writing and labeling for complex scores.
• Ability to prototype with low and high fidelity.
• Design accessible interfaces with clear states and transitions.

Responsibilities

• Translate goals into defined, scoped, sequenced features.
• Design dashboards, comparison views, filtering, and metrics screens.
• Write UX copy, labels, empty states, and score explanations.
• Prototype at required fidelity; specify motion and timing.
• Maintain clean Figma files and create handoff docs.
• Ensure accessibility and keyboard/screen-reader considerations.
• Create interfaces that survive evolving scoring logic.

Skills

Product design

Data-dense interfaces

Information architecture

UX copywriting

Prototyping fidelity

Functional motion

Figma expertise

Handoff quality

Accessibility

Evolving scoring model

Tools

Figma

Lottie

Rive

After Effects

Job description

Location: Kolkata, India

ABOUT THE ROLE

We are building a product whose core job is explanation: it takes something complex — an investment-readiness score and the analysis behind it — and makes it legible, navigable, and actionable for founders. You will own the interface of that product end to end: the dashboards, the score views, the comparisons, the words on every screen. This is not a role for decorating screens. It is a role for someone who can take a one-line intention like \"founders should understand their score\" and return a defined, scoped, sequenced feature — and then design, document, and hand it off so well that engineers build it right the first time.

WHAT YOU'LL DO

Translate loosely framed product goals into defined, scoped, sequenced features — flows, states, and specs, not mood boards. Design data-dense, analytical interfaces: score dashboards, comparison and ranking views, filtering systems, and metrics-heavy screens. Write the product's language — UX copy, labels, empty states, error messages, and the explanations of the score itself. Prototype at the fidelity each question needs — low for exploration, high and interactive when a flow can only be judged in motion. Design the product's functional motion — loading and skeleton states, transitions between views, and score changes — and specify easing, duration, and reduced-motion behaviour so engineers can build it exactly. Maintain clean, structured Figma files and produce handoff documentation that covers states and edge cases without a stream of follow-up questions. Build accessibility into the design itself — contrast, hierarchy, keyboard and screen-reader behaviour specified up front, not discovered in QA. Design interfaces that survive change: our scoring logic will evolve underneath you, and your work must flex with it.

WHAT WE'RE LOOKING FOR

1. Product and feature design strength — Demonstrable ability to take an intention like \"founders should understand their score\" and return a defined, scoped, sequenced feature — not a mood board.


2. Data-dense and analytical interface experience — Serious, hands-on work with dashboards, comparison and ranking views, filtering, and financial or metrics products. You have opinions about tables.


3. Information architecture and interaction design fundamentals — Strong command of hierarchy, progressive disclosure, density, and state design.


4. Writing — UX copy, labels, empty states, error messages, explanations of the score. In a product whose job is explanation, the words are the design — weak copy sinks this role.


5. Prototyping to the fidelity a question needs — Low for exploration; high and interactive when a flow can only be judged in motion.


6. Functional motion — Short, non-blocking motion that explains rather than decorates: continuity between views, what changed in a score, real loading progress. You can specify timing and easing, and you design the reduced-motion version too. Comfortable with Figma prototyping (Smart Animate), and able to work with Lottie, Rive, or After Effects when a state needs more than Figma can show.


7. Expert Figma — Components, variants, variables, auto-layout — and files another person can pick up without a walkthrough.


8. Handoff quality — Engineers should be able to build from your specs without a stream of questions. Show us how you document states and edge cases.


9. Accessibility as a working practice, not a final audit — Contrast, hierarchy, keyboard and screen-reader behaviour specified in the design, not discovered in QA.


10. Comfort designing against an evolving model — Scoring logic will change under you. You need interfaces that survive that.

Bonus: Expressive moments done with restraint — for example, a first-time score reveal that is short and skippable. Not required.

Employment Type: Full-time