Curated Remote Jobs in Europe

At Linear, we are on a mission to bring magic back to software. To empower product teams to do their best work, we are building an issue tracking and project management tool that combines UI elegance with world-class performance. Founded in 2019, Linear has become the platform of choice for 20,000+ companies to plan and build their products.

Linear was set up as a fully remote company from the start. Today, our small but mighty team is distributed across North America and Europe. What unites us is relentless focus, fast execution, and our passion for software craftsmanship. We are all makers at heart and care deeply about the quality of our work.

Over the past few years, Linear has experienced incredible organic growth and has become the default tool of choice for many of the world’s best product teams. We are now layering a product-led sales motion on top of our existing self-serve business to further accelerate our ambitions and bring the magic of Linear to even more and larger companies. You’ll play an instrumental role in defining our enterprise sales motion, contribute to the future of our product, and help high-impact companies build better software.

Please note: While Linear is a remote-first company across the US and Europe, this role is based in London. We’re looking for someone who can work from our London office 2–3 days per week, as this role will be closely connected to in-person collaboration with our growing sales presence in the region.

What you'll do

• Become a product expert and help customers use Linear effectively; assist prospects through the trial and evaluation phase
• Generate a strong pipeline and exceed quarterly and annual targets
• Stay up to date with our product offering, industry trends, competitive landscape, and market trends to continuously adapt sales strategies and approaches for maximum impact
• Build relationships with key stakeholders within accounts; understand client needs deeply, align Linear’s solutions to business objectives + shape decision criteria. Effectively communicate and align our value proposition to decision-makers
• Be the voice of the customer; advocate for customers by surfacing product or adoption blockers to our product team
• Help build the foundation and define our enterprise sales process

What we're looking for

• 5+ years in a quota-carrying sales role
• Experience selling a technical product to both engineering and product leadership; bonus if you have experience selling collaboration or project management software
• SaaS and startup experience; comfortable working and adapting in a fast-paced and flexible environment
• Ability to understand complex client needs, craft tailored discovery, and drive sales through consultative approaches.
• Strong written and verbal communication, presentation, and product demonstration skills
• Highly autonomous with a bias for action. Owner’s mindset to quickly come up to speed on product, market, ICP, and unique differentiators

What we offer

• Interesting and challenging work
• Work-life balance
• Competitive salary and equity
• Employee-friendly equity terms (extended exercise)
• Stipend to set up your home office
• Paid lunch and coffee during workdays
• Work remotely, no commuting to the office
• Paid co-working space/desk at an office
• Health, dental, and vision insurance (based on country requirements)
• Regular team events and off-sites
• 5 weeks of paid vacation
• 4 months of paid parental leave (or more based on country requirements)

Learn how we think and work:

• A story about our mission: Read Me
• How we work: Designing remote work at Linear
• Our CEO and co-founder, Karri at 20VC: How to Grow Capital Efficiently in a World of BS Growth
• Make an Org Chart You Want to Ship — Advice from Linear on How Heirloom Tomatoes Should Inspire Team Design
• Building our teams: Why and how we do work trials at Linear
• A video series: Conversations on Quality
• Read about our recent Series C Fundraise and Giving our team liquidity

About Us

Socket helps devs and security teams ship faster by cutting out security busywork. Thousands of orgs use Socket to safely find, audit, and manage open source code. Our customers — from Anthropic to xAI, and Figma to Vercel — love Socket (just check out their tweets to see for yourself!)

Founded by Feross Aboukhadijeh, a long-time open source maintainer with software downloaded over a billion times a month, Socket has raised $65M in funding from top angels, operators, and security leaders.

About the Role

We're seeking a Sales Engineer, EMEA to lead Socket's growth in Europe. This is a unique hybrid role combining pre-sales technical expertise with post-sale customer success ownership. You'll be the bridge between prospects evaluating Socket and existing customers expanding their usage, driving both deal closure and long-term customer outcomes.

What You’ll Do

Pre-Sales & Demos:

• Lead technical discussions and product demonstrations tailored to prospect needs
• Design and execute proofs of concept (POCs) that enable prospects to evaluate Socket effectively
• Address technical objections, troubleshoot issues, and build customer confidence
• Translate Socket's capabilities into business value for security and engineering teams

Post-Sales & Growth:

