Staff Software Engineer, Product Engineering, EU

Ashby; A distancia; EUR 50.000 - 80.000; Jornada completa

Descripción de la vacante

A innovative tech startup in Madrid is looking for a Senior Full Stack Engineer focused on AI products. In this role, you will own significant portions of the product, work on innovative features, and engage deeply with both technical and product aspects. Ideal candidates will have strong full-stack development experience and be comfortable with ambiguity. The company offers competitive salary, unlimited PTO, and a culture that emphasizes ownership and minimal process, fostering creativity and innovation.

Servicios

Competitive salary and equity

Unlimited PTO

12 weeks paid parental leave

Education budget

Formación

• Experience in Full Stack Development across frontend and backend.
• Strong problem-solving skills with a customer-focused mindset.
• Excellent communication skills for collaboration with stakeholders.

Responsabilidades

• Take ownership of major portions of products and projects end-to-end.
• Conduct user research and write detailed product specifications.
• Design user interfaces and prototype ideas with responsiveness in mind.

Conocimientos

Full Stack Development

Problem Solving

Collaboration

Technical Ambiguity

Quality Assurance

Communication

Educación

Computer Science Degree or Equivalent

Herramientas

TypeScript

React

Node.js

Postgres

GraphQL

Descripción del empleo

Senior Full Stack Engineer - AI Products

Base pay range

I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for an ambitious full-stack engineer who is laser-focused on solving customer problems and making the right long-term investments to solve them, not only today but in our future features and products. What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature. We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing 100% year over year, very low churn, and many years of runway. We’ll share more details once we meet. You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).

About the Role And How We Work

Our 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. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. 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. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation. 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.

About

At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. 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). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have:

• Designed and built automated interview scheduling. 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. This solves the “Calendar Tetris” problem.
• 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.
• Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. 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.

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.

Why You Should or Shouldn’t Apply

Software Engineers Come In Many Flavors, Not All Of Which Fit Our Model. Here Are Some Things To Help You Decide If This Fits You And What You’re Looking For

• You’re not afraid to tackle any part of a technology stack. 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.g., design system, SRE team).
• You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.
• You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high‑quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC‑backed startups with a very small team.
• You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it).
• You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. 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. Clear and concise communication helps a lot here!
• You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time‑consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.

Put Another Way, You Shouldn’t Apply If

• 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 technical details and challenges.
• 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.
• You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.
• You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them.
• You want to mentor earlier‑career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.
• To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign‑off.

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
• Natural collaboration and deliberate communication
• Investing in tools and abstractions that give us leverage
• Pushing for a diverse team

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.

Collaboration is Natural & Communication is Deliberate

Our engineering team consists of lifelong learners who are talented but also humble and kind. 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 sacred, and deliberate communication keeps engineers in sync.

Increase Leverage, not Team Size

We built Ashby with the goal of delivering high quality at speed. We’ve done this through:

• Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day.
• A debugger that works out of the box. Everyone on the team has contributed to our developer experience.
• Building blocks to create powerful and customizable products fast, including a common component set (analytics modeling and query language, policy engine, workflow engine, design system).

Interview Process

Our interview process helps you show your best self. We’ll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and discussing decisions. There are no LeetCode or whiteboard exercises. Our interview process is three rounds:

• Introduction call with Hiring Manager (15–30m, live)
• A technical screen where we pair in our actual codebase (1h, live)
• Three non‑coding interviews focusing on product thinking, technical design, and infrastructure (3h 15m, live; can be split across days)

Depending on leadership bandwidth, there may be an additional 30m recruiter screen. Your hiring manager will prep you for interviews. You’ll meet 4–6 engineers. If we don’t offer, we’ll provide feedback.

Your First Three Months at Ashby

We want an exceptional onboarding experience. Your dev environment is set up with a single script, you push your first product change on day one, and you continue shipping product changes that illuminate our codebase and best practices. Your manager will conduct 30, 60, and 90‑day reviews to calibrate on how we work together. You’ll have a peer paired with you to answer questions, pair program, and check in often. The rest of the team runs training sessions on our culture, product, engineering process, and technical architecture.

Technology Stack

I’m sharing our tech stack with the caveat that we don’t require prior experience in it (but a love of typed languages is helpful): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. When engineers joined Ashby, many switched from other languages like Swift and Kotlin, platforms like iOS, and Windows. We care about fundamentals and how fast you learn. For folks who switch, it’s nice seeing hot reload vs waiting for XCode to compile.

Benefits

• Competitive salary and equity. 10‑year exercise window for stock options. You shouldn’t feel pressure to purchase stock options if you leave Ashby — do it when you feel financially comfortable.
• Unlimited PTO, and we encourage you to take it.
• A minimum of 12 weeks of fully paid parental leave, covered by Ashby (outside the US may be longer to align with regional requirements).
• Generous equipment, software, and office furniture budget.
• 100/month education budget with more expensive items (like conferences) covered with manager approval.
• If you’re in the US, top‑tier health insurance for you and your dependents, with 100% of premiums covered by Ashby; in other countries, high‑quality supplemental health insurance for you and your dependents, also fully covered by Ashby.

Equal Employment Opportunity Statement

Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.

Employment type : Full‑time. Seniority level: Mid‑Senior level. Job function: Engineering and Information Technology. Industries: Software Development.