Ashby
Design Engineer, UK
How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Hi đđŸ Iâm Abhik, Ashby's Co-Founder and VP of Engineering. This role is close to my heart because, as someone who can both design and code, itâs where Iâve always done my best work, but also where I was seen as a rebel and an outsider. I want folks like me to feel at home at Ashby, and so I made Design Engineering a formal role and department that works closely with me. Our first hire was over five years ago, and weâre doubling the team from five to over ten in the next year.
This role truly expects you to design and code. Design Engineer at Ashby isnât just a Frontend Engineer with new branding, nor is it a Designer vibe coding prototypes. Combining excellence in both is where magic happens. I found that when I put my best effort into both the design and technical implementation of a feature, I had a nimbleness and creativity that was hard to achieve when I did only one or the other. For instance, the UX and UI I envisioned often influenced the data model's design and flexibility, while the understanding of technology's capabilities often simplified or improved the design. This role embraces that.
The Design Engineer Role Is More Common Today Than Five Years Ago, But I Believe Ashby Offers a Unique Opportunity That Few Can Match:
- This role has always had the commitment of both Benji (CEO & Co-Founder) and me: Iâve held the role, steadfastly championed it since we started hiring in 2020, and havenât diluted its responsibilities as weâve grown (in fact, weâve doubled down).
- You work on a product at scale, not at an early-stage startup struggling to find users and get feedback on what youâve designed and built. At Ashby, your work will touch over 100,000 weekly active users, millions of candidates per week, and notable customers like Notion, Linear, Shopify, and Snowflake. Youâll get to test out ideas with our own recruiting team and hiring managers who use Ashby every day (like me), and often hear customer feedback as early as the day you release.
In This Role, Youâll Work On Our Most Challenging Design Problems, Help Others Improve Their Designs By Expanding And Enhancing Our In-house Design System, And Consult On Bespoke Design Work Needed By Product Engineers. To Ground It With Examples, Design Engineers At Ashby Have:
- Redesigned our mobile web app by talking with customers who use it often, wireframing new flows, implementing its design system, and using it to make the wireframes a reality.
- Built a set of flexible, composable components in our design system that allow other engineers to easily build beautiful, consistent setup wizards across our product.
- Helped a Product Engineer improve the information hierarchy and scannability of their design for viewing a candidateâs assessments. Recruiters can quickly parse information and pick out anomalies.
Why You Shouldnât Apply
Design Engineers Come In Many Flavors, Not All Of Which Fit Our Model. Here Are Some Reasons You Might Not Enjoy The Role:
- You only want to work on design systems. While improving our design system is one of many responsibilities, you wonât be able to work on it exclusively.
- You like to do extensive research and user testing before implementation. The beauty of being part-Engineer is that you can build conviction by shipping to a subset of users (including our own team) and gathering feedback!
- You want everything to be perfect before it gets into a userâs hands. One of the drivers of our success is that we ship fast. That often means we donât agonize over every detail and instead iterate over time, often letting user feedback and business needs drive prioritization.
- You donât have excellent taste and execution in visual design. Design Engineers set the bar for visual design in our app and continually improve it, pushing its boundaries with each new feature or redesign.
- You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. Youâd rather focus on the design and technical details.
- You only want to do exciting work. Weâre building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.
Reasons to use Rodeo
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet â that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
It searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right â and where to focus when applying.
What Seniority/Level To Apply For
Weâve posted levels from Junior to Staff. The higher the level, the more experience and alignment with the role we expect when reviewing your application and while interviewing. Please apply to the one that sets the right expectations.
- Junior Design Engineer - You should have no more than 2 years of industry experience as a designer or engineer. We want to see projects (personal or professional) with at least a couple of users that showcase great visual taste and burgeoning talent in both UI/UX and Engineering.
- Design Engineer (This Posting) - This posting covers both Mid and Senior levels. You have 2+ years of continuous experience (e.g., internships donât count) as an Engineer or a Designer. You have good proficiency in both Design and Engineering, with exceptional proficiency in the discipline you practice full-time. Regardless of which discipline youâre coming from, we expect experience designing products and shipping code to hundreds of users (even if through side projects).
- Staff Design Engineer - Weâre looking for folks whoâve practiced our flavor of Design Engineering professionally. It may not be through a formal title, but youâve made major contributions to a design system and designed and implemented features for hundreds of users and iterated on them through user feedback.
Internally, we do not use these titles, but Engineers are leveled based on proficiency (which you can read about here).
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 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.
Get help with your application
Your very own career expert that helps elevate your application to the next level.
As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software thatâs 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 want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are!
Engineering Culture
Our Engineering Culture Is Motivated By Benjiâs (my Co-founder And CEO) And My Belief That a Small, Talented Team, Given The Right Environment, Can Build High-quality Software Fast (and Work Regular Hours!). We Do It Through:
Minimal Process & Lots of Ownership
The best engineers weâve worked with delivered reliably magical outcomes. They took customer problems and relentlessly drove them to solutions that were not only successful but often brilliant and creative. While they did this with minimal oversight, stakeholders were never in the dark as to what was going on, and no setback was a surprise.
Traditional product-development processes arenât meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineerâs skill. But, consistency comes at the expense of an engineerâs time and freedomâboth ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesnât give others the opportunity to practice the behaviors that made the best engineers the âbest.â
At Ashby, we want to build an environment that encourages every engineer to be their best. So, at Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end. We rely on engineers, not process, to push information outward to the relevant folks (e.g., Product Managers) and pull folks in to help (e.g., Designers, Infra). Itâs a new level of ownership for many engineers, but weâd rather an engineer fail a bit and coach up their skills than use process as a crutch. Not everyone succeeds in our culture, but those who do thrive.
Collaboration is Natural & Communication is Deliberate
Our engineering team consists of lifelong learners who are talented but also humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week (I wrote about it here).
To Drive It Home, Here's a Recent Calendar Of An Engineer Who Has Been With Us For Over 4 Years. ~34 Hours Of Focus Time, 2.5h Of Interviews, And
âIt took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what Iâve been looking for.â
Jessica, London
Skills