Profile picture

Junior Engineer Career Development Videos, Forum, and Q&A

How A Junior Engineer Can Grow Their Career

Almost every software engineer starts their full-time career journey here. The content here breaks down how you can start your career off with a splash and grow past this level as quickly as possible.

Switching teams after joining for 6 months - How to go about it?

Entry-Level Software Engineer at Flatiron Health profile pic
Entry-Level Software Engineer at Flatiron Health

Hey all, I'm a new grad Data Scientist and I've been working for my current employer for about 6 months now. It's a mid-sized company so I didn't get the chance to pick the team when I first joined. I realized not that long into the job that I don't want to stay on this team for the long term, and today I just heard the news about another team actively hiring for Data Scientists. But I'm not sure if I should pursue this opportunity for a few reasons:

  1. I've only been at this company for 6 months and haven't gone through a formal perf cycle yet. This means that I would be evaluated on a "case-by-case basis" and would need approval from the HRBP and my manager.
  2. They are hiring for one level above my current role, although someone on that team told me it's flexible.
  3. My current team is understaffed and is currently hiring as well, so there is a risk of my manager not approving this transfer. This also means I won't have enough time to prepare for the interview.
  4. This is not currently listed on the internal job board (although supposedly this position was only released externally today so the internal job board might have been updated yet)

Here are a few reasons why I want to transfer to the new team:

  1. Due to the scope of the work on my current team, I feel that I'm not learning as much as I'd like to. It's not very technical and relies heavily on specific business contexts. I'm more interested in improving my technical ability in writing code and building products over learning business contexts, at least for now.
  2. A lot of my current work involves writing ad-hoc SQL queries to support other functions. I don't find a lot of value in this kind of work and want to invest my time in building stuff from which I can learn new skills.
  3. I interned on the team I want to transfer to and really enjoyed it. I keep good relationships with many of the team members and am familiar with their work. Also, I genuinely think the work they are doing on that team is very interesting.
  4. I don't see a clear way of progression on my current team. My current team was only established two months before I joined due to a reorg. Every IC on my team is brand new and my manager is brand new to being a manager as well. There are no senior engineers to learn from and I can't see what senior engineer scope looks like on our team.
  5. Our team supports the sales team in client communications, which means we have very unpredictable workloads and deadlines. Sometimes I have to work very long hours and take on-call requests which can be very stressful.

I really want to switch to a new environment but I feel like my chances aren't great. It would be great if folks could share their thoughts on:

  1. Should I reach out to the prospective team's manager to express my interest in this role right now?
  2. Since manager approval is required before starting the interview process, it's possible that I would have to stay on my current team with my manager knowing I want to transfer out. I think it is a situation I want to avoid but also don't want to miss the opportunity because of this.
  3. In general, what would be a good approach to this? And is there any specific advice?

Thanks in advance!

Show more
Posted a year ago
619 Views
2 Comments

Stuck as an Entry Level Engineer

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

Hello,

As the title says, I’m stuck as an entry level engineer in FAANG for almost 4 years now. I’ve been reflecting on what I’m doing wrong.

My first company I worked for 1 year and didn’t not like it because the lack of mentorship. I joined and my questions never got answered, the tech lead didn’t really care about giving mentorship, just gave me links and bug IDs. I was able to survive for 1 year but I left the company because I felt so lost. My manager mentioned that I was “on track” to getting promoted but I hated the culture.

Then worked for 1.9 years on another company, where I received awards for my projects and contributions. I did receive mentorship here, but I was not able to get promoted. At the end of the timeline my manager mentioned I was moving slower and slower. I was working as a full stack and I believe my error here was not playing my strengths, since every time I had to take another project it would be on a different area, such as server on a language I never used before. I had a few discussions with my tech lead and I felt I lost my team trust because they would give a lot of comments, and just get a lot feedback from other people. This kinda demoralized me and made it hard to keep working so I changed teams. My last team I worked for 8 months before getting laid off. Here I also received recognition for my projects. My first project I missed the deadline because the onboarding had nothing to do with my project. I integrated our tool with an external team, so most of the code base I worked was not even ours (the techlead and team didn’t have much knowledge). Then I was given another project where I was starting to get traction, onboarding and project matched, I had to ramp up again on the new tech stack and my manager was getting frustrated with me, my team was very helpful and I was slowly to become independent. I feel like people trusted me here and code reviews would go smooth this time, at the end I was finally getting positive feedback, but was affected by the layoffs. From reflecting, here is what I did wrong:

  • Not communicating well enough my work with my managers. Status updates I was blocked/learning and that would make me look slow.

  • Not very good mentorship, I feel like at the beginning I needed lots of 1:1 to be able to learn our teams codebase. Sometimes I got very good mentorship but not complete. So I learned well parts of the code base where the tech stack applied.

  • Switching projects too much, went from front end, full stack, server side with several languages. Every time I had to re learn a lot of new of the tech stack.

