Career Advice About Grab

I have often found platform teams to be quite "tech-heavy" rather than being driven solely by business. On the other hand, it is easier to convey impact for product teams for the metrics that the org cares about much more.

If I am trying to move from Mid Level to Senior Level i.e. Senior Software Engineer to Tech Lead level in my org, what kind of teams should I target?

Does choosing a certain one help you in fast-tracking your career growth?

In fast-paced organisations that launch a lot of features on a quarterly basis and teams with large sizes, how should a tech lead or team members ensure that everyone knows about everything or is enabled to get to know about it?

Quite often, whenever a new feature comes in, it could be repurposing technology built for other features as well. But, given the pace at which these are developed, it is often hard to know what everyone is working on. Sometimes, each of these features may have idiosyncracies that may be getting missed out by new joiners, especially due to the volume of information, especially for teams that have been in existence since a long time.

I recall once when changes for a new feature done by a developer reverted some conditionals for an older feature, thus causing an outage. How do you prevent this and ensure knowledge of everything is available to all, especially to people new to an organisation?

Also, are there some general practices to ensure that these are easily discoverable? Video recordings are time consuming to go through, and wikis though they exist, are sometimes difficult to navigate, when you don't know what you are searching for? I am thinking of something like a mind map could help here, but what are your thoughts?

Prepping for interviews always feels detrimental to actual career growth. At the same time, what are the things one should look out for to avoid getting laid off and jump ship when things are about to go south.

One advice mentioned often is to look for finances of the company, but I am not aware how to analyse it. Can you help with resources for the same?

In uncertain times, and given the risk of job security in tech, what are your views on passive income modes or side hustles such as writing a blog?

Can you suggest some of these for someone who is currently a backend software engineer?

Also, I am ruling out hustles such as driving Lyft/Uber as they require active participation.

I am trying to get promoted to Lead Software Engineer, which relates to an E5 level at Meta, if I am not wrong. I have seen several engineers in my organisation coast at the current level I am.

I wanted to understand if there are some key things I should be doing in order to perform at a Tech Lead level, so that I am promoted to one as well. This would be a bit long question, but please bear with me.

Following are some of the things highlighted in a few discussions:

1. Should have demonstrated complex backend system designs - How do I create this opportunity to build a complex system for myself? Often, the projects we are a part of don't require complex solutions.
2. Have a very strong code quality
3. Mentor other engineers - I started having 1:1s with Junior engineers on how to grow. Have not been doing this with Senior Engineers, but I try to jump in calls with them whenever they need some help. Often, the credit goes hidden, and sometimes it does bother me, but not sure if there is some way around it. What are your thoughts?
4. Handling production outages and incidents - Trying to be on top of it. Recently, have been putting out short term fixes, but alongside working on some libraries to fix it in an extensible way and have a larger impact with other teams as well. Sometimes, having visibility for my work in other teams seems to be difficult, but trying my way around this. If there is something you can recommend, that would be great.
5. Should I mention in my skip levels that this is something I am targeting for myself? - Right now, my focus is to try to uplift the code quality, work on larger designs (a question mentioned wrt this), trying to uplift the team (I have created a channel where I share stuff that can help the team upskill, brief nuggets of information on how to write good code etc. Doing this almost twice a week for around 2 months now), trying to mentor engineers within the team.

Another aspect is that my team would be getting changed soon due to organisational requirements. Given that, How do I make sure I am on the right trajectory to getting promoted ? (One thing on top of my mind is that I would be asking for junior engineers whom I can work with and try uplifting, alongside asking for opportunities/projects that would have large visibility and impact.)

Do you have any other advice for me?

I have gotten this feedback from my managers couple of times. Problem is - in the past (in some other companies), I have been on the receiving end of negativity. Often times, being reprimanded for asking a question, in some of the other teams I was a part of. I recall that I was shouted at in front of everyone because I was too tired during one of my on-calls and dozed off, missing an on-call call at 3:30 AM. I recall these events getting escalated to VP level. It impacted me deeply.

While it was hard, I moved on from such teams and now I try to be kind to all engineers, especially junior ones. I make sure that their onboarding journey is as fast as possible and they are granted help that is required. Extending it further, as a part of calls with other stakeholders as well, I often tend to be with a softer tone. It has been mentioned by my manager that - "You often come across as too kind. If you know that you're right, then why are you not speaking it with confidence."

