# Ido Tulman's Manager Readme

**Engineering Manager at Klear - Influencer Marketing Business Unit, Meltwater**

# Logistics & Availability

### ⏰ Working Hours

- **Flexible/Async** - I work asynchronously and don't expect immediate responses. I value focus time and deep work. I do expect to get async statuses as dailies, sprint status etc in order to be aware and get involved when needed. 

### 💬 Communication

- **1. Slack** - My go-to for quick questions and team discussions.
- **2. Video Calls** - I prefer face-to-face video calls for complex or nuanced conversations.

### 📅 Calendar

- **1. Ask First** - Please send me a quick message before booking time on my calendar.
- **2. Transparency** - My calendar is open so you can see my current focus. I will always suggest alternatives if I am booked when you need me.

# Feedback & Growth

### 🎯 Feedback Style

- **Radical Candor** - I believe in direct, honest feedback delivered with genuine care.
- I provide feedback both on an ongoing basis and at the end of every quarter.
- I am always open to receiving feedback - please don't hesitate to share yours with me.

### 🤝 1:1 Philosophy

- We meet every quarter following our established format. I am here to listen and help you and the team accelerate.
- I believe proper preparation for these meetings is valuable for both sides.
- Setting goals with clear KPIs and target dates is essential for personal growth. When possible, I prefer face-to-face meetings for more personal interaction.

# Values, Quirks & Pet Peeves

### ⭐ My Top Values

- Proactiveness, Transparency, Continuous Improvement, Growth, Ownership, Accountability, Teamwork, Thoroughness, Quality, Curiosity, Kindness, GSD (Get Shit Done), Initiative and Knowledge Sharing.

### 🐛 Known Bugs

- I occasionally let discussions run longer than expected. Please feel free to interject if we need to conclude or schedule a follow-up.

### 😤 Pet Peeves

Mediocrity, lack of ownership/accountability/Thoroughness, bringing up a problem without a specific recommendation, Surprises.

# 

# How We Build Together

### 🗺️ Feature Planning

- **Feature Lead**  - You own features end-to-end, from design through release.
- Depending on the complexity, we may assign a technical mentor to support you.

### Task Prioritization

- We maintain a balance between delivering product value and investing in technical debt/work that ensures long-term speed and quality.
- If you believe something is important, I am happy to discuss it and reprioritize if we agree on the impact.

### Project Alignment

We align early on goals, scope, risks, ownership, and success metrics before execution begins.

### 🚀 New Initiatives

- **Pitch Me** - Write a brief proposal so we can align on the "why" and "how" before you dive into the code.

### ✅ Definition of Done

- Released to Production, tested, and measurable.
- In full accordance with the agreed-upon design.

# 📌 What I Expect (Practices)

- **[Avoid Meeting Fatigue]** Whenever possible, prefer async communication (daily Slack updates, async sprint planning/status). Your time is valuable!
- **[Knowledge sharing, Communication]** Sometimes, it's better to update the team asynchronously via Slack for "context freshness".
- **[Communication, Transparency]** Use public Slack channels rather than private threads to keep information accessible.
- **[Continuous Improvement]** Add to the "Better Next" doc whenever you recognize an opportunity for improvement.
- **[Incident Prevention]** When an incident occurs, focus on what we can change to prevent it (or similar) from repeating.
- **[Retrospectives, Continuous improvement]** Leverage retro meetings (Sprint, Hackathon, or Project retros) as a primary tool for team growth.
- **[Knowledge Sharing]** Use Tech Sessions to share interesting findings and initiate meaningful engineering discussions.
- **[Proactiveness]** Suggest technical priorities for upcoming sprints or roadmaps based on our pain points and infrastructure limitations.
- **[Pro-Activeness, Ownership, Knowledge Sharing]** Always think about how we can improve as a team. For example: identify **knowledge silos** and document them to share the expertise.
- **[Accountability, Transparency]** Use production incidents or personal setbacks as opportunities for growth. Sharing these with the team helps us all learn and stay comfortable making (and fixing) mistakes.
- **[Teamwork]** Empower each other. Offer guidance through async reviews, but prioritize "enablement" via pair programming and deep discussion when needed.
- **[Big Picture Thinking, Ownership]** For every feature, consider the wider impact: product value, performance, cost (AI in the loop? 🙂), monitoring, and measurability.
- **[Early Alignment, Communication, Transparency, Decision making]** If you face a technical dilemma or notice things aren't going well, share it early. Move independently when the path is clear, but consult the team for brainstorming or direction.
- **[Preparation, Communication, Thoroughness]** Always include an agenda when scheduling a meeting or discussion.
- **[Symbiosis, Teamwork]** Recognize the unique strengths in your colleagues and leverage those advantages to create a stronger team dynamic.