I don't think either of you is necessarily wrong (or good/bad here). They prefer to work the way they work (glaring issues and all), and are apparently successful working that way. You don't want to work that way, and want a role where you're not just crunching tickets (even if you could work that way). Just sounds like a bad fit to me.

For next time: it's really easy to accidentally ruffle feathers if you come in and start proposing tooling or process changes. People get attached to their project if they've worked on it for a while, and can take observations from an outsider as judgemental or an attack, regardless of how valid those observations are (many of yours seem valid to me). You coming from big tech can make people even more sensitive to this (if you're triggering their latent impostor syndrome or whatever as someone from a prestigious company). The way you summarize your manager's feedback makes me think that you either rubbed him the wrong way or offended some more tenured people who complained. Kind of hard to undo that now, but helpful to keep in mind for the future. If you demonstrate that you can hack it on tickets as you ramp up and establish some trust with your teammates over a few months, you'll typically have an easier time with this type of stuff.

(I would normally add a caveat that another good reason to wait a bit before bringing stuff up is that you might be missing the bigger picture, and that can help you ensure that you're actually arguing for useful change. I omit it for you because "we should have any observability at all for our production application" seems pretty uncontroversial to me and doesn't make me think you're out of touch or focused on unimportant things)

Time to decide if you want to stick it out while trying to find work and explaining the short job, getting fired (might be eligible for unemployment), or quit.

Some startups are run by cowboys/cowgirls. They don't care about anything other than features until everything falls apart or they rebuild in a nightmare sprint.

I've been at one of these. You will fail to change them even if you stay for 3 years. You risk getting fired if the CEO realizes the mess and hires in someone to fix it. Your manager is already thinking about firing you.

Sounds like they have an established culture that works for them and you are feeling like you might not be a good fit. The Manager had a 1:1 with you to make sure you stay in your lane and it sounds like they just want someone who will do their assigned tickets. You'll need to decide if it's the role, environment and culture you want.

undefined

Do you want to work in a startup or big tech? This is most big tech for you.

For sure - this is a burning house, do what you can to land on your feet but it's a waste of time to invest anything into it.

I think you know the answer. Trust your gut.

Apply for new jobs immediately. In the meantime do 1 pr a day.

You won’t grow there. This shouldn't be normalised as acceptable engineering.

Terrible code quality is standard at startups. Not being trusted to fix it is not. Run.