Pros
Work schedule is flexible due to the international nature of the company Good opportunities for learning how to integrate AI into your own work but expect to do so on your own.
Cons
1. Heavy top-down push to adopt AI tooling without corresponding engineering guardrails. Usage is encouraged to the point of being an expectation, but there is limited guidance on where AI is appropriate vs. where traditional design/review rigor is required. 2. Evidence of reduced code quality in some areas (e.g. concurrency issues like improper mutex usage, including api/network calls executed inside lock scopes, and overly synchronous API designs) making it through review and into production. This appears correlated with over-reliance on AI-generated implementations without sufficient validation. 3. Increasing discussion of AI-assisted code review/merge processes without clear ownership or accountability models. 4. Frequent all-hands meetings with limited relevance to individual teams. A significant portion of these are focused on promoting AI adoption rather than addressing team-specific engineering challenges. 5. Leadership will simply lie to you or sugar coat things into oblivion to the point where their statement is on the line of truth and fiction. Was moved to another team after volunteering when told it would be a temporary allocation of resources. The end of the timeline comes and I am told there are no plans to transfer me back, despite the other product being alive and well. I would not have volunteered had I known. 6. "AI First, Requirements Second" atmosphere for some internal projects. Frequently told that there is no time for refinement of requirements for developer understanding, prodding, etc but then we will turn around and have time to reimplement the same thing that we did incorrectly the first time due to not refining in the first place. Company pretends to have a centralized process but it is very much the wild west depending on team you are on. 7. New applications in development to replace old ones, but they are largely the same broken core with a "fresh coat of paint" to "fix the reputation of the company". Resources are allocated to completely change front end frameworks instead of fixing critical API level bugs that would resolve the issues that prompt new project initiatives.