Senior Product Engineer - Americas

About The Role And How We Work

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. At Ashby, we're building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way.

What You'll Do

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.

Examples of what product engineers at Ashby have built:

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

What We're Building

We saw that Talent Acquisition software was holding recruiting teams back. Scheduling a final round is an excellent example. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform "Calendar Tetris" to find who is available to interview the candidate, schedule on the earliest date possible, and make any last-minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others.

We built and continue to build Ashby to give TA teams the highest standard of tooling—software that's intelligent and powerful, that provides insights into where they're failing and automates or simplifies many of the tasks they're underwater with.

You Should Apply If

• 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.
• 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. Ashby wasn't built quickly—we took four years to launch publicly—but we still move with urgency.
• You are ambitious and always looking to improve your skills. To thrive (and level up), you'll need to be open to feedback.
• You're an excellent collaborator and communicator. Ownership and freedom don't mean you work in a vacuum.
• You seek to create leverage in your work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.

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. Our most tenured engineers spend most of their time building.
• 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.
• You only want to do exciting work. Customer issues and investigations are distributed across the team, including our high-level ICs.
• You can get lost in the details. You like everything to be planned upfront.
• 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. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.

Engineering Culture

Our engineering culture is motivated by the belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:

• Minimal process with ownership over decisions normally made by product and design
• Natural collaboration and deliberate communication
• Investing in tools and abstractions that give us leverage
• Putting effort into building a diverse team

At Ashby, every Engineer runs their project. Product 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. We rely on engineers, not process, to push information outward and pull folks in to help.

Our engineering team consists of lifelong learners who are talented but also humble and kind. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in