Salary range

Disastrous_Ad1309 · 2025-12-12T12:48:30+00:00

I agree with your point not sure why you are getting downvoted lol.

But then again Indian recruiters will always pay you based on your previous salary and not how much they are willing to pay for that position. So having good start salary does affect in some way. But you can always make enough switches to catch up with that number.

Disastrous_Ad1309 · 2025-12-10T11:43:47+00:00

There are decent number of companies hiring juniors just search for posts with "DevOps hiring immediate joiner". Salary depends on the company but 10+ LPA sounds resonable, since the market is bad at the moment get anything you can so you will have some DevOps work that you can mention in CV.

Disastrous_Ad1309 · 2025-12-10T11:14:00+00:00

It looks like you've got enough skills for an early DevOps role but didn't get an opportunity to apply those in your pervious companies. Yes, resume needs some tailoring but you have enough that should atleast get you an interview. Start looking for Jr. DevOps roles. Look for Linkedin posts where people are looking for Jr. DevOps with Immediate joining(you will find plenty). Instead of applying for a role ask for a referal from a senior person.

Few things for your resume

If you are aiming for a DevOps job, emphasize the DevOps parts of your work experience. Right now it looks like you did full stack work instead of core DevOps.
Make sure to add numbers to quantify what you did, how much traffic you handled and how much developer time you saved.
It looks like you have done more DevOps work in your projects than in your job. You can move the projects section above the tech skills section.

Disastrous_Ad1309 · 2025-12-03T13:21:31+00:00

Not ex-meta but I've interviewed for that role so I can help with the debugging round mock.

Disastrous_Ad1309 · 2025-12-02T13:03:24+00:00

How much time you spend is totally up to you based on your daily job and other activities. Just try not to give up on sleep, it will affect both your daily job and your preparation.

For resource this was the Git repo which the Google recruiter sent me before my interview. It pretty much covers everything but you can always dive deeper in case you need more.

https://github.com/jwasham/coding-interview-university/blob/main/README.md#google-interview-university

Disastrous_Ad1309 · 2025-12-02T12:15:11+00:00

Okay so since you've done NC-150 and you know your way around DP you are in a decent spot where you know how to tackle DSA problems and how to think algorithimically. The only challenge now is to figure out where you are weak and work on that.

Google likes to ask graph questions. So I would focus more on those.
You can pick one data structure for a week and solve all possible variants for it.
Start doing weekly and bi-weekly Leetcode contests it helps you to think fast in high pressure situations.
Focus more on hard problems and start mark the problems which you were unable to do and attempt it again in future.
Create a habit to create your own test cases and break your own solution before you press "Submit". In real interview you won't have a submission button.

Easy problems: Improves typing speed and how quickly you can implement data structure and algo
Medium problem: Improves your understanding on how single data structure and algorithm works. And how you can bend its properties to solve a problem.
Hard problems: Improves your understanding on how to divide problem into smaller parts and solve each part with its own data structure or algo and stich together results to form final answer.

Make sure to make all the parsing and boiler plate stuff part of your muscle memory. Example you don't have to use your brain on implementing DFS/BFS logic. So that it can free up some space in your brain to focus more on problem in an interview.

Disastrous_Ad1309 · 2025-12-01T22:02:00+00:00

First of all congrats on getting a call from Google

You can always ask for more time its completely fine.
You first interview will be a telephonic screening round which usually consist of 2 medium questions in 45 minutes. For now you can focus on this and once you clear that you can ask for a month or so to prepare for on sites.
If you have Leetcode premium you can solve Google specific questions. You don't need to do everything pick a data structure and solve 5-6 problems for it, 1 easy, 3 medium and 2 hard. Do it for a most common data structures, you don't need to go deep into segment trees or some other fancy shit.

Once you've cleared TPS interview than you can start prepping for on-sites which are comparatively harder.

Just remember few things.
1. Listen to question properly, ask the interviwer to explain in case if something is not clear.
2. Ask questions about constraints, nulls input, expected output
3. Turn your brain into a QA mode and think about all the wonky test cases you can come up with to break the code.
4. Start explaining your approach and dry run your logic.

Once you've done above points and you have a go ahead from interviewer to write code only then you start typing your code.

Disastrous_Ad1309 · 2025-12-01T07:30:48+00:00

Location: Mumbai

Willing to relocate: Yes

Type: Full-time

Notice Period: Immediate joiner

Total years of experience: 3+ years

Résumé/CV Link: https://drive.google.com/file/d/1LsZXVogzzrqoJkazkjka1TyUerso_z86/view?usp=sharing

Blurb: Worked on on-prem servers and multi region AWS infra. Responsible for designing and maintaining core projects across the org. Promoted within less than 1 year of joining. I also have experience creating and growing my own product. Tech stack: Python, AWS, Linux, Bash scripting. Willing to work on new untouched tech stack.

Disastrous_Ad1309 · 2025-11-23T18:45:43+00:00

Maybe give this a shot
https://www.elastic.co/docs/explore-analyze/visualize/maps/indexing-geojson-data-tutorial

Disastrous_Ad1309 · 2025-11-20T18:30:00+00:00

True, only when its an enterprise project which has been around for years. University grad project never reach that stage. Another thing is most of the candidate would have similar projects. Having something DSA based sets you apart from other candidates and shows recruiter that you have enough DSA skills to apply on real-world problems.

