A complete application in a minute
Tailored resume and cover letter, ready to send.
Splixon Technologies Pvt. Ltd. is seeking a design-focused product designer to own the end-to-end interface of a scoring-focused product.
You will translate high-level goals into defined features, design data-dense dashboards, and craft UX copy across screens. This role emphasizes prototyping, motion design, and documentation to enable engineering teams to build right the first time. You’ll shape information architecture, ensure accessibility, and create interfaces resilient to evolving scoring
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.
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.
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.