高级产品设计师

### About [Cal.com](http://cal.com/)

[Cal.com](http://cal.com/) is building the open scheduling infrastructure for the world. We help individuals, teams, and enterprises book time without friction, used by companies like Deel, Notion, Framer, and AngelList.

We’re a remote-first, async-focused team working across 10+ time zones. We prioritize autonomy, transparency, and building scalable systems for both our users and our team.

### About the Role

We’re hiring a Senior Product Designer to own core product surfaces end to end, from the first sketch to a prototype running in the browser.

You’re a product designer first. The craft, the judgment, the taste, the decisions about what we build and why: that’s the job. But you don’t stop at a static file. You take your work to a working prototype, because a prototype answers questions a mockup can’t, and it removes the ambiguity that gets lost in translation.

Those prototypes get handed off. That’s exactly why they have to be built right. Real semantics, real keyboard paths, composed from our actual primitives, close enough to how it will be implemented that an engineer picks it up and recognizes it. A prototype that cheats is a prototype that lies about the design.

We build on [coss ui](https://coss.com/), our open-source component library built on Base UI. That part is settled. It’s our foundation and it isn’t changing. What isn’t settled is how good it gets. We want someone who treats the design system as a product in its own right: finding the gaps, tightening the primitives, and pushing new patterns back into the library instead of solving the same problem locally for the fifth time.

We’re building a world-class product, down to every detail. That means the empty state, the focus ring, the error copy, the 200ms of motion nobody articulates but everybody feels. If that level of detail is where you enjoy spending your time, this is the role.

You’ll work day to day with our Head of Product and our Design Engineer. It’s a small, deliberately complementary group. We want someone who thinks out loud, shares work early and unfinished, and gets sharper by being challenged. If your instinct is to disappear for two weeks and come back with something finished, this won’t feel good to you.

Async here means you choose your hours, not that you work alone.

This role is async by default, globally remote, and part of a company culture that prioritizes deep work, flexibility, and real ownership. You’ll be trusted to take initiative, experiment, and ship.

### What You’ll Do

- Own core product surfaces from concept through working prototype: booking flows, scheduling primitives, team and enterprise surfaces
- Build and test working prototypes with whatever answers the question fastest, whether that’s Figma, Claude Code, Cursor, or v0
- Hand off prototypes that engineers can build from directly. Correct semantics, real states, composed from our primitives, no shortcuts that fall apart in production
- Continually improve coss ui. Audit what exists, close the gaps, refine the primitives, and land new components in the library rather than one-off in the app
- Keep the system honest: tokens, spacing, states, dark mode, motion. Every new surface should make the library better, not route around it
- Pressure-test the architecture alongside Design Engineering: data shape, state boundaries, what’s a primitive vs. a one-off
- Own the outcome, not just the artifact. Frame the hypothesis, define what success looks like, stay with it through implementation, and read the results
- Hold the accessibility bar: keyboard paths, focus management, semantics, contrast, motion preferences. Non-negotiable, not a QA pass at the end
- Sweat the last 10%. Empty states, error copy, loading behavior, motion. The details that separate a good product from one people love
- Work in the open with the Head of Product and Design Engineer. Share early, invite the critique, and let other people’s constraints change your design
- Write your thinking down. Async means the doc, the Loom, and the prototype are the meeting

### What We’re Looking For

- Senior-level product design experience. You’ve owned complex, ambiguous product areas from problem framing through launch and iteration
- Exceptional craft. Your portfolio holds up at 400% zoom, and you care about the details most people never name
- You build interactive prototypes independently, in code. HTML, CSS, TypeScript, React. You don’t need an engineer to make an idea real
- You work in the AI tooling daily (Claude Code, Cursor, v0) and you have opinions about where it helps and where it lies
- Deep familiarity with web standards and platform primitives. You know what the browser already does before you reach for a library
- Real design systems experience. You’ve built and maintained one, not just consumed one. You know the difference between a component and a primitive, and when a pattern has earned its place in the library
- Fluency with headless primitive composition (Base UI, Radix, or similar). Direct coss ui or Base UI experience is a strong plus
- Real accessibility knowledge. WCAG, ARIA, assistive tech, and the judgment to know when the spec isn’t enough
- You understand the architecture of what you’re designing: APIs, data models, state, and the constraints they impose
- Comfort with evidence. You can form a hypothesis, pick a measure, and read what the data says even when it disagrees with the design
- Collaborative by default. You show unfinished work, take critique well, and give it directly. Strong opinions, genuinely held loosely
- Strong written communication (clarity > formality)
- High trust, high autonomy mindset. Thrives async, without going quiet

### Bonus Skills

- Previous startup or remote experience
- An engineering background, or production web code already shipped under your name
- Experience shipping AI or agent-facing experiences
- Open source contributions, whether to coss ui, [Cal.com](http://cal.com/), or anyone else’s project
- You’ve maintained a component library in public: docs, API design, versioning, the unglamorous parts
- Experience designing for developers, or designing developer-facing APIs and SDKs
- Familiarity with scheduling, calendaring, or the mess of timezones and recurrence rules
- Motion and interaction craft. You can make something feel right, not just look right

### Compensation

$100,000 to $150,000, same salary regardless of where you live. Equity included.

### Why Work at [Cal.com](http://cal.com/)?

We’re building [Cal.com](http://cal.com/) not just as a product, but as a place to do great work and live a good life.

- Work from anywhere, anytime, fully remote & async
- Earn the same salary no matter where you live
- No standups, no micromanagement, no unnecessary calls
- Real flexibility, take time for life stuff, no approval needed
- Work in your own flow, pajamas welcome
- 30 paid OOO days per year (wherever you are in the world)
- Yearly team retreats in beautiful locations
- People-first culture, stable, family-friendly, kind

### What Our Team Says

> At this company, I’m actually treated like a real person with ideas and a life, not just another number in the system. It’s refreshing to work somewhere that gets that happy humans do better work. ~ **Sean Brydon**, Software Developer

> Working at Cal has been a completely different experience from other jobs I’ve had. There’s real trust here. I’ve been able to take ownership of my work without being micromanaged. I started in support and quickly moved into a growth role because initiative is genuinely rewarded. Everyone communicates openly, and feedback is always encouraged. The async, remote culture has been a game-changer for me. I can structure my day around life: run errands and take breaks without the pressure of always being online. It’s all about getting the work done. As a dad of two, that flexibility means everything. If I need to step away for my family, I can. That kind of trust and support motivates me to do my best work every day. ~ **Milos Puac**, Enterprise Triage Manager

### How to Apply

Send us the work. A portfolio, a repo, a prototype you built because you wanted it to exist. Show us something you obsessed over, and tell us why. We care more about what you’ve shipped than where you shipped it.