Ha, you explaining the months spent meeting with folks only for a far simpler version to go to production is hilarious. I've been at it for about 10 years now and its so easy for new engineers to fall into that trap.
the best way to solve these arguments is to stop talking. put this down on paper {e.g. prototype}and test it by simulating the steps. Everything sounds great in peoples minds. Once its down on paper you can tear an idea to shreds in a tangible way - this how you go from shit ideas to good one[s].
For the record I did more than just add buttons at google, such as migrating Java microservices.. which wasn't much more difficult tbh. But yeah, in general I think the job is easier than the interviews.
I recently joined as a junior in a company's internal cloud team, and everything you said was EXACTLY my experience too, except I didnt have documentation, so I had to dredge through the code and DB directly. I had to implement a very similar feature too in their frontend.
Actual user of dataflow in prod here. And what do you know I actually used the force stop button feature the other day because we had some wierd behaviour where our pipeline was running fine locally (using Beam runner) but when deployed to dataflow runners it would bug out. Fully understand how difficult it is to make 'good UI' - props on building something that some people out here actually use! BTW if you are a junior engineer / wanting to get a SWE job, listen to this guy. This is how good engineers solve problems. Don't think just because its 'a few lines of code' it's an easy job, it's doing the research and covering all the bases to make sure you have the best implementation that makes the difference between a well designed feature and a shit feature that users hate to use.
You should do more videos like this, i was in a situation like this but i spent days coding crap and talking to the PM before i could finally get it. There were times i even asked my senior for help, he was like dont worry you'll figure it out.
@@gradientO not "all people" doesn't focused on frontend... That's like asking a mathematician to paint the Mona Lisa portrait. Not all CS students can't do art. That's why art major exists to teach you shapes, color theories, and ect.
Yeah that's a really fair point. I will say that Googles dev culture is backend heavy tho. Any frontend dev can be moved to a backend project (like in my case), but backend devs are not necessarily expected to be moved to frontend projects. Most frontend teams working on GCP also own middle ware microservices running graphql. And to debug these, backend knowledge is pretty essential. Even just collecting metrics to justify the impact of feature launches requires writing your own SQL queries.
@@StfuSiriusly imagine asking a fortend engineer to solve a hard math leetcode problem but he only knows how to animated pictures with frontend tools. He's gonna only animated spinning circle around the interviewer time. Leetcode isn't for frontend developers. The point is, the google interview process is broken... They're different websites or process to test someone who's good at frontend skills meanwhile Neetcode is good at "backend" by solving problems with a backend tool called "Python". He wasted his time to be as an Google frontend engineer... Google didn't knowledge his backend skills as we do now. I don't see Neetcode solving leetcode problems with only html. Html is a frontend tool.
@@s4ltokyoi am ok with interviewing candidates with leetcode, but not okay if they put them in frontend teams. the candidate spent months grinding algorithms and system design and microservices and design patterns just to create a react component
I can commend your work on ui - observability of dataflow is quite good. But man, I hate dataflow itself. We used it for rather simple etl, and after years of attempts to make it work efficiently and reliably I just gave up. Dropping it for self-written service and very happy.
So regarding the fact that the metrics page was launched and much simpler than what you had been planning/working on, it's likely that because you left they had to launch with some MVP to get something out there. Whoever took on that page likely had other stuff they were working on and so the team has to weigh various priorities.
people in comments complaining he grinded algo's to do ui well thats the reason he was able to implement it and understand the project without anyone spoon feeding him ......i know leetcode is not helpful in jobs but it helps you know how to do something when you don't know how to do it ......thats why they do white board interviews so the seniors dont have to waste time explaining everything to junior they can expect the junior to learn on his own
If you check comments please answer me, how long did it took you to solve a problem of knowing if task was actually canceled? I get that you've read some docs and got the answer but how long did it take you, 10 minutes, an hour, two days?
Codewise, i think it was < 100 lines of code, most of the work was doing meetings, writing docs, testing, etc. Took multiple weeks, but it's not like I was full time working on this feature alone during that time.
How do people manage to get across all of these different areas I've never heard of and be almost experts in it. Where does one learn about this stuff. Just a side note, please dont move the mouse over an area of the screen and then shake the cursor up and down, its very distracting. We can see where you are pointing just fine.
You should definitely never do research as a junior or senior. If they don't want to provide full feature task requirements and an insight into how the code works, just pad the resume and move on. That place is a sewer and isn't interested in anything good.
bro im graduate kid i have question for u , how the ui can interact and can able to controle datacentre machine , how basicalliy the sandbox are built plzzz help me out .
Hey... do you have some hints on what it is like to work for Google Core Engineering? Is that something exciting on a software development perspective? I am asking specifically for Governance team. Thanks in advance for any help
Oh man, a simple page that requires going through 20 approvals. That's big tech SWE life bro. Everyone wants a piece of your features/work. Talk about corporate drama.
Actually, delivery something to production in FAANG as a junior is a great achievement!
wasnt super exciting? lol now what do you do?
This is the first time ive seen someone really answer the question "What they worked on at ...". Thank you for sharing.
Ha, you explaining the months spent meeting with folks only for a far simpler version to go to production is hilarious. I've been at it for about 10 years now and its so easy for new engineers to fall into that trap.
the best way to solve these arguments is to stop talking. put this down on paper {e.g. prototype}and test it by simulating the steps.
Everything sounds great in peoples minds. Once its down on paper you can tear an idea to shreds in a tangible way - this how you go from shit ideas to good one[s].
For the record I did more than just add buttons at google, such as migrating Java microservices.. which wasn't much more difficult tbh.
But yeah, in general I think the job is easier than the interviews.
For real tho, is there anything difficult for you?
I recently joined as a junior in a company's internal cloud team, and everything you said was EXACTLY my experience too, except I didnt have documentation, so I had to dredge through the code and DB directly. I had to implement a very similar feature too in their frontend.
Actual user of dataflow in prod here. And what do you know I actually used the force stop button feature the other day because we had some wierd behaviour where our pipeline was running fine locally (using Beam runner) but when deployed to dataflow runners it would bug out.
Fully understand how difficult it is to make 'good UI' - props on building something that some people out here actually use!
BTW if you are a junior engineer / wanting to get a SWE job, listen to this guy. This is how good engineers solve problems. Don't think just because its 'a few lines of code' it's an easy job, it's doing the research and covering all the bases to make sure you have the best implementation that makes the difference between a well designed feature and a shit feature that users hate to use.
It'd be nice if the stop button had a timer or timestamp somewhere to let you know how much longer you need to wait before it can be used.
You should do more videos like this, i was in a situation like this but i spent days coding crap and talking to the PM before i could finally get it. There were times i even asked my senior for help, he was like dont worry you'll figure it out.
Imagine grinded backend leetcode problems to end up as an frontend ui/ux engineer meanwhile some random starving frontend artist trying to find a job.
That's all people focus nowadays
@@gradientO not "all people" doesn't focused on frontend...
That's like asking a mathematician to paint the Mona Lisa portrait.
Not all CS students can't do art.
That's why art major exists to teach you shapes, color theories, and ect.
? that starving frontend dev could also just grind leetcode. Not sure what your point is.. FAANG companies need frontend devs as well.
Yeah that's a really fair point. I will say that Googles dev culture is backend heavy tho.
Any frontend dev can be moved to a backend project (like in my case), but backend devs are not necessarily expected to be moved to frontend projects.
Most frontend teams working on GCP also own middle ware microservices running graphql. And to debug these, backend knowledge is pretty essential.
Even just collecting metrics to justify the impact of feature launches requires writing your own SQL queries.
@@StfuSiriusly imagine asking a fortend engineer to solve a hard math leetcode problem but he only knows how to animated pictures with frontend tools. He's gonna only animated spinning circle around the interviewer time.
Leetcode isn't for frontend developers.
The point is, the google interview process is broken... They're different websites or process to test someone who's good at frontend skills meanwhile Neetcode is good at "backend" by solving problems with a backend tool called "Python". He wasted his time to be as an Google frontend engineer... Google didn't knowledge his backend skills as we do now.
I don't see Neetcode solving leetcode problems with only html. Html is a frontend tool.
The core library that powers Dataflow is open-sourced as Apache Beam. I use this frequently at my job.
I use to work on dataflow.. its really fascinating to know that you have designed it. 🎉
whats always daunting to me is working through the abstractions and understanding the overarching purpose of the product we re building
We use data flow at my company and it's so unbelievably expensive
I love how you explain everything
imagine grinding all algorithms patterns and getting into FAANG to do UI
Well, Facebook could really use some UI people.. half of their website is unusable.
Yeah thats typical. The job is so much easier than interviews honestly.
@@s4ltokyoi am ok with interviewing candidates with leetcode, but not okay if they put them in frontend teams. the candidate spent months grinding algorithms and system design and microservices and design patterns just to create a react component
I can commend your work on ui - observability of dataflow is quite good. But man, I hate dataflow itself. We used it for rather simple etl, and after years of attempts to make it work efficiently and reliably I just gave up. Dropping it for self-written service and very happy.
I follow the same strategy. Generally I am shy to ask questions and try to solve it myself as hard as I can.
Love your work!
So regarding the fact that the metrics page was launched and much simpler than what you had been planning/working on, it's likely that because you left they had to launch with some MVP to get something out there. Whoever took on that page likely had other stuff they were working on and so the team has to weigh various priorities.
people in comments complaining he grinded algo's to do ui well thats the reason he was able to implement it and understand the project without anyone spoon feeding him ......i know leetcode is not helpful in jobs but it helps you know how to do something when you don't know how to do it ......thats why they do white board interviews so the seniors dont have to waste time explaining everything to junior they can expect the junior to learn on his own
I saw it live and I enjoyed this streem a lot
What did you do at google?
Spark can do both - batch and stream processing
Technically yeah, afaik it's not "true" stream processing but micro batch.
Silly question but what does Google Cloud uses as their frontend framework? Angular, React or something else?
It's Angular. You can inspect the HTML yourself to see the references to "ng".
the way you describe this makes me never want to work at a large company lmao.
I'm lazy I don't want to make a full stack app every week
I need to invest time to get into fang to work less
Nice advice
Big Fan🎉
hey i'm in this one!!
If you check comments please answer me, how long did it took you to solve a problem of knowing if task was actually canceled? I get that you've read some docs and got the answer but how long did it take you, 10 minutes, an hour, two days?
Did they give enough time to do the research? Or
Did they force you to complete within X days?
Дуже круто, приємно і цікаво.
A question also asked by the live chat, do they actually use all MUI in google for react projects?
What react projects? 🤭 Google doesn't use React at all, only Angular and a bunch of other internal-only frameworks.
But what are the cases when a job gets stuck?
Did you have to learn some data engineering stuff for this work?
😂 the professionalism delay is so relatable
MorrisJS library to render those line/bar charts?
just to know, how much time you spend on creating the button? was it an afternoon or a week?
Codewise, i think it was < 100 lines of code, most of the work was doing meetings, writing docs, testing, etc. Took multiple weeks, but it's not like I was full time working on this feature alone during that time.
@@NeetCodeIO💀
Curious why did you split into two channels?
Is it possible to work on Google for an average programmer?
How do people manage to get across all of these different areas I've never heard of and be almost experts in it. Where does one learn about this stuff. Just a side note, please dont move the mouse over an area of the screen and then shake the cursor up and down, its very distracting. We can see where you are pointing just fine.
Which algorithm did you use?? XD
hi ,
Does Google or any faang hire trainees from North Africa?
They hire interns.... Even currently we have positions for interns at Microsoft Kenya ADC
You mentioned at the end that the job didn't excite you. Did you ever consider doing an internal transfer?
hes probably making more $ now and doing what he loves with no boss.
MQL may be the MongoDB Query Language.
It's actually Monitoring Query Language: cloud.google.com/monitoring/mql
@@NeetCodeIO Thank you for your reply! Same acronym for different query languages 😂👍
Thanks for all the great content! Slightly unrelated question, would you be able to share the office chair that you use?
First here... Navdeep😀
wait I thought you left google (?)
You should definitely never do research as a junior or senior. If they don't want to provide full feature task requirements and an insight into how the code works, just pad the resume and move on. That place is a sewer and isn't interested in anything good.
bro im graduate kid i have question for u , how the ui can interact and can able to controle datacentre machine , how basicalliy the sandbox are built plzzz help me out .
Generally everyone uses a cloud provider these days to abstract that away. Google uses Borg, an internal tool.
Thanks dude cool.
Do they look at our search history before hiring?
Hmm, what do you think? 🤔 Would that be legal?
Yes, they do.
Is It they check our google history before hiring ?
@@thegrind9628
@@NeetCodeIO legal until busted 😂
Shouldn't this validation be done on the backend though? Doing business layer stuff in the UI layer just feels wrong..
Yeah it's also enforced by the backend
wasnt super exciting? lol now what do you do?
Hey... do you have some hints on what it is like to work for Google Core Engineering? Is that something exciting on a software development perspective? I am asking specifically for Governance team.
Thanks in advance for any help
Oh as a software engineer, I thought you were Google's plumber.
By God dataflow... Lol
Oh man, a simple page that requires going through 20 approvals. That's big tech SWE life bro. Everyone wants a piece of your features/work. Talk about corporate drama.
cute
Shoutout to all the others making complicated buttons 🫡