The opportunity
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.
What you'll do
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.
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.
What they're looking for
- 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.
- 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.
