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 . click apply for full job details
Jan 04, 2026
Full time
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 . click apply for full job details
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 . click apply for full job details
Jan 04, 2026
Full time
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 . click apply for full job details
We live in a world that runs on physical industries like energy, logistics, manufacturing. These sectors are essential to our economy and daily lives, yet they are held back by inefficiencies, fragile legacy systems, and decades-old ways of working. This is not just a business problem; it is a societal one. When grids fail, supply chains stall, or factories falter, entire economies are disrupted. These companies face unique, complex challenges that typical software was never designed to solve. Cogna was founded to change this. Our mission is to give critical industries their own AI-powered Software Factory: a way to build and deploy bespoke digital tools that solve pressing operational challenges. Since our launch in May 2023, we've seen incredible customer traction and revenue growth. We're backed by leading VCs, including Notion Capital and Hoxton Ventures, and we're building a world-class team to take on one of the most important challenges of our time. Tackling challenges at this scale takes people who are curious, adaptable, and motivated by impact. If our mission resonates with you, we encourage you to apply, even if your experience doesn't match every requirement. We are committed to building a diverse team that reflects the industries and societies we serve. Overview We are looking for a creative Software Engineer with a passion for developing scalable, reliable, efficient, and beautiful AI-first software and have a strong sense of ingenuity. You will be part of an all-star early team, building the future of software. We've been building product with AI at its core for enterprise customers since the early days of GPT-3.5 to the latest and greatest models, and have built internal tooling to efficiently and effectively work with LLMs. We understand that building reliable products using AI is much more than writing a good prompt. We put a lot of thought and effort into making outputs of LLMs reliable and verifiable in our product, whether that's code or more unstructured outputs. We have frameworks for evaluation, verification, specialized code and test generation pipelines, agentic behavior, RAG, observability and orchestration tooling, and many more all widely used across our product, neatly integrated, and informed by real customer and product needs. Each of these are constantly evolving to adapt to the state of the art, and being built by a world-class team who are always experimenting. You'll be helping to develop these, as well as using them to build the "brain" of our platform: building agents and end-to-end pipelines to understand the customer's pain points, define requirements, and generate & verify software to address these in a reliable way. We're truly building at the edge of what's possible and we need creative minds who can move fast to push the boundaries. What you'll do Define, build, and maintain reliable AI-first product features, including internal frameworks and tooling for working with LLMs Experiment with various AI/LLM techniques, models, and approaches to increase the accuracy and reliability of our outputs. Build and improve evaluation systems and benchmarks. Design and build reusable application architectures and toolchains, working closely with the software synthesis team. Write and ship high-quality, efficient, and reliable code that is extendible, scalable, and observable. You know how to move fast without breaking things and you know how to keep the right balance between experimentation and shipping. Take ideas from experimentation to shipping. You intuitively know what a great product looks like. Build and help foster an engineering culture that encourages innovation and high-quality code standards, while shipping fast. Collaborate closely in a small highly motivated team to build world-class software. What we're looking for At least 3 years of relevant work experience. The drive to work at an early-stage startup. You thrive in a fast-paced, quickly changing, and independent environment. You're highly proficient in modern typed Python, docker, and PostgreSQL. Experience in a compiled typed language like Go or Rust, or in modern frontend development is a plus. You're proficient in modern Python ecosystems and toolchains and have worked with them in complex large codebases. You understand the intricacies of them. You're a creative experimentalist at heart and have industry experience in an environment where this was necessary. You either have professional experience using LLMs or have enthusiastically experimented in your own time. Industry experience with LLM toolchains and ecosystems (e.g. libraries like Langchain, observability tooling, RAG systems, etc.) is a plus. You have a fundamental understanding of code analysis, compilers, domain-specific languages, or related topics, and are keen to learn in this area. You are passionate about clean and reusable interfaces, but can iterate fast on them. You can work closely with a product manager to turn customer requirements into reliable systems quickly, and iterate from there, while balancing long-term engineering maintenance effort. You're great at communicating technical systems succinctly to a product-focused audience. Familiarity with e2e testing frameworks, large language models, CI/CD tooling, workflow orchestration systems such as Argo or Temporal, and/or experience with Kubernetes is a plus. Special note about career breaks: We accept candidates with career breaks and CV gaps. Life happens, we get it. Please apply anyway! What we offer Competitive salary and share option plan 25 days annual leave, plus public holidays Excellent pension scheme, matched to 7.5% Private healthcare, including family cover and pre-existing conditions Flexible hybrid working with 2 days per fortnight in our Farringdon office, but different schedules can be negotiated. Regular social events and offsites Access to a gym and fitness classes in our office building
Jan 01, 2026
Full time
We live in a world that runs on physical industries like energy, logistics, manufacturing. These sectors are essential to our economy and daily lives, yet they are held back by inefficiencies, fragile legacy systems, and decades-old ways of working. This is not just a business problem; it is a societal one. When grids fail, supply chains stall, or factories falter, entire economies are disrupted. These companies face unique, complex challenges that typical software was never designed to solve. Cogna was founded to change this. Our mission is to give critical industries their own AI-powered Software Factory: a way to build and deploy bespoke digital tools that solve pressing operational challenges. Since our launch in May 2023, we've seen incredible customer traction and revenue growth. We're backed by leading VCs, including Notion Capital and Hoxton Ventures, and we're building a world-class team to take on one of the most important challenges of our time. Tackling challenges at this scale takes people who are curious, adaptable, and motivated by impact. If our mission resonates with you, we encourage you to apply, even if your experience doesn't match every requirement. We are committed to building a diverse team that reflects the industries and societies we serve. Overview We are looking for a creative Software Engineer with a passion for developing scalable, reliable, efficient, and beautiful AI-first software and have a strong sense of ingenuity. You will be part of an all-star early team, building the future of software. We've been building product with AI at its core for enterprise customers since the early days of GPT-3.5 to the latest and greatest models, and have built internal tooling to efficiently and effectively work with LLMs. We understand that building reliable products using AI is much more than writing a good prompt. We put a lot of thought and effort into making outputs of LLMs reliable and verifiable in our product, whether that's code or more unstructured outputs. We have frameworks for evaluation, verification, specialized code and test generation pipelines, agentic behavior, RAG, observability and orchestration tooling, and many more all widely used across our product, neatly integrated, and informed by real customer and product needs. Each of these are constantly evolving to adapt to the state of the art, and being built by a world-class team who are always experimenting. You'll be helping to develop these, as well as using them to build the "brain" of our platform: building agents and end-to-end pipelines to understand the customer's pain points, define requirements, and generate & verify software to address these in a reliable way. We're truly building at the edge of what's possible and we need creative minds who can move fast to push the boundaries. What you'll do Define, build, and maintain reliable AI-first product features, including internal frameworks and tooling for working with LLMs Experiment with various AI/LLM techniques, models, and approaches to increase the accuracy and reliability of our outputs. Build and improve evaluation systems and benchmarks. Design and build reusable application architectures and toolchains, working closely with the software synthesis team. Write and ship high-quality, efficient, and reliable code that is extendible, scalable, and observable. You know how to move fast without breaking things and you know how to keep the right balance between experimentation and shipping. Take ideas from experimentation to shipping. You intuitively know what a great product looks like. Build and help foster an engineering culture that encourages innovation and high-quality code standards, while shipping fast. Collaborate closely in a small highly motivated team to build world-class software. What we're looking for At least 3 years of relevant work experience. The drive to work at an early-stage startup. You thrive in a fast-paced, quickly changing, and independent environment. You're highly proficient in modern typed Python, docker, and PostgreSQL. Experience in a compiled typed language like Go or Rust, or in modern frontend development is a plus. You're proficient in modern Python ecosystems and toolchains and have worked with them in complex large codebases. You understand the intricacies of them. You're a creative experimentalist at heart and have industry experience in an environment where this was necessary. You either have professional experience using LLMs or have enthusiastically experimented in your own time. Industry experience with LLM toolchains and ecosystems (e.g. libraries like Langchain, observability tooling, RAG systems, etc.) is a plus. You have a fundamental understanding of code analysis, compilers, domain-specific languages, or related topics, and are keen to learn in this area. You are passionate about clean and reusable interfaces, but can iterate fast on them. You can work closely with a product manager to turn customer requirements into reliable systems quickly, and iterate from there, while balancing long-term engineering maintenance effort. You're great at communicating technical systems succinctly to a product-focused audience. Familiarity with e2e testing frameworks, large language models, CI/CD tooling, workflow orchestration systems such as Argo or Temporal, and/or experience with Kubernetes is a plus. Special note about career breaks: We accept candidates with career breaks and CV gaps. Life happens, we get it. Please apply anyway! What we offer Competitive salary and share option plan 25 days annual leave, plus public holidays Excellent pension scheme, matched to 7.5% Private healthcare, including family cover and pre-existing conditions Flexible hybrid working with 2 days per fortnight in our Farringdon office, but different schedules can be negotiated. Regular social events and offsites Access to a gym and fitness classes in our office building
About DELLI DELLI exists to empower the independent economy, the makers, creators, and producers whose craft shapes the way the world tastes, feels, and connects. We imagine a world where every maker has a companion; a quiet, intelligent partner who handles the chaos so they can stay focused on the joy of creating. Every day, millions of small businesses lose hours to invisible labour - the unseen admin, the back and forth messages, the clarifications, the late night catch up that keeps everything moving. It's the unspoken cost of being independent, and it steals time and energy from the work that actually matters. We believe commerce should feel natural again. A baker shouldn't have to wrestle with emails, calls, spreadsheets and tools that don't talk to each other. A retailer shouldn't need to scan across fragmented channels just to understand who has stock or what's available. In the world we're building, AI agents become the connective tissue, listening across conversations, interpreting intent, and quietly taking care of what needs to happen next. They reduce noise, restore clarity, and give makers and retailers the freedom to operate the way they already do, but with far more ease, confidence, and flow. It's intelligence that feels human, supportive, and alive - technology that steps in without stepping over. We're starting in food, where culture, community, and craft collide most powerfully. What we learn here will shape how we support other categories across the independent economy, amplifying the people who make our world more interesting, more human, and more alive. Your Role Join us as a Full Stack Engineer and help build the foundation of DELLI's agentic platform. You'll work across the entire stack, from the intelligence powering our Order and Payments Hubs to the infrastructure that keeps everything running smoothly. This is a hands on role where you'll build, ship, and learn quickly based on feedback from real makers who rely on what we create. You'll be part of a collaborative engineering team where everyone contributes to architecture, problem solving, and delivery. Instead of being limited to a narrow slice of the system, you'll work across platforms end to end. You'll architect, build, deploy, and iterate in an environment that values autonomy, trust, inclusivity, and thoughtful engineering. We're looking for someone excited to help create something new and meaningful. The work you do here will shape the future of independent commerce. Responsibilities You'll design and build core features across the Order, Payments, and Discovery Hubs, working closely with the team to make technical decisions and carry them through to implementation. You'll take responsibility for what you build and when you deliver it, while working in a supportive and collaborative environment. You'll shape backend systems, contribute to frontend flows, and support the infrastructure on AWS with tools like Terraform. You'll ship quickly, gather feedback, and iterate based on the needs of real makers. Your work will also include supporting deployments, monitoring, and ensuring our systems run securely and reliably. As the platform grows, you'll help refine product direction and engineering standards. What We're Looking For Must haves Full stack capability across backend (Node and Python), frontend (Next.js and React), and strong experience with TypeScript. Experience with AWS, CI/CD, and infrastructure tooling such as Terraform. Familiarity with MCP, LangChain, or equivalent frameworks for agentic or AI powered systems. Curiosity about intelligent software design and how AI should shape modern architecture. A builder mindset focused on learning quickly and delivering real impact. Comfort working with autonomy in open problem spaces. Nice to haves Experience integrating LLMs or other AI systems into production environments. Background in early stage companies and an understanding of the zero to one journey. Interest in payments infrastructure. Early stage startup experience, you know what 0 1 feels like. Empathy for non technical users and a desire to design clear, accessible experiences. Why Join DELLI Early ownership- help shape the architecture, product direction, and technical standards that define how the independent economy runs. Direct impact- your code powers real businesses; every feature you ship saves makers hours and gets them paid faster. True autonomy- small, flat, senior team; no red tape, just clear ownership and shared ambition. Frontier learning- build in one of the most exciting frontiers of software - agentic AI and real world commerce infrastructure. Top tier backing- supported by Balderton Capital and HV Capital, building with intent and long term conviction. Purpose that matters- you're not optimising clicks; you're building systems that sustain culture, creativity, and independence. We're at that rare inflection point - early enough that your fingerprints will be everywhere, but real enough that your work ships to makers every week. If you want to build foundational systems that change how the world's independent economy operates,this is your moment. Practical Details Location:UK based, London hybrid with two days in the office Start date:January or February 2026 Compensation:Competitive salary and meaningful early stage equity Team:Collaborative engineering team with high autonomy and shared ownership
Jan 01, 2026
Full time
About DELLI DELLI exists to empower the independent economy, the makers, creators, and producers whose craft shapes the way the world tastes, feels, and connects. We imagine a world where every maker has a companion; a quiet, intelligent partner who handles the chaos so they can stay focused on the joy of creating. Every day, millions of small businesses lose hours to invisible labour - the unseen admin, the back and forth messages, the clarifications, the late night catch up that keeps everything moving. It's the unspoken cost of being independent, and it steals time and energy from the work that actually matters. We believe commerce should feel natural again. A baker shouldn't have to wrestle with emails, calls, spreadsheets and tools that don't talk to each other. A retailer shouldn't need to scan across fragmented channels just to understand who has stock or what's available. In the world we're building, AI agents become the connective tissue, listening across conversations, interpreting intent, and quietly taking care of what needs to happen next. They reduce noise, restore clarity, and give makers and retailers the freedom to operate the way they already do, but with far more ease, confidence, and flow. It's intelligence that feels human, supportive, and alive - technology that steps in without stepping over. We're starting in food, where culture, community, and craft collide most powerfully. What we learn here will shape how we support other categories across the independent economy, amplifying the people who make our world more interesting, more human, and more alive. Your Role Join us as a Full Stack Engineer and help build the foundation of DELLI's agentic platform. You'll work across the entire stack, from the intelligence powering our Order and Payments Hubs to the infrastructure that keeps everything running smoothly. This is a hands on role where you'll build, ship, and learn quickly based on feedback from real makers who rely on what we create. You'll be part of a collaborative engineering team where everyone contributes to architecture, problem solving, and delivery. Instead of being limited to a narrow slice of the system, you'll work across platforms end to end. You'll architect, build, deploy, and iterate in an environment that values autonomy, trust, inclusivity, and thoughtful engineering. We're looking for someone excited to help create something new and meaningful. The work you do here will shape the future of independent commerce. Responsibilities You'll design and build core features across the Order, Payments, and Discovery Hubs, working closely with the team to make technical decisions and carry them through to implementation. You'll take responsibility for what you build and when you deliver it, while working in a supportive and collaborative environment. You'll shape backend systems, contribute to frontend flows, and support the infrastructure on AWS with tools like Terraform. You'll ship quickly, gather feedback, and iterate based on the needs of real makers. Your work will also include supporting deployments, monitoring, and ensuring our systems run securely and reliably. As the platform grows, you'll help refine product direction and engineering standards. What We're Looking For Must haves Full stack capability across backend (Node and Python), frontend (Next.js and React), and strong experience with TypeScript. Experience with AWS, CI/CD, and infrastructure tooling such as Terraform. Familiarity with MCP, LangChain, or equivalent frameworks for agentic or AI powered systems. Curiosity about intelligent software design and how AI should shape modern architecture. A builder mindset focused on learning quickly and delivering real impact. Comfort working with autonomy in open problem spaces. Nice to haves Experience integrating LLMs or other AI systems into production environments. Background in early stage companies and an understanding of the zero to one journey. Interest in payments infrastructure. Early stage startup experience, you know what 0 1 feels like. Empathy for non technical users and a desire to design clear, accessible experiences. Why Join DELLI Early ownership- help shape the architecture, product direction, and technical standards that define how the independent economy runs. Direct impact- your code powers real businesses; every feature you ship saves makers hours and gets them paid faster. True autonomy- small, flat, senior team; no red tape, just clear ownership and shared ambition. Frontier learning- build in one of the most exciting frontiers of software - agentic AI and real world commerce infrastructure. Top tier backing- supported by Balderton Capital and HV Capital, building with intent and long term conviction. Purpose that matters- you're not optimising clicks; you're building systems that sustain culture, creativity, and independence. We're at that rare inflection point - early enough that your fingerprints will be everywhere, but real enough that your work ships to makers every week. If you want to build foundational systems that change how the world's independent economy operates,this is your moment. Practical Details Location:UK based, London hybrid with two days in the office Start date:January or February 2026 Compensation:Competitive salary and meaningful early stage equity Team:Collaborative engineering team with high autonomy and shared ownership