Big Tech Q&A and Videos

I just found out that I was rejected from one of my dream FAANG companies :(

The recruiter told me:

Thanks so much for taking the time to interview with our team - they really enjoyed meeting with you. Unfortunately at this time, we will not be moving forward with an offer. The team really enjoyed your positive demeanor, thought you had great communication skills, and a well thought out process throughout the technical interviews. I am not able to share specific feedback as per company policy, but I am of course happy to jump on a call if you have any questions.

What can/should I ask her in this call to maximize my learning to be a better candidate?

I am a senior software engineer working primarily in Python. I consider myself a pretty good coder, being able to solve problems and deliver software on time at the necessary SLA. I understand and have worked with the major Python web frameworks such as FastAPI, Flask, and Django.

But I see a lot of things lacking in myself. I am not able to handle algorithms very well, nor am I able to efficiently use design patterns.

I see that all of these skills are part of FAANG interviews and much sought after.

I also understand that there is Leetcode, HackerRank, CodeSignal and that help better ability.

What is the best way one can upskill self given the many options?

Hi!

I have a question regarding Meta's interview selection/rejection criteria.

I recently interviewed with Meta for E4 Software Engineer role and I actually did well on the interview. I answered both questions with optimal algorithms and also did everything that is expected of the candidate in a good interview (like asking clarifying questions, making a framework for the code to be written/ pseudo code, with the explanation of the process of how I came up with the solution, writing optimal code, discussing time complexity and verification/ dry run - everything within that time limit). I received a rejection from my recruiter. I can't think of anything being the reason for the rejection except that I have been a bit nervous during the interview (but did manage to get everything done still).

Is it normal for Meta to reject a candidate in the screen in spite of such performance? What else would they be expecting to proceed with a candidate? It was not easy for me to get this opportunity to interview with Meta, as I didn't have any previous big tech experience. I'm kind of losing hope on my journey to crack a big tech with this experience. To be honest, I kind of feel like I am being discriminated against. Can anyone please share your thoughts on this experience?

I'm an E5 at a big tech company. I've been on multiple projects where stakeholders waited until the very end of the projects to say, "That's not what I wanted." What can I do to prevent this from happening? I got feedback that I "need to navigate ambiguity". Does "navigating ambiguity" mean somehow predicting that stakeholders want something besides what they sign off on? If so, how do I develop this skill?

This seems to only happen on projects led by E6+ engineers or an M2. I have not had this experience when working with other E5's or more junior engineers.

Examples:

• Misaligned OKRs: At the beginning of the quarter, my M2 told me that it was okay to have a multi-quarter effort, so I planned to do an analysis and roadmap in the first quarter, then execute on improving metrics in subsequent quarters. My M2 signed off on my OKRs for the first quarter. When I provided my deliverables at the end of the quarter, the M2 said, "That's not what I wanted." Then he told me that he wanted metrics moved, even though my OKRs clearly said it was just an analysis & roadmap. I asked 2 mentors (a Director & an M2 - both not in my management chain) for a 3rd party opinion and they both agreed that there was no way to read my OKRs as moving any metrics. I'm confused why the M2 signed off on it and didn't say anything about it in our team's weekly OKR review meetings if that's not what he wanted. He gave me feedback that I need to "navigate ambiguity." When I asked him for concrete, actionable steps to navigate ambiguity, he said, "If you need to ask that, then clearly you don't know how to navigate ambiguity." I'm so confused! Please help!
• Low-level design missing on a cross-functional project: The DRI (an E6 backend engineer on a different team) kept talking in circles & refused to answer questions whenever the other mobile engineer and I asked about the low-level design for our project. The other mobile engineer tried escalating to our EM, but our EM did not help us. As a last resort, the other mobile engineer and I aligned on the mobile implementations and built that. During end-to-end testing, the DRI said, "That's not what I wanted." He did the same thing to the data scientist. The project was initially scoped for 6 weeks, but ended up taking 2.5 quarters due to all the churn around "late findings". My EM gave me feedback that I need to have a low-level design before starting implementation.
• Wrong requirements on a cross-functional project: The DRI (E8 web on a different team) provided a requirements doc that was confusing, meandering/disorganized, and hard to follow/understand. An E7 mobile engineer flagged that the doc is not a proper requirements doc at a TSG (Tech Steering Group), but the DRI ignored him and forced me to implement it. I asked for requirements clarification, acceptance criteria, and end-to-end test cases, but he refused to provide any of them. He told me that the requirements doc was all I needed. I escalated this to 3 EMs (my EM, the project's EM, and the DRI's EM) due to my bad experience from the previous project, but none of them helped me. When I asked my EM point-blank how to avoid building the wrong thing, he told me to just make sure I get sign-off on the low-level design in my mobile RFC. I made sure to get sign-off from the DRI before implementation. I also provided TestFlights every 2 weeks for the duration of the project. On the final day that I was allocated to the project, the DRI asked what happens in an error scenario. I said, "Exactly what was documented and signed off in the low-level design of the mobile RFC. Why would it be any different?" Sure enough, he said, "Oh, that's not what I wanted." When I asked why he signed off on the low-level design, he said he missed the flowchart that described the error handling. This happened even though I explicitly tagged him on that flowchart in the Google Doc. So the overall mobile design was about 80% wrong. Turns out his requirements doc said the opposite of what he wanted and that's why the wrong thing got built. The TestFlights had the wrong behavior starting with the initial build, but he missed this as well. His feedback for me: "needs to make sure we build the right thing". How do I avoid this in the future? My EM was unable to provide any advice on how to avoid this in the future. All 3 EMs resigned towards the end of the project.

I have worked as a software consultant for 4 years at companies like Amazon, Hitachi, etc.

My manager made it clear that my org is not offering return FT offers, but that he would put "incline return" for an internship position if I stayed another year in school (or somehow delayed graduation until 2025).

I could just take random classes or another major to extend my time in school. I also could do a 1-year Masters program which I have already been admitted into. But I am an older student and would rather not stay another year in school. I also feel like I am learning very little in school (I go to a small state school). Compared to the ridiculous amount I learned this summer in the industry, I feel like staying in school for another year would be a huge waste of money and time.

I could potentially work Fall/Spring internships for the next year (so basically a gap year) to artifically delay graduation by a year as well.

Becuase I go to a small state school, getting interviews from Big Tech is extremely hard. We send about 1-3 kids to each FAANG+ company each year and I was only able to get 2 FAANG+ interviews even with refferals to every top company, a 4.0 GPA and relevent experience. Even getting actual SWE engineering jobs is really hard with most CS grads getting jobs labeled "SWE" but that involve very little coding.

Because of that, my worry is this might be my only chance to break into Big Tech for a long time (if ever).

So is it worth delaying my graduation for a shot at big tech? Or should I just graduate and start my career, even if its at a non-tech company (with potentially very little actual engineering work)?

Looking forward to some great motivation and career advice. I am 55 years old and work for a local software company as support engineer for the last 5 years. Through out my 30 year old career, I have held jobs as software engineer. But in last few years I have lost my confidence.

I was advised to get into FAANG and for last 1 year I have been going through interview prep resources like LeetCode, AlgoExpert, and practicing from books like CTCI for interview prep. And then thanks to Chat GPT, AI, I lost my interest in becoming a good or even an average software engineer.

So I would like to get motivated, get a software engineer buddy here on Taro, who understands challenges of mindset at my age. I would like to expand my outlook and get energized about software engineering career. Or may be launch a SAAS application of some sort. Thanks for reading.

I’m an E5 on a platform team at a Big Tech company. I'm under aggressive timelines to create a proof-of-concept (POC) for a partner team. My skip-level emphasized the importance of this POC as well as its timeliness to me.

Our team's E6 is coding our platform infrastructure and is slipping his dates. The E6 said his infra code should be production ready in 2 weeks, but claimed there should be enough there to unblock my POC. I tried to forge ahead, but my POC is now delayed because I spent so much time trying to work around the deficiencies in our platform infrastructure. I eventually decided to prioritize some other parts of the POC to avoid losing more time while the E6 is taking his time with the infra work. How much of this should I communicate to our partner team's stakeholder? I'm hoping that I'll be able to hunker down to get the project back on track without slipping our dates. Another E5 on our team told me that he doesn't like to air our team's dirty laundry outside our team, so he usually says everything is fine until the last week of the project when he suddenly flags delays. Is this a good strategy? Or should I be honest and upfront with cross-functional partners external to my team?

Last year I was invited to an event at a Big Tech office and saw a few talks.

After the talks I ended up chatting briefly to one of the Big Tech speakers about certain aspects of their talk that resonated with me.

A few weeks after the event I had a meeting with one of the recruiters (you could submit your interest to have one reach out to you) and you could seek official mentoring from one of the employees.

I asked if it'd be possible for that person above to be my mentor and they said they'd arrange it if possible.

I got an email officially introducing me but they'd be busy for X amount of time.

After X amount of I time I reached out to them, no answer.

It's been many months and have tried to reach out to them sporadically between that time but have never gotten a response both via email & LinkedIn.

I'm not too bothered now but do still question why?

Currently, I hold a high senior position (~ L6) within a large tech company. At this point in my career, I often find myself grappling with the decision of whether to focus on advancing as an individual contributor (IC) or transitioning into a management role.

Although I genuinely enjoy mentoring junior engineers and helping them grow in their careers, I have a strong aversion to certain aspects of management, such as the frequent meetings that come with it. Given my introverted nature and my passion for staying closely connected to technology, I don't believe that a management role would be the best fit for me.

Conversely, the idea of progressing as an IC to roles like Principal or Senior Staff can be quite daunting. I grapple with feelings of imposter syndrome, wondering if I can meet the necessary standards and I am concerned that it might negatively impact my work-life balance.

I would greatly appreciate any advice or insights from the community regarding this situation.?

I recently passed 5 years of work experience as a software developer, mostly working at small companies/startups. I’ve been at my current position for almost 2 years and the startup is around 100 employees.

The company is doing great, we just raised another round of funding. I’m preforming well and I’m up for promotion to senior software developer next performance review.

With all that being said. My goal has always been to get into a big tech company and I think the earlier I do the better.

Overall I really enjoy working at this startup but I have always been career driven and I think going to a big tech company would be the right career move. Am I correct on this being the right career move or is this just the pressure developers feel to work at a big tech company?

Graduated in 2019, joined a FAANG that is notorious for really bad work life balance, so I was always on the edge, switched companies during pandemic times and first few months started good then pace picked up really quick after that, and I found myself losing sleep again due to stress, then I got laid off 2023. Now, I joined a startup and is the most stressful of all of my previous jobs, some weeks I have to work up to 9-10pm (taking breaks of course) because some very urgent issue needs to be fixed, stuff is always breaking and we might go under if we don’t resolve well.

To be honest, I’m burned out (I think that’s why I got laid off, showed in performance) but I ignore it and keep going with a A+ game because layoffs are a big thing right now, and I’m scared of losing my job again.

Has the industry always been like this? Or I have really bad luck?

How can I get better work life balance? Or less stress?

I am a Senior Software Engineer at a big tech company, and I was reached out by a recruiter at a big-tech equivalent company and decided to give it a shot (also for a Senior SE role). I'm in the final interview stages and expect to receive an offer soon.

My recruiter said I've received excellent feedback overall from all of the interviews. I honestly believe that I would be more suitable for a Staff-level role given the work they are planning to do and has a close alignment with what I'm doing now (working towards a Staff role).

I have a few days until I receive an offer; I'd like to know whether I should kick off the discussion now or post-offer?

I'm an E5 at a Big Tech company. My team's working on a very ambiguous project. 3 opinionated, vocal engineers (2 E6, 1 E5) tend to sidetrack our brainstorming discussions by playing devil's advocate to shoot down ideas. How do I drive these meetings forward with this dynamic? We often rehash the same discussions over and over. When we're close to reaching a decision, oftentimes someone would throw a wrench into things. Moreover, some engineers require upfront planning and want to finalize all the details before committing, while others prefer to defer the details to future milestones. Both my manager and team are getting frustrated, but are unsure how to fix this.

I’m a Data Engineer at a slow-moving finance company who’s looking for my next job in Big Tech. I just had a recruiter from Stripe reach out about scheduling an interview, which happened because I had a buddy who works at stripe refer me to the role. The position is for backend engineer.

The recruiter says the call will be 20 minutes and I should come prepared with “the most technically complex project” I’ve worked on, and talk about my role, duration, number of engineers, and stakeholders.

I’m nervous about this because my current role is something of a hybrid between data engineer and data analyst and I do a fair bit of data-analyst type work. It’s not that I don’t have projects I can talk about, it’s just that I’m insecure about them and I feel like they are unimpressive to a ‘real’ software engineer and this becomes apparent under sustained scrutiny. So maybe I can get by the 20 minute intro call, but there will surely be an hour-long session later where they want to go into excruciating detail. I do have some experience with backend as well, but it’s already almost 3 years ago now.

My question is this: how can I go about improving my situation? I’m applying for entry-level roles (IC1) and was under the naïve assumption that I just had to get very good at DSA/Leetcode. Obviously, this is not the case.

In order to better handle these project walkthroughs going forward, I see a number of potential approaches, which are not necessarily mutually exclusive:

1. Get better at discussing projects in my current toolkit. Ditch the imposter syndrome and spend more time thinking about what I already have.
2. Invest more in my current job to create better projects with ‘scope’ that are more impressive in interview rounds. Right now, I’m not very committed to my work and coast, doing whatever is assigned to me but in a minimalist way. My current manager has told me how he wants me to be more active in getting things done and taking on a larger role, but as a Tier-3 company, there is no expectation or requirement for me to do so (i.e. very low chance of me being let go), and furthermore, I tell myself I will be leaving soon, so why take on more responsibility? This might ironically contribute to it being harder for me to move since I don’t do the kinds of things that make it easier to interview.
3. Do side-projects outside of work that I can discuss. But here I run into the issue that I’m not working with anyone (unless it’s open source) and this is probably not the best approach unless my side-project is really good with users. I’ve heard Alex and Rahul say this a number of times.

Happy to hear anyone’s thoughts about how I can improve my situation. I probably have the wrong attitude towards my current role, as I’ve been wanting to leave it for over a year. I’ve thought about quitting a lot so I can have more time for interviewing, side-projects, networking, learning, and prep, but everyone says that’s a bad idea (especially in the current climate), so it’s easier to just muddle on in my current role.

Thoughts are welcome!

Layoffs are making me quite anxious. I understand job security might not really be a thing when it comes to big tech, but I do want to try pursuing employment security, if that makes sense. How do I "get good" so I can be a little more resilient when it comes to layoffs and employment? I'm not really sure where to start.

@Alex Earlier you mentioned:

Big Tech open-source is obviously ideal (many engineers got hired at :meta: contributed to their OSS), but it's extremely hard to ramp up on the library and get a major PR landed. And it's not like 1 PR will do it - You'll probably need 5 to 10 to get the attention of hiring managers. However, like with most things, it will get much easier over time (the first one's the hardest).

