After applying I received an email claiming I did not meet some (or any) of the requirements to move forward. Having spent up to 8-10 years at previous companies, leadership experience with many successful projects, and decades working at non-consultancy companies, it became pretty obvious they just had some automated system scan it. I've worked as roles as a SWE, DevOps, DevEx, and done UI design, but I guess that's not enough?
With more than 25 years as a SWE, a resume reflecting my career (that they are expecting) would be multiple pages. That is the exact opposite expectation of any other U.S. based company. If that is the expectation, they need to clearly state that in their job postings.
We've reviewed many applications for this role, and here are the factors we typically look for when reviewing applications. While we can't specifically say which apply to your background, if these were present, they would strengthen your application. I hope you find them useful. If you're able to demonstrate all of these in the future, it would give you the best chance to move to a first call the next time you apply for an engineering role at Ashby.
More than 2 years of tenure at the same place - It's important for our Product engineers to have experienced the consequences of their decisions, iterated based on those decisions, and honed their judgment for future decisions. We believe the outcomes of the most challenging engineering work sometimes take years to shake out.
Experience outside of a consulting or agency environment - Our engineers make product decisions and are highly user-focused here at Ashby, We believe consulting environments do not encourage the strong sense of ownership that is needed to succeed here.
Experience in an early-stage startup that is fast-paced - For understandable reasons, the product cycle tends to be longer at larger companies and every feature released requires more research and consensus. At Ashby, one of our strengths in the market is how fast we ship features, and we do this by removing blockers from engineers and relying on them to maintain a solid pace. We hire engineers who have proven they can thrive in that environment.
Description of individual contributions that is specific - This is an individual contributor role, and while we love hiring people who have leadership experience, we need to see sufficiently specific depiction of what you've done personally to assess the impact of it. Resumes with vague verbiage, such as "achieved performance improvements" are difficult to assess. In that example, we would need an extra line explaining exactly how you did that.
Sufficient breadth in achievements and responsibilities - We value versatility in engineers, and prefer hiring generalists who can do a bit of design, a bit of infrastructure, improve DevEx, track metrics, etc. (i.e. wear many hats!). If your entire experience has been within a specialization (frontend, backend, DevOps, etc) it will appear less of a fit compared to a more flexible profile.
The following metrics were computed from 2 interview experiences for the Ashby Senior Software Engineer role in United States.
Ashby's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Ashby's Senior Software Engineer interview process in United States.