Kombo provides an infrastructure layer that centralizes and connects employee data across HR systems for businesses.
SENIOR PRODUCT ENGINEER (FULL STACK) @KOMBO 📍 Berlin (On-site) · Full-time Hey, I'm Aike, co-founder & CTO at Kombo. I'm looking for entrepreneurial senior product engineers who want to own entire customer problems on our product. You won't get specced tickets at Kombo, but talk to customers, design the solution, build it, ship it, and make sure it actually works. This is a Berlin based on-site role. WHAT WE ARE BUILDING We are building the infrastructure platform that HR tech products are built on. Because my three co-founders and I are engineers, we have always been drawn to deeply technical problems. That's how we ended up building infrastructure for HR tech providers. Concretely, we built a unified API, a massive data synchronization engine, an observability platform, and an embedded integration setup/configuration UI. We offer this to other software companies so that they can provide prebuilt integrations with HR, ATS, LMS, and Payroll systems to their customers, instead of building and maintaining hundreds of integrations themselves. You can read more about our product here: What is the Kombo product? https://kombo-api.notion.site/What-is-the-Kombo-product-2fb6526d848a806793d1ccde34243879 We reached product-market fit about 1.5 years ago. Since then, both our revenue and product usage have picked up with insane growth. Currently, we are at ~10M annual recurring revenue, power integrations for more than 15,000 companies, and sync data of more than 250 million people globally. We are setting the standard for how companies build product on top of the most complicated enterprise systems. Our growth rate puts us in the top 5% of VC funded startups worldwide. Talking of which, we have just raised our 25M Series A funding round 🎉. ABOUT THE ROLE AND HOW WE WORK During the early days, all my co-founders and I worked very closely with customers, did support ourselves, learned about their problems, and designed features based on those inputs. This was a lot of fun and we preferred it over the typical setup where engineers just work through specced tickets without ever talking to the customer. When hiring our first engineers, we decided to offer the same way of working to everyone. No "code monkeys" at Kombo. That’s how we came up with what we call "Product Engineering" today. Today, this means that you will take holistic problems of our customers, join calls (or even visit them), design a solution to their problem, implement it end-to-end, and support it until the first users are using it successfully. You will talk to the customers, write RFCs, implement a solution, deploy to production, and enable the first customers to use it. You will take their feedback into account and improve the feature. Depending on your seniority, you will be supported by a PM and/or senior engineer. We optimized everything across the stack so that a single engineer is enabled to own and execute the feature end-to-end. That’s why we have a single programming language (TypeScript), a monorepo and have trunk-based development (on average, we release more than 50 times per day). Our teams operate like small startups inside a startup. They prioritize initiatives within their team and decide themselves how they work. Our teams usually consist of 1 product manager and 3-5 engineers. Over the next year, we will open up 3 new teams to capture new bets and are looking for entrepreneurial engineers who will drive those bets forward with high ownership or potentially lead those teams. I created a write up on this topic some time ago: What Product Engineering at Kombo Means https://kombo-api.notion.site/What-Product-Engineering-at-Kombo-Means-2f06526d848a805094c9e881a978403e THINGS YOU WOULD HAVE DONE AT KOMBO IN THE PAST - An AI agent https://docs.kombo.dev/ai-apply#ai-apply that parses arbitrary job postings from the web and makes them instantly applyable via API (built by Cornelius https://www.linkedin.com/in/corneliusrenken/). - A full observability stack https://docs.kombo.dev/ats/guides/debugging/introduction with logs, unified error codes, and analytics dashboard for debugging integrations (built by Johannes https://www.linkedin.com/in/jokaufmann/) - The new LMS integration category https://docs.kombo.dev/lms/introduction from zero to one, designing the data models, building a framework, introducing a new infrastructure primitive (built by Antoni https://www.linkedin.com/in/xxczaki/ and Alex https://www.linkedin.com/in/alexander-gerick/). - Real-time data syncing system https://docs.kombo.dev/ats/guides/upstream-webhooks through inbound and outbound webhooks (built by Felix https://www.linkedin.com/in/wotschofsky/) THE ENVIRONMENT AT KOMBO We are building the backbone of our customers' products. Hundreds of companies build their products on top of our API. That means if we design the wrong product or go down, hundreds of customers will have a major issue. We are very considerate about balancing where we can move fast because of cheap and reversible decisions vs. where we need to be extra diligent because of expensive one-way doors. We are building an API product, therefore we need to avoid breaking changes early. We put high emphasis on focusing on the most important thing and doing that very well. That comes at the tradeoff of sometimes moving slower on projects to do them well, delaying promises with customers, or letting many small fires burn in order to get the most important thing done. We always try to uncover what customers actually need, not what they ask for. We take high ownership of actually solving the problem for our customer, not just shipping a feature to spec. If you launch a feature and see that it's not solving the problem yet, it's your obligation to bring that up and improve the feature. We are living a culture of caring candidly at Kombo. Being honest and direct about the feedback you give and receive, while actually caring about the success of others and you