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

Is it common for candidates applying to FAANG companies to receive a timed online assignment as the first step in the interview process? Does this usually indicate that the company views the candidate as less qualified, compared to the typical recruiter phone screen involving two DSA questions? Is there any way to avoid this? Or beggers can't be choosers and we gotta just go through it anyway.

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.

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 "There Is No Such Thing As A Stupid Question" around asking for help after being stuck for 15-20 min, but I worry this might be too frequent.

I've been on my current team for around a half, working primarily on the back-end. Unfortunately, I discovered after I joined the team that Android work is very interesting to me, so in order to pursue this, I would need to switch teams. There is actually a team fairly close to mine in my org where there's compelling Android work. Right now, I'm heads down on a big project, so my immediate instinct is to wait until that's done to bring up this conversation with my manager, who I have a very good relationship with. Is this the right thing to do or should I have this conversation sooner rather than later?

Hi all, I entered the company as an L4 Frontend Engineer and it is my first tech job, so I started with 0 experience. Our team has a lot of frontend tasks, but also has a lot of backend work as well. As a result, I have been doing a lot of backend work when it is necessary and there isn't much difference betwee an SDE and FEE in our team in terms of the work we do. My manager knows that I had 0 experience prior to coming here and recognizes that that I'm able to do both backend and frontend work. He mentions that I could always transition into the SDE role if I wanted to. My question is, would there be any huge benefits of changing my role to be an SDE for my career? At this point, I wouldn't say that my skillset is more geared towards Frontend since I'm doing both and this is my first job. My original intention was to stay a Frontend Engineer as I find frontend work more fun and it was what I studied the most for when preparing for interviews. But my friends were telling me that SDE would probably give me more opportunities in the future, so I've been thinking about this lately.

I'm a 2023 new graduate working at a mid-sized software company that operates remotely. The company has a rotation program for new graduates, and my first rotation was with the backend team. After six months, I moved to the mobile team, and in another three months, I must decide whether to stay with the mobile team or return to the backend team. Both teams have positive cultures, work-life balance, teammates, and managers. However, it seems the mobile team's manager faces more pressure from the leadership. The work I've done on both teams has been interesting, although the mobile projects were more challenging. This has forced me to think more about structure and patterns when writing code. It's clear the mobile team needs more engineers, while the backend team receives a steady influx of new graduates each year. There were noticeable differences in the onboarding processes of each team. In the backend team, my tasks were intentionally organized, starting with simple tasks like deleting a few lines of code and gradually moving to small projects with pre-written design documents. The mobile team gave me a series of official tutorials for the first two months. The tasks varied greatly in difficulty—some incredibly challenging and others relatively easy. I understand the difference, as the backend teams have more experience with new graduates, while the mobile team typically hires experienced engineers directly. My decision pivots on whether I should pursue a career as a backend or mobile engineer. I am grateful for the rotation opportunity my company has provided, but I'm unsure about the next steps. What factors should I consider when making this decision? What kind of question should I ask my managers or help I can get from them for making a better decision?

My bottle neck is debugging when you can't run code. When practicing I am able to run code and add prints and trace the code. But often in a real interview you have to debug through pure reasoning which is hard My performance is getting hit because in DSA I often get an answer 95% correct but the interviewer tells me I have a bug and I find it really really hard to trace the bug especially in recursion problems

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.

I'm considering a team switch, but I'm wary of the effect that it will have on my E3 -> E4 promotion timeline, which I know we have to do within 2 years. I've been at Meta for around a half - Does the timing for a switch work out here and what other factors should I consider?

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?

Hello, I just wanted to get some advice last month I was terminated from my job after being placed on PIP/probation. When I first joined the company I had successfully completed training in React but was put on the team that didn’t use it. When the first review cycle came one of my teammates described my learning as flat and my technical skills as inadequate. There was even a time when I was ignored and tasks were passed over and one where I couldn’t come up with a plan. The junior who they assigned it afterward had the same issue couldn’t find and also didn’t need to come up with a plan but was allowed to work on it. Also, I was given noncoding tasks for a time or generic unit test tickets for functions that didn’t need it. Eventually, I and the other junior got a task that was basic and miscommunication led to a delay and they complained about us both because of how it took. Then the assignment that sealed my fate was I had to implement a microservice and node API with a unit test in 2 weeks. There was a reference code but we couldn’t ask for help from senior developers. When my manager saw my progress he PIP'ed me and then when saw the demo he was underwhelmed and said I couldn't justify the code had a poor understanding of restful API concepts and my test didn’t meet functional requirements he wrote up the paper to basically have me fired.

