Ashby

Manage scheduling and real-time analysis to ensure SLA attainment and optimize capacity planning for a global support organization. | Experience in workforce management or scheduling within technical support, strong analytical and collaborative skills. | Hi! I'm Allie, Head of Support at Ashby. 👋 As our Support organization scales globally, one of the most critical levers for delivering an exceptional customer experience is making sure we have the right capacity, in the right places, at the right times, without sacrificing flexibility, quality, or humanity. We recently hired our first Workforce Management Lead to build the forecasting and capacity-planning foundation for the team. Now we're adding a Workforce Management Analyst to own the execution layer: turning those forecasts into thoughtful schedules and managing coverage in real time as the day unfolds. This is not a traditional call-center WFM role. Our Support team is highly tenured, deeply technical, and made up of thoughtful practitioners who regularly contribute beyond tickets, partnering on projects, enabling self-service, shaping tooling, and influencing product direction. Your job is to keep coverage healthy and SLAs met while protecting the flexibility that lets this team do its best work. You'll treat real-time management as an enabling function, not an adherence-policing exercise. This role is for someone who loves the craft of scheduling and the fast pace of intraday management, is energized by live problem-solving, and sees patterns in real-time data that make the whole operation run smoother. About This Role As the Workforce Management Analyst, you'll own scheduling and real-time analysis (RTA) for a global Support organization. You'll partner closely with our WFM Lead, who owns long-range forecasting and capacity strategy, and translate those plans into practical schedules and live coverage decisions. Day-to-day, you'll monitor how the team is tracking against plan, recommend and make real-time adjustments, and surface the intraday signals that keep us ahead of SLA risk. Because our WFM function is still young, you'll have significant influence over how scheduling and RTA operate at Ashby, setting up scalable, humane practices rather than inheriting rigid ones. Role Responsibilities Scheduling and Coverage Design Build and maintain global schedules that align required coverage with our headcount, skills, and time zones, translating the WFM Lead's capacity plans into workable day-to-day schedules. Partner with Support Managers to evolve schedules as the team grows, regions expand, and needs change, including managing shift-change and time-off workflows. Design coverage that supports SLA attainment while preserving the flexibility and autonomy our team values. Account for skill distribution and routing so the right work reaches the right people. Real-Time Analysis and Intraday Management Monitor queues and team activity in real time, tracking how we're pacing against schedule and SLA throughout the day. Make and recommend live adjustments (re-prioritization, coverage shifts, breaks/offline time) to keep service levels healthy as volume and complexity fluctuate. Spot intraday risks early and communicate them clearly, coordinating with Support Managers to respond without creating unnecessary alarm. Manage real-time exceptions (spikes, outages, unplanned absences) with sound judgment and a calm, collaborative approach. Data and Insights Track team data and behaviors as inputs that improve planning, not as compliance metrics to enforce. Build and maintain dashboards that give visibility into coverage health, intraday trends, and emerging risk. Feed real-world scheduling and RTA learnings back to the WFM Lead to sharpen forecasts and capacity assumptions over time. Cross-Functional Partnership Partner closely with the WFM Lead, Support Managers, and Support Operations to keep coverage plans aligned with reality. Act as a trusted, day-to-day point of contact for coverage questions and live adjustments. Advocate for sustainable, human-centered scheduling decisions that scale with the business. Role Requirements Scheduling and Real-Time Management Expertise Hands-on experience with scheduling and/or real-time/intraday management in a Support, CX, or technical services environment (e.g., WFM Analyst, RTA Analyst, or Scheduling Analyst). Strong grasp of coverage strategies, adherence/shrinkage/occupancy/conformance concepts, and how they translate into daily service levels. Comfort making sound real-time decisions with imperfect information and a fast clock. Systems and Analytical Thinking Highly analytical, able to read live data quickly and turn it into clear, actionable adjustments and recommendations. Experience with WFM/scheduling tooling and comfort building or maintaining dashboards. Familiarity working with Support metrics and SLAs in a nuanced, non-mechanical way. Collaborative and People-Centered Deep respect for the expertise of Support professionals and an appreciation for flexible, trust-based environments. Strong communicator who can flag risk and coordinate live adjustments without reading as "policing." Comfortable partnering across managers and levels, and taking direction from the WFM Lead on strategy while owning the execution. You Should Apply If: You love the craft of scheduling and the pace of real-time coverage management. You see WFM as an enabling function, not a policing one. You're energized by live problem-solving and making quick, well-reasoned calls under pressure. You're excited to partner with experienced, technical Support professionals who value autonomy and impact. You want to help shape how scheduling and RTA operate as Support scales, while partnering with a WFM Lead who owns the forecasting foundation. You May Not Want to Apply If: You're looking for a traditional Support environment focused primarily on adherence enforcement. You want to own long-range forecasting and capacity strategy end-to-end (that sits with our WFM Lead; this role is the scheduling + RTA partner to it). You prefer fixed rules and static models over iteration, flexibility, and real-time judgment. You're uncomfortable operating in ambiguity or building structure where none yet exists. You believe there's one "correct" way to staff or schedule Support. About Ashby We’re building the next generation of enterprise software, and we’re starting with a suite of products that help talent leaders, recruiters, and hiring managers run their hiring process significantly better. Learn more on our website: https://www.ashbyhq.com/ We are well-funded and backed by great investors, including Y Combinator, Elad Gil and Lachy Groom. We publicly launched in October 2022 and are working with amazing companies we're proud to partner with. We’ve built an incredible team and exceptional product over the past few years, and we truly are just getting started. In short, this is the perfect time to join 🚀 About Go To Market Our Support team is a part of our Customer Success department, and thus is a part of our Go To Market function. Here are a few points that should give you an idea of what it is like to work with us: We spend a lot of time building best-in-class products, since we believe a highly differentiated product is easier to sell. We also spend a lot of time building a best-in-class customer experience. We aim to offer deep expertise whenever we interact with prospects and customers (we hope our 9.8 Support rating on G2 signals this). We strongly believe that small teams with very talented people and the right work environment deliver much high performance and we're built accordingly. Interview Process Our interview process is thorough — we aim to ensure each person that joins the team is the right fit for Ashby and will provide ample information for you to assess if Ashby is the right fit for you. The process for this role is as follows: Intro Call with Recruiting - 30 Minutes Hiring Manager Interview - 45-60 Minutes Take Home Assessment - 1 week to complete Final Round interview - 2 hours Executive Partnership Interview with our VP of Customer Success Operational Modeling and Manager Partnership Interview with our Director of Support and Analytics Product Manager Enablement and Cross Functional Interview with Support Management Benefits You’ll get the time to do things the right way; we put a lot of emphasis on high quality work and avoid quick hacks as much as possible. Competitive compensation is offered. 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. Unlimited PTO with four weeks is recommended per year. Expect “Vacation?” in our one-on-one agenda until you start taking it 😅 Twelve weeks of fully paid family leave in the US. We plan to expand this to employees in other countries as situations arise. Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! $100/month education budget with more expensive items (like conferences) covered with manager approval Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities. Ashby is committed to a fair and transparent hiring process. We confirm that this advertisement is for an active, existing vacancy within our organization. Please be advised that we may use artificial intelligence-driven tools to assist our recruitment team in screening, assessing, and selecting candidates for this position.

