Skip to content
Ashby

Engineering Manager - Canada

Remote - Canada; Calgary; Vancouver; TorontoRemote · Canada
Manager · FullTime · Engineering
POSTED 13 NOV 2025VERIFIED 1D AGO
Apply Ask
Role
365 days opentrue age
Past the 13d median close
Posted 13 Nov 2025 · n=11
Payats field
CAD 250k–370kposted
▲ +51% vs market median CAD 206k
CAD 193kCAD 370k
Market p25–p75
CAD 193k–CAD 237k
Vancouver · n=4 · 365d to 4 Nov
CompanyAshby →
72open roles
Opened · 30d
+2
Closed · 30d
−9
12d of snapshots · 30d window
Market
1,971open · Manager Engineering management
Opened · 7d
+1759% of open
All engineering management
2,293open
All tracked boards · live 14 Nov · n=1,971
Snowflake

Hi 👋🏾, I’m Abhik, Ashby’s Co-Founder and CTO. We’re looking for a great (former) engineer who built impressive products and now builds teams of great engineers. Ashby’s success and ambition mean we’re doubling the Engineering team in the next year, and we need your experience and leadership to do it thoughtfully.

Our product and growth are exceptional. Ashby All-in-One is powerful, easy to use, and replaces several venture-backed companies' worth of products (often with a better experience). We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway.

A big part of our secret sauce is how we run Engineering. We achieve incredible speed and quality by discarding many industry norms and being optimistic about Engineers. We consider what makes exceptional Engineers exceptional, figure out how to hire them, and build an environment that gives them the freedom and agency to actually be exceptional. In other words, if engineers writing product specs, making product decisions, and not breaking down projects into individual tickets excites you, you’ve found the right place.

As an Engineering Manager, you’ll work closely with me, Ben, Colin, and your peers to build out the team and continue scaling this unique culture.

You’ll first do that through grassroots leadership. You’ll manage three to five Engineers and hire three to five more. They’ll cover multiple teams and a variety of specializations, from Product Engineers to Site Reliability Engineers to Design Engineers. Your day-to-day will include:

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

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

You’ll also propose and lead department and company-wide initiatives. Some examples:

Rethink how we (and the industry) do pull request reviews by aligning on goals with the team, sampling a set of PRs to understand how effective they are, and writing a proposal to the team about what we could change to speed up reviews while giving reviewers the time and space to give useful feedback.

Design and improve interviews based on candidate and team feedback. We pride ourselves on thoughtful interviews that simulate actually working with us!

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.

I’ll share more details once we meet.

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 (TA) 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 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. 🥵 TA software didn’t help.

Source · AshbyFirst seen 2 Nov1 editsOriginal ↗