Profile picture

Productivity Q&A and Videos

About Productivity

Approaching burnout territory

Senior Software Engineer [E5] at Meta profile pic
Senior Software Engineer [E5] at Meta

I have been working less than a year at Meta and am just unable to understand and jell with the culture. There are a few main things contributing to me feeling burnt out.

Endless number of things to do...

There is equal emphasis on contributions to all axis and there is barely any overlap in the work that I need to do in order to meet expectations on all of them (except maybe Impact and Direction)

Better engineering projects that my team has scoped out are very separate from Impact projects

For people axis, I have to drive org level impact which is a thing of its own and adds on to the BE projects and impact projects.

Our oncall is extremely tough since we have a huge number of products with code dating back to 10 years ago.

Due to all this it feels like I'm having to do 4 jobs at once.

Process is bloated...

Especially for impact projects that result in changes to the product, there are a huge number of people involved, UX, DS, DE, 2 major orgs who are our customers and their representatives, Content, PM and business leaders. I get pinged for dates and status updates by 5 different people for either the same or different things every day. It is hard to keep up with and as someone who has some ADHD traits (unofficial diagnosis) and an introverted personality, just getting pinged and keeping up with responses feels exhausting let alone the coding aspect. Meta lives by its bottom up culture but in our org it just doesn't seem like its working. In my previous job, process was barely something I had to think of, and mind you we did weekly releases to 3 environments.

Laser focussed PSC conversations...

From having performance conversations 2 times per year to now having them 2 times a month seems like an extreme overkill and adds to the stress at all times. It isn't just the frequency. PSC self reports are so heavily dissected for every single word, every single metric that doing PSC right feels like a project in itself. so now it's 4 + 1 = 5 jobs.

What should I do? PSC season is again around the corner. Practically speaking I have a few options I want to get some thoughts on.

  1. Change teams (requires an exception since it hasn't been a year)
  2. Leave meta (and payback some comp components and say good bye to crazy TC)
  3. Take a medical leave (still risk getting dinged at PSC)
  4. Stick it out until the 1 year mark and revisit above options.
Show more
Posted 5 months ago
1.4K Views
3 Comments

Feedback that I'm underperforming for my level. Is this PIP? What now?

Mid-Level Software Engineer [L4] at Taro Community profile pic
Mid-Level Software Engineer [L4] at Taro Community

I was hired as a mid-level engineer, but I'm performing at the level below it. I had about a year and a half of experience coming into my company but didn't get much from it due to multiple re-orgs. In hindsight, I was a poor hire for my role and have felt this way the entire time. I am not interested in the niche and motivation is a struggle at times. I stayed because the team was really strong and I thought I could focus on the coding and grow technically. That was a mistake.

Fast forward a year and a half later (now), my manager tells me informally that my delivery is ok, but the way I go about my work needs improvement and I'm not growing, so I am performing at a level below. I need a lot of help from other engineers. And that I need fewer comments on my diffs and to do more research on problems because I'm not problem-solving well enough to be at my level. He's completely right. The team is full of high-performers and I know that I'm doing poorly by comparison. But I'm already consistently overworking into the evening and weekends.

I'm also hitting the limit with my mental health. I am putting in effort, but am being told it's not enough. For example, I spend some time understanding X and think I understand it, but teammate questions me in a way that makes me apply that knowledge and I realize my understanding is not so good or I did not think about it that way, so I am ashamed because I have spent a lot of time working on the task, but have failed to deep dive into this part. Or my teammate asks me for my thoughts on how to make something better, but nothing really comes to mind. How do I work on this behavior?

Some other questions:

  • Is this a sign to leave my team or company? And the profession? Despite my best efforts, I'm disappointing my team and it's taking a toll.
  • I haven't been served a PIP yet, but is this a sign that it's coming?
  • Naive take, but is it a bad idea/even possible to ask for a downlevel? The reasoning was that I'd rather keep my job than lose it.
  • Any advice?
Show more
Posted a year ago
1.3K Views
10 Comments

Working with a micromanager

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

I am a mid level engineer and I work for a manager who has micromanaging tendencies. Some of these tendencies include,

  1. Going deep into implementation details of tasks that engineers are working on. I have been in meetings/discussions where proposed solutions by engineers have been ripped apart by this manager without them having enough context about why the engineer is doing it a certain way. This almost always leads into the engineer having to explain the nitty gritty implementation details to this manager to convince them that the engineer is doing the right thing. Overall, the manager shows very little trust on the decisions taken by the engineers.
  2. When there arises a situation that the manager wants something from an engineer, they will want it immediately i.e. within the next few hours, eod etc. The manager is aware that the engineer is working on a bunch of things but they will not show any regard for that fact. This means that the engineer has to put everything they are working on aside to produce the thing that the manager wants. The problem is that this happens very often and it results in engineers either having to overwork to get their job done or affecting quality of their work.
  3. The manager will put the engineers under extreme pressure to deliver projects on or before the deadline. This includes minor nudges in meetings, lunches, team activities etc. reminding engineers of the timeline to having 2 hour meetings to discuss where we are in terms of meeting the deadline.

I have a few questions based on the above context.

  1. How to deal with such managers?
  2. Is it sustainable long term to work for such a manager? I am considering getting to the next level in my role within the next 2 years, would it be advisable to continue working with this person?
  3. Do most managers have more trust on their directs than described in the above situations?
Show more
Posted 2 years ago
1.2K Views
5 Comments

Learn About Productivity

Productivity is very important for a software engineers because it can greatly affect your career trajectory. Software engineers who can consistently deliver high-quality work within a defined timeframe can position themselves for faster career advancement. When you can execute tasks quickly, you build a track record of reliability.
When you can meet project milestones, it shows that you can manage your time effectively. When you are productive by optimizing your time, you’ll be contributing to the success of your team.
A strong flow state and ability to context switch are key components of productivity. If you can achieve a flow state, you can significantly increase your speed and efficiency. This is very helpful when you are dealing with a calendar filled with meetings.
You should also be able to manage meetings effectively. This involves not attending unnecessary meetings. It also means consolidating similar meetings to create more focused blocks of time for yourself. If your daily schedule has too many meetings, you run the chance of not being able to get any work done.
When you are in a meeting, you should make sure to follow certain guidelines to make the meeting as productive as possible for everyone involved. Make sure that a clear and detailed agenda is set for the meeting. You should share the agenda with all of the meeting attendees in advance so each of the attendees knows about the context behind the meeting. You should also remind people about the agenda document by pinging people in your company’s communication channels, like Slack or email. Make sure the meetings actually follow the agenda and give everyone in the meeting the opportunity to speak. This will lead to an inclusive environment where everyone is heard.
You also have to be aware of your own mental state to avoid burnout. It’s important to communicate with your manager and tech lead about project timelines and priorities to manage your workload and prevent burnout. Just because you can execute on the work doesn’t mean you are delivering the most meaningful work. Always be prioritizing with your stakeholders to make sure you are meeting the most important goals of your customers
Show more