Design and execute enablement programs to equip Customer Success teams for retention and growth. | Develop and manage onboarding and training programs for Customer Success teams, collaborating cross-functionally to drive business outcomes. | About Ashby • We’re building the next generation of enterprise software, starting with products that help talent leaders, recruiters, and managers unlock hiring excellence • Raised our Series D earlier this year, and we’re growing ARR >100% YoY • Have over 3,000 amazing customers including OpenAI, Ramp, Deliveroo, Notion and Reddit • Built multiple products to win both land-and-expand and material new business deals • Rapidly moving up-market with no signs of slowing down • Implemented AI throughout the platform • Known for our pace of innovation and advanced analytics About this role: As the Customer Success Enablement Manager, you will be a critical partner to our Customer Success organization, ensuring CSMs, Implementation Specialists, Contract Management and Professional Services teams have the skills, knowledge, and resources to deliver exceptional customer outcomes. Reporting to the Head of Revenue Enablement, you will refine and execute programs that accelerate CSM and Professional Service onboarding, reinforce customer engagement excellence, and ensure CS leaders and their teams are consistently equipped to drive retention and growth. This is a hands-on role with high visibility, where you’ll collaborate closely with CS Leadership, Professional Services, Implementation, and cross-functional partners like Product Marketing and Revenue Operations. Your success will be measured by the effectiveness of the CS organization—knowledgeable, well prepared CSMs, stronger renewal and expansion execution, and consistent adoption of strategic playbooks (such as our Customer Outcomes Framework) that underpin Ashby’s growth. Customer Success will be a nearly 100 person customer-facing team next year, and your work will directly impact our trajectory to $100M ARR and beyond. Role Scope & Requirements: • 🤝 Business Partnership: You partner closely with CS Leaders across segments to deeply understand their priorities. You ask tough questions, surface gaps, and design enablement programs that align to business outcomes like NRR, expansion, and customer satisfaction. You build trust across Product Marketing and RevOps to deliver cohesive GTM programs. • ⚙️ Program Development: You create and curate learning paths, playbooks, and frameworks tailored to CSM needs (e.g., value discovery, partnership reviews, renewal conversations). You translate insights from calls, customer data, and frontline feedback into practical, repeatable programs that drive consistent execution. • 🧑‍🏫 New Hire Onboarding: Near-term, you own onboarding for our Customer Success Managers , Implementation Specialists, and our Professional Services team, building on our role- and segment-specific tracks to accelerate time-to-value. Over time, we anticipate our onboarding tracks willto better support our Contract Management and Supporfunctiont as well. Through program development,you simplify and prioritize what new hires need to know, ensuring they’re ready to lead customer conversations with confidence. • 💻 Systems & Tools: You manage enablement systems (LMS, content hubs, call libraries) to make resources easy to access and apply in the field. You bring perspective on how AI-enabled tools can reinforce learning and support real-time customer interactions. • 🚀 Scaling Impact: You thrive in dynamic, high-growth SaaS environments. You’ve supported CS organizations at scale and know how to reinforce skills and behaviors over time (certifications, peer learning, scenario practice) to ensure programs stick. • 📈 Impact Measurement: You partner with CS Ops to measure program effectiveness. You go beyond activity tracking to link enablement to business outcomes like faster ramp, improved NRR, and higher expansion rates. You iterate programs based on both data and observation. • 👷 Program Execution: You are organized, detail-oriented, and comfortable managing multiple initiatives concurrently. You balance strategic program design with rolling up your sleeves to facilitate sessions, deliver training, and embed new practices in the field. Out of Scope: To set expectations clearly: • Technical Enablement / Ashby Product: While you will partner with Product, SE, and CS leadership to ensure teams have the product knowledge they need, you will not own deep technical enablement. • Competitive Intelligence: You’ll collaborate with PMM and Sales Enablement on competitive readiness, but you are not expected to be the subject matter expert in this area. You Might Love This Role If: • You’re passionate about enabling Customer Success Teams to deliver business outcomes via their expertise • You love building scalable programs that directly impact retention and expansion outcomes • You thrive in cross-functional work and enjoy building trust with leaders and customer-facing teams • You’re known for operational excellence, clarity, and execution • You’re energized by both designing programs and reinforcing them with Customer Success Teams This Role Might Not Be for You If: • You prefer focusing only on training content without engaging in reinforcement or measurement • You’re uncomfortable facilitating live sessions or role plays with CSMs and leaders • You need a large team or mature infrastructure to be effective—this is a lean, hands-on role • You dislike documenting and systematizing—Ashby is an async-first culture that values clarity in writing Our Philosophy Here are a few key points (relevant to the go-to-market side) that should give you an idea of what it is like to work with us: • We believe a highly differentiated product is a lot easier to sell, so we continually invest in product innovation and this has proven to be a sustainable source of competitive differentiation • We always aim to show up well prepared and with deep industry acumen. This caliber of customer experience is another way we differentiate. • We strongly believe that small teams with very talented people (and the right work environment) deliver much better performance than teams with large headcount. We hire and compensate accordingly. We value a strong sense of ownership, principled thinking over experience, and thoughtful communication (we put a lot of effort into using the right communication channels) - we’ll get into these and other values during the hiring process. Benefits • You’ll get the time to do things the right way; we put a lot of emphasis on high quality work and avoid quick hacks, but equally move with precision and urgency • Competitive compensation, including equity • 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. • Unlimited PTO with four weeks is recommended per year. • Twelve weeks of fully paid family leave in the US. We plan to expand this to employees in other countries as situations arise. • Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! • $100/month education budget with more expensive items (like conferences) covered with manager approval. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities. Ashby is committed to a fair and transparent hiring process. We confirm that this advertisement is for an active, existing vacancy within our organization. Please be advised that we may use artificial intelligence-driven tools to assist our recruitment team in screening, assessing, and selecting candidates for this position.

