Ashby Software Engineer Interview Questions
& Process

I thought the interview process was pretty good overall. They gave me a lot of info so I knew what to expect. Everyone was nice and I enjoyed it. I got rejected at the technical assessment stage. They act like a pair programmer and code based on your instructions. My biggest tip is: DON'T try to understand the codebase, they want you to implement; focus on execution, not understanding. Go bottom-up and don't go too deep into the component chain. I tried to understand the code holistically, but that wasn't what they were looking for.

I got a standard rejection email after applying, which detailed what my resume supposedly lacked to move forward. It's pretty obvious that no actual person reviewed it, because I clearly meet and exceed all the requirements they mentioned. This seems to be a recurring issue with this company's hiring process, as many people have reported similar experiences, suggesting they don't read resumes. You should really pay attention to the feedback here; it's consistent, so something is definitely wrong. I won't be considering this company again because they seem to waste candidates' time.

I applied online for the "Engineer Who Can Design" position and had an initial chat with a co-founder about my past projects. My background is mostly in web and product engineering, but this role was heavily focused on design systems, which is an area I want to grow in. They told me afterwards that I might not be the best fit for this specific role and suggested I might be a better fit for their Product Engineer opening. I wasn't as keen on that role because it was more fullstack, so we wrapped up the conversation. It was a bit disappointing as I was really interested and they seem like a great company, but they were very polite about it. I'd suggest making sure you apply for the right opening and can explain why you're a good fit.