Pros
- nice, smart people - interesting projects - a vision for the future - good pay - remote friendly
Cons
- terrible communication - not really agile, only pseudo-agile - shifting expectations, e.g., a release kept getting pushed out over 8 months (looks like it still hasn't released) because the definition of the MVP changed at least once a month - there was one feature that was not in the original MVP, then added, then removed, then added back in - and then they'd complain that the deadline wasn't met - I never once saw a user story or an acceptance criteria - not once. Often all we'd get is a sketch of the component without any explanation. I had PRs rejected for "not meeting acceptance criteria" - I begged to see the acceptance criteria - they just ghosted me. This happened over and over. It is ridiculous how often I couldn't get a simple answer to a simple question. I had PRs rejected in QA because the designs changed *while it was in QA*. Insane. - It was very difficult to know who to talk to in other departments. Often I'd have to wait a week for an answer to a question that was blocking me. - Sometimes there was a lack of focus - one week, story A was the most important thing. Oh wait, stop that, go work on this other app! Oh wait, that's not important, half of you work on Story A and the other half work on something else... - back on planning, we had a big drive to get a big release ready. OK, we have x number of devs and y amount of work, so we estimate that it will take z number of sprints. But then the release definition changes, and devs get pulled of for other things, a sprint here and a sprint there, we lose a week waiting for a design to be clarified - then we get reamed because the estimate was off