Manage mid-market customer portfolio to drive adoption, retention, and growth through strategic guidance and product expertise. | Requires 2+ years in B2B SaaS customer success managing mid-market accounts with strong communication and technical skills. | About this Role Hi, I’m Denise, and I’m the Head of High-Touch (Mid-Market) Customer Success at Ashby. Our team is passionate about shaping and scaling an exceptional customer experience for our high-touch customer segment, which primarily supports mid-market and growth-stage organizations. I’m excited to be hiring our next CSM as we continue expanding globally. As a member of our Customer Success team, you will help us continue to grow our High-Touch Customer Success function. In this role, you’ll partner closely with customers to drive adoption, deliver strategic guidance, conduct product trainings and partnership reviews, and identify opportunities for expanded use cases and long-term value realization. You’ll also collaborate with a talented group of CSMs across the High-Touch team to continuously evolve how we support companies ranging from high-growth startups to public enterprises. Ashby is designed to be powerful and flexible, allowing customers to tailor the platform to their unique hiring processes and workflows. Because of this, there is a lot to learn. You will become both a product and domain expert, enabling customers to make the most of Ashby and drive hiring excellence across their organizations. Role Requirements: • You have a strong track record of Customer Success experience in B2B SaaS (at least two years), supporting customers through the adoption and long-term optimization of complex technologies. You enjoy building trusted partnerships with customers and helping them realize measurable value throughout the customer lifecycle. • You have experience managing a portfolio of approximately 60 mid-market customers with over $1.5M in total ARR. You’re comfortable balancing proactive engagement across a broad book of business while building strong relationships with a diverse set of stakeholders to drive adoption, retention, and growth. • You have experience partnering cross-functionally with teams such as Sales, Marketing, Product, Support, and Operations to advocate for customer needs and deliver a seamless customer experience. • You enjoy becoming a product expert and have demonstrated this in previous Customer Success roles. You create “aha” moments by tailoring trainings, workflow guidance, and strategic recommendations to each customer’s unique goals and challenges. • You’ve worked with technically complex products and bring strong curiosity and problem-solving skills to understanding how systems, workflows, and integrations operate in practice You Should Apply If: • 📣 You demonstrate mastery of clear communication. You ask questions with precision and can explain complex concepts in simple terms. • 🎧 You are a great listener. You see your role as providing the voice of the customer to internal stakeholders so we can ensure that our product roadmap continues delivering value. • 📊You enjoy working with a larger book of varied customers, and can effectively prioritise your time to make the biggest impact. • 🧩 You’re energized by learning and supporting a complex product. You enjoy diving deep into technical details, navigating advanced configurations, and data workflows, and you enjoy helping customers make sense of them. • 🧑‍🏫 You love to teach. Whether it’s a complex report to a very tenured data analyst, or a workflow to a brand new recruiter, who is new to SaaS tools, you see every teaching moment as an opportunity. • 🔍 Your peers describe you as detail oriented. You obsess over sending crisp follow-up emails, on time. You take pride in internal operations, like real-time CRM updates. • ⚡️ You move fast. You leverage tools/technology to maximize your time. You are at home managing a wide range of customers, and prioritizing effectively. • 🗺️ You're energized by an ever-improving work environment. Our team is growing, and continually iterating on processes - we live by our Operating Principle of "Implement Continuous Improvement" • 📊 You are always looking for ways to improve your work through data. Why you shouldn’t apply: • You thrive with a smaller, more focused book of customers,. Our High-Touch CSMs typically manage a book of 60+ customers, balancing personalized relationships with efficient, scalable support. • You're interested in managing customer accounts with well-defined touchpoints (rather than excited by the fluidity required of early stage CS work) • You shine as an exclusively commercial CSM, motivated by variable compensation. While our team's north star metric is revenue retention, we focus on adoption and engagement as our leading indicators. For renewal negotiation and upsell, we have a lovely team of Contract Managers. As such, this role does not currently include variable pay. • You’re afraid of rolling up your sleeves. If the idea of getting in the weeds with a customer about the nuance between a time in process report and a time to hire report feels too granular, or project managing a workflow change for offer approvals feels “beneath you”, this job isn’t going to be for you. About Ashby We’re building the next generation of enterprise software, and we’re starting with a suite of products that help talent leaders, recruiters, and hiring managers run their hiring process significantly better. Learn more on our website: https://www.ashbyhq.com/ We are well funded and backed by great investors, including Y Combinator, Elad Gil and Lachy Groom. We have thousands of amazing customers including Snowflake, OpenAI, Shopify, Ramp, Notion, and Zapier (and many others who we cannot name!). Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet. In short, it's the perfect time to join! 🚀 Interview Process Our interview process is thorough - we aim to ensure each person that joins the team is the right fit for Ashby and will provide ample information for you to assess if Ashby is the right fit for you. The process for this role is as follows: • Intro Call with Ashby Recruiting - 30 Minutes • Hiring Manager Interview - 45 Minutes • Mock Customer Call - 45 Minutes • Final Panel Interview - 2 hours Benefits • You’ll get the time to do things the right way; we put a lot of emphasis on high quality work and avoid quick hacks as much as possible. • 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby - do it when you feel financially comfortable. • Unlimited PTO with four weeks is recommended per year. Expect “Vacation?” in our one-on-one agenda until you start taking it 😅 • Twelve weeks of fully paid family leave in the US. We plan to expand this to employees in other countries as situations arise. • Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! • $100/month education budget with more expensive items (like conferences) covered with manager approval. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.

