# Peleg Bahar's Manager Readme

**R&D Director at Viber**

# Motivation for this document

When I came across this tool it was clear to me that I must write my own README.&nbsp;

This document will allow you&nbsp;to better know me, my beliefs and my expectations so we can work better together.

This document will not replace any of our interactions. It is intended to give you an overview of how I think and act.

# My role

I lead the R&D organization in Viber's Core Unit. The group contain&nbsp;software engineers, quality engineers, tech leads, project managers,&nbsp;team leads and directors.

I'm here to create an environment that will allow my teams to create the best software available, while always considering their personal wishes and career goals.  
  
**Deliver**  
Deliver. Always.  
Delivering a product in time, and at the best quality is super important to me.  
I will give you all the tools to support that. I will provide context, the big picture, clarity, prioritization, full cooperation and more.  
  
**Help you grow and thrive**  
I want to make sure&nbsp;you are enjoying your work, learning, having a fun team to work in and have a clear personal-progress plan.  
I'm here to listen. To whatever you feel like sharing. Whether&nbsp;it's work related, home related or just a funny joke :)

**Professionalism**  
Software development is a field that is constantly evolving.  
To stay relevant, you must learn and improve your skill set on a daily basis.  
I will ask you to constantly&nbsp;learn and be better at what you do. I will also ask you what you need in order to do that.  
I will provide you with the guidance, courses and any other tools to support that.

But note - it is your responsibility to act and work for improvement!

**Data driven**  
Data collection is very important to me and I believe that we should act upon real data.  
This is true&nbsp;during the sprint, during sprint demos and especially while attending the retrospective.

I believe in setting goals and KPIs. Data is key to understand if we are on the right path to achieve our goals, or if some adjustments are required.

I will always share the data and KPIs we are collecting and I expect my team to think of more data points we should be monitoring, on our path to become a better team.

**Make a positive influence**  
As a manger, I'm always looking for opportunities to do more to improve my surrounding. From better food in the kitchen,&nbsp; shuttles, mastery portals and volunteering in the community.

In a sentence - "I'm here for you". Let me know how I can help you

# What do I value most?

**Accountability**  
When you're working on something, I know that you will do the best you can to get the job done. No matter the cost. If you need someone, get them to help you. If you need help, make sure you get it.  
If you hit a wall, come and see me. I will help you craft a hammer.

**Ownership**  
A software engineer today has a much bigger role than just writing code. Our responsibilities are to design it, think how it will affect our users, test it and deploy it to production. You are expected to take end to end ownership.

**Taking&nbsp;initiative**  
When you see something that can be done better, when you read about a new technology that we can leverage, or when you have an idea of how to improve our team-work - act on it!  
Share the details and let's make a change.

**Transparency&nbsp;**  
In order to succeed as a team, we must share as many details as we can with each other. You should do it in the daily stand-up meeting, in team meetings or in private.  
I will share information with you. I expect you to do the same.

**Team player**  
We work together to accommodate the needs of our product and users.&nbsp;  
Respect your teammates, actively listen to them and share your thoughts and ideas.

# My Expectations

Enjoy your work and be proud of what you do! This will generate great success.

Be positive.&nbsp;

Don't be afraid of changes.&nbsp;

Done is done. Make sure you complete your work and don't leave loose ends.

Test your code. It is your responsibility as a software engineer. Automate your tests.

Look for opportunities to evolve.

When things are good tell me about it. When things are bad tell me about it. I promise to do the same.

You might get an email from me at odd hours, but&nbsp;you can respond when you get to work.  
When it's urgent I will call.

# 1:1s

We will have a periodically&nbsp;1:1 meeting. However, my door is always open. Feel free to come by with every issue you might have. Don't hold back.

During our 1:1 meeting I want to hear about you. Are there any issue? What were your major successes lately?  
Are you enjoying the project, the technology, the people?   
What are we doing good as a team and what should we improve?  
What else would you like to do?

I will normally lead the talk, but feel free to come with your own agenda.

At least once a quarter, we’ll talk about your long-term career development, but we may monitor our plans more frequently.

# Personality quirks

I LOVE a successful release. I love to celebrate all the team's successes. I'll bring the cake&nbsp;:)

On meetings be&nbsp;attentive. Don't play with your phone or read emails. If you have nothing to contribute you are excused,&nbsp;just let the organizer know beforehand.&nbsp;