Technical Lead / Senior Engineer for Growing SaaS product

Technical Lead / Senior Engineer for Growing SaaS Product I’m looking for an experienced senior engineer who can become someone I genuinely trust on the technical side of a growing SaaS product. We already have a working product and developers actively building it. I’m not looking for someone to come in and rebuild everything, and I’m not looking for another developer who simply waits for tickets. What I’m missing is someone who can look at what we’re building, review the code and decisions being made, catch problems I may not see myself, and help make sure we are building things the right way as the product grows. I’m very close to the product and I know where we want to take it. What I’m looking for now is someone I can trust on the technical side, someone who can challenge decisions when needed, help the developers move in the right direction, and give me a clear answer when something is uncertain. Our current stack includes: - Next.js / React / TypeScript - Supabase - PostgreSQL - Supabase Auth and RLS - Stripe - GitHub / pull request workflow Strong experience with this stack, or something very close to it, is important. Experience with HR tech, recruiting technology, employee experience, people analytics, or another HR-related SaaS product would be a plus, but it is not required. The role will involve reviewing important code and pull requests, helping guide the existing developers, thinking through architecture and technical tradeoffs, helping us estimate and prioritize work, and stepping in when there is a technical blocker or an issue that needs senior judgment. You should still be comfortable getting into the code yourself when necessary. At the same time, I’m not hiring based on who can write the most code the fastest. Communication may actually matter more to me in this role. If a developer is blocked, something unexpected happens in production, or I need to make a technical decision, I need to know I can reach you and get a clear response within a reasonable amount of time. I don’t expect anyone to sit in front of Slack all day, but long periods of disappearing or delayed communication will make this difficult to work. I also value someone who can explain technical issues without making everything unnecessarily complicated. If you disagree with something we are doing, I want you to say so and explain why. If there are three possible solutions, help me understand which one you would choose and what we are trading off. I would prefer to start with a defined paid milestone so we can both see how well we work together. The first step would likely involve reviewing the current codebase, understanding where things stand, identifying anything that deserves immediate attention, and beginning to work with the existing developers. If the relationship works well, I would like this person to become increasingly involved in the product and eventually take much broader ownership of the technical side of the company. I’m looking for continuity, not someone I have to replace after one project. When applying, please tell me briefly about a product where you were responsible for technical decisions beyond your own individual coding work. I’d especially like to know how you worked with founders, product people, or other developers and how you handled situations where something was going wrong technically. If you’re comfortable doing so, feel free to include a short Loom video introducing yourself and explaining why you think this role is a good fit. It’s completely optional, but I’d be happy to watch it. Please write to me in your own words. A short and thoughtful proposal is much more useful to me than a long generic one. I will personally read every proposal submitted for this job. I’m not planning to choose someone based on who applies first, so take the time to tell me why you think this particular role fits you. I want to find the right person, not simply fill the position quickly.