Design and build end-to-end product features with ownership over product specs, design, and implementation. | Senior-level engineers comfortable with product ambiguity, cross-stack development, and ownership of complex projects. | Hi 👋🏾 I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for a versatile, persistent product engineer who’s not afraid to set up reusable building blocks across the stack and advocate for the time and space to do so. At Ashby, all our engineers ship features end-to-end at a high pace. Example is the best leadership. We’ll give you the room to do your best work, and you'll be our guide! If that speaks to you, read on. What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature. We 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, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet. You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner). About the Role and How We Work Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software. I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings. I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation. Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey. At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have: • Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building." • Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it. • Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features. What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back. Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s 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 want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are! Why You Should or Shouldn’t Apply Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for: • You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team). • You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems. • You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team. • You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it). • You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here! • You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc. Put another way, you shouldn’t apply if: • To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off. • You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges. • You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs. • You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront. • You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them. • You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited. Engineering Culture Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through: • Minimal process with ownership over decisions normally made by product and design • Natural collaboration and deliberate communication • Investing in tools and abstractions that give us leverage • Putting effort into building a diverse team Minimal Process & Lots of Ownership The best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise. Traditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive. Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here). To drive it home, here's a recent calendar of an engineer who has been with us for over 4 years. ~34 hours of focus time, 2.5h of interviews, and 3.5 hours of meetings: We also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region. Increase Leverage, not Team Size We built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in: • Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾. • Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below). • AI-powered tooling. We think of AI as a way to automate the mundane parts of building and maintaining high-quality software. We use a combination of third-party and internally built tools that, for instance, auto-triage customer issues, suggest fixes, prototype ideas, generate production-ready code, and conduct code reviews. Engineers have an unlimited token budget (but are not measured on it). Here’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby: And a demo of one of these building blocks: Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. Today, 25% of engineers and 50% of our engineering leaders at Ashby are from underrepresented groups. We are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. Interview Process At Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises. Our interview process is three rounds: • Introduction call with Hiring Manager (15 to 30m, live) • A technical screen where we pair in our actual codebase (1h, live) • Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days) Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter. Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback! Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together. It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture. Technology Stack I’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Sergey). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅. Benefits • Competitive salary and equity. • 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. • Unlimited PTO, and we will encourage you to take it. • A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements. • Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! • $100/month education budget with more expensive items (like conferences) covered with manager approval. • If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us. Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.

