# Tanmaya Kulkarni's Manager Readme

**Senior Engineering Manager at Henry Schein One**

# Motivation for this document

The document aimed for my direct and indirect reports as well as my peers to understand who I am and ways to collaborate effectively with me. This is a living document and gets updated as I mature myself.

# About me

I’m a Software Engineering Manager with 20+ years of experience in building and delivering business-critical solutions. I hold a Computer Engineering degree and spent 12 years as a hands-on full-stack developer before transitioning (accidentally) into engineering leadership. Since then, I’ve built and shaped high-performing engineering teams, consistently delivering against tight deadlines by adopting fit-for-purpose Agile methodologies.

Here at Henry Schein One, I lead multiple global engineering teams in the Financial experience group, delivering products across Canada, the UK, and Australia.

Previously, I worked with Xero, NHBC, Airbus, Infosys, and Persistent, gaining a breadth of experience across industries and technologies.

On a personal note, I have a wonderful husband (also in the same field) and teenage twins who keep me on my toes. When I’m not at work, I’m usually playing taxi driver—shuttling them to various activities!

# About my leadership style

I’m a people-focused leader who believes in empowering teams through autonomy and flexibility. I’m outcome-driven and trust you to choose the right path to achieve results.

I believe in give and take. You’ll have the flexibility to plan your day, but in return, I expect a strong sense of ownership and accountability. You don’t need my permission to attend a doctor’s appointment, but I do appreciate being kept in the loop. In return, I trust that you'll manage your time responsibly.

I have an open-door policy—feel free to reach out anytime, whether it’s for support, feedback, or just a chat. You can expect timely, honest feedback from me, whether through Slack or during our 1:1s. You won’t be blindsided during performance reviews—if there’s a concern, I’ll raise it early.

As a software engineer myself, I love engaging in technical conversations. Whether you want to brainstorm, debug, or talk architecture, I’m more than happy to jump in—even if it's just for some good old-fashioned rubber ducking!

# My expectations from you

- **Ownership and accountability:** If you’re stuck or facing a blocker, don’t wait for someone to ask—be proactive and speak up.
- **Think like a product engineer:** Be curious about the _why_ behind the feature. Understand its purpose, and always look at your work through the customer’s lens.
- **Be courageous:** Don’t hesitate to voice your opinions or challenge the status quo. I’d much rather hear your concerns than see silent agreement.
- **Work iteratively:** Avoid over-engineering or endlessly polishing. That delays value delivery. Instead, focus on building a solid MVP and refine it as we go. Remember—_the world always remembers the first person to step on the moon_.

# 1:1s

**1:1s are not status update meetings.**  
They’re dedicated time for us to connect beyond day-to-day work—to understand your goals, motivations, and challenges. We’ll use this time to share feedback (both positive and constructive), discuss areas for growth, and help you develop as a professional. These conversations are confidential unless there's a serious issue that requires escalation.

I also welcome feedback about myself—your input helps me grow, too.

To make these sessions effective, I prefer having a shared agenda. I encourage you to add at least one topic before each meeting so we’re making the most of our time.

**A typical 1:1 agenda might look like this:**

- Light check-in or icebreaker
- How are you doing—personally and professionally?
- Agenda items from both of us
- Any blockers or areas where you need support
- Feedback exchange

I recognise that one size doesn't fit all. We’ll agree on a 1:1 cadence that works for both of us. Early on, we might meet weekly and reduce the frequency as we establish a rhythm.