The following is based on being on the same team the past several quarters. On paper web seems like a company where the development process works great, but in practice it slowly breaks down for outsiders who haven't worked at the company for years.
Web pushes many development patterns to the point where junior developers end up falling in love with the idea of them and implementing blindly without thinking about code duplication/implications for actual system use. Junior developers will typically cycle on ideas, implement non-reusable code due to the pushing of those patterns. Key words tossed around quite a bit "domain driven" and "anemic", but other principles of patters are often forgotten. Architects are supposed to help with larger code reviews/questions, but often time you'll wait months for simple decisions.
Development environment has multiple issues per month that completely stops development from occurring due to access issue.
Microservice architecture was attempted, but no one steps back to ever ask is this the right decision. A simple call to retrieve order data may be 10 plus different web requests plus multiple unique db calls as putting calls together is frowned upon (imagine searching for data in one call and returning paging information in a second db call rather than just a 2nd dataset).
Nearly every item you work will go through Development, DB Development/Review, Peer Review, QA/Review, AT, and release. Many of the groups inside of that have large backlogs due to being shared. Not a problem at most places, however quarterly dev refreshes mean you'll end up duplicating all efforts to get environments working again.
Managers will consistently talk about how "no one is looking at your numbers", but then in the next sentence stress how we need to start tracking time on items but give 0 guidance on what type of tasks need tracked.
Teams are often required to figure out how to implement policies (i.e. we're implementing tasking, no one from the top has guideline--figure out what you want to track). Meetings, meetings, meetings. Meeting to estimate time a task will take. Meeting to assign an effort. Meeting for team members to be caught up. Meeting to review issues for the week. Meeting to pre-refine items.
Speaking of meetings, you'll sit through many where no one will make a decision. Teams leads aren't educated enough on the project/have enough real-world experience to move items forwards. Managers will take months to get simple tasks done and push decision making back on developers. Reviews/PBIs will end up in the air due to the lack of decision making.
As a developer, you'll be responsible for creating the PBIs for work, yet you'll get many tickets that having incorrect details, 0 requirements, and wrong Acceptance Criteria. You'll also have a Project Manager and Technical Project manager on your teams giving high level asks.
During interview was told there was very little ColdFusion code, but end up spending the bulk of the time in ColdFusion in VSCode, but don't expect any of the standard CF tools to work correctly (no breakpoint debugging or easy stack tracing--everything is in docker).
Very little intra-team communication. You'll feel like you are working on an island the bulk of your time here.
Call rotation that won't be brought up until after you start.
Very few company holidays (5 to 6). Little PTO for the tech group.
When the end of the day comes, don't expect any help. Teammates will leave right on time even if there is a major issue.
If you are a developer who enjoys working on an item as written and being able to complete work, move on. This place will slowly kill your joy of engineering.
