Situation: Joining an established engineering team as a Senior Engineer can create anxiety if teammates worry you intend to immediately criticize their codebase or impose rigid external opinions.
Task: My goal during my first sixty days was to build authentic trust, listen deeply, and earn credibility through humble contribution before proposing major architectural changes.
Action: I adopted a 'listen, learn, and deliver' roadmap. I scheduled 1-on-1 listening sessions with every engineer, asking: 'What is the most frustrating part of your daily development workflow, and what are you most proud of in this codebase?'. I took on unglamorous bug fixes and on-call rotations to experience their daily operational friction firsthand. I resisted the urge to criticize legacy code, recognizing that earlier trade-offs were made under past constraints. When I did propose my first architectural improvement—automating our flaky test suite—I framed it around solving the pain points teammates had voiced.
Result: By focusing on solving their daily pain points rather than asserting authority, I established deep mutual trust. Within three months, the team enthusiastically endorsed my proposal to modernize our core API architecture.