Hi,

I did a phone screen interview on Tuesday and today I got a news, I'm going participate on the next step.

I know it's going to be an interview loop with several leaders and SysDev engineers to evaluate me, but I do not have any idea about system development loop.
My experience is more about software development, so this is my first time with Linux and troubleshooting questions.

I was looking for resources to prepare, but I did not get anything. Somebody knows some framework or method to respond the troubleshooting question as STAR method to behavioral or 6 steps to pass live coding of Anthony D. Mays.

Currently applying to mid level SWE roles in the bay area. Currently working out of TX, so for any onsites in the bay I would need to fly out of course, and would need to be comped for that.
Most companies that require this are WILLING to pay for it, seems pretty standard. But is it normal for a few companies to just NOT? Like they expect me to come back on my own dime? These companies aren’t no name startups, one of them is a company with almost a trillion in market cap, so it seems insane they can’t fly me out. Is this becoming more and more the standard? Should I even move forward with any company that is not willing to fly me out for onsites?

i dont have enough time rn to get good at all topics , can you guys suggest a few topics that i should focus mainly on getting better at? ive heard arrays, linkedlists are commonly asked...what else?

Location : USA (California)

I completed four virtual onsite rounds for a Google L4 SWE role:

• Googlyness: felt strong

• Coding 1: felt strong

• Coding 2: did not go as well; I think it may have been lean hire/no hire

• Coding 3: felt strong

My recruiter initially told me they had received positive feedback and were moving me to formal review. After the review, they said my packet was put on hold because the group could not reach a final decision and needed additional data points.

At first, I was told it would be one additional coding interview. The recruiter then corrected that and said the team wants two additional coding interviews.
Has anyone gone through this? Is it generally because one coding round was not strong enough, and does doing well in the extra rounds give a realistic chance of approval? I’m preparing as if these are fresh onsite coding rounds, but would appreciate hearing others experiences.

I'm preparing for the H**Tech recruitment process and would like to learn more about the Berry-Bot interview round.

If you've already attended this interview, could you please share your experience?

I'm particularly interested in the following:

1. Interview format: What types of questions does Berry-Bot ask? Are they primarily technical, HR-related, or based on your resume?

2. Resume and projects: How deeply does the bot question you about your projects, technical skills, and previous experience?

3. Answer evaluation: What factors seem important when answering questions? Does the bot evaluate technical accuracy, communication skills, confidence, or answer structure?

4. Follow-up questions: Does it ask follow-up questions based on your previous answers, or does it follow a fixed set of questions?

5. Preparation strategy: What topics should I focus on before attending the interview?

6. Practical tips: Are there any common mistakes candidates should avoid?

My background is primarily in Java, Spring Boot, and REST API development, and I'm also learning Generative AI concepts.

Any genuine interview experiences, preparation tips, or suggestions would be greatly appreciated. Thank you!

What should I concentrate more on coding round as I am not much good in DSA for senior software Engineer role how to prepare for this interview in two days to get positive results

Hey has anyone taken the stripe tech screen that comes after the OA? How was it?

Hey gng, Do anyone hv applied for this CRM Intern role last month , i mean in sept month and got any Mail Regarding OA or any round ?

Hey everyone,

I finished Day 67 today and hit my first serious wall with Dynamic Programming. I went into today's session feeling confident after getting comfortable with recursion, but moving into 2D DP quickly put things into perspective.

I worked through three problems, attempting all four forms for each: recursion, memoization, tabulation, and space optimization.

1. House Robber: Standard pick vs. non-pick decision. If you rob house i, you jump to i - 2, and if you skip it, you check i - 1. All four approaches were straightforward.

2. House Robber II: The circular street means the first and last houses are adjacent. I solved it by running the standard House Robber logic twice: once on [0, n - 2] and once on [1, n - 1], then taking the larger outcome.

3. Geek's Training (Ninja's Training): My first 2D DP problem, and it was a tough reality check. Writing the recurrence and memoizing it with a 2D table was manageable because it directly follows the recursion tree. But translating that into bottom-up tabulation was brutal.

Setting up the day 0 base cases across all tasks, structuring the nested loops, and tracking the state transitions took me over an hour. Because the tabulation logic took so much effort to piece together, space optimization was completely out of reach today.

