Mid-level Engineer Career Development Videos, Forum, and Q&A

In the middle of the hiring process I decided to review the company I had applied to in Glassdoor.

The reviews were very demotivating because they all mentioned multiple waves of layoffs in the last year.

By the time I read the company reviews in Glassdoor I had already had 3 interviews: phone screen, technical interview (leetcode) and system design interview. I performed excellently in all of them. The feedback from the interviewers and the recruiter was really good.

In my last interview with the hiring manager, everything went perfectly until it was my turn to ask questions. I could almost tell he was about to offer me the position. This was the question I asked him:

"When was the last wave of layoffs at <company>?"

He was surprised; I could tell by his facial reaction.

One week later, the recruiter sent me an email with an absurd reason for why they decided not to extend me an offer.

Do you think that the question I asked was the sole reason for my rejection?

WLB also means something different to people and therefore I'm curious what the best way is to discover the "truth" of the team you are interviewing into before both applying and joining a company.

For example, when I worked at Amazon, I did not work beyond 40 hours in either of my teams, but the occasional weekend because I was oncall, and this was fine for me personally. At Google Cloud, I was working longer during the weekdays (self-imposed because this was during COVID and I never worked weekends), but other teams at Google have been more relaxed in general.

I've been told Meta, Amazon and a few others have a poor WLB balance, but then I've also spoken to managers (and experienced it myself in the case of Amazon) that this is team dependant and manager dependant. I also assume it varies by your level.

That said, I'm a DE, so likely the stress level overall is also different to a SWE, hence this post.

I've been a Data Engineer for most of my career and my observation is that scope as a Data Engineer can plateau and therefore I see a lot more L4/5 DE's than L6+. I think it is because you don't impact the bottom line directly and regularly.

At FAANG's I've worked at so far, finding new scope can be difficult even when you are working with stakeholders: it is "easier" to scope/build a product (i.e. SWE work) and show metrics of success to add value vs building a data pipeline which may be limited to them having a reporting need for example which often isn't the case especially in a more established firm.

I moved into a partner facing DE role to help more with scope/stakeholder exposure. The highest impact project I worked on so far is influencing an internal team to change the way we measure a particular metric. This involved mostly stakeholder management and nothing more complex than SQL queries from a technical standpoint. While it was fulfilling, this is also something I 'stumbled' upon and is rare due to challenges like partner scope/vision is limited/slow (their leadership can change and therefore you projects/ideas can), technical challenges of automating things because of larger concerns (e.g. privacy, lack of infra on their side which you have no control over) and so on (you generally have even less control than an internal DE).

In my current role, I am generally able to derive projects, but (in my opinion) they are limited in scope/value: i.e. build a pipeline, deliver an analysis. Therefore, even though the projects 'ticks the boxes' for an L5, it is not really driving a 'transformation' as an L6+ would. I also directly asked my manager what are some of the hardest problems we have, and have been told we have a lot, yet, I'm not hearing or seeing them.

Given the situation, would you:

1. Move to a SWE role internally at FAANG for a more established path 'up' (not sure this resolves the scope problem especially at FAANG as I think SWE-DE's can almost be even harder to get to L6+ on because they generally lack stakeholder visibility and focus on more top down work?).
2. Seek roles outside of FAANG where the scope of the work is already scoped to L6+ e.g. Airbnb so the 'heavy lifting' has been done in terms of scope.
3. Refine your scoping strategy within you own team, and if so, how?

Note: my motivation is to thrive at work, this isn't for a promo, just incase the post comes across as promo-focused. :)

When it comes to software engineering or landing out features or doing tasks I feel I excel in them but when it comes to showing my task to a wider audience I don't think I do a great job at it. Does anyone have any tips on how to do effective demo of your work?

I'm specialized in mobile engineering anything specific to it would be very helpful.

I am at the final stage of a interview with the CTO of a startup.

All my interviews were scheduled via an automated system on their end and hence have no method to contact a recruiter or anyone from the said company. The interviews till now followed a “big tech” process with tech phone screens, system design, etc.

This final interview is for 30min and i am guessing its going to be behavioral and some “getting to know each other” type of thing.

What are some questions i can ask to show I'm interested in the company and the role. But, at the same time i want to understand their long term plan (think 6 months, 1 year and forward)?

A side question: Should i keep interviewing for public companies? Given I'm on a visa, but the tricky situation for me being that my current employer will be undergoing a layoff in the last week of April. If i do end up getting an offer from this startup should i still be looking out for jobs at more stable companies? (i do acknowledge that there isn't any such thing as “stability”)? Any pointers or guidance on this would really help me out in making a final decision 🙏

Note: they are willing to sponsor visa

Looking for resources on increasing your team's / peer's productivity. I thought I've seen some videos / posts in the past about this and wanted to brainstorm some ways I can boost the productivity of those around me.

I have 3+ years in the industry and have been privy to layoffs since 2023. I wish to understand how you view/process these layoffs and is the current situation unprecedented or just a sine wave occurrence in the industry.

I have 3+ years of coding experience, primarily in Java, and working in a Fintech startup. The backend is primarily powered via Spring Boot here.

