I had an interview with this company.<p>Their website is basically a mostly subscription-based ecommerce CMS, for physical products.<p>They have a lot of clients, but there doesn't seem no need anything remotely complicated on the website<p>The company is almost 10yo.<p>Does that make any sense to you?<p>Could it be terrible management/devs?<p>Or just some hidden complexity that I'm not seeing?<p>I'm pretty sure there is shopify websites more complicated than that made by one guy.
The two key take always here are:<p>* lots of clients (their needs might differ considerably from each other. So it’s not unreasonable to assume an FTE per client or two)<p>* is there a dedicated design, et al team or are you, the developer, expected to wear multiple hats. Like CMS patch management, managing inventory updates, design / formatting the image assets etc.<p>Even CMSs like Magento can be a multi-person exercise to put live. And while there is down time between updates to the CMS (whether that is backend or frontend changes), that downtime could easily be absorbed by other clients in a multi-client eCommerce web shop.<p>So having 10 engineers doesn’t sound unreasonable but if you’re worried you should definitely ask what an average day is like in that role.
I work in a business that looks super easy on the outside yet full of case studies that could go into business books. Don't run on assumptions. Ask those questions.
What a normal day for a dev looks like?<p>Can you meet the devs and discuss their workflow?<p>What's the backlog like?<p>These should give you some good indications
Depending on the extend of the project, it could be. Do the devs offer maintenance support, does the company use a "unique" ERP? Is there middleware involved to sync store and product info?<p>I am no webdev, but I would not want to develop such a project alone.