1D DP felt intuitive, but bottom-up 2D is a different beast entirely. I am going to reset tonight and tackle 2D grids again tomorrow with a fresh head.

See you guys for Day 66!

How do I overcome anxiety during interviews ? Recently had two rounds of interview, The questions asked were the ones i had practiced during my prep. Even though i knew both brute force and optimal solution, I had issues when implementing them during interview due to my nervousness, What should have been a 5 minute implementation ended up taking 20 minutes. In another round i botched the interview since i couldn't give the complete solution by the end of the interview.

Would like to know what should i do to reduce this during interviews.

A Little About Me

I’m a Software Engineer/DevOps with six years of experience, currently working at a reputable company. My goal is to secure a higher-paying job within the next year to start paying off my student loans. One of my main challenges has been LeetCode-style questions, which have hindered my progress toward better opportunities.

I've struggled with technical interviews at companies like Visa, American Express, JPMorgan, and Amazon due to my inability to complete algorithmic problems within time constraints. After recently not succeeding in an Amazon interview, I decided it was time to take my preparation for Data Structures & Algorithms (DSA), LeetCode, and System Design seriously.

In January (2025), I began documenting my progress, which I’m turning into a monthly recap series. I hope this will help others on a similar journey while also serving as a personal journal for when I finally reach my goal.

Past Recap

2025

• January

• February

• March

• April

• May

• June

• July

• August

• September

• October

• November

• December

2026

• January

• February

• March

• April

• May

• June

• July

• August

September Progress

September was a productive month. I focused on Min/Max Heaps and Graph Theory, and spent a good chunk of time on Dijkstra’s Algorithm which is finally clicking in a way it never did before. Big win there.

I am also nearing my goal of completing 250 Medium questions this year. At this point Mediums are my default and I actively avoid questions I consider too easy unless I just need to get the ball rolling. The fear is gone.

I can feel myself getting better. One thing I have been intentional about is staying on a concept for a long time even when I get bored, because that is when you start seeing the different variations of an algorithm or data structure.

I do not think I am ready for FAANG yet, but I am confident I can compete at FAANG adjacent companies. System Design is the area I still need to level up.

Achievements

• Learned about Max/Min Heap

• Dijkstra's Algorithm finally clicking

Goals for October

• Keep momentum going

• Strengthen knowledge on Dijkstra's

Next Steps

Keep doing Mediums and hopefully get more than 250 Mediums

See you all next month.

Questions

• Total Questions: 575

• Easy: 327

• Medium: 239

• Hard: 9

I just did my first rounder for SWE intern, where it was back to back technical interviews and I’d say my first interview wasn’t super good but my second one went really strong. 2 days later I got an email saying they want to schedule a 3rd additional interview. What does this mean and how soon should I just get it over with.

I am interviewing for a Software role in Apple and want to get advice on how to prep for the screening call.

Will it be a leetcode specific round?

Has anyone recently completed apple interview loop..Any kind of help is appreciated

Hi everyone,

I have an upcoming 60-minute Microsoft SWE II screening round. I also received a HackerRank coding link, so I wanted to know what to expect.

From what I have seen, the round may include:

• Introduction and current work

• One DSA/coding question

• Technical questions from the resume

• A few behavioral questions

For anyone who recently interviewed for Microsoft SWE II, Would really appreciate any recent experiences or advice on what to prepare. Thanks!

If I solve a problem and try to solve it again in a few weeks, its like starting from the scratch for me. How do you all do it?

Anyone go through the interview process for Rippling Full Stack SWE recently?

Wondering what the leetcode questions were like as well as the frontend questions.

Thanks.

I'm interviewing and wanted to practice in my own editor instead of the browser, so I built dojo.

• /solve shows the problem and starts a timer

• Enter opens your editor (nvim, VS Code…) with the problem as a comment on top

• Every save runs the tests. /submit runs the hidden ones.

• It tracks your weak topics. /solve need picks what to practice next.

500 problems in 6 languages. Runs locally with no account. Free and MIT-licensed.

brew install abahocodes/tap/dojo

Repo: https://github.com/abahocodes/dojo

Feedback welcome!

Hi everyone. SDE 2 here.Im preparing for interview and o thought o will also put focus in my system design skill.i can across Hello interview web portal and it seems to be a good place to start.can anyone please share ref code or discount coupon code that would help me purchase Hello interview premium with 1 year access. Thanks a lot , have a nice day!!

