As stated here, first round is with a technical recruiter -- asking more or less if you can survive a startup and ownership over something
Second round is with an engineer, doing basically the same thing. Talking about projects, things of that nature. An interesting thing about this is the feedback provided for myself was that the interviewer felt it was hard to get information out of me. In a sense that's true, but you're always trying to gauge what the interviewers acceptable answers are.
What I mean by this is, the interviews become a game of cat and mouse of "saying the right thing" and you need to constantly adjust to "I did the whole project" and "Here's what I think you want me to say" -- and you know that saying the wrong thing is immediate rejection and you don't want to get lost in technical implementation details in a 20 minute conversation
Anyway, I passed to the coding round with the VP of engineering, the task is to debug and implement some new feature. In my case, filtering on some report. I'll say it was "fine" I passed the interview and finished the code but was ultimately rejected for "Thinking too hard" as in, taking some time to walk myself through the problem after some prompting from the VP.
It's a funny balance between communicating your thoughts, constructing the mental model of the code in your head, and answering the interviewer's question. There's a final bit at the end where the VP asks you a bit about why you think they architected the code this way (a big monorepo of everything and a bajillion layers of abstraction with custom queries) and again, the true exercise here is stroking the VP's ego a little bit to find why he built it this way, I felt I got asked this question rephrased multiple times as he didn't like my initial answers (because it's hard to think on the spot why you'd do it this way) as this small change to filtering requires in totality a change in 15 or so custom SQL queries on various Query Types. So there's a little bit of thinking on your feet here
So my advice:
To their credit, they did provide me a blurb on the "whys" which I do appreciate.
The following metrics were computed from 1 interview experience for the Ashby Product Software Engineer role in Vancouver, Canada.
Ashby's interview process for their Product Software Engineer roles in Vancouver, Canada is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Ashby's Product Software Engineer interview process in Vancouver, Canada.