Profile picture

Building Relationships Q&A and Videos

About Building Relationships

There's more to working in tech than just shipping software. It's vital for your career to build deep professional relationships and make real friends at work, especially if you're looking to grow to senior levels.

Communicating and Asking Questions with Seniors Who Lack Strong Technical Skills

Mid-Level Software Engineer [E4] at Meta profile pic
Mid-Level Software Engineer [E4] at Meta

I’ve gone through Taro's courses on communication and asking questions, which were insightful, especially in showing how juniors can learn from senior engineers with deep expertise. However, as an MLE, I face different challenges and would appreciate some insights or thoughts from Alex or Rahul.

For context, I majored in math and hold an MS in ML from a top 3 university, so I'd say I have a solid grasp of both the mathematical and practical aspects of ML. Machine Learning can be deeply mathematical, often requiring formal training to fully get it. Some SWEs who transition into MLE roles may lack this foundation, and while they might have been excellent SWEs, the gap in math knowledge can hinder their abilities as MLEs.

Here are a few challenges I face with some SWE-to-MLE seniors:

  1. Sometimes, my tech lead asks questions that suggest a lack of understanding of ML basics. While directly correcting them doesn’t seem right, what’s the best way to handle this?
  2. This becomes a bigger issue when they set project goals that are mathematically infeasible. Without a strong math background, they rely on intuition, making it hard to guide them away from misguided directions.
  3. Their informal grasp of ML can also complicate design documents by introducing unnecessary features that don’t align with the project’s objectives.
  4. As seniors, they can get defensive and dismiss alternative ideas, which is frustrating, especially when I would need to work on a project with a high risk of failing.
Show more
Posted a month ago
74 Views
1 Comment

How to deal with a peer who tries to micromanage and push their work onto you?

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

My team has 1 E5 iOS (me), 1 E5 Android, 1 E4 iOS, 1 E4 Android, and several backend engineers. We also have a few web engineers, but I don't work with them.

I optimize for quality even if it takes more time, while my E4 iOS optimizes for speed (often cutting corners, skimping on testing, neglecting edge cases, etc.). My E5 Android's quality is somewhere in the middle of my E4 iOS's and mine, but he takes a lot longer than me on comparable tasks.

My E5 Android tends to push tasks onto others, with the excuse that he "doesn't have time". For example, our team's manager wanted our mobile engineers to learn the backend, so she specifically assigned a backend task to the E5 Android engineer. However, in a 1:1, the Android engineer asked me to take that backend task "if I have time" -- I had finished my iOS tasks early, so I technically had time, but I was hoping to work on a side project to demonstrate E6 scope. When I mentioned that I didn't have time because I was writing a 1-pager, he asked me to share it with him. Then he said we should focus on finishing our existing projects before starting new ones and added a lot of negative comments to my 1-pager, which made it more difficult for me to get buy-in from other engineers.

My team's EM had told me I could DRI a particular project I was excited about. However, the E5 Android convinced our PM that we should finish existing projects before starting new ones, so they forced me to deprioritize the project I was excited about to work on some boring E4 tasks. My E4 iOS was busy with another project, so he didn't have the bandwidth to take those tasks. However, I was hoping the E4 could take those E4 tasks after he finished his current project.

Do you have an tips on how to navigate this? I get the impression that the E5 Android pushes a lot of tasks onto the E4 Android as well, based on the latter's annoyed look in meetings when it happens.

My team will start our H2 scoping soon. Apparently the E5 Android engineer already set expectations with my team's EM that Android will take a lot longer than iOS for that project that I'll DRI.

Show more
Posted 4 months ago
73 Views
4 Comments