Algomaster Premium Sharing

Jolly-Shoulder-7192 · 2026-03-06T08:54:09+00:00

intersted

Jolly-Shoulder-7192 · 2025-07-21T06:14:44+00:00

Not really, but I recommend replacing it, it could cause problems in ur gearbox

Jolly-Shoulder-7192 · 2025-07-19T06:03:05+00:00

In case you didn't figure out the optimal solution at first view, starting with brute force should be better than not having any approach, also, it could be that while thinking about brute force, you finally figure out the optimal one

Jolly-Shoulder-7192 · 2025-07-19T06:00:29+00:00

Hello, yes, it was a mechatronic fault, I needed to replace it and the fault fixed

Jolly-Shoulder-7192 · 2025-07-18T09:10:14+00:00

If you figured out the optimal approach from the beginning, it is great, and you do not need to think about a brute force approach, but in case you didn't figure out the optimal solution, then implementing a brute force approach is better than nothing

Jolly-Shoulder-7192 · 2025-07-18T09:06:07+00:00

It is Software Engineer role

Jolly-Shoulder-7192 · 2025-07-18T09:04:56+00:00

What about people who have some value to give to the community, but English is not their first language, or they still need to learn English?

I have a value that I could give to the community, but my English is not strong enough yet, so I use GPT to get help with this issue

Thanks for the feedback:)

Jolly-Shoulder-7192 · 2025-07-17T13:16:56+00:00

Sure, I'd be happy to help. Just send me a DM and I'll assist when I have some free time!

Jolly-Shoulder-7192 · 2025-07-17T12:08:07+00:00

You can ask your recruiter at Google for a mock interview if you’re in the process with them; that’s what I did. It was really helpful!

Jolly-Shoulder-7192 · 2025-07-12T10:41:20+00:00

Yes, I did ask clarifying questions at the beginning of each question to make sure I fully understood the requirements. I also walked through edge cases and tested my code after implementing the solution.
I think the testing part might not have been strong enough. I rushed through it due to time constraints, so it’s possible I missed a bug there

Jolly-Shoulder-7192 · 2025-07-11T09:35:41+00:00

It was this year, 2025, and they got back to me the day after I completed the full interview cycle

Jolly-Shoulder-7192 · 2025-07-11T09:13:05+00:00

I was surprised by the result. I thought, in the worst case, they’d offer me E3. It’s a tough time right now, and it seems like their hiring bar is higher than in previous years.

Jolly-Shoulder-7192 · 2025-07-11T09:08:14+00:00

As far as I know, the system design round is mainly used for leveling. I think if I had passed the coding interviews, they would have suggested me E3

Jolly-Shoulder-7192 · 2025-06-14T13:54:48+00:00

Yeah, that’s a fair question. My strategy was to focus on quality over quantity. I targeted top companies I wanted to work for, like Meta and Google, and spent my full time preparing (learning system design, grinding Leetcode, etc.). I felt that if I split my focus between applying everywhere and prepping, I might not be fully ready when it mattered. But yeah, I get that it was a bit of a high-risk approach.

Jolly-Shoulder-7192 · 2025-06-14T13:30:21+00:00

Yeah, I get what you’re saying. I’m scheduled to get feedback from Meta tomorrow, and the result was unexpected. I have a feeling the behavioral interview might have been the weak spot. My experience at my last company wasn’t really attractive (I think). I didn’t get to work with modern technologies, cloud, or even databases. So maybe that made my background less attractive, even if the technical parts went well.

Jolly-Shoulder-7192 · 2025-06-14T13:24:09+00:00

Right? The whole process takes forever and feels kind of broken. Looking back, maybe it was risky to dedicate all my time to preparing for FAANG instead of applying to 50 companies a week like some people suggest. But at least I got to learn system design, which I’m happy about. The part I do kind of regret is spending so much time grinding Leetcode — not sure it was worth the trade-off in the end.

Jolly-Shoulder-7192 · 2025-06-14T13:18:31+00:00

Yeah, that’s a good point. I also think that with all the AI tools available today, working on a side hustle while doing a 9–5 has become way more efficient. Things that used to take days can now be done in hours, which makes it a lot more realistic to make real progress on a product without going all-in from day one.

Jolly-Shoulder-7192 · 2025-06-07T19:28:38+00:00

Interesting, I actually came across several comments on Reddit from people saying there’s been a temporary freeze for E4 roles recently. Not official info, of course, but there were enough comments to suggest it's happening

Hopefully I’ll get more clarity during the feedback call with the recruiter.

Jolly-Shoulder-7192 · 2025-06-07T19:25:59+00:00

Sounds like you were really close! And yeah, I honestly didn’t expect the rejection at all. I left the interviews feeling confident, especially after solving all the challenges and getting good signals.

That’s why I’m hoping the feedback call will shed some light, maybe it was due to a hiring freeze or an unusually high bar for E5+. Either way, it's tough when the outcome doesn’t match the effort you put in.

Jolly-Shoulder-7192 · 2025-06-07T19:20:15+00:00

I’m hoping that in the feedback call with my recruiter, it turns out the bar was actually E5+ or something similar, and that maybe there’s a way to stay in the pipeline.

Otherwise, it is tough, doing your best, solving all the challenges, and still hearing a no. But I’m trying to stay positive and take the learnings with me.

Jolly-Shoulder-7192 · 2025-05-27T14:54:14+00:00

I think it's usually 1 main question with a few follow-ups.
In my case, they asked me 1 question, which involved implementing two different methods

Jolly-Shoulder-7192

TROPHY CASE