And here: , you said:

These companies all have a large OSS footprint, and I know several people who got hired into these companies by submitting major PRs into them.

What are the parameters for determining whether something is a major PR in Big Tech Open Source according to you? Am currently working on Microsoft Windows Terminal.

Would you consider the below major PR candidates that would get the attention of hiring managers?

Btw they're both from this list as heroic tasks (7158 on completed tab since I've already completed that one):

To my understanding Major PR means lots of people want it and 7158 has around 100 upvotes so that's Major PR. But there are also some PR's where people make commits with 500 - 1000 lines of code

Hi folks,

I'm a mid-level engineer at a big tech company in the bay. While at my company, I haven't felt connected with the product, excited about the work I've been doing, or that connected with the team. I was interviewing for an internal transfer -- and I just had verbally accepted the offer. It was supposed to be a transfer to an acquired company I was excited about -- but I found out they just cut budget for the role. The role is to be remote. I'd have to move back home with my parents. I'm open to doing this, but it also comes with a 15% pay decrease, and I'm already out of and not refreshed on rsus. The transfer offer is a 15% reduction in salary.

The last option is I've been working on a side project with some friends to learn building a web-app end-to-end, so I could take some time off, recharge, and potentially work on my own thing. Overall, I'm quite burnt out and feeling tired of my job. Rather than working on large-scale infra, I'd like to get back to my roots (health-related technology). Any thoughts on this decision? I'm a US citizen, so no visa restrictions.