Design and build end-to-end product features with ownership over product specs, design, and implementation. | Senior-level software engineer comfortable with full-stack development, product ambiguity, and ownership of projects. | Hi 👋🏾 I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for a versatile, persistent product engineer who’s not afraid to set up reusable building blocks across the stack and advocate for the time and space to do so. At Ashby, all our engineers ship features end-to-end at a high pace. Example is the best leadership. We’ll give you the room to do your best work, and you'll be our guide! If that speaks to you, read on. What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature. We 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, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet. You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner). About the Role and How We Work Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software. I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings. I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation. Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey. At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have: • Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building." • Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it. • Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features. What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back. Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s 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 want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are! Why You Should or Shouldn’t Apply Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for: • You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team). • You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems. • You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team. • You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it). • You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here! • You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc. Put another way, you shouldn’t apply if: • To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off. • You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges. • You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs. • You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront. • You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them. • You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited. Engineering Culture Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through: • Minimal process with ownership over decisions normally made by product and design • Natural collaboration and deliberate communication • Investing in tools and abstractions that give us leverage • Putting effort into building a diverse team Minimal Process & Lots of Ownership The best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise. Traditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive. Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here). To drive it home, here's a recent calendar of an engineer who has been with us for over 4 years. ~34 hours of focus time, 2.5h of interviews, and 3.5 hours of meetings: We also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region. Increase Leverage, not Team Size We built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in: • Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾. • Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below). • AI-powered tooling. We think of AI as a way to automate the mundane parts of building and maintaining high-quality software. We use a combination of third-party and internally built tools that, for instance, auto-triage customer issues, suggest fixes, prototype ideas, generate production-ready code, and conduct code reviews. Engineers have an unlimited token budget (but are not measured on it). Here’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby: And a demo of one of these building blocks: Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. Today, 25% of engineers and 50% of our engineering leaders at Ashby are from underrepresented groups. We are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. Interview Process At Ashby, our team and interview process want to help you show your best self. We’ll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises. Our interview process is three rounds: • Introduction call with Hiring Manager (15 to 30m, live) • A technical screen where we pair in our actual codebase (1h, live) • Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days) Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter. Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback! Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together. It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture. Technology Stack I’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Sergey). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅. Benefits • Competitive salary and equity. • 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. • Unlimited PTO, and we will encourage you to take it. • A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements. • Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! • $100/month education budget with more expensive items (like conferences) covered with manager approval. • If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us. Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.