• Own the success and growth of assigned European enterprise accounts
• Create and execute success plans aligned to customer goals with clear KPIs
• Drive feature adoption and expansion opportunities across the customer base
• Conduct quarterly business reviews and renewal discussions
• Escalate customer feedback to product and engineering teams

Cross-Functional Partnership:

• Collaborate with Sales, Product, Engineering, and CS teams to understand customer needs
• Contribute to scalable processes and playbooks for European enterprise accounts
• Provide strategic feedback on market needs and feature requests
• Support the creation of technical documentation and integration guides

What You'll Bring

• 5+ years in pre-sales technical roles (Sales Engineer, Solutions Engineer, Solutions Architect, TAM) with enterprise customers
• 2+ years of experience in customer success, account management, or post-sale technical roles
• Prior experience in security, developer tools, or SaaS environments
• Hands-on technical background: prior software engineering, data science, or equivalent role
• Deep familiarity with package managers (at least one of npm or PyPI) and programming ecosystems (at least one of JavaScript or Python)
• Understanding of software supply chain security and vulnerability management concepts
• Ability to read/write basic scripts in Python, JS, or Go
• Knowledge of source control systems (Git, GitHub, GitLab, Bitbucket)
• RESTful API and integration experience

Our Interview Process

1. Phone Screen with our Talent Team
2. Virtual f2f with the Hiring Manager
3. Virtual f2f with members of our Sales Team
4. Presentation
5. Final call with our Founder
6. Debrief
7. References
8. Offer

We know how important clarity is when looking for a new role, so we've put together a read-me about the Interview Process at Socket.

Benefits

Our benefits are crafted to support you and your family, so you can take care of what matters most and thrive in and outside of work. We offer:

• Market competitive salary bands
• Meaningful equity program
• Comprehensive health benefits for you and your family
• Flexible time-off, holidays, and winter shutdown to rest & recharge
• Paid parental leave
• Remote-first, with quarterly team off-sites

At Socket, we

1. Pursue Excellence: We set ourselves apart by consistently delivering work of exceptional quality and distinction.
2. Move with urgency and focus: We prioritize swift, decisive action.
3. Think rigorously: We care about being right and it often takes reasoning from first principles to get there. We value alternative perspectives and have constructive discussions.
4. Trust and amplify: We overtrust, always assume good intent, and give specific feedback to help each other improve.
5. Feel a strong sense of ownership: We wear many hats and feel a strong sense of overall ownership of the company and we're non-territorial regarding our nominal domains.
6. Are customer obsessed: We relentlessly prioritize the needs of our customers, striving to exceed their expectations and delight them at every interaction.

About lemlist

lemlist is a global B2B SaaS business with one mission: help any business grow.

We’re doing $43M+ ARR, while being:

• Bootstrapped & profitable
• 140 people, remote-friendly, agile
• Majority-owned by our founder Guillaume Moubeche, giving us freedom and independence

We run two product lines:

• Sales Engagement with lemlist ($38M ARR, growing +50% YoY)
• Social selling with Taplio & Tweet Hunter ($5M ARR)

Our ambition: become a world-class giant in Sales Tech.

Our mantra: Keep growing.

About the role

We’re looking for a Tech Lead or a Senior Fullstack TypeScript Developer to join our team.

👉 The role starts as a Senior Developer, then evolves into a Tech Lead position after 3-6 months, once you’ve proven yourself in the squad.

You’ll design, build, and ship features across frontend and backend, improve performance, and progressively take leadership within your squad to set technical standards, mentor peers, and drive delivery.

What you’ll do

• Build new features end-to-end (frontend + backend) by working hand-in-hand with a strong Product team
• Improve the codebase (refactoring, bug fixes, optimization)
• Collaborate with the rest of the team to solve technical issues
• Mentor fellow developers, share knowledge, and raise the bar
• Step up as Tech Lead in your squad: drive quality, make technical choices, and align delivery

What success looks like

Within 3 months

• You’re fully onboarded and comfortable in our stack
• You’ve shipped meaningful features in production
• You’ve contributed to improving our codebase

Within 6 months

• You’ve led delivery of multiple successful projects
• You’ve had direct impact on scalability & performance
• You’ve grown into your Tech Lead role and mentor others

What’s in it for you

• Join a bootstrapped, profitable, fast-growing SaaS company
• Build products used by thousands of businesses worldwide
• See your impact quickly with a very short feedback loop
• Work with senior engineers who love to learn and share knowledge
• Remote-first culture (office in Paris if you prefer 🇫🇷)
• No endless meetings, high autonomy, big impact