Hello, everyone. It is March 29, 2024 at the time I am creating my first ever post on Taro. This is the Friday night where as of now, I am no longer an employee of a Fortune 500 company I used to work for. I was, how one says in corporate talk, "impacted by a layoff". I was given news of this on March 7th that I had a few weeks before I needed to return all my work technology and leave. This is the night of my last day in the company. People in the company liked me, so they told me to apply and come back again. A LOT of people were willing to let me use them for referral. It was one of the top 10 worst feelings of my life. But, it should not be one of the top 10 worst things to happen in my life. It's on me to make sure of that. I'm only 24, so I'm confident I can bounce back. I was also given a severance package to last me until the end of July. My company provided me outplacement benefits (resume writing, interview prep, etc), but I heard they honestly weren't too helpful. That's why I'm here. What I've done in the meantime is update my résumé. I also have a plan of action for how I want to handle this upcoming first week of the job search. I want to build small-scale projects of each programming language on my resume which showcase understanding of mid-level to advanced topics of the skills I list in my stack. I want to treat my job search like a 9-5 job, where half the work day is spent building meaningful connections, applying strategically, and interview prepping (I need a LOT of that now), and the other half is spent on coding, be it refining what I think I know and adding new skills: hopefully getting chances to contribute to open source and giving back to the community. I think I need to work on things such as making my résumé stand out, ensuring my interview prep is rock solid, and finding opportunities to show what I can do. In the meantime, I'll check out some content that Alex and Rahul have on Taro, but I want to ask everyone else how I can refine the best way to begin my approach. What do you all think I can do? Thanks!

Hello, I am an Entry Level Engineer at a mid sized company. The thing is, my team has a very strict deadline which we have to meet at all costs. For more context, I have been with this team for around a year now. I had done some menial tasks of building small easy features and styling the components in React. I have a task now where I am supposed to write unit tests for a particular component from scratch in jest. ( I think this is a learning opportunity in disguise but concerned if I might not able to finish the task, as I already got a call out in team standup that my area is lagging behind ) The thing is I have not done this kind of task before. I am super overwhelmed with this kind of situation and everyone in the team is expecting me to deliver it asap as we have a strict deadline. I tried to convey that this is something of a new task I am trying to a senior engineer to understand how they solve these kind of problems, but was mocked in return and was told I should already know (I agree to some extent ). The approach I am trying right now is to understand the functionality of that part of component, trying to understand the code written for that and start making my own tests cases. I am also looking at the other unit tests written for other components but feeling super overwhelmed as I am clueless what to do. Could someone please advise me how to approach this problem ?

One of the tips for processing feedback is “to convert it into action items”. What should you do if you don’t really know what to do with the high-level feedback you get? Example: I got the feedback that other engineers don’t think that I understand the framework/library we’re working with deeply, not understanding the patterns and whys behind things that we do in our project, not knowing how to use different/“better” patterns. Unfortunately, they didn’t give me a specific example, so I’m unsure on how to convert this into an action item. We don't have mentors, so there isn't anybody who can "teach" me, except learning from code reviews, asking to do more pair programming, etc. My idea would be to study up on “design patterns”/best practices for the framework we’re using, but I’m unclear on if that would really solve the issue.

Hey folks, I recently got promoted to L5 (Mid Level). Looking for any advice in general on how should I approach my work, what to look for etc. Any words of wisdom that people would like to share? TIA PS: Apologies if this sounds too generic. My intention is just to learn from other people's experiences. Any advice is welcomed.

I am a back end engineer that works with Java. What steps could I take to make a switch to a job that works with hardware and software? I have some small side projects to learn more firmware related skills but I'm not sure how I could make something that could help me switch career fields.

I joined about 6 months ago and my manager is absolutely great. I don’t have anything where I think they can be better at at this stage. At the current stage, I feel like I have a lot of self improvement to do before expecting anything more from them. What do I say in the critical feedback section for my manager?

I was laid off on November 15 2022 and since then, I have been tinkering in different stacks building small projects in C#/.NET and Java / SpringBoot based on job demand from postings. Professionally, I used JavaScript / TypeScript and React as well as Python, Ruby on Rails, some Docker and AWS for 1.5 years. However, somehow, because of anxiety over getting a job, I have strayed from getting good at any stack and revising Django to build a MVP of a URL link sharing app and building just because I don't know if I'll ever get users or scale as I never did something really impressive hitherto in my career. Because I wasn't really targeting big companies, I have been casually leetcoding etc. this past year and a half and am decent enough to do easies and some mediums in Python. However, recently, I haven't been really applying as much, but got reached out by Google and Meta based on yolo applying mainly; I failed my Google early career phone technical and have my Meta screening 45 minute round for an IC4 role I applied to in 2 weeks. I am preparing as the recruiter sent me some resources after our call, but I don't know what my priorities should be. As I don't have high hopes, I assume I should still try to go deep in a stack, use more of Taro's resources such as its jobsearch tool etc. Any help is appreciated. Thanks.