I did get several recognitions for my contribution with at least helps me think I’m not completely inadequate for the field.

I am looking for a new position, is there anything that could help me perform well as a mid engineer?

Thanks

Show more
Posted 2 years ago
612 Views
2 Comments

Finding Your Identity in a Role that Doesn't Quite Fit (while everyone else seems to be growing faster than you)

Entry-Level Software Engineer [SDE 1] at Amazon profile pic
Entry-Level Software Engineer [SDE 1] at Amazon

Hey everyone,

I've been abit lost in my job recently and feel disappointed by own performance. I'm part of an infrastructure team, and while the primary force pushing me forward is my personal engineering growth, I can't shake the feeling that the domain itself doesn't resonate with me. That said, being an average l4 I'm not in a position to switch teams.

What's keeping me going is the goal of self-improvement, which is helped from being surrounded by my incredibly talented colleagues, each bringing their unique strengths to the table. For instance, our senior engineer is an incredible communicator, teacher of concepts and general problem solver, another engineer is a coding machine and works extremely hard, and an L4 who joined at the same time as me is very customer-centric. In particular, it was through observing the L4 leveraging his strengths, while almost neglecting his weaknesses (he doesn't care as much about code quality and is quite argumentative) that I felt uncomfortable with my own trajectory. I've been so busy with trying to improve all my weaknesses that I'm now reflecting on whether I should focus on my strengths.

All of that said, I've been here for a year, and I'm struggling to pinpoint where my strengths lie. I'm willing to put more hours than others but for obvious reasons that should in no way be considered a strength (my manager described me as a hardworker, which i don't want to be known as haha). I'm also a very enthusiastic person and very open to feedback, but it leads me to being pulled in different directions. I don't think I can be an engineer that does it all and I think Amazon wants you to focus on your strengths through their conflicting leadership principles (e.g. bias for action versus insist on the highest standards, deep dive versus thinks big). I've been reading this book called Atomic Habits recently and it really focuses on the idea of identity and how that shapes your habits. It seems like everyone in my team has built an identity based on what they're good at, how can I find mine? And are there certain skills that provide higher ROI over others that I can perhaps focus on, given that I don't really have any strengths right now?

Show more
Posted a year ago
577 Views
4 Comments

How can I handle a situation where honest mentoring resulted in junior acting rude?

Anonymous User at Taro Community profile pic
Anonymous User at Taro Community

I am a senior engineer and closely guiding a junior engineer on the implementation of a new micro service. I have provided her the high level design for same and staying consistently involved in any low level design discussion, blockers and code reviews.

However, I am involved in multiple tracks and it’s not possible for me to randomly pause everything and answer her queries right away. Therefore, to keep her unblocked, as there are stricter deadlines, I also setup twice a week invite where she can get my help on any discussion or questions, as required.

Still, in an unofficial feedback she told me that she was blocked on my time and I need to give more time to discussions and PRs. I tried to give some helpful return feedback that she should be asking pointed questions to get quicker help, and also she should do some research before right away asking for help. I also told personal examples from my career journey regarding how I navigated situations when I got blocked on a senior’s time.

However, this resulted in her passive aggressive behaviour towards me. One such behaviour example is in code review - when I commented that local environment specific initialisation code shouldn’t be in the main classes, she responded that she doesn’t see any problem and it’s just unnecessary.

How do I handle this situation better?

Show more
Posted 2 years ago
558 Views
5 Comments

Should I be wary of what tools I work with to maximize delivering impact?

Entry-Level Software Engineer [SDE 1] at Amazon profile pic
Entry-Level Software Engineer [SDE 1] at Amazon

I've always been the one to dive into problems and solve them without thinking about how difficult they are but recently I've been running into this failure mode where many of the problems I work on involve using old tools that are cumbersome to work with. The result is that it takes much longer to deliver my work compared to those that work on packages with newer tools (I'm talking about native AWS lambda, s3, dynamo, etc) and sometimes I wonder if I'm doing what's best for my career.

Some cumbersome tool examples include

  • One package uses an old technology that doesn't allow us to test our changes in our dev desktop before we can submit a PR
  • Another package doesn't map correctly our dev desktop to the prod environment so it's sometimes difficult to reproduce the issue
  • Some non aws tools do not really provide much information to help the user debug their problems compared to the native aws tools

My company has at least acknowledged the issues with the above first two bullets and has slowly started deprecating those tools. Oftentimes the senior and mid-level engineers work with newer tools and therefore aren't as familiar with the older ones, which is fine. I could just avoid working with these packages altogether and only work on the packages that involve the shiny new aws tools but I'm not sure if that mentality is what's best for my career.

Show more
Posted 2 years ago
507 Views
2 Comments