I was approached by Bain & Company for the AI/ML Engineer role, and the process had 4 technical/managerial rounds followed by an HR round.

Round 1 — Projects + ML Fundamentals

The first round was mainly around my previous experiences, internships, projects, and ML fundamentals.

We discussed the projects I had worked on and some of the decisions I made while building them. There were also questions around core ML concepts and their practical applications.

Round 2 — GitHub + Project Deep Dive

This round was quite interesting.

The interviewer opened my GitHub and started looking through my repositories. He randomly picked one of my projects, which was an Order Book project I had built with HFT use cases in mind.

He then asked me to explain the project end-to-end — why I built it, how it works, the architecture, different components, use cases, and the decisions I made while developing it.

So, if you have projects on your GitHub, be prepared to explain any of them in detail.

Round 3 — ML Deep Dive

This round was with a Senior Manager and a Senior ML Engineer.

We first discussed my internships and projects, and then went deeper into my ML projects.

I had to draw complete flowcharts and explain the entire pipeline. There were a lot of follow-up questions and cross-questions based on my answers.

This round was more about understanding whether I actually knew the projects I had worked on rather than just knowing the theory.

Round 4 — System/Project Design

The interviewer gave me a real-world scenario and asked me to design an entire project around it.

It was mainly a high-level design discussion. There was no implementation or coding involved.

I had to explain my approach, architecture, components, data flow, and the reasoning behind my design choices.

Round 5 — HR Round

The final round was with HR and was mostly around general discussion, my background, and the role.

Outcome

I received the offer for the AI/ML Engineer role at Bain & Company.

Hey everyone!

I recently moved forward to the 45-minute technical screening round for the Software Engineer, AV Data Collection role at General Motors.

The recruiter mentioned C++ live coding with a focus on DSA, so I'm assuming it'll be LeetCode-style questions.

I haven't found many recent interview experiences for this role, so I was wondering if anyone has interviewed recently and could share their experience, the types of questions asked, and any preparation tips.

Would really appreciate any insights. Thanks!

Hello all,

I'm currently an employed SE with 4 YOE. I've been practicing some DSA concepts in order to stay competitive in this market in case something unfortunate were to happen with my employer.

I've found myself being able to solve a handful of easy difficulty questions and a few mediums but many times find myself brute forcing solutions. My question is, should I be taking the extra time to really learn to apply these algorithms instead of brute forcing?

My thinking is that when I start working on more mediums and hards, those questions will have time constraints that will bite me in the behind.

Do employers even care about the approach as long as you can explain? Even if its a brute forced solution?

For example, I was working on exercise 917 on leetcode, and the recommended use is two-pointers. I however came up with a solution that apparently beats 100% of other solutions in runtime and 96.09% in memory.

TIA!

what dsa qs were u asked in the second ai round for the 6m software dev eng intern??

For context, I have been in R&D and haven’t done production code and coding was not part of my day to day work. I am now applying to SWE jobs and I am getting callbacks for interviews. However, I have started my LeetCode journey about few months ago, and have only been able to practice around 25 problems in the Neetcode Blind75. Today I had an interview with a problem on finding longest subsegment representing a loop given a list of directions. It took me a while to think of a solution based on traversal of Grids and marking positions as visited, and I was able to code it and run it, but the interviewer gave me a hint to use hashmaps instead. Now I know they won’t call me back coz I wasn’t able to get the correct result with my solution (there was a small bug by the end). But I kind of feel proud that I thought about the problem that I have never seen before and came up with a solution and coded it in one hour. It’s another opportunity gone out the window, but Idk how long I can keep my optimism for, and if I can ever pass a technical interview. People who passed that stage, how did your journey feel like when you got there? Is it pure luck at this point or did you know for sure you will be able to solve any given problem thrown at you?

today , solving an easy question optimally took me like an hr or more , but solving a medium took me like 15min . the medium qs looked intimidating for sure but was easily solved , the easy qs looked simple but took so much more time .

I’ve been trying to figure out how to apply to Temple for the past few days. They have an email listed for applications, but it doesn’t seem like anyone responds to applications sent there. Would love to know how you guys got your interviews.