Profile picture

Building Relationships Q&A and Videos

About Building Relationships

How to handle being on a team with slackers?

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

We are 3 people in my team. I've been at the company for 2 years roughly and my team mates for 15+ years. I'm in a situation where my coworkers do stuff, but stuff that's often completely unrelated to our backlog. One of them struggles with being motivated by the job. Occasionally, a 16-hour job takes a month to complete. Maybe 2. And you never know why or when it will be done. This causes a lot of tension with the product lead. The other teammate (focused on the front end) rarely makes any PRs. I'm not sure if it's due to the fact that they have mostly done HTML/CSS and are unsure of how to navigate the frameworks we use or what it is. Our manager tends to cover for us, but obviously he's not loving this situation. It's been like this for 1–2 years. Now it has started affecting my pay raise, and I'm starting to feel tired of always playing dumb or referring to the other great work that they're doing when asked what my teammates are up to. Both seem to be struggling somewhat with stress and anxiety, so I've tried to be compassionate with them. But what do I do? I want to take ownership of the team's performance, but it's difficult to know what to do. They have the senior roles, and they have most of the ownership of the project, so I also feel weird telling them "what to do," if that makes any sense. The company size is roughly 20 engineers, FYI.

Any advice on how to handle this situation nicely, i.e. making sure we're still friends afterward, would be highly appreciated.

Show more
Posted 2 years ago
187 Views
2 Comments

Explain day-to-day operations and decision-making in Meta

Staff Software Engineer [E6] at Meta profile pic
Staff Software Engineer [E6] at Meta

What is the prevailing culture within the organization, and how does it manifest in day-to-day operations and decision-making? The prevailing culture within an organization is the shared values, beliefs, norms, and practices that shape the social and psychological environment of a business. This culture influences employee behavior, motivates management styles, and affects decision-making processes. What are those for Meta?

What are the hidden things to notice and to worry about? For example:

  1. Cliques and Silos: Pay attention to the formation of exclusive groups or departments unwilling to share information. This can indicate a fragmented culture that hinders collaboration.

  2. Resistance to Change: If there is noticeable resistance to new ideas or changes in procedure, the culture may be rigid and resistant to innovation.

  3. Overwork and Burnout: A culture that consistently expects long hours and overwork may prioritize short-term gains over long-term employee well-being and sustainability.

  4. Turnover Rates: High employee turnover can be a red flag for issues within the organizational culture such as lack of growth opportunities, poor management, or a toxic work environment.

  5. Office Politics: Pay attention to how much politics influence decisions and progress. A culture heavily influenced by politics rather than merit can demotivate employees.

  6. Feedback Mechanisms: Lack of mechanisms for providing constructive feedback, or a culture where feedback is ignored, can indicate a culture not open to self-improvement or employee development.

  7. Diversity and Inclusion: Observe whether the organization actively supports diversity and inclusion, not just in policy but in practice, reflecting a culture of respect and equality.

Show more
Posted 9 months ago
154 Views
3 Comments

What type of environment allows fast career jumps?

Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro Community

I was wondering if you need to be part of a specific type of environment in order to make quick jumps in your career? Like to get promoted to senior level in 2 years.

I was asking because from my experience, there seems to be an invisible social hierarchy in every work place. Other people in the team may not allow me to make these jumps since this kind of anomaly will break the social hierarchy:

  • There is project specific information, in absence of really god wikis you have to rely on the peers in the team to provide you such information (like how are specific parts in a service working, or how is an obscure internal tool working etc). From what I see, often times they will provide small chunks of information, as much as you need to do your task, but small enough such that they still have the information and you depend on them (probably a measure to prevent others from replacing them).
  • Envy might appear between other senior folks if you progress quicker than them and might start to backstab you (For example, you need some information from them about a piece of code they wrote in order to progress, but they might do the knowledge transfer in such a way that it looks like they told you what you need to know, but in reality you got nothing; or might tell you to go debug to figure out how is something working, and you can spend days debugging modules when it would've been an 1 hour stretch if they simply told you or there was any wiki).
  • Manager might not want to give you extra money and compensate at your true value.
  • If you work too much, or too hard there's going to be problems withe the peers, because you increase the bar and kind of force them to work harder too.

I was asking these things, because I was wondering if I got anything wrong about these fast jumps or in general that I have a broken view about work. My first professional experience was an internship at a big tech and when got there the seniors told me that I have the same knowledge as a senior engineer, but best they could do was another internship next year (still in college).

Show more
Posted 9 months ago
153 Views
2 Comments

How collaborative, creative, and engineering driven do you get to be in an L5 role in FAANG+?

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

At my startup I was asked to deliver feature after feature + bug fixes by PMs as fast as possible without much time for proper refactoring work or engineering initiatives. Also it was pretty individualistic where you get assigned a task and only work with other engineers during a tech spec review meeting, code review, and syncing with a backend engineer (as an Android dev).

From Alex’s video on getting promoted to tech lead, I saw how you can 1) drive projects as an L5 engineer (vs a PM putting that together with designers) 2) Not have to know how to implement everything yourself for a project, but work with many others and facilitate the team. This sounds 100x more engineering driven and collaborative than at my start up with few developers. Is this common to many people’s experience of the norm in FAANG?

What I liked about Alex's story is also how he had the time and space to do things like document the differences between iOS and Android, as well as go all the way through to making a data analytics plan for monitoring it himself. Seems like a lot of freedom and ownership which I didn't feel I always had the time for personally. Being able to not have to spend 80% of your time coding but rather doing deep work thinking, planing, designing holistically sounds extremely satisfying and rewarding as an engineer. Maybe this also comes with experience at startups as well?

Show more
Posted 2 years ago
128 Views
2 Comments