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

I've not had great reviews from manager in the past few months. I think it all started with me taking PTO for 3 weeks in december and something I handed over to team before leaving not working as expected. Before that maybe I had a made an impression that I was not proactive enough and it all escalated with this issue in PTO. They had to source a member from another team to get it done.

After I was back from my PTO I did work really hard to get back at the work left and finish diligently, but it again happened that after this work was merged, some other api's failed in Integration environment. And I fixed it soon and got it working. But by this time my manager had decided to put me in PIP I guess.

Now about the PIP, its 60 days long and the way my manager talked about it seemed like she wants me to take it very seriously and improve and she and other seniors can support me during that. My skip manager who is a director, however seems like a not so nice person, I also have a have monthly connect with him next week. He can easily influence the decision even if I do well and my manager wants me. How do I talk to him is one question? And how do I navigate this whole PIP is another.

Since the market is also very bad right now, I'm planning to work hard and complete every objective there is on the PIP document. What do you think about this? I am on stem opt visa and might have 3-5 months to find another gig that's all.

I'm just curious about people's opinions from a tech perspective

• Does this impact current tiktok employees?
• Can this affect their RSU/equity?

Any other thoughts are also welcome!

One common complaint I get from my friends to who I pitch Taro is why they should trust a company that is "Selling shovels during a gold rush".

I personally believe there is a ton of value in joining Taro but I can see their perspective since not every coaching/mentorship service has their clients' best interests in mind.

This question is more for Alex and Rahul but others are free to chime in. What is your response to this?

Hi Taro. I got laid off in April from AWS. I interned at NASA JPL and I am considering going back fulltime and continuing to apply to tech companies. I don't have an offer but I am hopeful I would be able to connect with a team since I interned there one year and have 1.5 YOE at AWS. I have some concerns about joining JPL, because they are prototype and research focused.

• They don't have many production systems or serve customer traffic.
• They also operate mostly in small and independent groups so the engineering standards can differ a lot. The research group I interned at had poor engineering and code quality compared to AWS.
• The engineering environment is different than corporate. Some technologies and experiences missing at JPL that are common in tech are pipelines (CI/CD), TPS, tickets, oncall, debugging large and distributed systems, customer traffic, metrics, operational reviews.
• JPL pays poorly and has slow growth. You can be there 10 years and make less than an SDE-1 in FAANG.

I don't have any visa issues. Finances are not a problem. Currently I have very low expenses and good savings because I didn't RTO and I am living with my parents. I have 1.5 YOE at AWS and 3 years of internships before that. I see the market picking up so I am tempted to keep trying for a tech company.

Another thing to consider is that there is a lot of inertia when you join a job. I will have little time to look for other jobs in the first few months because I will be busy onboarding. I will also have less time to look for jobs and study for interviews.

Please give advice :)

An exception is if you talk to them such as asking a question. Sometimes I get a connection request from someone with no message that can lead into a conversation.

What is the value in connecting with someone I will never talk to?

Right now, I'm on the test side in my company, writing some automated tests but doing a lot of manual tests as well. I would like to transition to software engineering, but I'm not entirely clear on my path there. There has been precedent of making that transition within my company, but I don't have any hard commitments there on allowing me to do the same. Any advice on how I can plan out this switch?

I don't have a CS degree but I am working as a junior engineer. I am currently in the process of learning software engineering concepts and building foundational knowledge of systems (haven't really gotten into it but that's my next plan).

With the whole AI frenzy going on, my attention keeps diverting from one area of focus to another. It's hard to prioritize the things that I want to learn, and I am getting quite overwhelmed. Why? Because I've 1 year of experience and as a result of this constant flip flopping, I don't think I have really gained foundational knowledge of a certain topic which is appalling.

I failed out of my computer science program at university for this exact reason - did way too many hackathons at the cost of gaining a foundational understanding of topics. I want to do things right this time and not fall for the same trap where I sacrifice becoming good foundationally.

Has anyone faced this issue before? Looking for some advice on how to manage expectations and learning to grow as a developer.

What is the average promotion timeline from an entry-level engineer (SDE I) to mid-level engineer (SDE II)? What is considered great?

What is considered a fast promotion? How do you convince others of impact and take on more meaningful projects?