Hi, I'm from India. I have been unemployed since February 2024 following a layoff from my last job as a Full-Stack Developer (4+ years of experience). After that experience, I decided it was time to move away from startups and their unbalanced lifestyle. My goal is now to secure a role at a FAANG company (only in the U.S.) and nowhere else. I have savings that will last me about six months to support this transition.

Initially, I planned to focus on Data Structures and Algorithms (DSA), an area where I had very limited knowledge. After reading a few posts on LinkedIn (mainly from influencers), I mistakenly believed that three months of preparation would be sufficient for technical interviews. I now realize I was wrong. It's been 10 months, and while my DSA skills have improved to an "OK" level, I still don't feel confident. My System Design skills are also at an OK level.

I've been applying to FAANG and other companies, but I keep facing rejections. I suspect this may be due to the employment gap or the lack of big-name companies on my resume.

What I'm doing to bridge the gap:

• Working on side projects that demonstrate my skills in System Design, Databases, Programming Languages, Distributed Systems, and Microservices.
• Building a mini-startup that I can showcase on my resume, allowing me to highlight my Full-Stack development knowledge.

My goal:
I'm aiming for at least an L4 role at Netflix or a Full-Stack position at Google or Apple.

With this employment gap, is it bold or foolish to still aim for FAANG?
I’d love to hear any suggestions that could help me get shortlisted.

