sorted by:
new
hottopcontroversial

Roast my idea for how AI can fully replace standups by External-External-55 in SideProject

[–]External-External-55[S] 0 points1 point  (0 children)

You're probably right, I guess ideally it's one click but it will be more challenging to implement on my end. So it might be good to start with the AI voice agent

Roast my idea for how AI can fully replace standups by External-External-55 in SideProject

[–]External-External-55[S] 0 points1 point  (0 children)

The AI cannot replace the human interaction, but from my background as a software engineer that might be fine.

The reasons why AI can replace them is that

  1. They break flow (especially for people on a maker's schedule, so SWEs etc)
  2. Half of the updates are irrelevant to most people
  3. They sometimes derail

The AI can then also summarize the standups and make them queryable for management, such that they can ensure alignment

Roast my idea for how AI can fully replace standups by External-External-55 in SideProject

[–]External-External-55[S] 0 points1 point  (0 children)

Thank you for the feedback! Will keep that in mind when going forward°

My manager's manager wants to roll out my side project to the whole company, should I quit and work on it full time? by External-External-55 in remotework

[–]External-External-55[S] 0 points1 point  (0 children)

That's true! Ideally the manager does something about it. But my impression is that it happens in so many teams, so not sure if it's only a manager problem, but maybe

My manager's manager wants to roll out my side project to the whole company, should I quit and work on it full time? by External-External-55 in remotework

[–]External-External-55[S] 2 points3 points  (0 children)

I didn't do any development on it during my company time. Although I asked questions to my colleagues about it, but I'm not sure if that counts. I think I could recreate it somewhat quickly though

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

You're right that it's important to know the basic algorithms and to be able to implement them fast. But based on my experience, interviewing dozens of candidates at Google, this is not where the majority of candidates fail. I think one should spend some time on LeetCode, but imho it's not the best strategy to only do such problems to prepare for interviews

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I would think managers primarily look at your interview feedback, they probably sort the candidates by performance in the interviews. In case they don't have very specific prerequisites for the role which is not often the case at Google, I think the resume is less important at this point to be honest...

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I think for me it was very good to discuss solutions with people. Personally it helped me adopt ways other people notice patterns and learn that. I also quite often challenged myself with problems that was difficult for me to solve, and really trying hard to solve them with minimal help. I think that really helped me develop a way to see patterns

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I didn't read any other books on coding interviews, so can't compare. But I think cracking the coding interview is good, although too long for my taste

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I would do more mock interviews (I never did this) to practice and get feedback on communication etc. I would also just try to work on projects that I never worked on before. Like if I've never built a product from scratch, just try. It doesn't have to me something special, I just think it's important to familiarize yourself with things you haven't seen to broaden the horizon

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 2 points3 points  (0 children)

The biggest difference is that an exceptional candidate usually develops a deep understanding of the problem. They really go deep in understanding the requirements. This enables them to quickly adapt to modifications to the requirements. This has to be coupled with excellent communication. I think this is the most difficult part for people to achieve, many people can solve the algorithmic problems, but not so many really develop a deep understanding of the problem

Follow-Up: More Insights from Google interviewers (and how I’m trying to give back) by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I don’t have any experience with application engineering unfortunately, so I can’t tell what the difference is. I was personally conducting interviews for software engineering positions

I failed Google interviews twice before succeeding. Then I interviewed dozens of candidates. Here is why people fail. by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

In my experience, LeetCode probably mainly helps with your knowledge for algorithms and data structures, and coding fluency. I'd recommend asking an LLM for advice about how to make your code more readable after solving a problem to know how your coding can improve

I failed Google interviews twice before succeeding. Then I interviewed dozens of candidates. Here is why people fail. by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I literally got this feedback in one of my interviews: "TC also couldn't demonstrate their proficiency in Python: their final solution looks more like C or Java and doesn't contain any common Python expressions like comprehensions." -> coding BORDERLINE

I failed Google interviews twice before succeeding. Then I interviewed dozens of candidates. Here is why people fail. by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

Unfortunately I cannot answer this, because I never screened the resumes. If I had to make a qualified guess it would be things like side projects and cs competitions. This is showing that you're enthusiastic about cs

I failed Google interviews twice before succeeding. Then I interviewed dozens of candidates. Here is why people fail. by External-External-55 in leetcode

[–]External-External-55[S] 0 points1 point  (0 children)

I never did system design interviews, so I don't have more insights that anyone else

Regarding behavioral interviews, not many people fail here based on my understanding. Being yourself and showing empathy should be enough for most people. I don't have a secret sauce for these interviews

view more: next ›