Mid-level Engineer Career Development Videos, Forum, and Q&A

I have worked as a software consultant for 4 years at companies like Amazon, Hitachi, etc.

I joined Tiktok coming from not such a big company & fast culture. I had two projects where I needed to read massive code bases for tasks. The code base is in C++. A language I haven't used in years. How should I go about it?

Should I spend time learning the language before diving into the code or otherwise? I feel under-confident; other engineers scan & understand code even when they don't know the language too well.

I have never worked at a big tech company, but I'm just preparing continuously for the same, though my resume is not getting shortlisted, so I rarely try applying and keep studying.

Can I get a resume review and some pathway to stay in the interviewing loop?

I have been repeatedly told that I have a tendency to drop things when doing context switch between multiple tasks. How to manage my tasks effectively so that I can minimize this pattern?

I was recently laid off from AWS. I see few open roles for SDE-1s but descent number for SDE-2 roles.

Should I study system design and apply for SDE-2 roles or focus on SDE-1 roles?

I have not studied for system design interviews. I estimate that I will need 2-3 months of studying before I can pass the interviews. My YOE is low for SDE2 and I might be wasting my time applying for SDE2.

Here is a breakdown of my experience:

• SDE-1 at AWS: 1 year 9 months (not including 2 months for WARN)
• SDE intern at NASA JPL: 1 year
• Undergraduate Researcher: 3 years. Co-author on 3 papers. First-author on 1 paper. All reputable journals.

My manager at AWS was telling me that I should apply for promo in the next few months (after finishing a project). I got laid off before I could apply.

Is there anything I can do now to make me stand out as an SDE2? For example, contributing to open source. I want to try being an entreprenuer but I know few ventures make more money than working at FAANG so maybe it's not a good idea.

I am looking for some good books or detailed courses on system design which are targeted for Mobile engineers specifically.

Hello community ✋I am going to start interview preparation for SDE-3 roles. Need your suggestions on what should I prepare and how much should I prepare? How much should I focus on DSA, system design, machine coding etc?

I have experience interviewing for SDE-2 roles but attempting for SDE-3 role first time so need valuable inputs from experienced people here.

I'm not sure exactly how to phrase this, but to give an analogy, I love card games (ex: Legends of Runeterra, Race for the Galaxy, Hearthstone, etc). There are a fixed set of rules and a fixed set of cards. I can "grind" games and get better by noticing patterns, picking up new strategies or tactics by playing against a diverse set of players. The outcome of an interaction is usually idempotent (i.e. card 1 interaction with card 2).

In real life, things are quite complicated. Asking a certain question in a certain way to person 1 and person 2 may give wildly different responses, and may even depend on your mood, their mood, your tone, time of day, etc. It's super messy and unpredictable.

I also feel a similar way about system design. The nearly infinite possibility of inputs, outputs, TPS, throughput, scenarios make it difficult to reapply the same set of rules to different scenarios. This is just talking about one component, when we bring in N components, the interaction gets very complicated and the "rules" change" case by case. I'm sure it gets better with practice, but I also feel I have a limited opportunity to learn or practice these on the job.

Has anyone found a way to structure these learnings in terms of a repeated "grind", because oftentimes I feel overwhelmed and don't know where to start. This is a complicated question, so answers regarding either a) soft skills or b) system design separately I will treat as valid answers.

Engineer A on my team was working on big refactoring project. I joined same project around 65-70% completion. Now he’s leaving for a vacation and I’ll be leading project and finishing it. By time he’ll leave it will mostly be completed 90-95%. My questions are:

1. Since project is almost done, I know I won’t have much scope but still how do I show my best in whatever is remaining?
2. What are things to look into and clarify with that engineer during handoff or before he leave?
3. Any other tips for making best out of this opportunity?

I'm a premium member from India and want to be in the same club.

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.

I'm looking to level up and am currently designated as an SWE-2, where I take end-to-end responsibility for an Android app. I have a couple of juniors who report to me. I also took responsibility for writing backend APIs.

I even led a feature using guidelines of system design playlist and made a brag journal for promotions.

What are the exact behaviors to become one level up as SWE-3 (Mid-level)?

Hello,

This platform is awesome and I've been looking at a bunch of resources for career advancement. One aspect that strikes me is to play into my strength. While I do enjoy coding (only if it's front-end or mobile -- visual stuff!), it's not my strength or something I will really do outside my job. I do love being in any conversations that involve innovative features for our customers, making our product more modern aesthetically, or questioning the features we do have. The idea of being a staff/lead/principle engineer keeping up with latest angular features or being on call outside job hours to fix some server or UI issues come up isn't really appealing. But I do want to grow. I want the chance to mentor people, influence a project, be in cahoots with people who make decisions about what we want to create, be close with customers, etc. I love the design (UX) aspect as well.

If I stay as I am, I know I will slowly grow linearly in this software engineer role. I do think I will get the senior developer role next year. But most folks who have a C-suite role in product or beyond seem to have an MBA but I am not sure if that's a valid move nowadays. I am taking a couple of tiny PM projects but outside that, what can I do to have the best chance of landing a C-suite role later in my career and making an impact beyond coding?

