Mentors are responsible for: 1) providing technical guidance, 2) reviewing code contributions, 3) ensuring delivery of tasks, and 4) meeting regularly with mentees. Effective mentoring includes: orienting new hires, providing initial minor tasks, reviewing work, testing deployments, explaining processes, and assessing understanding and motivation over time. Regular check-ins help mentors address challenges, provide support respectfully, and ensure mentees feel connected to the work.

1. Mentoring

2. Mentor Responsibilities
1. Technical mentor
2. PR & functionality reviews
3. Deliverables
4. regular 1x1

3. First day
1. Send intro email
2. Set expectations on communication mediums
3. Architecture overview
4. Help local setup, including fyle-baap (very important to get them a win here)
5. Explain PR review process, including squash merge
6. Provide all Blockers information
7. Don’t share critical credentials or repos

4. First task
1. Very minor bug fix or improvement
a. you already know how to fix it; <10 line code change;
2. Say the problem; not the solution.
3. Send mail about first commit.

5. First deploy
1. Test before (on staging) and after the deploy (on prod)
a. Have a list of test cases around the changes
2. Be available at the prod deploy time, if your changes are going out
3. List out the p0 features in the module they are working on
4. Communicate the levels of the bugs & their importance

6. Testing first (and further) releases
1. Mentor to explain test cases properly.
2. Ask themselves to test as a user.
3. Mentors to test themselves & give green.
4. Get time from modules experts to test.
5. In case of new feature, include more people to test

7. Good practices
1. Make them connect with the task
2. Approaching to solution
3. Agreeing on the solution
4. Check motivation levels
5. Interaction levels
6. Day off - if you are off for a day or more, let people know about it. Also inform whom to
contact to and provide a handoff to another mentor before leaving.

8. How I do 1x1
Schedule: once in a week
Get to know:
1. What are they enjoying / not enjoying
2. What were the blockers
3. Any other issues wrt work
4. Aspirations

9. How I manage my time
- Frequent interactions are productivity killers;
- Allocate time slots to interact.
- Googling is an art. Make them learn it.
- If all this interactions takes more than 30 mins a day, then something is
wrong.

10. Good practices
1. Make people understand why they are working on the task/feature; why it is important; how will it impact the user/product/team.
a. Sometimes repetition of information in the different contexts helps.
b. Assess them on how they solve the task
2. Ask for how they are going to solve it once they are ready with the solution.
a. Be open for any solution(not the best and optimal approach).
b. Debate why that would be better. If they came with a better solution, Great.
c. If not say what are the problems/setbacks/blocker/unnecessary things in the solution.
d. Control your urge to give out the solution you already know and ask to come up with a better solution.
3. If they are working on a same thing/solution for a long time(more than a day without any progress), might get frustrated.
a. Usually means they are out of ideas to try.
b. > 45 mins if they’re stuck, ask them to come to you
c. Give them ideas to try, not the solution.
4. Interact with people here and there if they seem introverts. (Include interaction levels)
5. Culture fit, are they motivated to do bigger tasks

11. Local setup
- Tell what all repos we have
- What are the frameworks and stack used for it
- Why we have? What does it do?
- Go through readme to setup those
- A high level architectural explanation helps a lot.
- Explain our PR review flows, how we deploy
- If stuck for more than 15 mins, come to mentor or ask help around.

12. Intern Mentor Responsibilities
1. Technical mentor
2. PR reviews
3. Deliverables
4. regular 1x1
5. Make people understand why they are working on the task/feature; why it is
important; how will it impact the user/product/team.
- Sometimes repetition of information in the different contexts helps.
- Assess them on how they solve the task
- Culture fit, motivated to do bigger tasks

13. Internal Norms
- How to use git ? how to commit?
- Our PR review process?
- How to deploy to staging?
- When to merge & test for a prod deploy?
- What to do on prod deploy night?
- What if your changes are problematic at last minute of deploy?
- How to revert? How to create hotfix?

14. Interaction levels
First 2 weeks:
- All internal norms to communicated a few times and make sure they do it.
coming weeks:
- Periodic intervals of communication
- Maybe twice a day at scheduled time.

15. Push backs
- If you think they can find this in the world wide web in few searches(5~10
mins), ask them to read through about it.
- Ask for how they are going to solve it once they are ready with the solution.
- Be open for any solution(not the best and optimal approach).
- Debate why that would be better. If they came with a better solution, Great.
- If not, say what are the problems/setbacks/blocker/unnecessary things in the solution.
- Control your urge to give out the solution you already know and ask to come up with a better
solution.
- Be polite while pushing back.

16. Motivation
- If they are working on a same thing/solution for a long time(more than a day without
any progress), might get frustrated.
- Usually means they are out of ideas to try.
- Give them ideas to try, not the solution.
- 2nd and 3rd tasks they work on can also be of minor ones but not strictly
more than that.
- Interact with people here and there if they seem introverts.

17. Vanakkam