UX/UI Designer

UX/UI Designer at YesAstrology

The UX/UI Designer at YesAstrology is a full-time, fully remote position within the Design department, open to candidates worldwide. The role centers on designing intuitive interfaces for reports, tools, and mobile experiences across the YesAstrology platform. This is a hands-on product design position: you will shape how users move through natal chart reports, interactive astrology tools, and mobile reading flows, turning dense celestial data into clear, elegant screens.

Day to day, the work spans the full product surface of a multilingual astrology, horoscope, tarot, numerology, and spiritual guidance platform. A natal chart report alone contains layered information — planetary placements, house cusps, aspect grids, and interpretive text — and each layer needs its own visual hierarchy. You will design layouts that let a reader scan a Sun–Moon–Rising summary in seconds, then drill into a Saturn square Pluto aspect or a 10th-house stellium without losing their place. The same care applies to tool interfaces, where users enter birth data and expect immediate, legible output.

Because YesAstrology serves readers across multiple languages, your interfaces must survive translation: flexible text containers, right-to-left readiness where needed, and typography that holds up when a German compound word or a Turkish suffix chain runs longer than the English string. Mobile experience is equally central — chart wheels, transit timelines, and tarot spreads must remain readable on a small screen at night, often in low light, which shapes decisions about contrast, color temperature, and touch target sizing.

This is a remote-first role with no fixed office, so clear asynchronous communication matters as much as visual craft. Designers here work from Figma-style flows and prototypes, document component behavior for engineering, and iterate against real usage. If you want to see how the broader product ecosystem fits together before applying, explore the platform at YesAstrology tools and study how existing report and tool screens handle data density.

Professional Background and Design Experience

The position requires a portfolio showing clean, data-rich designs with a mystical touch — that is the single stated requirement, and it defines the candidate profile precisely. YesAstrology is not looking for generic app screens; it is looking for evidence that you can organize dense, structured information (tables of planetary degrees, aspect matrices, multi-section report pages) while preserving an atmosphere of depth and ritual. A portfolio that pairs a well-resolved data table with a beautifully typeset interpretive reading demonstrates exactly the range this role demands.

Strong candidates typically bring several years of product design experience, with at least part of that spent on information-heavy products: analytics dashboards, financial or health reporting, scientific visualization, or editorial platforms with long-form content. What transfers to astrology is the discipline of hierarchy — deciding what a user sees first, what recedes, and how a chart wheel, a transit list, and a paragraph of interpretation coexist on one screen without visual noise. Experience with design systems, component libraries, and accessibility standards (contrast ratios, focus states, screen-reader labeling for chart graphics) is directly applicable.

Domain familiarity with astrology is helpful but not the barrier it might appear to be. Designers who understand why a 1st-house versus 7th-house emphasis changes a reading's framing, or why an exact conjunction reads differently from a wide orb, will make sharper interface decisions about grouping and emphasis. If your astrological knowledge is still developing, the expectation is curiosity and a willingness to learn the vocabulary — signs, planets, houses, aspects, and the distinction between natal placements and moving transits.

Practical collaboration skills round out the profile. You will hand off to engineers who implement chart calculations and rendering, so documenting spacing, states, and edge cases (missing birth time, unknown location, partial data) prevents downstream ambiguity. A designer who can specify how an interface behaves when a user has no exact birth time — and still presents a coherent, honest result — is worth more here than one who only designs the ideal case. If you would like a sense of the editorial voice and content depth your designs will frame, the YesAstrology blog is a useful reference point.

User Experience (UX) Research and Strategy

UX research and strategy at YesAstrology means deciding, before a single pixel is placed, how a reader should move through dense astrological data — a natal chart report, an interactive tool, or a mobile reading flow — and then validating that path against real behavior. The designer's job is to map the journey from birth-data entry to interpretive payoff, so that a user can scan a Sun–Moon–Rising summary in seconds and still drill into a Saturn square Pluto aspect or a 10th-house stellium without losing their place. Research here is not abstract: it is the discipline of turning layered celestial information into a sequence that feels calm, legible, and genuinely useful.

Strategy begins with the information architecture of a chart itself. A natal report contains planetary placements, house cusps, aspect grids, and interpretive text, and each layer needs its own hierarchy. A practical research question is whether a reader arrives looking for a single answer — "what does my Saturn return mean?" — or for open exploration of the whole wheel. Those two intents produce different navigation models: a search-and-answer flow versus a scrollable, sectioned report. Testing both against real usage, rather than assuming, is what separates a considered interface from a decorative one.

Edge cases drive much of the strategic thinking. A user with no exact birth time, an unknown birth location, or partial data still deserves a coherent and honest result, so the research phase must define how the interface behaves when the chart is incomplete and how that limitation is communicated without undermining trust. The same applies to multilingual readers: flexible text containers, right-to-left readiness where needed, and typography that survives a longer German compound word or Turkish suffix chain are research findings, not afterthoughts.