Hello! I'm a junior SWE (about 1 year of SWE work experience) and I'm currently building my portfolio + side projects and intend to start interview prep in about July/Aug this year. Hoping to move into a new role by the mid of 2025. Does anyone have recent experience with formation dev and could share on what the experience was like & if it is worth it, especially in the current job market? I am aiming for big tech firms and definitely willing to put in the effort that is needed. Also spoke to a recruiter at Interview Kickstart but read online that the quality has dropped + the recruiter was kinda pushy so if anyone has experience with IK, do share here too. Thank you so much in advance, I'll appreciate any kind of advice on how to go about prepping as this is my first time!

I just joined a new company (7 months of industry experience) and I want to make sure I can come in quickly and make an impact. More specifically, I want to become a quality contributor to the team as soon as I can.

Hey Taro members,

Since in most companies, I believe the 1:1 with Managers is biweekly or weekly I was thinking about what to communicate in every meeting. At times, I run out of things to discuss. We cover topics related to how tasks are going, feedback if any, and after that, there's not really anything else. Given the fact these meetings are recurring, I want the communication to be more natural. Any advice for that since I do realize the importance of 1:1's and would like to make the most of it?

Also, any other topics besides the ones mentioned above that should be discussed in 1:1 something I can initiate a discussion about as an Entry Level Engineer and make the most out of these 1:1s?

Thanks.

Context: I work as a Entry Level SWE at Series B Startup with 25 people; the SWE team is 7 people total. I am the only person currently under my manager & my coworkers are fairly clear about what I am building & why. Also, the SWE team morale is strong and productivity seems to be at a sustainable rate.

In general, I think my manager & mentor is an incredible engineer & empathetic person open to feedback/trying new things. He’s personable, highly knowledgable, is available to answer my questions, & answers all my noobie questions. While I love these aspects, I do feel he is a bit reactive as a manager. When I asked him if he wanted to be my mentor, he agreed but I think he interprets it as being available to answering more of my questions. I don't think he is used to being a mentor or a manager and would like to see a more proactive effort from his side to help me level up as a engineer (right now I am mostly bringing up the ideas for 1:1 meetings, and creating a growth plan, etc).

So how do I help him?

I'm relatively new to software so would love to understand more here. In particular, what does it look like at Big Tech compared to other companies? My goal is to eventually transition into a Big Tech company - Do you always need to work 60+ hours a week to do well there?

As I read through some of the technical design docs / OKRs on the team, I've noticed some fellow engineers put out some really thoughtful comments (especially the more senior folks), however coming up with such feedback observations is not always super intuitive. As a new-hire junior, I'm looking to build up this skill of conducting an effective design / OKR review.

What do you usually look for / pinpoint when reviewing a design doc or OKR for a new project? How can I still provide good feedback despite not having the same level of exposure / experience?

I am a new grad Software Engineer who has completed 6 months ago. There's a lot of internal tech stack and plenty of codelabs. Lately, I have realised that I am not prioritising learning about the stack my team uses (but I do not currently use directly).

I understand it would be helpful in one-off occasions when I have to interact with a new part of the codebase or during on-call, which I am expected to begin soon. However, I always end up prioritising my current work that I have in hand. (It is also because of the fact that I find the codelabs pretty slow and boring)

How should I prioritise learning new things? I remember Rachel's video where she said she spends 20% of her time learning new things and that seemed like a good strategy to me.

Hello, I'm doing a rewrite of my resume. I'm having trouble describing some parts I did for my job. Specifically, I was given a sink or swim I had described earlier which got me terminated. I had to develop a microservice and node API with unit tests without any guidance from senior developers. What is the best way to describe this experience in the best light?

My work is in C (which I do not have much experience in), so if I don’t understand some error that emerges (after ofc trying Google & Stack overflow & my own tests), are you sure it would be appropriate to ask a question around that??

It seems to me that after asking a few questions, my team members may feel that I should be able unstuck myself or that getting myself unstuck is simply a natural part of the process of growing as an engineer.

I'm following the guide in around asking for help after being stuck for 15-20 min, but I worry this might be too frequent.

There is a mentorship program at Booking, but I am not currently enrolled. This is because I’m not entirely sure what sort of mentorship I should seek out. How can I figure out the optimal mentor to have?

In terms of what a potential mentor can help me with, I'm currently spending a lot of cycle on a Perl -> Java migration effort across the company's legacy codebase.