Design and build product features end-to-end with ownership over product specs, design, and implementation. | Senior-level software engineer comfortable with full-stack development, product ownership, and working in a minimal process, high ownership environment. | Hi 👋🏾 I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious full-stack engineer who is laser-focused on solving customer problems and making the right long-term investments to solve them not only today but in our future features and products. What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature. We 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, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet. You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner). About the Role and How We Work Our engineering culture strives to recreate the environments where we did our best work as ICs - where we had the ownership and agency to impact our users with creative and innovative software. I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings. I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation. Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning. In those companies, I felt like a JIRA jockey. At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have: Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem I talk about in "What We're Building." Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it. Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features. What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back. Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. 🥵 TA software didn’t help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s 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 want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are! Why You Should or Shouldn’t Apply Software engineers come in many flavors, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for: You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team). You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems. You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team. You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it). You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here! You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc. Put another way, you shouldn’t apply if: You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges. You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs. You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront. You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them. You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited. To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off. Engineering Culture Our engineering culture is motivated by Benji’s (my Co-founder and CEO) and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through: Minimal process with ownership over decisions normally made by product and design Natural collaboration and deliberate communication Investing in tools and abstractions that give us leverage Putting effort into building a diverse team Minimal Process & Lots of Ownership The best engineers we’ve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise. Traditional product-development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But, consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). It’s a new level of ownership for many engineers, but we’d rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive. Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here). To drive it home, here's a recent calendar of an engineer who has been with us for over 4 years: We also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region. Increase Leverage, not Team Size We built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We’ve done this through investment in: Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience 💪🏾. Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app (short video below). Here’s an impromptu quote from Arjun in our company Slack of what it’s like to build a feature at Ashby: And a demo of one of these building blocks: Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non-diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. Today, 21% of engineers at Ashby are from underrepresented groups. It’s not great, and we are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together. It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture. Technology Stack I’m sharing our tech stack with the caveat that we don’t require previous experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Sergey). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile 😅. Benefits Competitive salary and equity. 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. Unlimited PTO, and we will encourage you to take it. A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements. Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! $100/month education budget with more expensive items (like conferences) covered with manager approval. If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us. Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.

