For companies:
For professionals:
For everyone:
For developers:
Responsibilities
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.What Ashby gives you in return is the best of both early and growth-stage environments.At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. 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.Designed and built automated interview scheduling.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.Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby.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 studied computer science to solve problems, not tickets.At Ashby, we’re building an environment that embraces innovative engineers, and often stays out of their way.About the Role and How We WorkOur 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.As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end-to-end.Product engineers at Ashby have designed and built features across scheduling, filtering/SQL architecture, and completing signing offers in Ashby.What We’re BuildingWe built and continue to build Ashby to give TA teams the highest standard of tooling: software that’s intelligent and powerful, provides insights into where they’re failing, and automates or simplifies many tasks they’re underwater with.Why You Should or Shouldn’t ApplyHere 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’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.You are ambitious and always looking to improve your skills.You’re an excellent collaborator and communicator.You seek to create leverage in your work.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.You need company-driven process and structure to get your projects across the finish line.You only want to do exciting work.You can get lost in the details.You haven’t led or taken ownership of projects before.You want to mentor earlier-career engineers.Engineering CultureOur engineering culture is motivated by Benji’s and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!).Minimal process with ownership over decisions normally made by product and designNatural collaboration and deliberate communicationInvesting in tools and abstractions that give us leveragePutting effort into building a diverse teamMinimal Process & Lots of OwnershipProduct 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.Collaboration is Natural & Communication is DeliberateFocus time is something that we hold sacred, and engineers are in <2h meetings per week.We also meet in person at least twice a year, once as a department and once as a company.Increase Leverage, not Team SizeWe’re built with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales.Great developer tooling.Building blocks to create powerful and customizable products fast.AI-powered tooling.Put Effort into DiversityWe are taking conscious steps to improve diversity, including sourcing diverse candidates and providing generous paid family leave.Interview ProcessThere 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 First Three Months at AshbyYour dev environment is set up with a single script. You push your first product change on day one, then spend the rest of your time shipping product changes to tour the codebase and best practices.Your manager will do a 30, 60, and 90-day review. You’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help.Technology StackTypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.BenefitsCompetitive salary and equity.10-year exercise window for stock options.Unlimited PTO, and we will encourage you to take it.A minimum of 12 weeks of fully paid parental leave.Generous equipment, software, and office furniture budget.$100/month education budget.If you’re in the US, top-tier health insurance with 100% of premiums covered by Ashby; in other countries, high-quality supplemental health insurance fully covered by us.Compensation Range: CA$195K - CA$248K
This job post is closed.