Profile picture

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

How A Mid-level Engineer Can Grow Their Career

Mid-level engineers have very strong technical proficiency, able to execute on small to medium-sized projects with minimal hand-holding, leveling up from junior engineers.

Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro CommunityPosted July 26, 2024

How can I scope out and vet a project idea to match senior competencies?

I have been making progress towards meeting senior level competencies. My manager is aligned and wants to put me up for promo at the end of the year. However, I’m looking for a third project in Q4 to really nail down my case. Additionally, I want to provide more impact and learn how to define new initiatives. I love creating “swim lanes” for my teammates and leading projects that grow their scope. How would you recommend: Coming up with a project idea Vetting the project to make sure it has enough scope for a senior level (or staff! I would love to provide more impact) Vetting the project to make sure it has enough impact for a senior level I have a lot of ideas for step 1, but am struggling to choose which are appropriate to pursue. Previously, I built a reusable web component at a company wide scale, and am working with a cross org team who wants to use it. I am also working on a technically complex web authentication project that has potential to be used by other teams. Both of these project were scoped by me (with some guidance from my staff mentor) and my manager has communicated they are senior level projects. I have built good relationships with my teammates, our direct stakeholders, and several cross-org engineers. I’m also exceeding expectations at my current level, so there isn’t anything to worry about there. However, I feel like I’m hitting a wall and need to figure out the next project that will turn my promo case into a slam dunk. Any advice? I’m a frontend web engineer if that helps. :)

64 Views
2 Comments
Mid-Level Data Engineer at Instacart profile pic
Mid-Level Data Engineer at InstacartPosted August 15, 2024

Paying Attention During Team Stand Ups Vs. Working Through Them

I'm on a team of 10 people, including my manager. During our weekly meetings, I struggle to pay attention to what's happening when other people give their updates. I only work closely with 2 of my 8 coworkers. For those 2 coworkers, I already have a weekly sync with our manager on a different day. For the time being, I don't have much to do with the other 6 people on my team. I have 2 questions: Should I try paying attention to others' updates or should I try and reclaim this time and do work during the meeting? One can make an argument that long-term, it's beneficial for me to know what's happening with the other people on my team, but in general, I'm under the impression that the greedy (short-term) approach is best. If I should try and pay attention to others, does anyone have tips for doing so? I'm not sure how normal/abnormal I am in being able to pay attention to people, but I've always been a big day-dreamer. In elementary and high school, I was a good student in spite of day-dreaming during class because school was pretty easy and I was self-motivated to learn from the textbook. In university, I was still a big day-dreamer, but I was no longer a good student because school was hard and I couldn't just learn from the textbook. Now, post-school, I am motivated to pay attention to things that really count. e.g. when my boss wants me to do something, you better believe I'm motivated to pay attention closely to what he says. But by default, my mind doesn't want pay attention to anything unless it knows I need to do it. I can try taking notes, but often times there's so much additional knowledge and context the people working on the tickets have that my notes are kinda useless. Ultimately, this team meeting is only a half hour per week, so it's a huge deal either way, but I'm leaning towards trying to continue working on my tickets during them (i.e. what I know counts).

63 Views
3 Comments
Mid-Level Software Engineer at Unemployed profile pic
Mid-Level Software Engineer at UnemployedPosted July 19, 2024

How to add depth to my career and profile?

TLDR: How to pick side projects This might have been answered multiple times and a very well-known answer would be working on side projects but I want the answer to be more in-depth so it can be helpful for many engineers. Please don't answer in a generic way but try to answer this by posing in my shoes Let's say you have 1.6 years of experience as a Software engineer and 3 years of experience in IT but not in development now if you want to stick to the SE career. This market is very challenging for me to get a job with 1 plus year of experience. I have to convert my IT experience into developer experience and try. But when I give interviews I tend to fail the Hiring manager rounds because they can see the depth of my SE career. So how to convert my IT experience to SE experience? I have put a lot of effort into Leetcode and now I have gotten to a decent stage the same thing applies to System design as well I have read books blogs etc and getting the depth would be my next target. We can hear a lot of stories in the past where a person who started his/her career as a tester or a QA and got it converted to Senior software engineer etc by working on problem-solving skills but I don't think this works in the current market. So I felt I was missing depth. How to achieve a mid-level engineer status where I can effectively tell a lot of stories and challenges I have faced in my career and show bias for action etc The most simple answer would be to do side projects but selecting a repository and a project is very hard as there are countless repositories and projects. All I need is a small ignition to start on the side projects then I think discipline would take care of the rest as I was at zero questions at LeetCode a few months ago and now I have solved 250 plus with discipline.

62 Views
2 Comments
Mid-Level Software Engineer at Quant Trading firm profile pic
Mid-Level Software Engineer at Quant Trading firmPosted April 25, 2025