Looking forward to your replies!

I have a SDE 3 mentor who is very nice and helpful. I started working with them a while ago because I am trying to get promoted to SDE 3 but I don't always have great questions to ask. I also want to be respectful of their time.

What are some questions that will be most beneficial to ask? How can I make the most of this mentorship?

Context:
Over a conflict, an aggressive conversation occurred between the engineering manager towards the business lead. From the point of experience, there are ten years more on the side of the BL. Everything happened over Slack over the weekend.

Due to this, today, the entire engineering team had a 1-1 to skip meeting with HR to give our statements about the issue.

What usually happens after this meeting?

I am in a platform team that has had many senior-level folks since the start. There are many great things already present for our team's productivity like:

1. Automated CI pipelines. ( Deployment is manual - via button clicks though )
2. Local validation scripts for linting, code generation, testing.
3. Slack bots for sending reminders for PRs.
4. Detailed runbooks for On-Calls
5. Good amount of monitoring stats and alerts.

I am the junior-most in my team and want to target for a Senior Engineer role. One way of approaching this is by trying to improve the life of my fellow teammates. But I do not know what I should be adding. Because I do not know what more would be needed.

I know this may be a flawed way of thinking. I think it's better if I just keep on doing tiny improvements every day. But in terms of impact, I feel adding some tools / taking initiative here will help. I want to know what can I add to the team's arsenal which can also help me in my journey to Senior Level.

A feature I'm building has no straightforward process or to-do list, where designs are unfinished, and designing and development go hand in hand for weeks.

We have been pushed to develop in parallel, creating much rework.

All my engineering manager asks now is ETA, even when they know it is difficult to achieve, and asks why it is late, pushing us to work late at night or on the weekends.

They do it in front of everyone or via Slack to create pressure.

What is the fundamental role of the Engineering Manager?

I want to figure out how to draw explanations in Google Docs efficiently:

• I only find these resources if there is a mock interview recording.
• But is there a standard way to communicate with the interviewer?
• I struggle a lot in this area - Even though I know the solution, I get stuck

Just curious about opinions here. My main language is JavaScript, and I know people probably assume I am a front-end developer / full-stack (reasonable biases). In reality, I've been primarily backend for several years now. Throughout my experience at Microsoft and Twitch, I've used a fair amount of Node.JS / vanilla JS, then a bit more TypeScript for the CDK constructs we all know at Twitch (our team was primarily responsible for building and debugging Amazon Builder Tools things). I've done the majority of my interviews in JavaScript and it has been mostly OK, since I've used it for so long, but just wondering if it matters.

I used to do my interviews in C++, but then I got burned during a Google interview when my interviewer talked about the inefficiencies of emplace_back vs push_back (I had no idea). After that point, I just decided to do JS because I was reasonably proficient at it, and it is actually faster to write than C++ in a lot of cases (less boilerplate).

The top LeetCode answers / YouTube explanations and such are usually in Java or Python, so sometimes it's also hard to find a good JS answer. I'm leaning towards Python, because it is more like JS and with less boiler-plate like Java, but I'm worried about something throwing out some random trivia about Python that I have no idea about, because honestly I haven't used it much in my career thus far.

I would like to understand how can I drive an effective Tech discovery session (just had a PRD walkthrough) with the team (remotely working) before we start writing a detailed system design document. The engineers are mostly L4 and are still learning how to effectively collaborate instead of full blown meeting.

Hey John, I hope you are well. I am really passionate about CS (specifically Software Engineering) and I want to pursue a career in it. But I can't help but be a bit concerned about the future availability of coding jobs due to Al (chatgpt4 and stuff). I understand it's hard to predict how things will be in the next 10-15yrs, but my main concern is that I may be putting in all this hard work for nothing. I'm concerned Al will make my future job(s) obsolete before I even get it. Any thoughts on this?

If you build full "product skills" and use the best tools for the job, which today might be hand coding, but later may be Al guiding, you will probably be fine.

I see....by "product skills" do you mean hard and soft skills?

Software is just a tool to help accomplish something for people many programmers never understood that. Keep your eyes on the delivered value, and don't over focus on the specifics of the tools.

Source:

Saw the above discussion on twitter and it got me thinking with advent of ChatGpt4 and Github Copilot X, what can I do to not get negatively affected by this change.

What are the various skills referred to as "product skills" mentioned in the above discussion and how should we go about developing them?

Big companies have multiple teams across. There will be a team just for the login, a team for backend logic, etc. There are so many teams and microservices and internal jargon all around.

Problem is during team meeting, seniors have more in depth discussion where I'm unable to provide value as good as them.

How do I get familiar with them fast? Or am I focusing on the wrong idea and should just narrow down what I'm working on and just let time do its thing?

Thanks

Context:

I'm a mid-level engineer looking to grow to the senior level. I'm currently leading a team of 2 other engineers on a large migration project that's revamping a big part of our API architecture. This is a platform team so the biggest objective of this project is to make the lives of other engineers easier.

Questions:

(1) How can I measure and demonstrate the business impact of this project, given that it is aimed at internal teams?

(2) What metrics could I be using to quantify the technical impact of this project?