About you

Must have

• 8+ years in TypeScript / JavaScript (frontend + backend)
• Solid skills in Node.js, React, MongoDB
• Proven track record building & maintaining web apps
• Always hungry to learn more, particularly around JS/TS
• Autonomous, fast learner, and collaborative
• Fluent in French & English, based in French timezone (+/- 2h)

Nice to have

• B2B SaaS startup experience
• You already worked on Meteorjs or on real-time apps
• Self-taught hacker or side-project builder
• Passionate about experimenting & creating beyond work

Package

• 65 - 75K€ fixed + 15K€ bonus
• Profit sharing: when lemlist wins, you win too
• Full perks: Alan Blue (healthcare) 100% taken care of for you and your family, Swile meal vouchers, 100% of your Navigo card, MacBook Pro & remote setup budget
• Annual global team retreat in amazing locations 🌍

Recruitment process

1. Interview with Lucas (TAM)
2. Interview with Mickael (CTO)
3. Technical interview with Mickael (CTO) & Corentin (VP Engineering)
4. Final chat with Charles (CEO)

We're building a new healthcare clearinghouse

In the healthcare sector, the Health Insurance Portability and Accountability Act of 1996 (HIPAA) requires that all insurance payers exchange transactions such as claims, eligibility checks, prior authorizations, and remittances using a standardized EDI format called X12 HIPAA. A small group of legacy clearinghouses process the majority of these transactions, offering consolidated connectivity to carriers and providers.

Stedi is the world's only programmable healthcare clearinghouse. By offering modern API interfaces alongside traditional real-time and batch EDI processes, we enable both healthcare technology businesses and established players to exchange mission-critical transactions. Our clearinghouse product and customer-first approach have set us apart. Stedi was ranked as Ramp’s #3 fastest-growing SaaS vendor.

Stedi has lightning in a bottle: engineers and designers shipping products week in and week out; a lean business team supporting the company’s infrastructure; passion for automation and eliminating toil; $92 million in funding from top investors like Stripe, Addition, USV, Bloomberg Beta, First Round Capital, and more. To learn more about how we work, watch our founder Zack’s interview with First Round Capital.

What we’re looking for

Stedi is the world's only programmable healthcare clearinghouse. By offering a modern API interface for running eligibility checks, processing claims, and ingesting ERAs, healthcare technology businesses can exchange transactions with payers without dealing with the EDI protocol or carrier-specific connectivity.

As we continue to scale, we are looking for a Frontend Engineer to bring the Stedi vision to life. You'll work closely with other engineers, designers, and product managers to execute on a broad range of projects – from building foundational features in our web product to testing for reliability and consistency throughout.

How we build

• Our backend teams use AWS exclusively for all customer-facing backend infrastructure. We use tools like GitHub, Stripe, and PagerDuty, but all the application work happens on AWS.
• All exposed API endpoints are available to the frontend via strongly-typed SDK clients.
• Our frontend applications are built using React, Next.js, and TypeScript, based on designs provided by our design team in Figma.

What you'll do

• Collaborate with design, product and backend engineering to build web interfaces that power our products and features.
• Develop reusable, responsive, accessible components using scalable, semantic React components.
• Contribute to our design language system.
• Contribute to a culture of engineering excellence and rigor through both coding and writing, as well as high-quality, effective communication

Who you are

• 4+ years of relevant web front-end development experience at a tech-forward software company.
• Solid understanding of modern frontend technology stack (React, UI testing, CSS-in-JS, Server-side rendering).
• Advanced knowledge in JavaScript/TypeScript.
• Experience setting up and maintaining build, test, and deployment tools in production environments.
• Strong communication skills to bridge the gap between design, product, and engineering.
• An exceptional contributor who creates and executes their own work.
• Highly curious; not satisfied with getting something to work, you want to understand why it works and how to make it high-quality.
• Philosophical alignment with the Stedi Standards.

We’ve been made aware of individuals impersonating the Stedi recruiting team. Please note:

• All official communication about roles at Stedi will only come from an @stedi.com email address.
• If you’re unsure whether a message is legitimate or have any concerns, feel free to contact us directly at careers@stedi.com.

We appreciate your attention to this and your interest in joining Stedi.

