- About PurplegloPurpleglo is an at-home red light therapy device built for one specific moment: the skin changes that come with GLP-1 weight loss — crepiness, softening, loss of firmness. Our audience is women, largely 40–55, who did something hard and are now dealing with something nobody warned them about.
- Why this role existsOur site lives in Framer. It currently reads like a discount gadget store — badge clutter, slashed prices, urgency timers, generic anti-aging testimonials — and it contradicts a brand strategy built on restraint and honesty. The first job is to rebuild it, surface by surface, into something that looks like it costs $299 and sounds like it's telling the truth.

But we're hiring in-house rather than contracting this out because the rebuild is the beginning, not the deliverable. Purpleglo's web surface is about to grow quickly — a creator co-creation program that will need co-branded product and asset pages, a widening library of diagnostic tools and quizzes, SEO editorial at volume, and a continuous testing cadence on the pages that sell. That work needs someone who holds the whole system in their head and keeps it coherent as it expands, which is exactly what a rotating cast of freelancers cannot do.

This is not a "make it pretty" role. Every surface you build is judged on whether it converts the right buyer and filters out the wrong one.

- Requirements (must have)Framer craft

- 1+ years building and shipping production sites in Framer — not prototypes, not Figma files handed to a developer
- Fluent with Framer CMS: collections, energetic pages, filtering, and templated article/blog architecture
- Components and variants built for reuse, with a real design-token setup (color, type scale, spacing) rather than one-off styling
- Breakpoint discipline across desktop, tablet, and mobile, including states most people skip — long-text overflow, empty states, loading, error
- Comfortable with code components or code overrides in Framer when a native component won't do the job

Web and conversion fundamentals

- Demonstrable DTC or e-commerce work — you've built a page whose job was to sell something, and you can talk about what it did
- Understand PDP anatomy: above-the-fold hierarchy, objection ordering, sticky add-to-cart behavior, review placement, trust signals that aren't badge spam
- Accessibility as a baseline, not a phase: real contrast ratios, focus states, keyboard navigation, semantic heading structure, alt text. Our audience is 40+ and reads on phones in low light.
- Performance ownership: image formats and sizing, lazy loading, font loading strategy, and keeping Core Web Vitals green on mobile.



A beautiful page that loads in six seconds is a failed page.

SEO and analytics literacy

- Framer SEO fundamentals: per-page titles and meta descriptions, canonical URLs, Open Graph, clean slug structure, sitemap and redirect handling when pages move
- Can implement structured data (Article, Product, FAQ) in Framer without hand-holding
- Comfortable wiring analytics and tracking — GA4, Meta Pixel, Microsoft Clarity — and reading heatmaps and session recordings to argue for a change

Working style

- Typography-led. You can look at an editorial serif and a sans and make them behave together across a whole site.
- Restraint. Our brand is quiet. If your instinct on every section is to add a gradient, an animation, and a badge, this will be frustrating for both of us.
- You work from a written brief and existing copy rather than needing everything invented for you, and you flag copy that isn't working instead of silently designing around it.
- Self-directed. This is currently a team of one on the web surface. Nobody will be assigning you tickets — you'll be expected to hold the roadmap, prioritize against revenue, and tell us when something we've asked for is the wrong thing to build.
- You build for the version of the site that exists in a year, not just the page in front of you. Shortcuts that make one page ship faster and every future page slower are the wrong trade here.
- Comfortable working closely with copy, growth, and creator partnerships rather than receiving finished briefs over a wall.

- Nice to have
- Experience in beauty, wellness, skincare, medical device, or health-adjacent DTC
- Familiarity with regulated-claims environments — you've had a lawyer or compliance reviewer redline your page before
- Shopify or headless commerce exposure, especially Framer or a similar builder connected to a Shopify backend
- Motion design that stays subtle: scroll-linked reveals, considered easing, and knowing when to leave a section still
- Basic art direction for photography — briefing or selecting real, unretouched-looking imagery of women in their 40s and 50s
- A/B or multivariate testing experience on landing pages

- Craft and process standardsBecause you'll live with this project for years rather than hand it off, we hold it to a maintainability standard from day one:





- A Framer project organized so a second designer could join tomorrow: named layers, documented components, a published design-token set, and no orphaned pages
- A component library covering the recurring modules — honesty qualifier, timeline, spec table, review block, FAQ, CTA — extended deliberately rather than duplicated per page
- Responsive behavior verified on real devices, not just Framer's canvas
- A short written rationale for each major surface, so decisions survive team changes and don't get relitigated every quarter
- Staging link for review before anything goes live; YBS approves before launch, every time

- What we offer
- Ownership of the entire web surface of a brand at the point where it's being built properly for the first time
- A locked brand foundation and finished copy for the core surfaces — you're not designing into a vacuum or waiting on decisions
- Direct line to the people setting strategy, with no design-by-committee layer in between
- Budget for the tooling, testing, and photography the work genuinely needs
- Room to grow into leading the web function as the team expands

10. What to send
1. Portfolio with live Framer URLs. Case study PDFs and Dribbble shots aren't enough — we want to open the sites, resize the browser, and run Lighthouse on them.
2. One deep case study on a page you built that had a commercial job. What was the brief, what did you change, what happened to the numbers, what would you do differently.
3. Editor access or a walkthrough of at least one Framer project so we can see how you actually build — components, CMS structure, and whether it's maintainable.
4. A short note (under 200 words) on this: our product page has to tell some visitors that we're not the right product for them, near the top of the page, before they've bought anything. How would you design that section so it builds trust instead of losing the sale?

Applications without live Framer links won't be reviewed.
- Signals that this isn't a fit
- Portfolio is Figma mockups with a Framer logo attached
- Every site in the portfolio looks like the same template with different colors
- Heavy reliance on stock animation libraries and parallax as a substitute for hierarchy
- Can't discuss performance, accessibility, or SEO without changing the subject to visuals
- Uncomfortable being told a section is off-brand and rebuilding it
- Wants to redesign the brand rather than execute it — the brand foundation is locked and inherited by every touchpoint
- Wants a pure project role. Most of this job's value shows up in year two, in the pages you haven't built yet.

📌 Framer Designer / Design-Engineer (web) (India)
🏢 Purpleglo
📍 India