How do I improve on this aspect ? Recently, I did but thinking if there are some other tips from your end.

How does it differ from an entry level engineer to the head of engineering level at each of the levels, given the scope grows as well at each level?

• Software Engineer
• Senior Software Engineer
• Tech Lead
• Staff Software Engineer
• Principal Engineer
• Head of Engineering
• Director of Engineering
• Vice President
• CTO

How do each of the levels ensure they are onboarded as quickly as possible to have maximum impact ?

Joining a new team/vertical with the company, I often feel intimidated with the sheer expanse of domain knowledge to be grasped. Given that it takes time, what are the best ways to approach it, so that you are the most effective.

I often struggle with conveying more in lesser number of words. As a result, my slack messages often go in multiple paragraphs and bullet points.

I find a need to explain myself in detail, especially when trying to resolve some queries from other domains such as product managers and QA engineers. Are there some ways to make communication succinct and to the point, at the same time conveying what is necessary.

This was a feedback I have gotten once from my manager as well, though when I asked if he had some suggestions on how to work on the same, he mentioned - "Keep it short!" ¯_(ツ)_/¯

Now, I try to vet my messages after I type them before sending, but thinking if there are some ways to improve on it further.

I have been working from home since 2020. From 2020-2021, I used to work in a healthcare startup with lots of responsibility, tons of work, crazy deadlines and needed to firefight incidents on a daily basis. The managers used to keep us on our toes and everyone was expected to put in more hours than the standard 40 hours/week. I was pretty much working most of my waking hours so productivity was not my concern. I did learn a lot but eventually burnt out.

I took a year off to do my masters and joined my present company in June 2022. It's a much bigger company with amazing culture, clear processes and I have very supportive and brilliant teammates. No one micromanages me. There is still good amount of responsibility and tons of work. In this environment I also want to give my best. While my productivity is great when in office, I do feel I am at 70-80% productivity level when working from home. We follow a hybrid model where we go to office twice a week.

Being in rent crazy Singapore, I do not have the luxury of having a separate office space at home. I do have a proper desk setup and enough things going on to be productive.

I want to be more productive in days I am WFH.

Have tried keeping up a schedule, wearing noise cancelling headphones, listening to binaural beats.

But nevertheless I do find myself on my bed after a couple of hours of work and it becomes difficult to resume work again. Also I tend to be hard on myself for taking that rest and the day just spirals from there.

I have tried working from cafes and even going to office every day. But along with going to gym, commutting and cooking healthy food I am too tired at the end of the day.

I really want to be more productive when WFH so that I can also manage the other parts of my life well. My team doesn't care where I work as long as the work is done.

Would like some tips on how to be a better remote worker and manage the entire day better.

Currently, I am only going through Neetcode's roadmap. I have solved 40+ problems.

My process is:

1. Understand problem
2. Try to solve the problem
3. Try for 10 mins
4. If not, go see the solution video
5. Understand the solution and code up the solution
6. Take notes in an excel sheet for revising later

I only read up theory related to the video in case its something I do not know about from before. Only for max 30 mins, so that I do not waste a lot of time reading up. My primary aim is to learn by solving problems.

I am able to solve some problems but I feel I still do not have the intuition for solving new problems.

My questions:

1. Should I be reading up on more theory before I start doing more of the roadmap? Maybe go through Neetcode's courses.
2. Does it simply take solving more problems to build up the intuition?
3. Should I try harder on my own before checking the solution video?
4. How did you build the intuition to solving new problems?

I have recently joined a team which works in Go (no frameworks). My team handles multiple backend services ( exposed through REST APIs ) which are like a platform for various other services.

I have picked up the language grammar and have enough understanding to write working code. However, I feel I don't "get" it. I don't understand how to organise the code into a well-defined folder structure and interfaces.

I would like to understand what are some of the good ways to learn a new language. It's been 2 months since I started learning it and feel like I am working with incomplete knowledge. Maybe at 50% level. I know there's no point in understanding all the features of a language but I would like to understand design patterns, best practices and how to write high-quality code.

