Senior Product Engineer
Posted Updated
Description
- At Ashby, all our engineers ship features end-to-end at a high pace
- 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
Benefits
- $100/month education budget with more expensive items (like conferences) covered with manager approval
- Unlimited PTO with four weeks recommended per year
- Twelve weeks of fully paid family leave
- 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
- Generous equipment, software, and office furniture budget
- 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
- You know how to strike the right balance between speed and quality
- You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure
- To thrive (and level up), you’ll need to be open to feedback (and we give lots of it)
- Ashby wasn’t built quickly
- Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc
- You are ambitious and always looking to improve your skills
- We’ll provide a supportive environment to do it successfully (e.g. , design system, SRE team)
- The nature of software is that you can often automate or abstract what would be tedious, time-consuming work
- You seek to create leverage in your work
- 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
- 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’re an excellent collaborator and communicator
- We took four years to launch publicly because convincing customers to switch required a high-quality product
- You’re not afraid to tackle any part of a technology stack
- 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
- For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past
- Clear and concise communication helps a lot here!
- You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two
- Ownership and freedom don’t mean you work in a vacuum
- 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
- 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!
Skills
Sign in to read and join the discussion.