Are you the only "Engineer" or the only "Full-Time Engineer" (i.e. employee)? First, neglecting meetings is a huge miss. If you believe they are unnecessary, i

Are you the only "Engineer" or the only "Full-Time Engineer" (i.e. employee)? First, neglecting meetings is a huge miss. If you believe they are unnecessary, it's your responsibility to explain why, and to provide a work-around to your other team-members so they can get what they need. Second, your question about production ready vs hackathon is a classic tradeoff with startups. There was missmanaged expectations around creating a Minimum Viable Product, vs a production ready system. Somewhere your team and yourself did not have aligned understanding of what was being delivered. Third, did you speak to your team about their perceived value of things like meticulous ticket tracking, well maintained rep, monitoring etc? Those things do matter in the long term, but reductively in the short term, unless your business is going to generate money from your issue tracking work et al, it's a waste of time. Ultimately it comes down to your ability to make the case as to why the time spent on the work you did, ultimately impacted the business at it's current state. From what you wrote, while you weren't slacking off, you spent a non-trivial amount of your time on things that were not of value to the business. Did you have anyone on your team with startup development experience?