I heavily use Gen AI services like ChatGPT & ClaudeAi while coding. While this has helped me learn new things, I am beginning to see a mental pattern emerge.

I often find myself generating code rather than writing it myself. Sometimes this also leads to drag, as I am left explaining the context to GenAi. The pro is that I perhaps get a more optimal, finetuned code leveraging the large language model's knowledge capabilities.

Is that an optimal path I am headed for? Or should I introduce an emergency tweak in how I work to better my career as a stronger, confident software engineer?

Thanks.

Aside from LC questions, what do interviews for senior mobile roles (L5 equivalent), specifically iOS Engineering, look like at FAANG-like companies? If they are system design heavy, are there resources for mobile specific system design questions, since most of content out there is geared towards web system design?

How can I best prepare for these interviews?

Thanks!

I am a 15 year experienced software professional holding H1B. In my last 3 companies, I was a Senior Software Engineer. In my penultimate company, I was due for Staff promotion. Fast Forwarding, I was impacted by layoffs in Jan this year. I had 3 months to find a job in this market. I was applying and passing on my resume through all my network. Most of my applications got rejected quoting they picked another candidate. Some of my applications materialized into interviews , but I ended up not clearing (was in bad form and stress and also didn't get ample time to prepare thoroughly).

Finally, I got my application picked at a company through a referral, but they only considered me for SWE2. I explained them my experience and requested to consider me for SSE level, they said the panel will be open to it. But in the end, they ended up offering me SWE2. I took the offer as I had no choice. I was running out of time and did'nt want to risk rejecting this offer and waiting for a better offer. I took up the offer and joined, but I don't feel happy. I wish I had more time to really choose what I wanted.

I would like your thoughts on how "wise" is it to be SWE2 with 15 years experience. Would my age become a factor for further career progressions as they would prefer younger people? I am confused if I should stick to this, be patient, work smart and work my way up inside, or would it make more sense to keep interviewing and find something that I feel happy about. Look forward to helpful replies or referrals for SSE :)

I complained to my skip manager about my colleague's (their manager) code review standards, but ultimately discovered deficiencies in the quality of my own pull requests. As a result, I believe I have lost credibility. How can I regain trust and credibility in this situation?

What strategies can I employ to excel in my new role as a senior software engineer at a tier 1 tech company, coming as a mid level engineer.

I was wondering if you need to be part of a specific type of environment in order to make quick jumps in your career? Like to get promoted to senior level in 2 years.

I was asking because from my experience, there seems to be an invisible social hierarchy in every work place. Other people in the team may not allow me to make these jumps since this kind of anomaly will break the social hierarchy:

