Hi I'm Abhik, Ashby's Co-Founder and VP of Engineering.
We're looking for a versatile, persistent product engineer who's not afraid to set up reusable building blocks across the stack and advocate for the time and space to do so.
What Ashby gives you in return is the best of both early and growth-stage environments.
While also the product-market fit and scale of a growth-stage startup: 100,000+ weekly active users who depend on your software and eagerly await your next feature.We have notable customers like Notion, Linear, Shopify, and Snowflake.
You've probably seen this role posted before, and it's because we're always expanding the team (we're on track to double Engineering this year).
We're bubbling with ideas for how to support Talent Acquisition with software, and we recently launched Talent Management products to expand our total addressable market and become a company worth $60B+.
About The Role And How We WorkOur engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software.I started my career building software for artists in the Visual Effects industry.
It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer.
No daily stand-ups, no t-shirt sizing, no planning meetings.I studied computer science to solve problems, not tickets, and this felt exactly like that.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer's force of will and ability to push back against culture (rather than any encouragement from it).
Engineering was narrowed to implementation and delivery,



partly due to the influence of other departments and partly due to the influx of "Agile" processes like sprint planning.
In those companies, I felt like a JIRA jockey.As a Product Engineer, you'll take ownership over a large portion of one of our products and own projects end-to-end (wearing hats traditionally worn by product and design).
To ground it with examples, product engineers at Ashby have:This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app.
Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend.
Many user-facing features use it.This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features.When we started Ashby, we saw the opposite with Talent Acquisition (TA) 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.
As we've set the standard for excellence in TA software, HR teams have pulled us into solving their problems in areas like onboarding and performance management.You do what's necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure.
We'll provide a supportive environment to do it successfully (e.You've tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two.
You know how to strike the right balance between speed and quality.
We took four years to launch publicly because convincing customers to switch required a high-quality product.
To thrive (and level up), you'll need to be open to feedback (and we give lots of it).
You'll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line.
The nature of software is that you can often automate or abstract what would be tedious, time-consuming work.
Put Another Way, You Shouldn't Apply IfTo you, a tech lead, staff, or principal engineer is someone who spends m

📌 Senior/Staff Software Engineer, Product (La Coruña)
🏢 Ashby
📍 La Coruña