Lead and manage the revenue enablement team to develop and execute programs that improve sales and customer success team performance, onboarding, and adoption of frameworks to drive revenue growth and retention. | Proven experience leading enablement teams in SaaS companies scaling to $100M+ ARR, strong cross-functional partnership skills, program development expertise, LMS management, and ability to measure enablement impact. | About Ashby • We’re building the next generation of enterprise software, starting with products that help talent leaders, recruiters, and managers unlock hiring excellence • Raised our Series D earlier this year, and we’re growing ARR >100% YoY • Have over 3,000 amazing customers including OpenAI, Ramp, Deliveroo, Notion and Reddit • Built multiple products to win both land-and-expand and material new business deals • Rapidly moving up-market with no signs of slowing down • Implemented AI throughout the platform • Known for our pace of innovation and advanced analytics About this role As the Head of Revenue Enablement, you will be the business partner to our VP Sales and VP Customer Success to ensure consistently high caliber execution to support revenue growth and customer retention. You will play a pivotal role in developing and, with your team, executing programs that foster excellence in our Sales and CS organizations. Success in this hands-on leadership role is measured by the overall effectiveness of our customer-facing Sales & CS teams — this includes but isn’t limited to: fast time-to-ramp for new hires, consistent adoption of our frameworks and methodologies, strategic business partnership with GTM leadership and ultimately delightful customer experiences that drive growth. In 2026, Revenue Enablement will be a team of three. You will lead and manage two practitioners, one for each Sales and Customer Success. You will operate in a player-coach capacity, with an eagerness to roll up your sleeves to support program delivery and ensure execution against company priorities. Sales & CS will be close to 200 people by the end of next year, and so you and your team will have a high impact role on Ashby’s growth trajectory to $100M ARR and well beyond. Role Scope & Requirements • 🤝 Business Partnership: You are innately curious about the work and priorities of our Sales and CS Leaders. You ask the hard questions to understand the nuances of the business to identify how you can have the greatest impact. You partner effectively with stakeholders including Product Marketing, Revenue Operations and Senior Leadership to deliver comprehensive programs in support of our go-to-market strategy. • ⚙️ Program Development: You understand business needs and identify gaps in knowledge or skills. You’re a quick learner who is at home creating and curating materials for go-to-market teams. You collect disparate information through quantitative and qualitative approaches (e.g. interviews, internal documentation, and recorded customer calls) to create tailored learning paths that drive behavior change. You actively elicit feedback for program improvement. • 🧑‍🏫 New Hire Onboarding: You have experience developing onboarding programs for GTM teams that ensure new hires ramp quickly. You have a knack for simplification and prioritization—sometimes less is more. You can be the master architect for role and segment specific onboarding tracks. • 💻 Systems: You’ve managed an LMS and have perspective on which software capabilities best support learning outcomes and in-field execution. You closely follow AI-native enablement vendors and can separate marketing fluff from powerful new features. • 🚀 Scaling: You’ve helped a SaaS company scale to over $100M ARR where you lead an enablement team. You thrive in a high growth, dynamic environment and are familiar with reinforcement learning techniques to support organizations of this scale. • 📈 Impact: You use both analytics and observations to assess the impact of your enablement programs. You have a proven track record of achieving measurable improvements in team performance and productivity. You iterate on your approach based on results, evolving company goals, and changing market conditions. • 👷 Team Management: You are highly organized and have managed an enablement team who deliver multiple projects concurrently. You’re an “in the details” leader who ensures the success of your team’s work. You know when to advocate for additional resources to maximize impact. Out of Scope Since every organization thinks about Revenue Enablement a little bit differently, we intend to be clear about what we currently view as out of scope for this role, while also acknowledging that things may evolve, and your perspective also counts. • Technical Enablement / Ashby Product: We have an expansive product surface area as a full-suite talent acquisition platform. Our Support, CS and Solutions Engineering teams especially need to develop deep product acumen to be effective in their jobs. We anticipate you being a partner to other owners of Technical Enablement but it is not your primary responsibility. • Competitive Intelligence: You would not be expected to become the subject matter expert on our competitive landscape, but would partner with our PMM and Solutions Engineering teams on the creation of competitive enablement programs, leveraging existing knowledge and frameworks. You Might Love This Role If • You have a desire to build a world-class GTM practice. • You’re a systems thinker with experience scaling enablement programs. • Your peers would describe you as operationally excellent. • You excel in cross-functional collaboration. This Role Might Not Be for You If • You are uncomfortable rolling up your sleeves and executing. This is not a role for hands-off delegators. • You prefer working independently vs as part of an interdisciplinary team. • You love meetings! We’re a documentation first, async friendly team that values written communication as a core mode of communication. (We’re not anti-meeting but highly value the written word). Our Philosophy Here are a few points relevant to go-to-market that should give you an idea of what it is like to work with us: • We believe a highly differentiated product is a lot easier to sell, so we continually invest in product innovation and this has proven to be a sustainable source of competitive differentiation • We always aim to show up well prepared and with deep industry acumen. This caliber of customer experience is another way we differentiate. • We strongly believe that small teams with very talented people (and the right work environment) deliver much better performance than teams with large headcount. We hire and compensate accordingly. We value a strong sense of ownership, principled thinking over experience, and thoughtful communication (we put a lot of effort into using the right communication channels) - we’ll get into these and other values during the hiring process. Benefits • You’ll get the time to do things the right way; we put a lot of emphasis on high quality work and avoid quick hacks, but equally move with precision and urgency • Competitive compensation, including equity • 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby —do it when you feel financially comfortable. • Unlimited PTO with four weeks is recommended per year. • Twelve weeks of fully paid family leave in the US. We plan to expand this to employees in other countries as situations arise. • Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! • $100/month education budget with more expensive items (like conferences) covered with manager approval. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.

