Hi Im

Abhik

, Ashby''s Co-Founder and VP of Engineering. Were 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.

If youve seen this role posted before, its because were always looking for incredible engineering talent to help build the future of Ashby, as we more than double our business year over year. So far weve hired 10 Product Engineers in 2025 (thats a 20% increase in our total engineering headcount from this one role in the first 4 months!)While also the product-market fit and scale of a growth-stage startup: thousands of daily users who depend on your software and eagerly await your next feature.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. 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 engineers 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. At Ashby, were building an environment that is optimistic about what engineers can own and achieve. As a Product Engineer, youll 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. 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. 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 Were BuildingTalent teams aspire to build a hiring process that identifies great candidates, moves them quickly through the interview process, and provides an excellent experience for the candidate. Ashby provides talent teams with intelligent and powerful software that provides insights into where theyre failing and automates or simplifies many of the tasks theyre underwater with. 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 youre looking for:You do whats necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. Youve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two.

Were 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.

We took four years to launch publicly because convincing customers to switch required a high-quality product. Youll 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!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. Were building a team of kind, collaborative folks. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You havent led or taken ownership of projects before.

Youre used to working with tech leads and taking on tasks distributed by them.We rely on engineers owning their projects, so we need engineers with that experience. 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, its 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!).