Staff Software Engineer, Product

Senior Full Stack Engineer - AI Products 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. 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. 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. 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 did industry research, designed interfaces, and prototyped ideas. 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. 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). To ground it with examples, product engineers at Ashby have: 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. 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. 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. 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. Software Engineers Come In Many Flavors, Not All Of Which Fit Our Model. 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., You've tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. You know how to strike the right balance between speed and quality. We took four years to launch publicly because convincing customers to switch required a high‐quality product. To thrive (and level up), you'll need to be open to feedback (and we give lots of it). 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. The nature of software is that you can often automate or abstract what would be tedious, time‐consuming work. 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. Once you start implementation, it can be hard to take a step back and think about the project as a whole. 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. 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. 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. 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 We Built Ashby With The Quality, Breadth, And Depth That Many Customers Would Expect From Much Larger Teams Over Larger Time Scales. Each improvement to a common component cascades throughout our app (short video below). We'll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. Three non‐coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days) It's a team effort to get you successfully onboarded; 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). For folks on the team who switched, it's nice seeing changes hot reload versus waiting for XCode to compile . 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. For folks outside the US, it may be longer to be in line with regional requirements. Generous equipment, software, and office furniture budget. 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 Ashby. Mid‐Senior level. Full‐time. Engineering and Information Technology. Industries: Software Development. #