Amazon.com, Inc. is an American multinational technology company which focuses on e-commerce, cloud computing, and much more. Headquartered in Seattle, Washington, it has been referred to as "one of the most influential economic and cultural forces in the world".
Hi all, I need an advice on quite a random thing. I recently changed teams at Amazon. Since I shared a close bond with my previous team members, I continue to hang out with them sometimes and my ex-manager is quite aware of it. (He was new, and has worked with the team for less than an year)
Is it fine if I continue engaging with old friends, or does it make me look bad from professional aspect?
I am not able to login to Slack channels even though I have prime membership.
Is this the right email address? It looks like there isn’t an account on Taro Premium tied to this email address.
XXX@gmail.com doesn’t have an account on this workspace.
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?
I received an offer from AWS for a SDE 2 role. I was planning on asking for an additional 50k sign on bonus for year 1. I would justify this ask with evidence of past work (saving on infrastructure costs, mentoring multiple engineers) and being willing to cancel other interviews (mix of onsites and first rounds).
I'm a boomerang and the offer is the same as my TC before I got laid off. I also read some Taro Q&A and negotiation videos but couldn't find a situation similar to mine. The email states:
This will be the highest offer we are able to put forward at this time.
Is this a trick to try to get me not to negotiate?
I know the general advice if one does not know is to ask their manager but sometimes an inexperienced manager might not know themself. Can anyone provide an example to make these concepts clear?
A few criteria I came up with that can be included in the framework involve
For reference, when I talk about mid-level vs. senior-level I am referring to the leveling system across big tech (L4/L5 for Amazon, E4/E5 for Meta, etc.). Thanks!
During session, Rahul mentioned only a few projects are important. I would love to get some concrete examples from Rahul or others on what that looks like. This is my very first question that I am posting in Taro forum. Thank you for the encouragement Alex. Looking forward to everyone's answers.
I have been an Android engineer since my first job 7 years ago. I learned React and React Native along the way and made myself into making apps for iOS. I really like working on this environment and would like to gear myself up with native iOS dev skills.
I do get to design solutions and review other mobile engineers' design docs and code. I often find myself struggling to review the objective C code and nuances of iOS platform API usage (like animations, background operations, ARkit etc).
Where should I start to get better in iOS native app development?
I want to become better at
I've been abit lost in my job recently and feel disappointed by own performance. I'm part of an infrastructure team, and while the primary force pushing me forward is my personal engineering growth, I can't shake the feeling that the domain itself doesn't resonate with me. That said, being an average l4 I'm not in a position to switch teams.
What's keeping me going is the goal of self-improvement, which is helped from being surrounded by my incredibly talented colleagues, each bringing their unique strengths to the table. For instance, our senior engineer is an incredible communicator, teacher of concepts and general problem solver, another engineer is a coding machine and works extremely hard, and an L4 who joined at the same time as me is very customer-centric. In particular, it was through observing the L4 leveraging his strengths, while almost neglecting his weaknesses (he doesn't care as much about code quality and is quite argumentative) that I felt uncomfortable with my own trajectory. I've been so busy with trying to improve all my weaknesses that I'm now reflecting on whether I should focus on my strengths.
All of that said, I've been here for a year, and I'm struggling to pinpoint where my strengths lie. I'm willing to put more hours than others but for obvious reasons that should in no way be considered a strength (my manager described me as a hardworker, which i don't want to be known as haha). I'm also a very enthusiastic person and very open to feedback, but it leads me to being pulled in different directions. I don't think I can be an engineer that does it all and I think Amazon wants you to focus on your strengths through their conflicting leadership principles (e.g. bias for action versus insist on the highest standards, deep dive versus thinks big). I've been reading this book called Atomic Habits recently and it really focuses on the idea of identity and how that shapes your habits. It seems like everyone in my team has built an identity based on what they're good at, how can I find mine? And are there certain skills that provide higher ROI over others that I can perhaps focus on, given that I don't really have any strengths right now?
I have a new grad offer from Amazon, which was forcefully deferred earlier this year.
I currently work as an SRE (which I don't want long-term), and my offer is for an SDE role in the same team I interned at when I was there pre-layoffs. Plus despite me working for >6 months elsewhere, they're not increasing my comp in any way.
I'm attracted to the Amazon job since it's a SWE role and that's something I want career-wise, but given that the company and current economic situation have been kind of unstable, I'm hesitant to join. Does anyone have any advice for me on how to navigate this? I'm on a student Visa so I guess that's why the threat of layoffs is a bit higher in my eyes.
I’ve been a senior FEE at Amazon for almost a year now, and I’m still figuring out time management.
Sometimes I get overly involved in others’ tasks, or have too many meetings, or get overwhelmed by all the new campaigns and estimation requests constantly coming through the door while we’re in the middle of meeting deadlines.
How do senior FAANG engineers balance their priorities without overworking or burning out?
P.S. it’d be amazing if Taro can get Steve Huynh (PE at Amazon) to talk about this topic in detail.
How do you respond to an email or over a phone conversation from recruiter asking:
Could you please tell how to handle such questions?
This is a really well funded company (Bank) that underwent a large scale leadership change. The company's primary source of revenue was never it's tech capabilities, however with the new leadership change they're looking for a large scale revamp on how the existing systems work and are working on setting upto a FAANG equivalent engineering environment. This is vision is consistent across the leadership upto the CEO. This org currently consists of multiple Staff engineers from Twitter, Meta, Amzn and Google leading big initiatives.
I'll be soon taking up an offer in this company and will be joining this freshly created Org, where I've opportunity to be among the first 10-15 engineers to join with potential of the org to grow over 100+ engineers. There are lot of existing tech that have been already deemed unscalable due to previous decisions and have been a known business blockers, these tech require either re-write or a large refactor or a completely different viewpoint on tackling this problem. This will involve me working with Engineers who've built this system (Not part of this new Tech Org, rather the old existing infra), I've been already given a heads up from my potential manager that there can be potential hesitancy that the existing engineers may feel and wouldn't be too open to provide all information necessary as our systems will be replacing their soon (Have been reported that this has happened). There isn't a concept of internal wiki similar to Amazon or other Big Tech, hence lot of this is just domain knowledge etc. Fortunately the leadership is aware of this and is taking steps to answer this, and takes into consideration when scoping for projects and setting up right expectations.
The following are certain concerns that I've, and wanted to understand what is the best course of action I can take up to make my onboarding successful.
This is my Current plan, given i'll be among first engineers to join this team.
Understand domain, reach out to multiple PMs and document all pain points, problems we are solving in long term & Short term.
Go through code base of relevant packages and start adding their UMLs, HLD etc to best of my abilities to a document to move towards creating a Knowledge base.
Socialize with engineers from the related org and try to gain their confidence, and potentially get few KT sessions (Not sure how i'll go about this as the team is situated in different city).
Work with manager to setup boy-scout rule, such that everyone onboarding will incrementally add more to the existing knowledge base.
Follow Up Questions :
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.
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 :)
Backend: Distributed Systems, scalable applications, fault tolerant systems, control plane applications, API development, uses higher-level languages like Java/Python.
Low-Level: Database Internals (Query Optimization, Transaction processing, Data/Storage engines), Compilers, GPUs, latency sensitive software, accelerators. Usually C/C++.
Which is better for long-term career growth and compensation?
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)?
I like my team and management. I would like to stay here and yet address the comp concerns. Promos are too difficult.
So I would like to learn from Alex, Rahul and community members here on how I should go about the retention offer.
What are the things I should do in order to increase my chances. I want to plan it thoroughly and execute it without getting burnt out.
Hi Taro. When choosing a team, we also have to choose their specialization and tools. If the specialization is niche and the team uses exclusively internal tools I won't gain any transferable skills. I got laid off from AWS and I am realizing that I have little transferable skills. I used mostly internal tools. Believe it or not, many AWS teams do not use AWS extensively.
How can I choose a team or focus area for transferable skills? I was considering pivoting into Android and IOS development because I see many job openings for these.
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?
PS: Apologies if this sounds too generic. My intention is just to learn from other people's experiences. Any advice is welcomed.
Hi all. I joined AWS after university and recently got laid off. I have 2YOE at AWS and a 1 year internship at NASA.
During undergrad the only thing I stood out for was having multiple publications. I suspect really talented undergrads in CS programs where targetting FAANG so there wasn't much competition. Maybe I was good at research though.
I am a US Citizen and I went to a medium tier university for undergrad. The name is recognizable but it's not impressive. What kinds of doors does attending a top university for MS CS open for me? I might be able to get into a top school like PHYMS.
Most people tell me that top schools are not useful after getting a couple YOE. I remember I was talking with someone that went to MIT for undergrad and they told me that there is a company that will basically give students $100,000 to do a startup and all they needed was an idea. They told me that it was pretty easy to get and many people got that at MIT. That's not something that would ever happen at my university.
I have some concerns:
I'm a support engineer in big data profile working in Amazon web services, and I'm looking to transition into a SDE role within the teams like Spark, Hadoop, Yarn EMR infrastructure, etc
At the same time I have been working hard on my promotion from L4 support engineer to L5 support engineer.
Given a scenario if I get promoted to L5 support engineer and later, down the line I also get L4 software engineer role within Amazon, should I take the SDE role at a downgraded level, should I look outside or what should be the best route?
Somebody I know has been working in Amazon BA and related positions for seven years, however they switched to SDE intern positions within Amazon. Do you think it is a wise move?
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?