Lead and grow a team of Customer Success Managers to enhance onboarding, adoption, and long-term customer partnerships while driving process improvements and advocating for product enhancements. | Experience leading Customer Success teams in a B2B SaaS environment, expertise in customer lifecycle management, operational process improvement skills, strong cross-functional collaboration, and data-driven problem solving. | Head of High Touch Customer Success 👋 Hi, I’m Casey — Head of Dedicated Customer Success at Ashby; I look after our upmarket customers in the Strategic and High Touch segments. One of my favorite aspects of Ashby is our operating principle of Continuous Improvement. Coupled with our principle of caring deeply about our customers, we often find ourselves wondering ‘what is a better way to accomplish this’. That’s why I am thrilled to be hiring my backfill: the Head of High Touch Customer Success! In this role, you’ll have the opportunity to elevate the customer experience to the next level. You’ll join our Dedicated CSM leadership team, working alongside our Heads of Strategic and EMEA Customer Success, as well as leaders from our Startup CS, Support, Customer Education and Contract Management teams. About the Role As Head of High Touch Customer Success, you’ll play a critical role in ensuring our customers continue to have an exceptional experience with Ashby as we scale. You’ll grow a talented team of CSMs, lead the current Manager of High Touch Customer Success (a recent internal promotion), and drive the overall strategy and execution of our High Touch CS function. In this role, you will: • Lead and coach both the current Manager of High Touch CS and your own team of CSMs supporting customers across onboarding, adoption, and long-term partnership • Drive process improvements across the customer journey, with a focus on post-onboarding and adoption • Help evolve how we deliver consistent, high-quality customer experiences at scale • Serve as a key product advocate — partnering closely with internal teams to champion improvements that better support our upper mid-market and lower enterprise customers Role requirements: • Team Leadership & Coaching: You have experience leading and developing Customer Success Managers in a B2B SaaS environment. You know how to foster a culture of empathy, accountability, and continuous growth. • Customer Journey Expertise: You understand the customer lifecycle and have helped improve onboarding, adoption, and retention through thoughtful, repeatable approaches. • Operational Mindset: You’ve helped implement and improve team processes, and you bring a structured lens to scaling what works while staying adaptable. • Cross-functional Collaboration: You’re comfortable partnering with teams like Sales, Product, and Support to align around customer needs and elevate the experience. • Problem-Solving Orientation: You don’t rely on “what worked before” — you’re thoughtful, pragmatic, and eager to find solutions that fit the unique needs of your team and customers. • Data-Driven: You are comfortable using data and metrics to drive decision-making, continually improving both the team and customer experience. • Customer-First Thinking: You have a deep understanding of B2B customer needs and have a history of ensuring outstanding support experiences. • Lifecycle Awareness: You’re familiar with key stages like onboarding and adoption, and you’ve supported efforts that drive product engagement and help customers achieve their goals. You’ll Be a Great Fit If You: • 📣 You demonstrate clear communication. You ask clarifying questions with precision and can distill complex concepts into simple themes. • 🎧 You are a great listener. You see your role as 1) Advocate for the Customer Success Team as well as 2) Voice of the customer to internal stakeholders so we can ensure that our product roadmap continues to evolve. • 📈 You are a problem solver. You thrive at solving complex challenges with innovative, scalable solutions. • ⚡️You know process matters. You are eager to improve processes and workflows to enhance efficiency and efficacy. • 🔍 Your peers describe you as detail oriented. You take pride in internal operations. • ⚙️ You’re an advocate for the team. We’ll be looking for your help when it comes to defining resourcing and headcount planning. • 🧑‍🏫 You love to coach. You see every teaching moment as an opportunity and are excited to help teams grow. You Might Not Be a Fit If: • You prefer an in-person role over remote. • You’re not eager to roll up your sleeves and get into the weeds (e.g. call shadowing isn’t interesting to you). • You are accustomed to defining ideas and strategies, yet not responsible for their execution. • You thrive in environments where you lead a simple, established product rather than a dynamic, evolving one. • You prefer exclusively to build (rather than build, iterate, optimize) Our Philosophy Here are a few key points (relevant to the go-to-market side) that should give you an idea of what it is like to work with us: • We spend a lot of time building best-in-class products since we believe a highly differentiated product is a lot easier to sell. • We want to offer deep expertise whenever we interact with prospects and customers. • We strongly believe that small teams with very talented people (and the right work environment) deliver much better performance than teams with large headcount. We hire and compensate accordingly. We value a strong sense of ownership, principled thinking over experience, and thoughtful communication (we put a lot of effort into using the right communication channels) - we’ll get into these and other values during the hiring process. The Interview At Ashby, our team and interview process want to help you show your best self. Our interview process is structured to get to know you and your career as well as empower you with insight into our key focus areas. Here is the process in its entirety: • 30 min - Recruiter Screen • 60 min - Hiring Manager Interview with Global Head of Dedicated CS • 60 min Presentation & Interview with our Manager of High Touch, Head of Startup & Head of Strategic • Final Round: • 30 min - Interview with VP of Customer Success • 30 min - Interview with CEO • 10 min - Closing Questions with Hiring Manager Benefits • You’ll get the time to do things the right way; we put a lot of emphasis on high quality work and avoid quick hacks as much as possible. • You get to represent a product that our prospects & customers are truly excited about. • 10-year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby — do it when you feel financially comfortable. • Unlimited PTO with four weeks is recommended per year. Expect “Vacation?” in our one-on-one agenda until you start taking it 😅 • Twelve weeks of fully paid family leave in the US. We plan to expand this to employees in other countries as situations arise. • $100/month education budget with more expensive items (like conferences) covered with manager approval • Extended health benefits for you and your dependents (subject to availability with our Employer of Record) • Generous equipment, software, and office furniture budget. Get what you need to be happy and productive! Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.