I graduated with a master's in CS 1.5 years ago and since then I have been working at a no-name brand company as a full-stack engineer. I would love to join Spotify but I lack prestigious grades and side projects. The tech stack I work in is somewhat old (Angular 2, .NET, no cloud, in-house solution for CI/CD, etc). The company is nevertheless alright and my colleagues are all very friendly, including my boss and manager.

If I would want to join Spotify, should I double down at my current job and try to get those side projects started, or should I consider another position in-between my current position and Spotify in order to increase my chances to join Spotify? The reason why I’m not a big fan of this idea is that I don’t like to join a company with the intent to leave within 1-2 years. The reason why I'm considering changing company is because I worry that my current growth could potentially be a lot higher than what it currently is.

Will my lack of experience in newer frameworks/tools be a large disadvantage to me when I’m looking for a junior/midlevel role at a tech company where being efficient in languages/tools is a must? Is it better to stay since I can make more of an impact now since I’m familiar with my company’s tech stack compared to having to go through an onboarding process at a new company which may result in decreased impact for that period? I would prefer to join big tech in 1 year as a junior engineer, rather than in 10 years as a mid-level engineer.

Breakout startups are basically startups that have found product-market-fit and are growing at an incredible pace. So think of the OpenAIs and Databricks of the world. Back in the day these would've been baby Google and baby Facebook. Here's a link for more examples:

