Its a small firm and these are not uncommon issues. The size of the firm means that likely the focus of the CEO is to bring in the next client, not worry about

Its a small firm and these are not uncommon issues. The size of the firm means that likely the focus of the CEO is to bring in the next client, not worry about whether there is a development server setup properly. A lot of the times, these are the exact reason he has hired someone that knows their job. He isn't going to want to know about all the little details, he just wants everything to work so he can sell. And the feature he has you working on may be critical, as he sees it, to land a client or give existing clients something new. My 2 cents. Don't judge everything just from 2 weeks. All of your issues are valid, but give yourself a little time to acclimate to the team. Gain their respect, gain the CEO's respect by showing you can do the job and take care of details. Take some of these issues you highlighted and fix them. Add automated testing for your new feature, add documentation for it, setup a quick monitor to alert when the API goes down and learn the development setup so you can fix that process. In fairness most of these issues show a lack of development leadership so be the leader. Don't try to convince the CEO why you need to do these things, just do them and the results will speak for themselves. Do yourself a favor first, get the respect of the team by playing along and getting the feature done and do it with proper process and documentation. That'll go a long way. In the end, you may hate it and need to leave, but give yourself a chance to see if it is systemic issues, or just a lack of development leadership. I have seen many times when a small business CEO tries to control development because he doesn't have anyone strong to do it. Usually this is because he doesn't trust the results from the team totally because of things like an API going down and it takes a customer call to fix it. Why else would he have hired an "outsider" to run the team? He doesn't know what he doesn't know. Show him through doing and see if it changes, if not, move on.