I’ve been at meta for about 6 months now as a new graduate and my team recently got re-orged. The project of the new team is very uninteresting to me and honestly I realized that I’ve chosen an “easy” work team. I recently got advice that I need to do more meaningful work such that my skills develop and I can create credibility. I don’t think the work on my current team or the new team makes me excited or even happy in anyway. I would love to explore the metaverse org as I was heavily involved in VR/AR development work in college.however, I’d have to wait until July to start this process+ this would mean I moved 3 teams in 1 year implying I spent more time ramping up than doing meaningful work. I’m also considering switching companies. I am able to secure interviews from a few companies that seem interesting to me. Does anyone have any suggestions ?

Hi, I was wondering how you deal with constantly changing stock prices from the company you work at. I saw a video from @Rahul where he talked about the mistake to check stock prices at the beginning of each day or something. Not sure anymore where he said it. @Rahul @Alex I was wondering how you dealt with your stocks constantly changing in value. I've been experimenting with Big Tech stocks and find myself constantly looking at them. I wonder how people in Big Tech deal with that with the stocks they receive from the company. Do they sell when they think it's going bad and turn it into cash, or just keep them for the long run? How often do they check their stocks? How to they deal with the constantly fluctuating prices?

I appreciate the value of side projects mentioned on Taro, and I'd like give one a shot. Whenever I've looked before, I got caught up in not finding ones relevant to my work. I work on the backend side, working in the machine learning infrastructure/ops space. That's literally the example used in the side projects video of one where it's hard to do on your own... so is it still worth doing a side project? Maybe one in a similar language (C++), even if it's not related? I feel like I'm just not being creative enough here, but I'd rather not do a side project that's super unrelated to my area (e.g. learning a ton of frontend to build an app that has a small machine learning component) unless it's still valuable. Maybe to make this more general, how did those of you working on the backend get started with side projects?

Part 1: Before Joining an organisation How can one identify the best kind of organisation to join at different point in one's career? I understand that the advice to this question may not be a prescription for all, but how can one identify places that would help them to maximize their learning and growth. For several other people, different parameters may be important for them as well such as work-life balance. Personally, I feel that WLB is dependent on a person more than that on the organisation. Thoughts? Quite often we feel that growth may be fast paced at startups, but there can be startups that do and don't promote the growth of a person. Given that there is no list out there to check, how can one make the best suited decisions for their career, not landing at a place they should not be at? What kind of research can a person do before joining an organisation? *** Part 2: After joining an organisation Given that a person has joined an organisation, what are the kind of signals that they can identify to see whether the organisation is supportive of their career growth and is indeed the right place to be, for them? On several anonymous portals, there are people from the organisation that will talk poorly about an organisation when things are not going good for them. Managers can quite often paint a really rosy picture about the place. How do you identify the honest signal from the noise all around? If you find an organisation not good for you after you join there, how quick is it too quick to leave? How much time should you spend there before you can make a judgement about the same?

Hi I wanted to ask how valuable a bootcamp can be and can I do that instead of a four year degree? The reason for this is because of how expensive college tuition is and I'm really worried about the return on investment. I feel like there's a lot of information that I'm learning right now that I feel like I won't really need and instead, I can use that time at a bootcamp to work on projects and learn valuable skills I can use in the work field. Would I be at a huge disadvantage by not completing my 4 year degree and are there valuable concepts that I would be really missing out on by not completing my four year degree?

We are working on a technical product solution which provides APIs in a B2B fashion. We do not have any interface apart from these APIs. There are some internal tools which replicate this functionality (web dashboard) for us to view the data and some smaller B2B Companies to use, but is outside the scope of our Product / Team as it's just parity that is maintained. Our PM is not a technical person and sometimes it gets very hard to explain the reasons why something cannot be done. Or their suggestions completely miss the point / question I was asking. They view it from a visual perspective and suggest things that require a lot of back and forth to explain why it isn't feasible. I've tried in the beginning to help them get setup with basic Postman collections of our API to see the flow. Our EM is also doing their best to prioritise tech vs product. I feel some of this is reactive and not proactively helping as I feel a bit frustrated to what seem quite obvious which isn't helpful at all. What do you suggest one can do to better improve communication or even how to view things from their perspective. The one con is as a PM their calendar is always full