Because the role is remote-first and open to candidates worldwide, research is conducted asynchronously — documented flows, prototypes, and written findings that a distributed team can act on. If you want to see how the existing product ecosystem handles data density before shaping its next iteration, studying the live report and tool screens is the most direct starting point; the YesAstrology tools show how birth-data entry and chart output currently meet.

User Interface (UI) Design and Visual Identity

UI design and visual identity at YesAstrology means giving the platform a single, recognizable visual language that holds across natal chart reports, interactive tools, tarot spreads, and mobile reading flows — while keeping data-rich screens readable in low light. The stated requirement for the role is a portfolio showing clean, data-rich designs with a mystical touch, and that phrase is the brief: precision and atmosphere in the same frame. A chart wheel, a transit timeline, and a paragraph of interpretation must coexist on one screen without visual noise.

Concretely, this means defining a type scale that can carry both a table of planetary degrees and a long-form interpretive reading, a color system with enough contrast for night-time mobile use, and touch targets sized for one-handed chart browsing. Chart graphics need accessible labeling and clear focus states, because a glyph-heavy wheel is meaningless to a screen reader unless it is described. Component behavior — hover, expanded, empty, and error states — must be documented for the engineers who implement chart calculations and rendering, so that spacing and edge cases are not left to interpretation.

Visual identity also has to survive translation. Layouts built on fixed text widths break when a localized string runs long, so the system should rely on flexible containers and resilient typography rather than pixel-perfect English strings. The mystical register is carried by material and light — deep indigo and midnight blues, warm brass and candle-gold accents, generous negative space around dense data — rather than by ornament that competes with legibility.

The result is a design system, not a set of one-off screens: reusable components that keep every new feature consistent with the wider platform as it grows across astrology, horoscope, tarot, numerology, and spiritual guidance. Designers work from Figma-style flows and prototypes and iterate against real usage, which is why the visual language must be specified precisely enough to be built and tested, not just admired in a mockup.

Wireframing, Prototyping, and User Testing

Wireframing, prototyping, and user testing at YesAstrology are the stages where a natal chart report stops being a data problem and becomes a reading experience. The UX/UI Designer builds low-fidelity wireframes first to settle structure — where the Sun–Moon–Rising summary sits, how house cusps and aspect grids are grouped, where interpretive text begins — then moves into interactive prototypes that can be clicked and tested before engineering writes production code. Testing validates those flows against real behavior, so decisions about hierarchy come from observed use rather than assumption.

Wireframing a chart interface is genuinely difficult because a single screen carries several information layers at once. A practical sequence looks like this:

1. Sketch the birth-data entry form, including the fields for date, exact time, and birthplace.
2. Block out the chart wheel and its surrounding placement list as separate, scannable regions.
3. Place the aspect grid so it can be read without competing with the wheel.
4. Reserve a distinct zone for long-form interpretation, set apart from the numeric data.
5. Define how the layout collapses on a small screen, where the wheel and the text cannot sit side by side.

Prototyping then tests the two intents a reader actually arrives with. Someone asking a single question — what does my Saturn return mean, or why does my 7th house matter — wants a search-and-answer path, while someone exploring the whole wheel wants a scrollable, sectioned report. A clickable prototype lets both paths be tried with real people, and the findings usually reshape navigation rather than decoration. The same prototypes should include the incomplete-data case: a user with no exact birth time, an unknown birth location, or partial input still needs a coherent, honest result, and that state must be designed rather than discovered in production.

Because the role is remote-first and open to candidates worldwide, testing runs asynchronously — recorded sessions, written findings, and annotated prototypes that a distributed team can act on. Designers work from Figma-style flows and iterate against real usage, documenting spacing, states, and edge cases for the engineers who implement chart calculations and rendering. If you want to see how the current product handles data density before shaping its next iteration, the live report and tool screens are the most direct reference; you can study how birth-data entry and chart output currently meet at YesAstrology reports.

Design Systems and Cross-Functional Collaboration

Design systems and cross-functional collaboration are what keep YesAstrology's interfaces consistent as the platform grows across astrology, horoscope, tarot, numerology, and spiritual guidance. The UX/UI Designer maintains reusable components — chart wheels, placement tables, aspect grids, transit timelines, tarot spread layouts, and the typographic scale that carries both numeric data and long-form interpretation — and works alongside engineering, product, and content teams so every new feature inherits the same visual language instead of inventing a new one. The stated requirement for the role, a portfolio showing clean, data-rich designs with a mystical touch, is essentially a test of whether a designer can build that kind of system rather than a set of one-off screens.

A working design system here has to solve specific problems. Component behavior — hover, expanded, empty, and error states — must be documented for the engineers who implement chart calculations and rendering, so spacing and edge cases are not left to interpretation. Chart graphics need accessible labeling and clear focus states, because a glyph-heavy wheel is meaningless to a screen reader unless it is described. The color system must hold enough contrast for night-time mobile use, and touch targets must be sized for one-handed chart browsing. Layouts also have to survive translation: flexible text containers and resilient typography, rather than pixel-perfect English strings, so a longer German compound word or a Turkish suffix chain does not break a table.