I really need to be able to ramp up in another month's time.

Majorly need advice on

1. Learning to write high-quality Go code
2. Writing with Dependency Injection in mind
3. Design patterns and low-level system design

In the age of IDEs with autocomplete, chat gpt and copilot does it makes sense to learn it?

I have seen Devs who use Vim browse through files and make changes at tremendous speed and am curious if it's a good tool to improve my productivity.

I did do a bit of Vim during my bachelor's but mostly used IDEs in all my jobs. It will take me some time to learn and make the switch but I feel it's a good time to learn it.

Also what is the importance of setting up your tooling and IDEs in being able to code faster.

More often than not, problems are enlisted in quarterly roadmaps.

From a tech complexity perspective, how do you evaluate problems which are highly complex in nature. If such problems don't exist in my team or if they exist but don't generate high outcome, should I look for outside my team to solve such problems?

1. What are the things you can suggest to reduce the turnaround time for onboarding a new engineer within the team?
2. What are the things that can enable them better?
3. How does this differ based on the stage of their career at which the new hire is in?

US has a lot of big tech and startups. India has seen some growth in recent past as well. What are other locations worldwide where one can propel their career with good compensation and growth ?

I am thinking about this, more from a long term perspective, in terms of getting a Permanent Residence and moving with my family there.

I understand this question is slightly out of hard core tech.

I am looking for a location to settle long term and originate from India. While I like it in India, wanted to check if there are indeed places with good:

• Software Engineering Opportunities
• Cost of Living
• Earning to Spending Ratio (I am usually a spender on low side, living minimally)
• Safe to live at
• Healthcare, Education and other things needed in life usually

This is really important to me since my parents are getting old and I would want them to stay with me. Thus, it is pertinent for me to decide where I would want to stay so that it becomes easier for them to adapt themselves slowly. At the same time, I don't want to compromise too much in terms of my career as well. I consider safety really important and financial health as a hygine factor.

I am starting this thread/question for folks in various locations to share how their experience has been. Hopefully this can serve as a guiding point for folks in similar situation.

I went through and kudos to her for doing a great job at articulating everything so well.

But I was wondering at the same time if there are any differences in leading a tech team at a startup (100 engineers company) vs a FAANG company?

The benchmarks I am setting here are people like Robert Martin, Martin Fowler, Venkat Subramaniam (known for agile and Java), Guido Von Rossum (developed Python), Jeff Dean, Sanjay Gehlawat etc.

Latter two are Senior Fellow at Google. Up until a certain point, I understand that promotions are about the scope of impact inside an organisation, but how do you grow yourself outside the walls of it so as to be on your way to be extremely good in your craft and among top software engineering contributors in the world.

Would appreciate answers from as many folks as possible.

1. How do pull requests and pull request comments look like with an increasing level of seniority?
2. Are pull requests for senior engineers not expected to have any comments for improvements? If yes, then what kind of comments should be there?
3. Also, have seen some principal engineers not sharing their pull requests as they are quite high in seniority and merging it directly. Do you recommend that? If not, who should review PRs for very senior engineers if the team does not have engineers at that level?

Some engineers like to code, some like to manage projects, some like to stay close to the users. Software Engineers come in all shapes and sizes.

What are the major archetypes of Software Engineers and how can one identify one's own archetype to double down and improve.

1. Should one keep multiple offers till a week before the joining date as a safety net?
2. What are the steps one can take when an offer gets rescinded?

1. My new manager has worked with me in the past for around 2 years (6-8 months as a manager and rest as a teammate) after which his team got switched.
2. I have been working for the last 2 years (since the last time I got promoted) towards a promotion and even though organisational requirements need my team to be switched, I still want to target a promotion in upcoming year end review cycle.
3. I have brought in several process improvements in the previous team and have tried to uplift my previous team forward in the last 2 years as a mid-level engineer. Given that the new team I would be joining is in a similar scenario in terms of code quality/processes etc. as my previous team was sometime back, what all should I do to get maximum leverage for a promotion?
4. Do you suggest is it better to look for an up-level outside of the organisation or stay put ? What factors does it depend on?

Even for the existing money earned and invested, seems like it may face some impact due to the probable hit on US economy due to the same. What can one do best in this situation?