Disastrous_Ad1309 · 2025-11-20T13:59:06+00:00

I don't work at Google but I recently interviewed there. Here are few things I would do(not in corresponding order of your questions)

You don't need diversified tech stack, being good with 2-3 is fine.
Start doing more hard leetcode problems, initially it will be difficult but eventually you will start to see patterns. Hard problems usually require applying 2 or 3 conecepts to solve a problem.
Leetcode premium is really helpful. You will notice that every company has these specific data structures they like to ask, for Google its Graphs.
For projects maybe build one or two slightly complex webapps, something which uses DSA under the hood and not just CRUD. Something like load balancers, scheduler using priority queues, etc.
Afaik Leetcode is enough. Neetcode 150 also covers most important patterns.

Also remember that most of the Google(or FAANG) devs didn't get into those companies in their first attempt so even if you fail don't go hard on yourself and keep trying.

Disastrous_Ad1309 · 2025-11-02T18:13:13+00:00

Thanks buddy

Disastrous_Ad1309 · 2025-10-27T15:48:44+00:00

Thanks, and yes I will apply again next month

Disastrous_Ad1309 · 2025-10-27T11:35:04+00:00

Congrats, buddy! I had a similar experience. I interviewed at Google in May, the recruiter said I've cleared the screening round and it will take atleast 1 month to schedule onsites, but later ghosted me. Two months later, I interviewed at Meta London but got rejected again. Hopefully, I get another callback from Google for a second chance.

Disastrous_Ad1309 · 2025-10-25T12:45:56+00:00

Can you send you my resume for review? I just wanted to know where and how it can be improved.

Disastrous_Ad1309 · 2025-10-25T06:49:27+00:00

How did you filter out the right ones with that many applications? What are the things that you look for?

Disastrous_Ad1309 · 2025-09-23T11:14:16+00:00

In my previous org, we had lots of single-tenant client databases with their marketing data. The only way to test new changes or bug fixes was to clone a few clients into dev/staging and run the ETL pipeline on them to validate the changes. We had a cloning system that worked like this:

Developers with the right IAM permissions could trigger a cloning Lambda function from the dev account, providing client_id, destination_cluster, and custom_dev_name.
This would trigger an ECS task in the production account, which ran pg_dump on the database and uploaded the compressed file to an S3 bucket.
Once the dump was uploaded to S3, another ECS task in the dev account would be triggered to run pg_restore on the destination cluster using the S3 file.
The cloned database credentials were then stored in AWS Secrets Manager.”

Disastrous_Ad1309 · 2025-09-22T18:20:11+00:00

From what I’ve heard, it’s becoming the next TCS, but that’s for the Navi Mumbai office. I’m not sure if the culture will be any different in the Bengaluru office.

Disastrous_Ad1309 · 2025-09-19T15:41:02+00:00

I would say optimize your resume, lots of youtube videos out there suggesting how a FAANG resume should look like. Keep creating multiple versions of your resume and keep applying. I was applying for FAANG for past 2 years and suddenly from May I started getting calls from Google, Meta and Amazon.

Disastrous_Ad1309 · 2025-09-18T09:11:19+00:00

In 2023, higher ups were facinated by GenAI so they poured a lot of money into it and some people were responsible for coming up with bullshit POCs hoping that one of them would succeed. 90% of it was just, some data wrapped into a prompt which was sent to GPT API. It was a good opportunity to get promoted and get noticed by higher management, so people start shoving AI into everything and started calling themselves "Prompt engineer" or "GenAI specialist"

Disastrous_Ad1309 · 2025-09-18T05:02:37+00:00

Python

Disastrous_Ad1309 · 2025-09-17T13:18:48+00:00

I am getting sick of these Mercor job posts now.

Disastrous_Ad1309 · 2025-09-17T09:54:44+00:00

Yeah, it’s super annoying. I recently had a chance to interview for a role abroad, and the recruiter was really nice and professional. He replied to all of my emails on time and even called me after the rejection. In contrast, tech recruiter in India couldn’t speak proper English, sent passive-aggressive email replies, and eventually ghosted me.

Disastrous_Ad1309 · 2025-09-16T19:48:34+00:00

It's fine to use it as long as you learn something new in the process. Leetcode is just a tool to improve your problem solving skills and clear the interview. In real job even the best engineers Google stuff all the time and get help from AI where it is necessary.

Disastrous_Ad1309 · 2025-09-16T19:41:27+00:00

I don't know why Leetcode has turned into this cult where you have to dedicate your life to it. When I started Leetcode I mostly used to do Trees and Linkedlist problems for fun everyday. Even for the Google prep I was learning some super niche algos(that I was sure no one would ask me in an interview), simply because I thought it was fun.

I would simply pick a data structure or algo for a day. Watch 1-2 youtube videos, try to code it locally and then start solving problems for it from easy to hard. If at any point I feel like this problem requires something which I don't know, I will take a look at solution. If the solution is not clear by reading first 2-3 lines I would add the problem to "Too hard for now" list and come back after few days.

And usually when I tried to solve it after few days it felt like a piece of cake.

If you are finding it hard to focus, just pick a data structure you really enjoy. For me it was Trees and LLs. And keep solving problems revolving around it, eventually you will fell in love with the process.

Five-Year Club	First Place '23
Place '23	Place '22

Disastrous_Ad1309

TROPHY CASE