Cross-functional collaboration is where the system is stress-tested. A content editor may need a new interpretive section type, an engineer may need a component variant for a chart with an unknown birth time, and a product owner may want a new tool surface — each request either fits the existing system or justifies an extension. Designers who understand why a 1st-house versus 7th-house emphasis changes a reading's framing, or why an exact conjunction reads differently from a wide orb, make sharper decisions about grouping and emphasis when those requests arrive. Domain vocabulary — signs, planets, houses, aspects, and the distinction between natal placements and moving transits — is part of the shared language between design and the rest of the team.

Because the position is full-time, fully remote, and open to candidates worldwide, this collaboration happens asynchronously: documented flows, annotated prototypes, and written component specifications that a distributed team can act on without a shared office. The mystical register is carried by material and light — deep indigo and midnight blues, warm brass and candle-gold accents, generous negative space around dense data — rather than by ornament that competes with legibility. The end result is a design system precise enough to be built, tested, and extended, keeping every new report, tool, and mobile reading flow recognizably part of the same platform.

Key Responsibilities and Required Qualifications

The UX/UI Designer at YesAstrology is a full-time, fully remote position within the Design department, open to candidates worldwide, and the core responsibility is designing intuitive interfaces for reports, tools, and mobile experiences. The single stated qualification is a portfolio showing clean, data-rich designs with a mystical touch. Everything else in the role flows from those two anchors: turning dense astrological data — birth charts, planetary placements, house cusps, aspect grids, and interpretive text — into screens that feel calm, legible, and genuinely useful, while preserving the atmosphere of depth and ritual that YesAstrology readers expect.

Day to day, the work spans the full product surface of a multilingual astrology, horoscope, tarot, numerology, and spiritual guidance platform. A natal chart report alone contains layered information, and each layer needs its own visual hierarchy: a reader should be able to scan a Sun–Moon–Rising summary in seconds, then drill into a Saturn square Pluto aspect or a 10th-house stellium without losing their place. The same care applies to tool interfaces, where users enter birth data and expect immediate, legible output. Because the platform serves readers across multiple languages, interfaces must survive translation — flexible text containers, right-to-left readiness where needed, and typography that holds up when a German compound word or a Turkish suffix chain runs longer than the English string.

The responsibilities follow a familiar product design arc, and each stage carries concrete deliverables:

• UX research and strategy: map the journey from birth-data entry to interpretive payoff, and decide whether a reader arrives seeking a single answer ("what does my Saturn return mean?") or open exploration of the whole wheel — two intents that produce different navigation models.
• UI design and visual identity: define a type scale that carries both a table of planetary degrees and long-form interpretation, a color system with enough contrast for night-time mobile use, and touch targets sized for one-handed chart browsing.
• Wireframing and prototyping: settle structure first — where the chart wheel, placement list, aspect grid, and interpretive text sit — then build clickable prototypes tested before engineering writes production code.
• User testing: validate flows against real behavior, including the incomplete-data case where a user has no exact birth time, an unknown birth location, or partial input and still deserves a coherent, honest result.
• Design systems and cross-functional collaboration: maintain reusable components — chart wheels, placement tables, aspect grids, transit timelines, tarot spread layouts — and document hover, expanded, empty, and error states for the engineers who implement chart calculations and rendering.

On qualifications, the listed requirement is deliberately narrow: a portfolio showing clean, data-rich designs with a mystical touch. In practice that means evidence you can organize dense, structured information — tables of planetary degrees, aspect matrices, multi-section report pages — while preserving an atmosphere of depth. Strong candidates typically bring several years of product design experience, with part of it spent on information-heavy products such as analytics dashboards, financial or health reporting, scientific visualization, or editorial platforms with long-form content. Experience with design systems, component libraries, and accessibility standards — contrast ratios, focus states, screen-reader labeling for chart graphics — transfers directly, because a glyph-heavy chart wheel is meaningless to a screen reader unless it is described.

Domain familiarity with astrology is helpful but not a barrier. Designers who understand why a 1st-house versus 7th-house emphasis changes a reading's framing, or why an exact conjunction reads differently from a wide orb, will make sharper decisions about grouping and emphasis; if your astrological knowledge is still developing, the expectation is curiosity and a willingness to learn the vocabulary of signs, planets, houses, aspects, and the distinction between natal placements and moving transits. Practical collaboration skills round out the profile: this is a remote-first role with no fixed office, so clear asynchronous communication matters as much as visual craft, and designers work from Figma-style flows and prototypes, document component behavior for engineering, and iterate against real usage. If you want to see how the broader product ecosystem fits together before applying, you can study how existing report and tool screens handle data density at YesAstrology tools.