European Principal Product Engineer — Own End-To-End Features

European Principal Product Engineer — Own End-To-End Features
Viseu
Viseu, Viseu District, Portugal

Principal Product Engineer, EU role at Ashby

2 days ago Be among the first 25 applicants

This range is provided by Ashby. Your actual pay will be based on your skills and experience — talk with your recruiter to learn more.

Hi I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious
- stack engineer who is
- focused on solving customer problems and making the right
- term investments to solve a class of problems. . . .

What Ashby gives you in return is the best of both early and
- stage environments. The agency and
- nonsense of a seed startup: you write product specs, make product and design decisions, and build in an
-
- meeting culture. While also the
- market fit and scale of a
- stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature.

We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are
-
- class among our peers: we have tens of millions in ARR, growing>



100% year over year, very low churn, and many years of runway. We’ll share more details once we meet.

You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).

About The Role And How We Work

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. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily
- ups, no
- 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 engineer’s 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. In those companies, I felt like a JIRA jockey.

About

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. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects
-
- 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
  - 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 As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.

Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. 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
- 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.