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 March 23, 2024

What type of environment allows fast career jumps?

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).

163 Views
2 Comments
Mid-Level Software Engineer at Mastercard profile pic
Mid-Level Software Engineer at MastercardPosted December 12, 2023

How do I prep for Frontend job interviews? Do I apply for Fullstack?

Hello! So, my job's getting outsourced this summer, and I'm deep into figuring out my game plan for interviews. I'm mostly a frontend engineer, working with Angular, SCSS, and ngRX for our app. I've dabbled in backend too, even went full-stack in my team, but my backend skills aren't great. My manager supports me marketing myself as a full stack person, but I'm wondering if going all-in on full stack jobs is worth the effort during the interview prep, especially since I'm not a big fan of backend work. Then I wonder if the downside of applying for frontend jobs is that there are not that many and the barrier for frontend is lower (maybe because of coding bootcamps and it can be self-learned) so competition will be higher. Now, I'm drowning in prep work - data structures, algorithms, frontend know-how, and system design. Recently got hit with a surprise system design coding round in an interview (an internal position I arrogantly thought I had in the bag) I thought was all about frontend and DSA. Did okay, but not stellar, and now I'm feeling unprepared for every interview. I feel crippled to even apply to positions. It's a bit of a mess. So questions: Any tips on tackling system design questions, especially the coding part? Most online resources seem to focus more on design rather than coding specifics. How should I balance DSA, system design, frontend prep? What topics and how much time should I commit to each of them? Also, am I on the right track leaning towards applying for just frontend roles? Appreciate any & all feedback!!

147 Views
2 Comments
Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro CommunityPosted June 11, 2024

Asking for a LinkedIn Recommendation to a colleague in a professional way

Hi how can I ask a colleague for positive review on LinkedIn. My colleagues have worked with me and know what I can do they often say positive things about me. Yeah not sure how to ask for LinkedIn recommendation. The thing is it would be really helpful to me. In interviews I don't have 10 years of experience just 2 years. But my colleagues know that I learn faster than usual and what I did in 1 year was really a lot compared to average. But someone working at another company interviewing me they don't know. LinkedIn Recommendations from my colleagues can really help me. But I am worried about asking them for positive review on LinkedIn they might think that I want to leave the current company. Actually sometimes they kind off subtly tell me to leave the company, well some of them. My mentor at work tells me if I want higher salary it's best to look for different job than stay at 1 job. This will get higher salary faster and I shouldn't tell the manager he told me this. I want to ask my mentor for a recommendation for linkedin. Also after I ask my mentor this he/ the team might start treating me differently calculating for me likely/potentially leaving the company more so than staying. Giving me less scope. So how to approach this in a professional way. Hey, can you give me a LinkedIn recommendation? Why? So people that haven't worked with me before also know what I'm worth. Why? you intend to leave this company? Uh....

145 Views
3 Comments
Mid-Level Software Engineer [E4] at Meta profile pic
Mid-Level Software Engineer [E4] at MetaPosted November 21, 2024

Should I be worried

I joined this June. Our team has two chunks, one is doing project M and the other doing project H. For the first three month, project M was my ramp up project and manager said I did well. In the mid of October, my mentor told manager that I have code quality problem, writing too fast with bugs in diff. Manager talked to me once and pointed out, which I appreciate. Then the last quarter began, I was assigned both project M and project H work, project H is very coding heavy because of the design pattern and for project M, the tl didn't give any input, I would have to basically guess in the doc, according to the previous pattern, we can present the doc, let people comment, at the same time, start to work(it's building a dashboard), but my manager insist that I need to get a signoff from the project M tl, which I previously actively ask for input, no response, after the dashboard was drafted, the tl was not satisfied and told manager, manager told me he will let other people take over this. That's part one. Part two, the tl from project H provided detailed guideline and I raised diff in time, but the person was really busy, I can't get my diff reviewed, for a whole week, I only got one review, even though the work has a target date, but that seems not to be meaningful with the sluggish review process, I also asked other team members involved in project H to take a look at my diff, only one person responded after three days. The feedback from this tl is that he can't approve my diff fast. Then the manager think it's still my code quality issue, which I paid extra attention after last feedback, so I was really confused with what he said. The diff review process is always an issue, it was brought again and again during team meeting, but nothing was done to really solve it The PSC is looming, good part is that I don't need to participate it since I'm TNTE. But I still sense the atmosphere has changed from manager. I thinks the work assigning has some issue as I have never worked on project H before and because of this heavy coding task, I needed extra time for it, hence having no time for project M's dashboard. Should I be worried at this team? I am not eligible to transfer now, what should I expect next year?

145 Views
4 Comments
Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro CommunityPosted December 6, 2023

How to talk to my manager about switching companies?

I joined company A in October (prior to which I did a contract job at company C for 1 month) but I already had an offer from company B which was delayed and joining was pushed to Dec. Now, I need to inform my manager at company A that I have to leave the company. It breaks my heart because all we have been doing so far is kind of training and stuff and no active work however, I do not like the kind of work I would be doing here as it is more like a Salesforce developer/ tester with the development outsourced and they are building a team to bring development inhouse. So even though the company is quite stable and has good benefits I have decided to leave it for a better paying role that I feel will satiate my career aspirations. Here are a few questions I am seeking answers for: The company has a Winter break starting Dec 22 and my manager goes on leave from 20, when should I break this news to him? (In my last company I informed my employer with a two week notice and I was given the last date to be just a week later. I am a foreign student in USA who has just started working and utilized almost half the number of unemployment days I have for this year to be precise 2 July, 2024) How should I tell him about this decision without burning the bridges. Honestly, I have this feeling that I am kind of cheating my employer so I am finding it difficult to justify it in front of my manager. Thanks in advance!

145 Views
5 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