At Stedi, we're looking for people who are deeply curious and aligned to our ways of working. You're encouraged to apply even if your experience doesn't perfectly match the job description.

About Kilo: We're building the fastest-evolving open-source AI coding agent to make programming accessible to billions. In just a few months: #1 AI coding tool on OpenRouter, over 250K downloads, countless 5-star reviews, multiple Hacker News front page articles. But we're just getting started.

Kilo Code is more than just another coding tool. We're creating a superset of the best features from existing AI coding agents, combined with our own innovations, all built with community feedback at the core.

The situation: We’re an open source AI coding tool taking on Cursor, Windsurf, and the rest. We are growing fast and want to work with other engineers excited about accelerating software development across the globe while shipping features our users love.

You are:

• Into building features and product more than obsessing on the details of technology, but can also go deep on technology when needed to solve problems
• Fast. Like, uncomfortably fast for normal companies. Ship a bad feature Monday, fix it Tuesday, scale it Wednesday.
• Someone who both likes to use agents to code with them and still rolls their sleeves up and writes hand-typed farm-to-table code line by line when things get tricky
• Knows the balance between moving fast & breaking things and moving too fast & causing a forest fire and loves dancing on that knife edge
• Kind, thoughtful, honest, open, and patient with others

Week 1 you will:

• Be paired up with another engineer and immediately dive into the code
• Assist in testing features, shipping features, and fixing bugs
• Get plugged into our user community and start chatting with our users

Month 1 you will:

• Significantly contributed to shipping a large project or feature
• Have a solid relationship with the team & a good understanding of the codebase
• Have opinions and ideas on new products and features

Month 3 you will:

• Have hired a first teammate (or told us why we shouldn’t yet)
• Have championed and built a revenue or user impacting feature, end to end
• Be flying across the code base with comfort, confidence, and purpose

The work setup:

• Remote (EMEA timezones) but we ship together in Amsterdam every 2-3 months (think: hackathon energy, not conference rooms).
• You’ll spend 90% of your time building product. Be that backend, frontend, infrastructure, whatever is needed, we match your strengths to our roadmap while giving you room to grow. Our whole stack is Typescript and our database of choice is postgres.
• We work with folks from other timezones so doing effective hand-offs and writing things down or putting them in pull requests is critical. Prepare to be on lots of google meets calls but mostly short, focused 1:1 and very few meetings where you are just warming the chair
• We thank people publicly, give feedback directly, and own our mistakes
• Your dopamine needs to come from shipping, not from code for code's sake

Anti-requirements:

• Needing pixel perfect designs before starting on something
• Needing a QA department
• “I didn’t build that, so I’m not fixing that."
• Comfort with slow

Apply with:

Links to stuff you’ve shipped, github profile, portfolio etc. Not required, but we want to get to know as much about you as we can before we meet!

Hi 👋🏾 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.

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 I talk about in "What We're Building."
• 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.

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.

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!

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
• Putting effort into building 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.

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).

We also meet in person at least twice a year, once as a department and once as a company. 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. We’ve done this through investment in:

• 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. 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. Each improvement to a common component cascades throughout our app (short video below).

And a demo of one of these building blocks: https://www.loom.com/share/32c0cc3eedf2450fb66a901b76186ce4

Put Effort into Diversity

Diverse teams drive innovation and better outcomes. 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.

Today, 21% of engineers at Ashby are 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.

Interview Process

At Ashby, our team and interview process want to help 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 talking through decisions. There are no leetcode or whiteboard exercises.

Our interview process is three rounds:

1. Introduction call with Hiring Manager (15 to 30m, live)
2. A technical screen where we pair in our actual codebase (1h, live)
3. Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days)

Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter.

Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you’ll need minimal preparation). You’ll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback!

Your First Three Months at Ashby

We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together.

It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run 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 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). We care more about fundamentals (e.g., debugging, abstractions) and how fast you learn. For folks on the team who switched, it's nice seeing changes hot reload versus 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 will encourage you to take it.
• A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements.
• Generous equipment, software, and office furniture budget. Get what you need to be happy and productive!
• $100/month education budget with more expensive items (like conferences) covered with manager approval.
• If you’re in the US, we offer top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, we provide high-quality supplemental health insurance for you and your dependents, also fully covered by us.

Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re being deliberate about building that environment from the ground up. I hope that excites you enough to apply.

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.