Ask HN: Do multiple short stints in startups hurt even if you've learned a lot? I’m trying to get an honest perspective on how hiring managers evaluate candidates with startup heavy experience and short tenures. I have ~4.5 years of experience as a software engineer, mostly in early-stage startups. My path looks like this: Startup 1 (~1+ year): joined early, worked closely with the founder, learned a lot across product and engineering, but the company shut down due to funding Startup 2 (~1 year): contract role where I worked on scalable systems and LLM-based features Startup 3 (~1 year): joined full-time, built real-time systems, but the role ended due to restructuring In each case, the transitions were driven by company-level issues rather than performance. I also have strong references, including founders I’ve worked with who are willing to vouch for me. Early in my career, I intentionally chose startups to learn quickly and take ownership across the stack. I feel that paid off I’ve built and shipped real systems, worked on real-time infrastructure, and contributed to production products. Now I’m at a point where I want to focus on stability and long-term impact, and I’m being much more deliberate about the companies I evaluate. However, I recently got feedback that multiple short stints create a pattern and raise concerns about judgment and stability. I’m trying to understand: Does strong learning and ownership in early-stage startups offset concerns about short tenures? How much do references (especially from founders) actually help in reducing perceived risk? At what point do short stints become a real red flag vs understandable given startup volatility? What signals would make a candidate like this feel “low risk” again? I’m continuing to focus on improving and being more intentional about my career going forward, but I’d really appreciate honest perspectives from people who’ve evaluated or hired candidates in similar situations. |