Engineering Manager - EU

Ashby; Dublin; On-site; EUR 90,000 - 120,000; Full time

Job summary

Ashby in Europe is seeking an engineering manager to lead a growing team of engineers across Europe from its Dublin office. You will champion an ownership-driven culture, coach ICs, and help engineers take end-to-end ownership of their work while aligning with product and business goals.

You will balance technical leadership with people management, facilitate hiring, performance feedback, and scaling practices that enable fast, high-quality delivery in a fast-paced startup environment.

Qualifications

• Experience leading software engineering teams.
• Ability to coach engineers and ICs to own projects.
• Strong communication and stakeholder management.

Responsibilities

• Build and manage a high-performing engineering team in Europe.
• Drive product and technical decisions with ownership mindset.
• Foster a culture of ownership, accountability and collaboration.
• Balance hands-on coding with strategic leadership.

Skills

Engineering management

People leadership

Mentoring

Technical leadership

Job description

Hi I’m Colin, Director of Engineering, Europe. How do you feel about software engineers writing product specs, making product decisions, and not breaking down projects into individual tickets? If that sounds exciting (even if a bit scary), read on because I’m looking for an engineering manager to help us build a different type of engineering team and culture at Ashby.

To start, why do we need to be different? Time and again, I have witnessed engineers knowing what needs to be done yet being unable to get things done because of “the process” or because “more data is needed.” Some of the most effective projects have been skunkworks projects, where engineers have taken total ownership of a problem and driven it to completion. I want to normalize that at Ashby.

When we think about how these processes came about, we realize they carry a pessimistic mindset. They box people into smaller roles to minimize the chance of not meeting a certain standard. At Ashby. we’re building an environment that is optimistic about what engineers can own and achieve and embraces the innovative engineers (and frankly, often stays out of their way).

To accomplish this, our engineering leaders need to think deeply about individual performance, process, and culture - not running sprint planning or driving product and technical decisions. You’ll focus on building your team, their skills to thrive with the ownership they’re given, and an environment that empowers them to do their best work consistently, with little distraction. For junior EMs we try to stay within 6 direct reports. This enables them to spend time with our teams observing, correcting, praising, and, yes, coding. We like our managers to be hands‑on while also making sure they’re not on the critical path.

We’ve already gathered an experienced, talented, and collaborative team of 25+ engineers. You’ll help me manage the growing team of engineers in Europe.

In Addition To Working With Engineers You’ll Also Get To Work On Projects Yourselves. Some Examples Of Work Our Engineering Leaders Have Done

• Provide feedback on product and technical specs to help engineers identify where to cut scope or improve quality. You don’t make the final decisions, but you’ll influence and coach ICs to reach the right ones.
• Grow engineers to the point where they can take large, loosely defined projects, and deliver them with little intervention. They still ask for help when needed - the difference is that they’re driving.
• Jump into our systems and code to debug a customer issue, ship a small bug fix, or improve our developer experience. Engineering leaders at Ashby are great engineers and enjoy keeping their skills up‑to‑date (while staying off the critical path).
• Improve how we generate and simulate data in demo accounts. It’s a project off the critical path, but it helps you keep up‑to‑date on our codebase while immensely impacting the business, from Engineering to QA to Sales.

Why be a manager?

I had two experiences early in my career that set me on my path. I had a great manager who asked tonnes of questions about the decisions I was making and coached me without me realizing it. And I had a terrible manager - being told to work harder after a week of 3am finishes was not what I needed as a young engineer. The stark difference between these two experiences motivated me to become a manager: I wanted every engineer I worked with to have the support I had in the best case.

Since then, as I’ve learned more, I’ve realized that I love the kind of problems I get to solve as a manager. Deeply complex problems with long‑term impact both on the company and on people’s lives. One of my proudest achievements is creating a fully transparent pay system, and on the day it was revealed, everybody was happy with it. Nobody stormed out. By spending time thinking deeply about everybody’s pay and ensuring the mechanics of promotion were clear, I put the team in a place where they could see a peer was paid more than them, and it not be a problem.

Despite all this, I love being technical. I sometimes indulge myself and spend a morning writing some code to improve tests or provide better abstractions. If I couldn’t be a manager, I’d be super happy to be an IC.

Why You Should or Shouldn’t Apply

• You love being technical and can hold in-depth conversations with direct reports from infra to backend to frontend.
• You enjoy management problems. We want people who get excited about driving people to be their best, giving difficult feedback, and building systems that make this easier
• You hold your team to a high standard and don’t shy away from getting into the details and giving feedback, even to the best folks on your team.
• You are an excellent and empathetic communicator. Facilitating change at both an individual and organization level requires understanding how to navigate the beliefs, opinions, and past experiences of engineers and figuring out how to both convince them of a new way of doing things while also leaving yourself open to feedback.
• You know what exceptional engineers look like. You’ve thought deeply about what makes them tick, how to recruit them, and how to grow folks into them. I want to see depth here, the industry often regurgitates a vanilla description, but the reality is more nuanced.
• You’re good at thinking about product, business, and maybe even design, but you’re not interested in calling the shots and are more interested in building a team that can make the best decisions without you.
• You thrive in high‑trust, high‑autonomy environments. We're a young startup where leaders wear multiple hats, and you'll build your own (high-speed) on‑ramp through developing strong feedback loops.

Put Another Way, You Shouldn’t Apply If

• You don’t enjoy coding or don’t find time to stay up‑to‑date on technology.
• You’ve gotten into management because it was the only growth path available
• You want to make all the product decisions instead of empowering your team to make those calls.
• You're happy with a team of engineers that are predominantly early-career, mid-career, or don't thrive with ownership or autonomy. With enough guardrails, the team can get things done.
• A staff or principal engineer to you is someone who spends most of their time project managing or doing architecture reviews.
• You’re not optimistic or convinced that we can build a large engineering team that functions differently than the status quo. You think, at some size, common processes need to be implemented to ensure consistent product delivery (e.g., sprint planning, product managers writing in-depth specifications). You might not say it out loud, but you think, at some size, compromises have to be made for the sake of hiring numbers.

What We’re Building

Talent teams aspire to build a hiring process that identifies great candidates, moves them quickly through the interview process, and provides an excellent experience for the candidate. To accomplish this, recruiters perform thousands of daily tasks to coordinate and relay information between candidates, interviewers, and hiring managers. Teams struggle to keep up!

Scheduling a final round is an excellent example of our customers' challenges. A recruiter needs to collect availability from the candidate, identify potential interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and perform any last‑minute adjustments as availability changes. They must perform this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others.

Ashby provides talent teams with intelligent and powerful software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We put a lot of effort into designing products that are approachable to beginners but mastered and extended by power users. In many ways, spreadsheets set the bar here.

We have many customers, great revenue growth, years of runway, and amazing investors like YCombinator, Elad Gil, and Lachy Groom. I’ll share more once we meet.

Engineering Culture

Our engineering culture is motivated by Abhik and Benji’s (our co‑founders) belief that a small talented team, given the right environment, can build high‑quality software fast (and work regular hours!).

Collaboration is Natural, Communication is Deliber