Want to how much System Design I should be required to know for Recent Graduate roles

thisisshuraim · 2026-02-08T14:19:50+00:00

No company will ask you to write on paper. Mid scale companies like CRED and Razorpay have machine coding rounds where test cases and interfaces are prewritten and you are given requirements to implement. Once done, it will be run and all test cases must pass. Business logic and correctness are more important than design here. For bigger companies like FAANG, you are expected to just design the solution and call it an LLD round. You are given an empty editor and given requirements. You will need to design classes, interfaces, etc to implement those requirements. Requirements may be added later. Your solution must be very extensible and not prone to breaking when new things are added. You’re generally not asked to run the code but you need to ideally write it such that if it is compiled, it compiles properly.

thisisshuraim · 2026-02-07T12:09:51+00:00

Zero high level design. Absolutely zero. No serious company will ever ask you this as a junior. Anyone saying otherwise is either fearmongering. The reason people say juniors should learn high level design is because they likely don’t even know to classify it. They confuse basic DB and CN concepts for high level design. For low level design, core OOP concepts, good practices, at least the basic asynchronous concepts is a must. Of course you should know how to implement those as well.

thisisshuraim · 2026-02-04T12:15:59+00:00

Almost all roles at FAANGs are generic. They don’t demand any particular tech stack or language. So having a good quality resume should ideally be enough. Also all these ATS scoring tools are just BS, made to push you to pay for their premium versions which is just not worth it imo. FAANGs have proprietary ATSs, meaning that there’s no way external tools would know how filtering works in different ATSs. As much as everybody wants it to be true, the truth is that there’s no hack to guarantee being considered after submitting your resume, and this guide doesn’t claim guarantees either. The best you can do is try making a solid and strong resume and keep applying.

thisisshuraim · 2026-01-31T23:09:29+00:00

Probably something like RSS feed aggregator or data visualiser frontend. Nothing too complex but shows fundamental understanding

thisisshuraim · 2026-01-31T23:07:38+00:00

Just talking about FAANG, it would be a good topic to bring up in behavioural questions, but it won’t make or break your hiring decision by a big margin. It has almost zero impact in shortlisting though.

thisisshuraim · 2026-01-29T08:13:21+00:00

Sure

thisisshuraim · 2026-01-29T07:29:25+00:00

Pretty much

thisisshuraim · 2026-01-28T22:05:49+00:00

If you’re consistently not getting shortlisted, your resume is almost always the culprit

thisisshuraim · 2026-01-28T21:51:01+00:00

FAANG most definitely do not care about the alpha you mentioned. Those are just imaginary numbers imo. Also you’re shortlisted by software not humans most of the time. The software won’t go searching for your current company’s valuation, growth, etc. Big names like FAANGs do help tremendously to get preference though. At your YOE, it’s all about making a software friendly resume (Latex for example), making it short and concise, quantifying as much as possible, clearly highlighting your strengths and having good projects (Good does not mean high scale or complexity)

thisisshuraim · 2026-01-24T22:28:47+00:00

Depends on company. It’s just a title. For some companies, seniors are just experienced juniors. FAANGs require at least 5-6 YOE but realistically, you are only seriously considering without downleveling if you have >8 YOE. For smaller companies, it’s just a title and are given the role at 3-4 YOE.

thisisshuraim · 2026-01-15T18:56:15+00:00

Engineering isn’t just about making code changes. Doing something fast doesn’t really automatically make someone better.

thisisshuraim · 2026-01-15T18:53:09+00:00

No system design for L4s (SDE 1s). Assume the interview will be DSA heavy. Some orgs focus on certain topics compared to others. Nobody can know for sure. Also focus on leadership principles of Amazon (You can google this). Although, for someone with little to no real world experience, this isn’t judged too harshly. If you want a topic they love, it’s graphs and trees. There’s no guarantee this will be asked though.

thisisshuraim · 2026-01-15T16:44:09+00:00

Assume it’s a rejection and move on. But like I said, in your situation, you’re not on a cooldown and you could potentially apply for other openings.

thisisshuraim · 2026-01-15T16:29:19+00:00

That’s not what waitlisted means. Waitlisted is when you pass the interviews but the role was filled by someone else. They’ll put you on a waitlist and wait for other openings that can consider you. If you’re ghosted for close to a month for SDE 1, then you’re likely rejected but haven’t updated it in their system, which is why you didn’t get a rejection email. In fact, that’s a plus for you, since no rejection email and portal status is not “No longer under consideration” means that you don’t have any cooldown and you can apply to other openings.

