PokeVideoPlayer v23.9-app.js-020924_
0143ab93_videojs8_1563605 licensed under gpl3-or-later
Views : 6,652
Genre: Science & Technology
Uploaded At Feb 12, 2024 ^^
warning: returnyoutubedislikes may not be accurate, this is just an estiment ehe :3
Rating : 4.973 (2/294 LTDR)
99.32% of the users lieked the video!!
0.68% of the users dislieked the video!!
User score: 98.98- Masterpiece Video
RYD date created : 2024-05-10T14:04:44.263326Z
See in json
Top Comments of this video!! :3
In the data realm (data engineering, data visualization, data science), we ask questions that we encountered during the years and simplify it down to the core logic.
These problems usually take us hours or days to solve so we certainly don't expect candidates to solve them within 15 minutes, but we would like them to explain their thought process to see if them can Even understand where the logic problem lies and whether they'd know a set of high level solutions.
Data engineering related problems are different in nature than SWE. You guys deal with complexity that should be simplified and well managed i.e. better data structures and faster run time algorithms and cleaner code versus is dealing with more logical problems so interviews might take different approaches.
|
I really love this guy, he made a lot of sense in this video. I guess the whole idea behind the tough interview sessions is to find people who have been through hard codes to be managing some simple tasks and in case something tough comes up in the future you'll be able to face it and solve it... 🎉
|
The objective is not to assess whether you know the minimum subject matter for the job but rather to see how you think and handle a stressful problem under time pressure. My goal as a hiring manager is not to find some minimally qualified person to perform the required tasks but rather to find a smart person who can grow and advance in the company. The best questions are those that the candidate has not heard before or spent time preparing for. The problem with software interviews is that all candidates spend hundreds of hours studying LEET code. And interviewers tend to draw from the same database of problems. If I were interviewing candidates for a software engineering role, I would not ask coding problems; I would ask questions completely outside the field to see the candidate’s deductive and inductive reasoning skills. For example, I might pose a math or physics problem. Or maybe even an economics or finance question.
1 |
@Nagatacs
9 months ago
It's definetely messed up but the good part is: prepare for hard coding interviews and when you get approved you hardly will find anything as hard as the interview
10 |