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.

How to optimize career direction as a grad school student?

Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro Community

Hello Taro Community, I hope you are doing well.

I was hit by a lay off mid sept and I have been unable to land a job. I enrolled in Grad school since I have limited unemployment days because of my student visa. My degree starts Jan 2024.

During Grad School, I am only allowed part time work. I am still looking for part time work in the tech industry. And currently on 3 years of work experience.

I want to do things right this time when I graduate and go back into the job market again after Grad School.

An obvious mistake I made which was I didn’t have a clear direction of career in mind. I kinda wanted to have a tech job where I get to code, pretty vague and my applications were also shooting blind darts and seeing what sticks. I did land my first job quite fast after graduation from undergrad and got a new one a year after with a better pay and change of location which was my recent company I worked in for almost 2 years.

But these last 3 months were pretty brutal, I know the market wasn’t the best but I could’ve also been more prepared. I want to improve my odds for my next job hunt.

My goal after graduation: Front End Developer/ Full Stack Developer Position. Preferably in a non tech company example: Starbucks, Nike, H and M, Chase Bank etc.

and I set location and pay range goal too.

Question: From the seasoned in the industry here, what are some actions I can take on daily consistent basis during my Grad School to move closer to this goal and possibly achieve it when I graduate?

My plan:

  • Keep revising the fundamentals of Front End and Back End to have strong grip on interviews.
  • Personal Projects for a stronger portfolio

Open to any suggestions.

Thanks in advance.

Show more
178 Views
4 Comments

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

Mid-Level Software Engineer at Mastercard profile pic
Mid-Level Software Engineer at Mastercard

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:

  1. Any tips on tackling system design questions, especially the coding part? Most online resources seem to focus more on design rather than coding specifics.
  2. How should I balance DSA, system design, frontend prep? What topics and how much time should I commit to each of them?
  3. Also, am I on the right track leaning towards applying for just frontend roles?

Appreciate any & all feedback!!

Show more
134 Views
2 Comments

How to talk to my manager about switching companies?

Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro Community

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:

  1. 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)
  2. 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!

Show more
125 Views
5 Comments

Should I have worked on weekends to ramp up faster / deliver more?

Senior Software Engineer at Taro Community profile pic
Senior Software Engineer at Taro Community

Hi all,

I joined my current company (known in our industry for not-so-good WLB) 6 months ago as a Senior Software Engineer and have been doing side hustle in the evening and weekends over past 6 months beside my main job. This means I still completed the 9am to 6pm work schedule before doing my side hustle.

Now my manager is saying I have low bug fix count and my team consists of some weekends workaholics which I suspect I’m being benchmarked against. My upcoming performance review is due end of December 2023 (1 month away). The expectation for my level is ramping up in 3 months which means the last 3 months are no longer considered ramp-up period.

What should I do in this last 1 month leading to the performance review? Should I go all in on the weekends too or should I keep the pace I’m working (I’ve started working in the evening from 7PM to 10PM since receiving this feedback 2-3 weeks ago but on weekends I still hustle). Was I wrong in doing side gigs / projects while ramping up for my full time job and should have instead pushed weekends to ramp up? What could have I done better in the past 6 months and moving forward in 1 month ahead?

I know Rahul talked about doing side contract gigs and Alex talked about doing side projects while both are still at Meta (a very demanding big tech company). How did you guys handle the pressure and what are your schedules like? (Wake up @ 4AM, work on side hustle till 6-7AM, then go to sleep at night around 12AM LOL)? I'm curious about how people organize their side gigs schedule.

Thank you for your advices. I really appreciate it.

Show more
520 Views
2 Comments

Direct manager has opposing views with the rest of upper management. Which one should I follow?

Mid-Level Software Engineer at Pre-series Startup profile pic
Mid-Level Software Engineer at Pre-series Startup

I am working at a 2 year old startup that has just launched its product a few months ago. The launch was considered a failure because the product has so many issues and customer complaints. Some customers even stated that they prefer the competitor product.

After being here for less than 6 months, I observed that the company has a culture of rushing everything with lack of planning and resources/manpower to execute their vision. None of the upper management has business experience in this exact product, they only have experience in tangentially related product. Also, prior to the formation of the current engineering team, the company hired an overseas vendor that overpromised a 6 months project that dragged out into 2 years. That is the main reason the current engineering team I am part of is built: to replace the vendors. The investors are known to be very profit-oriented right from the start, and they are also funding another startup that has the exact same product as my company, although this startup will not be launching anything until next year. The combination of inexperienced upper management and culture of rushing things lead to product failure. Thankfully, I think the atmosphere in the office is still pretty positive and laid-back. People are not pointing fingers and they still do their best to recover from their mistakes and prepare for future initiatives.

My manager has stated from the very first time I join the company that he prioritizes quality over speed, and given our previous product failure by the vendor, I agree that this is the solution. However, the Product Manager doesn't agree with this and he pushes us to prioritize speed over quality, even if that's the exact mindset that leads to our product failure. The rest of the upper management seems to adopt the same mindset of quick fixes and rushing, and the most alarming part is that we don't seem to have identified our core users, so I'm not sure if our previous launch has actually taught us anything. Also, I noticed that the Product Manager is lacking competencies in some key areas. I expect a PM to be someone who can not only have a vision on what the product would grow into, but also someone who can do analytics, business projections, and prioritize the most impactful projects for the team. In our daily interactions, he seems to be someone who just passes words from one person to another without doing any substantial management. This is slowly leading to resentment from my manager towards the PM because the team is slowly being overwhelmed with unimpactful tasks that hinder our future milestones.

My questions are:

  1. Which direction should I follow? My manager's or the PM's (majority)?
  2. Should I consider this a sign for me to look for new company? Or is this still normal and workable? If yes, what kind of role / actions should I take in this situation?
  3. How should I convey this in my 1-1 to my manager?
Show more
75 Views
6 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