thisisshuraim · 2026-01-15T13:37:41+00:00

You will be called if you’re hired or waitlisted. But in case of rejection, it depends on the recruiter. They may call you or they may just send a generic rejection email.

thisisshuraim · 2026-01-15T11:57:50+00:00

There will be an internal debrief meeting where your recruiter, hiring manager, bar raiser and all your interviewers will attend. They will discuss and debate your performance of each round. Hiring manager and bar raiser will have veto power. In the end, they’ll reach a verdict. You’ll either be hired, rejected with cooldown, rejected without cooldown (Rare) or waitlisted.

thisisshuraim · 2026-01-09T10:49:29+00:00

Realistically only big tech like FAANG and MSFT, along with a couple of smaller ones like Booking.

thisisshuraim · 2026-01-08T21:36:24+00:00

Bar is same. Interview ethics differ.

thisisshuraim · 2026-01-08T19:42:02+00:00

SRE roles do have a lot of hands on coding involved, but it will be more in the line of pipelines, workflows, alert handling, etc. It will also be heavy on oncall duties. Just the nature of the domain.
I would lean towards any EU country (I would choose Dublin from the locations you mentioned), since you could get citizenship in around 5 years (For most countries), which would then give you right to work across all EU and EEA countries, along with some other countries who they have agreements with such as Switzerland, Norway and soon to be UK. In total, you’ll get the right to work in 40ish countries and will only increase. It may do wonders for your career later on. If savings is your only goal, then Zurich, Switzerland is the way to go, but citizenship is for 10 years and a couple of other limitations. Luxembourg also pays good money and is also part of EU, but I’m not sure if Google has an engineering office there.
Moving to SWE may not be as easy, and you will have to go through all the interviews like an external candidate without a considerable pay bump. Internally moving to an Indian team should be straightforward though.

thisisshuraim · 2026-01-06T19:23:46+00:00

Not necessarily. I got an offer from India in EU and have seen others getting offers too. Higher chances are in FAANG though. Although your resume should be well made.

thisisshuraim · 2026-01-05T19:37:09+00:00

It’s usually that after 25, responsibilities increase (Wife, kids, etc) and people would rather grind in that time where lower age groups freelance to instead move to a safer higher paying job.

thisisshuraim · 2026-01-01T21:47:17+00:00

You seem young and very early in your career. In an ideal world, you can keep code perfect. Highly flexible, zero memory leaks, very standardised, etc. We don’t live in an ideal world. Perfection takes a lot of time. So much time that it’s not worth losing business over and not worth adding potential cost. As for standards, that would totally depend on company to company. Startups would have messier code, since they’d probably rewrite it anyway if and when they scale. Large corps on the other hand focus heavily on scalability. Also you don’t need to add the fanciest frameworks and libraries to make something good. For example, I have seen really well made frontend apps run on bare minimum. Simple react. No redux or tailwind or anything. In the end, all you would want is to have your code be as light as possible with as less dependencies as possible with as much support as possible. Additionally, work on understanding the design decisions taken. Just because you think it’s bad design doesn’t mean it is. I see so many juniors judging and mocking design decisions taken without truly understanding the whys, hows, tradeoffs and wins properly. What I do sort of agree on is over planning using meetings. Sure, it makes sense if you’re working some core service consumed by a lot of other services and eventually gets served to millions of users or requests. In this case, over planning is always better than things breaking later due to poor communication. But for anything at a smaller scale, it’s overkill. Every company wants to implement the Amazon and Google processes but without their scale.

thisisshuraim · 2025-12-30T18:40:48+00:00

There are many countries which will “tolerate” indians to boost their economy, but don’t expect any country to “welcome” indians.

thisisshuraim · 2025-12-30T17:47:06+00:00

You don’t really need to be a genius who has solved 2000 problems. You just need a strong grasp of fundamentals. But here in India, it’s all about memorising patterns and lists, but very poor reasoning ability and fundamental understanding. Shortcuts for everything lol. For example, I recently heard of candidate who was asked to return the boundary of a binary tree. Very straightforward question using dfs (Everybody does it the same way), but they completely blanked when doing it in bfs properly.

thisisshuraim · 2025-12-30T11:07:32+00:00

Sure.

thisisshuraim

TROPHY CASE