⚠️ This post links to an external website. ⚠️
There are many ways to set up a startup software engineering team, and many teams follow the same progression and encounter the same issues. In this article I’ll do my best to showcase the different options and their limitations.
Note that there is no perfect organisation that will work for all situations… only tradeoffs and choices you’ll have to make depending on your circumstances. I’m not showcasing the logical progression. Instead I want to highlight how a team organisation can progress over time when facing limitations of each step.
For our example, let’s assume we have a post series A startup building a B2B SaaS with 18 engineers, 3 PMs and 2 product designers. To ship the product, they need backend, frontend as well as native mobile apps. They have some infrastructure work, but as they are mostly on the cloud they don’t have anyone fully dedicated to this just yet. Apps are standard native apps (Swift, Kotlin), frontend is one SPA with React and the backend is a NodeJS monolith.
continue reading on marcgg.com
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.