Manager README

This document is intended to help us skip the “guessing game” of a new working relationship. It’s an open RFC on my leadership style—I invite your feedback on it.

My Philosophy: The Multiplier Mindset

I believe my success is measured by your output and your growth, not my individual technical contribution. I view my role as a Systems Designer for the team. My goal is to build an environment where engineering excellence is the default and friction is the enemy.

How I lead

Multiplier Mindset: I am here to clear the path, not to hold the map. I prioritize high-leverage activities that unblock the team.
Clarity over Control: You will rarely hear me tell you how to code. I focus on providing the “Why” and the Context so that you can own the technical execution.
Process for Flow: I value “boring” (stable) systems. If a meeting or a process isn’t helping us ship high-quality work faster, we should automate, delegate, or delete it.

What You Can Expect From Me

High Support, High Challenge: I care deeply about your career. That means I will support you relentlessly, but I will also challenge you to step outside your comfort zone.
Transparency: I will share as much context from the “upper levels” of the organization as I possibly can to help you make better local decisions.
Availability: My calendar might look full, but you are my priority. If you are blocked, “ping” me. I value async communication but I’m always here for a 1:1.

What I Expect From You

Ownership: If you see a “broken window” in our ecosystem or our process, don’t wait for permission to fix it or raise it.
Directness: If I am doing something that is slowing the team down, tell me. I value honesty over hierarchy.
Documentation: If we discuss a strategy or a complex decision, let’s write it down. A “One-Pager” or an RFC is our best tool for alignment.

Logistics & Communication

1:1s: This is your time. I’ll always have topics ready, but the agenda starts with you.
Async First: I try to protect “Deep Work” time. I don’t expect instant replies to Slack messages unless it’s a P0 incident.
Feedback: I don’t believe in waiting for performance reviews. I strive to give and receive feedback in real-time.

Note: This is a living document. As the team scales and the DeepL Ecosystem evolves, my approach will adapt. Let’s keep the conversation going.