• There is project specific information, in absence of really god wikis you have to rely on the peers in the team to provide you such information (like how are specific parts in a service working, or how is an obscure internal tool working etc). From what I see, often times they will provide small chunks of information, as much as you need to do your task, but small enough such that they still have the information and you depend on them (probably a measure to prevent others from replacing them).
• Envy might appear between other senior folks if you progress quicker than them and might start to backstab you (For example, you need some information from them about a piece of code they wrote in order to progress, but they might do the knowledge transfer in such a way that it looks like they told you what you need to know, but in reality you got nothing; or might tell you to go debug to figure out how is something working, and you can spend days debugging modules when it would've been an 1 hour stretch if they simply told you or there was any wiki).
• Manager might not want to give you extra money and compensate at your true value.
• If you work too much, or too hard there's going to be problems withe the peers, because you increase the bar and kind of force them to work harder too.

I was asking these things, because I was wondering if I got anything wrong about these fast jumps or in general that I have a broken view about work. My first professional experience was an internship at a big tech and when got there the seniors told me that I have the same knowledge as a senior engineer, but best they could do was another internship next year (still in college).

I'm going to leave my current company in a month as I have accepted an offer from another company and I'm currently working on the H1B transfer step. H1B transfer should take three weeks at the most. Recently my org had a restructuring and my manager has been changed leading to newer project and new team member and nowadays I spend most of my time onboarding myself onto the new project. I have couple of questions here:

• What's the right time to inform the manager about my next move?
• Should I give my 100% into the onboarding? I feel low-key guilty on adding more burden to the team by doing work which will add no value at the end.

This might have been asked before but I couldn't find an answer. Can be a good video idea.

At my company, I am currently owning 3 L-sized (>1.5months) projects in parallel. They are with different teams and different product managers, and I am having difficulty managing all 3 at once.

Things I am facing:

1. Every morning, I face the question - "which one do I focus today"
2. When giving estimates in individual project sync meetings, I try to give estimates by assuming my time would be equally divided among the 3, but its almost always unequally divided, meaning some product manager is let down almost always.
3. A lot of times, if I am focusing on project A for the day, if I get pings about project B a lot, then my focus keeps going towards project B, and I can't make progress on both project A and project B.

I feel like this is such a common problem, but I cant find a solution that fits my needs.

Appreciate senior engineers' input on this

I'm curious what everyone else's experience with internal transfer was like? At Bloomberg, I failed to internally transfer onto 3 other teams in the company (1 of which I had a working relationship with). They essentially put me through a full interview process like hiring for another company (coding, system design, talk through a big project you worked on). I believe I failed these because I didn't know understand how to sell myself as a senior (these were senior internal transfers) and had never done a system design interview before which actually eventually led me to Taro.

Recently, I was required to work on multiple things in parallel. Like 1-2 features and couple of bugs.

In theory there are dead moments, like waiting 20 minutes for a build, that I can use to do something else. But even in those 20 minutes I feel like my context belongs to that task and it seems hard to switch the branch and investigate a bug while the build is running because of the context switch and when the build is done I have to come back to the previous task and re-switch context.

Also the pressure of knowing that I have to deliver multiple things is very stressing. Even though they might not be complicated things, the pressure alone of knowing that I have multiple items and the deadline is coming is very harmful.

Is there any "trick" or effective way to work on multiple items at the same time without feeling like "drowning" and to not be affected by the multiple deadlines pressure?

I recently got laid off working as a developer working within an agency. I currently have around 5 years of experience working in the agency setting utilizing React, Next js, Vue, Liquid, and the Shopify API to create custom eCommerce sites. During my time at these agencies, I also had the opportunity to act as a lead, interact with clients, set timelines, and cross collaborate with designers/projects managers to meet deadlines.

I have been looking for new opportunities since January and I've been able to secure a couple of interviews, technical challenges, and one onsite. Most of my interviews have been coming from agencies, but my preference is to join a tech startup or maybe more on the brand side of things within the Shopify niche. Below are a couple of questions:

1. Will working at another agency hurt my career in the long run? My ultimate end goal is to work for a bigger tech company if possible.
2. If an agency does want to hire me right now, should I take the job for now or just wait for one of my preferences?
3. I notice a lot of developers within the agency space freelance after their 9-5. Does studying for interviews or future jobs provide a higher ROI instead of freelancing?
4. Lastly, I just finished (super helpful!). It seems like the best course of action for me is to apply a lot, work on side projects instead of grinding leetcode, and study system design. Does this seem correct?

Thanks in advance!

I worked 3.5 years on the backend for a large applications with the stack of java, spring, hibernate and mysql + bunch of internal frameworks. Now I switched to another company and for 3 years I worked on the backend for another large applications (thousands of users) but with multiple languages. There were microservices in python, go, java and C++. I was also required to write some react code. While I was able to hack around (not the top notch code) and ship things that work, I was wondering if this kind of experience will damage my profile in the job market, since everyone wants someone that is specialized.

I passed my E4 phone screen round at meta and my recruiter offered me to go through a separate PE interview loop because of my background as a site-reliability engineer (5 YoE). Has anyone ever done a PE interview, ie troubleshooting phone screen and then a more in-depth Linux specific systems interview? Any tips or advice would be super appreciated!

Hi everyone,

I recently had my bi-annual performance review in a FAANG-like tech company, where I was evaluated against four key pillars: project impact, craft excellence, direction, and organizational impact. However, the feedback I received was an overall "met expectations" rating without specific details on how I fared within each pillar for individual tasks.

I'm now looking to engage in a follow-up discussion with my manager to gain a more granular understanding of my performance. Specifically, I want to discuss:

• How I was evaluated against each pillar for the tasks I undertook (whether it was met expectations, below expectations, or exceeded expectations).
• Clarification on which tasks were aligned with each pillar and how my performance was assessed accordingly.
• Identifying areas for improvement and potential growth opportunities within each pillar.

Any advice on initiating this conversation respectfully and productively would be incredibly helpful!

Thanks for your insights!

Is sprint planning and agile not a thing at meta? I’m doing a lot of research since I’m trying to see how it’s like as I’m spending time leetcoding and if the vibes there are it’s on you to plan your projects and set a timeline then sprint planning would actually make the engineers not excel in independent planning?

And it seems like it’s against good e4 performance to be prompted to set your deliverables at the end of the sprint? Just not sure how agile is used cuz if it’s on everyone to figure out how to project manage on their own then what’s the point of agile?

I've been working as a software engineer for 9+ years. Even though graduated in CSE, I never put a great effort in learning DSA into deep. Nor did I found interest in solving problems in leetcode.

I mostly worked in startup jobs. The expectations are kind of clear here. Build apis and features and deploy.

I believe I know moderate amount of system design and build product from scratch using js tech.

Have hands on experience in Node, React and AWS. Lead ~4-5 members for a short time. Never had the opportunity to build product which needed a great scale. DB sharding, working in a system that had 100s of micrsoervices is something I have never experienced.

I'm making around $75k in UAE. How can I give myself a learning path which would lead me to a better paying job. Ideally ~120k+. Spending 2-3 hrs daily would be difficult because of personal commitment. Maybe 6-8hrs total in a week I can manage.

Thanks

I received a verbal offer from Meta for the Android role and I'm in a team matching phase. Recently team matching has been a lot of struggle and could take weeks or maybe months. Last year a lot of hiring managers posted on LinkedIn about hiring for roles and I did exchange a conversation with them. Is it wise to ask the hiring manager on LinkedIn about open roles in their org and then telling my recruiter about it or I should go with a team that the recruiter helps me to connect with?