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

Does it get worse as you progress from L3 -> L4 -> L5 -> L6 -> etc? Intuitively that seems like what would happen as your scope grows across promotions: Is there more overtime associated with the more senior levels?

Hi all. I got laid off in April from Amazon. I have been looking for a job since then but I am a junior engineer and I haven't been able to get an offer. Someone at Taro suggested that I fill the gap by claiming that I was working on my own startup. This could get me to the mid-level bar.

I thought about doing some personal projects and claiming that I was trying to monetize them but failed. I am concerned that recruiters and hiring managers are going to see right through that though. Side projects are ideally done on the side of my full-time job.

What are some ways that I can fill the employment gap and get to the mid-level before I secure a full time job?

Let’s say 2 companies give you different levels, but the compensation is the same. Is it better to have the lower level to have lower expectations? Zooming out, how should I think about level and its overall importance across my career.

I'm looking to get promoted as fast as possible, so I really want to understand how very senior engineers think. Here's some additional questions to add more depth:

1. If you were to backtrack and retrospectively analyze the careers of the engineers who reach staff level at Big Tech, what's the common thread with all the projects they've worked on?
2. How were they able to land themselves on those projects?
3. What allowed them to put themselves in a position to contribute to such high impact projects?

I'm still navigating a career switch to SWE, and I tend to get pretty overwhelmed when looking at code. I already ask a lot of questions, and I want to be more self-sufficient because my full-stack team members are pretty busy. (They are all kind and would all be willing to to take some time out of their day.)

How can I get faster at reading code on my own while balancing a team transition? I'm at the point where I understand the high-level purpose of parts of our codebase but little as to how the moving pieces all fit together.

While I understand that there is likely no magic threshold to determine the point at one needs to ask for codebase navigation guidance, a good rule of thumb would be helpful when possible.

I used to try several courses to learn C++ for Unreal Engine, however after I finished all of them, I even can't came up an idea to make a project which matched on personal limited skills. As a result I tried lowering my expectations by finding it the most basic one (I found CS50 - programming with Scratch) to build logical thinking skills. When I did the assignment (the assignment has specific perquisite), unfortunately it turns out I trapped into tutorial hell and I still can't came up an idea. Feeling burnout, I decided to take a break for few days because I believe good idea doesn't come from burnout. But after few days recovered I somehow came up an idea by looking past interest game and turns it into my assignment , however after did a few days, my idea didn't match my knowledge skills. (in this moment I don't know about Jointaro yet)

I understand programming is about doing and doing as this explains and also communication . But I'm struggling to find the solutions based on my current situation. A lot of advice and courses on internet are omnipresent, and the comments more or less just say "thank you for your advice" or "Great video" whatsoever (especially YouTube) . I tried some of them based on my current situation, however I realized there is no progress and I slowly doesn't have principle of life.

Sorry if my questions seems so futile for experienced software engineer. However I want to give it a shot to breakdown my own problem. If you think my situation has something off, feel free to ask so there will be no misunderstanding. Thank you for your attention.

Additional: I also find out whether I write blog or write questions, it takes me a lot of time (maybe 1 - 3 hours or could be more depending the complexity), because I try every possibilities to avoid misunderstanding or miscommunication. I believe people who smart at great university or company might not need take such hours to do so.

I joined a new team a week back and will soon have my first 1:1 with the skip-level manager.

Given that I haven't spent much time to have any feedback on my manager or the org culture and process, what should I discuss to get the most value out of the time?

P.S. I have gone through this question: , and I did found some great insights, but wanted to ask if there's anything more I can do given my position and experience is different.

Thank you

With the current state of the market a lot of people's career has taken 4 steps back working jobs that are worse than what they had been working or it's gonna take much longer to break into whatever you are aiming for.

It can be hard to keep perspective/"trust the process" with how bleak things are especially for someone who has never seen a down market before and has limited on perspective on what a normal market is like

For people who work on side projects: I was wondering what is your system when it comes to coding at work and then coding after work? How do you divide your time effectively between the two?

I have just joined a new team, and have my first coding task. I am currently terrified about taking the first step and writing some code and testing it.

I have spent a lot of time researching solutions, but have found myself bit in the past because of a lack of testing and research, and also am just terrified of breaking things.

What are some suggestions for getting over this fear, and how can I be more confident that the testing and implementation cover all edge cases and won't have bugs?

Hey all,

I’ve been in my team for over a year now and I’d like to change teams. In my previous companies it took a lot (of luck) to change teams (typically would only happen when orgs restructured). I’ve heard the process in google, and tech in general, is really straight forward and I’d like to get out of my org and try a different team. Would anyone be able to provide tips or guidance on how to change teams?

Thanks!

For new grads, do you recommend starting career and living in California, despite the high living costs and high taxes?

Starting my first day and I was assigned an onboarding buddy. I was wondering what are some of the main questions I should ask.

Some questions I have asked:

1. Wiki on how to set up dev environment
2. Info about all meetings that I was invited to
3. More info about what our team does?

I'm wondering if there are any other main ones I should be asking or is it just ask as they come along?

Hello!

I was assigned my first JIRA ticket at my first official dev job, which I started about two weeks ago. Given my situation, I want to know how long my manager expects me to work on the ticket, so I don't end up underperforming or not meeting expectations.

Some background: before this job, I worked at a very early-stage startup (one other person and myself for about a year), so I don't consider myself a complete junior. Additionally, I don't know my official title since I came in as a contractor and the contractor title does not match the FTE title, so I'm not sure what is expected of me.

Some of my thoughts: I've considered asking my manager directly how long he expects me to work on this JIRA ticket, but I wasn't sure if the question was too noob-like or too forward. I've also considered that so long as I'm making progress (which I am), I should be okay (until it's not).

So, all this to ask, should I ask my manager how long he expects me to work on my first JIRA ticket?

I am joining Amazon soon as SDE 2. At my previous job, I was a higher end SDE1. I have owned small internal services at my previous job. I would like to know what are some of the things that can be expected from me as SDE 2 @ Amazon ? I am expecting more ownership, but is that the only thing? I did ask the same question to my manager but he seemed very chill about it and said that he cannot say anything at the moment, maybe in our 1:1s we can discuss more clearly. Also, if you can let me know how the expectations vary across levels for Junior and Mid level and what can I do to hit the ground running and create a good impression from the very start, that'd be great. I am sure that you must have seen various E3 / E4s at Meta. If you can relate to what exactly was the difference that you saw, that'll be super helpful.

When working on a new task, I often find myself asked to estimate how long a task may take. Luckily, my team is pretty forgiving, but a critical step will be to start more accurately estimating tasks.

How do you get better at breaking down tasks to understand what needs to get done, and then giving proper estimations for how long those tasks will take?