Pros
+ Senior engineers/team leads are exactly what a budding engineer could hope for: patient, knowledgable, and willing to lend insight both in matters in and out of scope for their respective teams. + Tech stack includes modern languages/libraries (React + TS, Apollo Client/GraphQL, and Golang among the primary tools used for new feature work). + Dedicated architecture team meant to pay down the legacy monolith's tech debt and optimize the programming experience for other engineers! + Consistent acknowledgment of experience/growth (Jr., SE I, SE II, etc.) and internal focus for leadership opportunities (i.e. team lead).
Kontras
- Agreement with leadership (including Product and Product Marketing) on goals and/or timelines for feature delivery can be unrealistic at times, on occasion flat-out implausible (this is a pain-point that seen some improvement over time, I will concede). - C-Suite leadership has a heavy influence on project direction, on occasion causing sizeable pivots while planned work is mid-stream. - Code-level testing needs to be prioritized more. Even modern features have sporadic coverage of varying degrees of quality - Some sort of dev team building or on-the-job growth opportunities would be nice (i.e. 10% time, company hackathon).