Hi! 👋 I'm Chris https://www.linkedin.com/in/chkrlee/, head of Product Design at Ashby. We're looking for a versatile, intrinsically motivated designer who is excited to contribute to rethinking how modern software is designed. At Ashby, you'll be part designer, part product manager, part consultant, and part design system manager (or some combination of the 4!). We do design differently here, and if that excites you, read on. Our unique approach is working - we're growing >100% year-over-year and have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, very low churn, and many years of runway. We're backed by amazing investors like Y Combinator, Elad Gil, Lachy Groom, and many more! We’ll share more details once we meet. HOW WE WORK In my previous roles, product teams always consisted of a product manager, a designer, and ~4-5 engineers. This may sound familiar to you! The product manager briefs the designer who then designs. After designing, mocks are handed to the engineers. We take a more principled approach here at Ashby. If you've been designing software enough, you'll realize in actuality, design is required in varying degrees on each project. Sometimes in the past, I'd be asked to design yet another settings page, when really all that was needed was an engineer to reuse existing components and just follow some documentation I had written. Other times, I felt I should effectively be the product manager and own a project from beginning to end. In these latter cases, it made sense that I was even the one providing project updates and managing resources rather than constantly being pinged by a separate product manager. This principled approach is now what we do here, and it is part of what has allowed Ashby to take down incumbents in multiple verticals all at once. We don't settle for the status quo—we actively resist reversion to the mean. Currently, I report to Benji, the co-founder & CEO. Both Abhik and Benji (our founders) care deeply about design, which at first glance may seem counterintuitive given the number of full-time designers that we employ. The belief is not that design is unimportant, but rather that it should be owned by the product team collectively, not solely by a group of full-time designers who happen to have the job title. The design department’s job at Ashby is not to make every single design decision but to equip our entire product team to make better decisions themselves, as well as edit decisions that PMs/Engineers choose to make. That, while tackling the biggest design challenges ourselves. Separate from design, you may also be excited by the fact that we maintain a near seed-stage-like culture with fuzzy lines between functional roles, as much autonomy as you can handle, and a focus on IC-work with an almost-no-meeting culture. While you get the product-market fit and scale of a growth-stage startup, you also get the agency and no-nonsense, no-red-tape culture of a seed-stage startup. WHAT WE’RE BUILDING Talent teams aspire to build a hiring process that identifies great candidates, moves them quickly through the interview process, and provides an excellent experience for the candidate. To accomplish this, recruiters perform thousands of daily tasks to coordinate and relay information between candidates, interviewers, and hiring managers. Teams struggle to keep up! Scheduling a final round is an excellent example of our customers' challenges. A recruiter needs to collect availability from the candidate, identify potential interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and perform any last-minute adjustments as availability changes. They must perform this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. Ashby provides talent teams with intelligent and powerful software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We put a lot of effort into designing products that are approachable to beginners but mastered and extended by power users. In many ways, spreadsheets set the bar here (and are what we often replace!). WHY YOU SHOULD OR SHOULDN’T APPLY YOUR QUALIFICATIONS: - 10+ years of product design experience, with the majority being in desktop SaaS - Able to take huge, ambiguous projects and break them down into actionable parts - Able to speak to patterns of the highest functioning design teams and how to create an environment of high performance - Able to leverage designers' superpowers to influence engineering, product, and the rest of the company - Able to create standards and principles that will help improve the quality of design across the product org - Able to think from first principles instead of simply applying the “standard” UX processes. - Enough experience that your intuition can solve most usability problems without having to rely solely on data & metrics or conducting user research. - Curious & resourceful enough to come up with creative solutions and de-risk them appropriately. - Best-in-class skills in layout, navigation, IA, UI, and interaction design. - Obsession with craft & details. - You have experience at an early-stage startup or have spent time as a solo designer on a team. YOU MAY WANT TO APPLY IF YOU’RE EXCITED ABOUT: - Creating leverage and impact far and above what you'd see in a typical EPD product team structure. You won’t be a cog in the wheel, the wheel is not very big! - Getting to work on all parts of a massive product surface area - spanning many user types, JTBDs, usability challenges, etc. Unlike in other organizations, you won’t be stuck working on one problem for many years. - Helping reinvent the design model for modern enterprise software—you don’t have to build wireframes, user journeys, personas, etc. What matters is solving a customer’s problem; what tools you use are up to you. - Covering all parts of the design process with a focus on design craft. You'll still be doing the occasional user research interview but will be focused on using heuristics & experience to improve our IA, navigation, interactions, UI patterns, and more. - Helping build our design system from (almost) the ground up. CONVERSELY, YOU MAY NOT WANT TO APPLY IF: - You feel uncomfortable designing independently without much guidance from a PM or design management. - You’re uncomfortable having your decisions and process being challenged constantly by engineering & product. - You prefer an in-person role over remote (Ashby operates remotely). - You dislike written documentation. - You want a set structure and rhythm to your projects. - PM gives you a brief, you do wireframes, then mocks, then pass off work to engineers. Rinse and repeat. - You prefer a narrow job scope - interaction design only, design system only, etc. ON A WEEKLY BASIS YOU WILL FIND YOURSELF: - Consulting for engineers who need help structuring layout, typography, flows, etc. - Digging into problems by consulting GTM, talking to customers, asking for data requests, and more in order to present confident assumptions about your proposals. - Using Figma to draw out your ideas and create visual artifacts for stakeholder alignment. - Writing specification docs (we call them specs!) that detail your design proposals. These documents are meant to get stakeholder alignment on the biggest decisions you want to make and are a core part of how we work at Ashby. - Taking ownership of larger product features and thinking through Jobs-To-Be-Done, navigation, information architecture, layout, interaction, etc. - Taking in customer feedback and using heuristics to build your own usability backlog and propose…