1.6The Reputation Framework

Your reputation in a new organization is built in concentric circles.

Week 1: Your immediate team. They see everything: when you arrive, what questions you ask, how you respond to feedback, whether you listen more than you talk. In the first week, optimize for one thing: demonstrating that you are thoughtful and observant. Ask good questions. Take notes. Do not volunteer opinions about what should change until you understand why things are the way they are.

Week 2-4: The broader engineering team. Your first pull requests, your first bug reports, your first test plans -- these form the second circle. Quality matters enormously here. A single sloppy PR or a bug report that wastes a developer's time can set your reputation back weeks. Conversely, a well-written bug report that saves a developer an hour of debugging builds trust fast.

Month 2-3: Leadership and cross-functional partners. By this point, your manager is forming opinions about your trajectory. Product managers are noticing whether you ask insightful questions about requirements. Designers are noticing whether you catch UX issues that others miss. These impressions solidify quickly and change slowly.

The core lesson: before writing tests, understand the system. The system is not just the software. It is the people, the processes, the politics, and the culture. Understanding all of it is not optional. It is the foundation on which everything else in this book -- and in your career -- is built.

Core Level 0 Question: When you start a new role, do you rush to prove yourself by producing output -- or do you invest in understanding the full system first?