Hi I'm Abhik, Ashby's Co-Founder and VP of Engineering. As someone who could design and build software, this position is close to my heart. I always felt I had a unique perspective because I could play with design ideas and iterate in code. My ideas could start in Figma but then be grounded (or sometimes more creative) in code. My prototypes used presente logic and data. My changes cascaded throughout the app for comprehensive critique (thanks, React component system). But, every company made me pick one — I couldn't design and build. While Every Engineer Can Design And Build, You'll Tackle Our Most Challenging Design Problems And Help Others Improve Their Designs By Expanding And Enhancing Our In‐house Design System And Consulting On Bespoke Work. To Ground It With Examples, Engineers Who Can Design 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 build custom autocompletes. Helped another engineer improve their design's information hierarchy and scannability for viewing a candidate's assessments. These projects reflect what we're accomplishing at Ashby: improving the productivity of working professionals (starting with talent teams) with intelligent and powerful software. In many ways, spreadsheets set the bar here. We have notable customers like Notion, Linear, Shopify, and Snowflake. 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. 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. TA software didn't help. As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. 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. 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 with ownership over decisions normally made by product and design But, consistency comes at the expense of an engineer's time and freedom — both ingredients necessary to generate those magical outcomes. So, at Ashby, every Engineer runs their project. 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. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in To drive it home,



here's a recent calendar of an engineer who has been with us for over 4 years. You also have a small budget to meet up with folks in your city/region. Increase Leverage, not Team Size We Built Ashby With The Quality, Breadth, And Depth That Many Customers Would Expect From Much Larger Teams Over Larger Time Scales. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Having seen my mother and partner build their careers as minority women in non‐diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. It's not great, and we are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. We'll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. Three non‐coding interviews that focus on product thinking, technical design, and infrastructure (3 h 15 min, live can be split across multiple days) It's a team effort to get you successfully onboarded; The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture. Technology Stack We are sharing our tech stack with the caveat that we don't require previous experience in it (but a love of typed languages is helpful ): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. When they joined Ashby, many of our engineers switched from other languages like Swift and Kotlin (Ben), platforms like iOS (Tom) and Windows (Sergey). Yo

📌 Staff Design Engineer (Barcelona)
🏢 Ashby
📍 Barcelona