Taro Logo
Profile picture

1 on 1 Meetings Q&A and Videos

About 1 on 1 Meetings

1 on 1 meetings are one of the most important mechanisms for any successful career in tech. As a senior engineer in particular, you will need them to build deep relationships and alignment.

Should I stay or leave?

Software Engineer II at Taro Community profile pic
Software Engineer II at Taro Community

I'm feeling very undervalued at my current position. I've been working on my service the longest and therefore was the one that onboarded most of my team. In 2023 my manager and tech lead have largely been too busy to help. For instance, I only have 1-1s one every 2-3 weeks.

The new members we got on our team were new to the company and one in particular has relatively poor communication skills, so I have had to spend a lot of time onboarding them.

Unfortunately, in my performance reviews the main emphasis is on the work that I am delivering and there is not much emphasis on the impact I've had through the rest of the team. But the couple of months I tried focusing more on my work, I noticed the culture on the team degrading.

The hardest part for me has been that I have found my manager very unhelpful in helping me with my career and other frustrations. There have been multiple times where instead of helping I've felt as if he's blamed me. I have expressed this to them, but they have not changed.

Now I'm in late stages of interviews with 3 companies. I estimate the pay increase would be between 10-25% if I receive an offer.

Our team also just changed significantly, we swapped a mid-level engineer with a senior-engineer and got a new manager. They will be reporting to my previous manager so that manager will still be around.

I'm optimistic that the new manager and teammate will upgrade my situation but given the more than a year of frustration without improvement I'm still leaning towards leaving. Though I am having second thoughts as well.

I'd love to get any advice on how to handle my situation. Thanks so much!

Show more
94 Views
2 Comments

Should I have worked on weekends to ramp up faster / deliver more?

Senior Software Engineer at Taro Community profile pic
Senior Software Engineer at Taro Community

Hi all,

I joined my current company (known in our industry for not-so-good WLB) 6 months ago as a Senior Software Engineer and have been doing side hustle in the evening and weekends over past 6 months beside my main job. This means I still completed the 9am to 6pm work schedule before doing my side hustle.

Now my manager is saying I have low bug fix count and my team consists of some weekends workaholics which I suspect I’m being benchmarked against. My upcoming performance review is due end of December 2023 (1 month away). The expectation for my level is ramping up in 3 months which means the last 3 months are no longer considered ramp-up period.

What should I do in this last 1 month leading to the performance review? Should I go all in on the weekends too or should I keep the pace I’m working (I’ve started working in the evening from 7PM to 10PM since receiving this feedback 2-3 weeks ago but on weekends I still hustle). Was I wrong in doing side gigs / projects while ramping up for my full time job and should have instead pushed weekends to ramp up? What could have I done better in the past 6 months and moving forward in 1 month ahead?

I know Rahul talked about doing side contract gigs and Alex talked about doing side projects while both are still at Meta (a very demanding big tech company). How did you guys handle the pressure and what are your schedules like? (Wake up @ 4AM, work on side hustle till 6-7AM, then go to sleep at night around 12AM LOL)? I'm curious about how people organize their side gigs schedule.

Thank you for your advices. I really appreciate it.

Show more
483 Views
2 Comments

Learn About 1 on 1 Meetings

1-on-1 meetings are important for building deep relationships and keeping key stakeholders in sync with the progress on a project. They can be an effective way to build deep relationships. These 1-on-1 meetings should be proactive, and they should ideally occur once a week for 30 minutes. It’s important to realize that there is a lot of value in 1-on-1 meetings because they can provide more depth of conversation than what can be provided in emails or team meetings. One has to be proactive in setting up meetings because it’s easy to wait too long to set up 1-on-1 meetings or consistently cancelling 1-on-1 meetings. The discomfort of discussing deeper, more emotional topics is where the majority of personal and professional growth happens.
It’s important to have a clear plan and agenda when having a 1-on-1 meeting with your manager. It makes the manager’s job easier, and it allows for a more focused conversation about tough topics. The purpose of the 1-on-1 meeting is to have proactive discussions where a manager and individual contributor can solve hanging threads and plan projects ahead. These meetings can be a powerful tool to discuss one’s career goals and seek alignment on solving the most pressing issues that a team faces. Managers can offer guidance, support skill development, and create a path for career advancement.
Remember that it’s important to embrace discomfort and avoid shying away from emotional topics during 1-on-1 meetings. Sharing feedback about what you’ve been doing, how you think things are going, and how you’re feeling can go a long way in building trust with the other person. It’s important to be genuine during these meetings because people are more willing to be vulnerable when they can sense that you are being vulnerable. Discussing what you liked or disliked about a project or meeting can lead to deeper conversations that can address problems from happening in the future.
1-on-1 meetings are an important part of effective management within a tech company. When they are approached with intentionality, these meetings become a necessary tool for fostering professional development, improving team dynamics, and driving overall success among individuals on a team.
Show more