Sam Altman, Dustin Moskovitz and a few others strongly suggest people in any stage of their career to join these startups.

I revisited Taro's course on picking a company, and there doesn't seem to be much info on them. The course does talk about startups but I feel that startups have so many stages that it's hard to make generalizations across them.

From my understanding, it seems like breakout startups are a great place to join:

Pros

1. You get incredible career growth since you're a part of a rapidly growing company
2. TC is usually pretty competitive with FAANG (with a caveat)
3. These startups usually have very strong engineering culture and network, with most people being Ex-FAANG

Cons:

1. Work life balance seems to be worse than big tech on average since there's so much stuff to do (like 20-30% worse on average?)
2. The equity portion of your TC is still paper money, so there's a chance the IPO flops and your TC basically halves
3. Brand name is not may not be as good as big tech, though this is heavily dependent on the company (like you'd definitely interview someone from OpenAI, but I doubt many have heard of Helion). A question I have is how big is the difference in the brand value between your average breakout startup and a big tech? Is it negligible?

The Taro course suggests new grads to pick big tech. Funnily enough Sam Altman laments that someone picked big tech over a breakout startup. I'm not saying that these two pieces of advice are contradictory, but what factors should you consider if you're deciding between big tech and breakout startups?

I have Staff interviews lined up with FAANG companies and would like to learn from the best resources out there. What has helped you the most in your journey/experience?

Hi everyone,

I'm a senior software engineer in Brazil, and I'm interested in exploring fully remote opportunities with FAANG companies.

Does anyone have experience or insights into whether these companies hire engineers from Brazil for fully remote roles? What are the main challenges or requirements? Where can I find such job postings? Do I need a referrer? Any advice or information would be greatly appreciated!

Thanks in advance!

I'm going to be joining Amazon soon and the team I'm on is going from 4/5 people a month ago to I believe 9/10 people (counting me). Our team is going to be comprised of SDE 2's and 1's (I'm an SDE 1).

I'm wondering what's the best way to have the best onboarding experience during this time.

While it will be nice that I will have a decent amount of people who will be in the same boat as me in terms of onboarding, I'm also worried that my manager and more senior teammates won't have as much time for things like 1 on 1s, answering questions, helping me onboard, etc. if they're also helping other people on our team in addition to their own work.