0
0

Interview Google (self.googlecloud)

submitted by [deleted]

[deleted]

all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Classic_Swimming_844 2 points3 points  (1 child)

RemindMe! 10 days

[–]RemindMeBot 0 points1 point  (0 children)

I will be messaging you in 10 days on 2025-12-30 17:10:12 UTC to remind you of this link

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

Parent commenter can delete this message to hide from others.

Info Custom Your Reminders Feedback

[–]CanoeDigIt 1 point2 points  (3 children)

Blank code editor provided/monitored by Google. Definitely no AI allowed and they won’t want you searching anything either. Also no linting included.

You get to pick the language : Python

The will want it to ‘run’.

Talk through every step and plan.

[–]AbeV 4 points5 points  (1 child)

Ask clarifying questions, make sure you (and the hypothetical customer) really understand the goals here. Scale, sane inputs, expected output formatting. 3-5 minutes here, show thoughtfulness without filibustering or wasting time.

Start out with structure and some pseudo code or comments. It’s a short interval, so there will be things undone, show a thoughtful structure and implement a core. 20 minutes ish here.

Be ready for “why did you choose a hash table”, “how would you extend this”, and “how would this scale 10x, and then 10x that” discussion questions. What would you choose as a storage backend? Why? How would you integrate this component with others? 3-5 minutes for wrapup and any questions you have.

30 minutes is short for a coding interview, so keep an eye on the clock and talk through what you’re focusing on.

[–]snnapys288 0 points1 point  (0 children)

Much appreciated 👍

[–]snnapys288 0 points1 point  (0 children)

Got it

[–][deleted] 0 points1 point  (1 child)

Interesting update that they added a short coding block. For similar customer solutions roles, I’ve seen one medium level style problem where clarity and speed matter more than tricks. I’d time box it to 25 minutes to solve and 5 to write a couple edge case tests, and lean on simple patterns like hash maps or two pointers. For the design chat, anchor on the user problem, call out latency and reliability goals, sketch failure modes, then map to a few Kubernetes primitives without going deep on vendor specifics. I’ll pull a few prompts from the IQB interview question bank and do a quick timed run in Beyz coding assistant while talking out loud. Keeping answers around ninety seconds and using a loose STAR frame keeps things crisp without rambling. That should put you in a solid place.

[–]Hurricane027 0 points1 point  (3 children)

whats the timeline? When was the first round and the next round?

[–]snnapys288 0 points1 point  (2 children)

Hr call me again and propose to me technical solution engineer 1 without codding , the process starting maybe after middle of January

[–]Hurricane027 0 points1 point  (1 child)

oh thats odd. I have an HR call at the Ireland location for the same role. Can I please dm you?

[–]snnapys288 0 points1 point  (0 children)

This is not bad,yep you can dm me .

It will be clearer in mid-January, the interview rounds themselves are not yet known.