My manager is acting strange

I'm at a small quant firm and I started working for a new manager a few months ago. Our relationship has had its ups and downs, but last week it suddenly got really weird. He avoided me throughout the entire week. When I'd come up to ask a question he wouldn't even look at me. Then we had our 1 on 1, he was asking me about specific results of my recent projects, which was a bit unusual. It felt like he was digging for reasons to punish me around the next performance cycle, but I can't be sure about that. He also seemed nervous at the end of it, and when I was talking during team standup too. This week, I'd say, was a bit less weird, but he ended the 1 on 1 very early. I could understand that on it's own, but combined with other things, it makes me stressed. My performance has been great so far, and it might be that he just doesn't like me and it doesn't impact my reviews that much, but I don't know if I want to keep working in such dynamic, and if I want to have a manager who is on my back waiting for me to make a mistake. In the past I tried talking to him and asking what am I doing wrong, referring to these non verbal signals. He seemed to have gotten anxious from me asking, said everything is fine and our relationship seemed to have improved after that. I'm afraid that if I ask him again because of what's happening now, he will just avoid me even more and it will make things worse. I'm just stressed out and would appreciate any advice or perspective I could get. Should I switch teams? Thanks.

60 Views
5 Comments
Mid-Level Software Engineer [SDE 2] at Amazon profile pic
Mid-Level Software Engineer [SDE 2] at AmazonPosted March 13, 2025

UI specialization vs generalist SWE

Hey all, I’ve been at Amazon for a while now and starting to think about what to look for next. I did a lot of innovative UI work on my last team but now have transitioned into fully backend/distributed systems work. The UI work that I was doing was extremely innovative and I felt like I was starting to develop a deep specialization in that space before transitioning to backend (not voluntarily since team priorities changed). I’m starting to casually look for new opportunities and I feel like I’m sort of at a cross roads on whether to pursue a specialized career in UI or focus on becoming a more generalist SWE. I really enjoyed the exciting UI work I was doing but I’m worried that most tech companies do not have enough scope to grow beyond senior levels as a UI engineer. This seems to be the case at Amazon, and my guess is that it’s because the backend always grows in complexity as your user base grows but the same can’t be said for front end. Of course there are some companies like Figma, Netflix that have a lot of UI scope/ambiguity. Im looking to eventually move to Chicago for personal reasons and am a bit concerned about the market out there (always open to remote also). I’ve been getting a bunch of big tech/unicorn/HFT recruiters reaching out. Some would let me interview for front end but there are others that seem to only be hiring backend. I’m comfortable working in both, but I feel like I need to pick a side since that will determine what prep work I need to do. Was wondering if I could get advice on whether it’s smarter to become more of a specialist vs generalist in today’s market. Right now im mostly interested in working at big tech/HFTs/large unicorns instead of smaller startups.

60 Views
3 Comments

Learn About Mid-level Engineer

A mid-level software engineer has all of the foundational technical skills, industry knowledge, and practical experience that allows them to contribute to software projects. They can collaborate with cross-functional teams, handle complex tasks, and demonstrate a deep understanding of the technologies they work with.
A mid-level software engineer can demonstrate a certain level of technical proficiency and independence. They should be able to handle most bugs without needing constant guidance. They should also be able to independently implement features with medium complexity. It is the level where one becomes less reactive and more proactive. Proactivity means anticipating where bugs may show up as well as suggesting improvements in the codebase. They should have a high standard of code quality and high velocity of code velocity.
The journey from a junior to a mid-level engineer is a significant step in one’s career. It’s important to focus on developing the skills necessary for the next level. This shift involves being able to write code to being able to write better code faster. One should be able to understand systems, plan out projects, meet deadlines, and occasionally function as a lead to make the transition. They should also be improving their communication skills during this period and seek feedback on their work from more experienced software engineers.
The transition from a mid-level engineer to a senior engineer involves a deeper mastery of technical skills, leadership capabilities, and a complete understanding of the software development lifecycle. Senior engineers are responsible for making high-level architectural decisions, guide the technical direction of a project, and mentor junior and mid-level team members. Collaborate with your manager to develop a formal growth plan. Take the initiative to write the document yourself and discuss it with your manager. One should be able to recognize gaps that a mid-level engineer has so they can improve them: writing more code rather than reviewing code, not being available to help out during big incidents, or only dealing with one’s own code. By focusing on these issues, you will be able to exert your influence more broadly across your team and company. You should also consider mentoring some of the more junior members on your team to help them grow and develop their skills.
The journey from a junior engineer to a mid-level engineer or a mid-level engineer to a senior engineer involves a continuous process of learning and refining one’s technical, communication, and leadership abilities. One should strive to have more and more impact and influence across their company to have a successful career progression.
Show more