Strong product, but challenging for senior engineers without documented system architecture - Senior Engineer AVEVA Employee Review

- Core product architecture, deployment flows, and system-level design documentation were either missing or not easily accessible - System knowledge appeared to be concentrated with a small number of individuals, creating high dependency and knowledge silos - New or incoming senior engineers were expected to make system-level impact without being given sufficient system-level context - 1:1 feedback focused heavily on outcomes without addressing gaps in documentation, onboarding, or shared architectural understanding - Knowledge transfer relied more on informal channels than on durable, written documentation - Raising concerns about missing architectural clarity or systemic risks was not always received constructively, and there was limited psychological safety to openly question system-level gaps. - Escalation paths beyond immediate manager were limited or none, and access to skip-level leadership for clarification or support was not clearly established.