I have no idea how I get into a company without interview as a junior. They called me for interview to their company. I got to wait like an hour and half for someone to show up and then Hr show up, give me employee contract and ask me " they already interview you, right?". I didn't answer that, and she kept talking about contract. And now I'm four months in software development team. Still have no idea wtf happened but I'm doing good now.
My mans rolled up with a nat 20 on luck and instantly got the job. Well done. Also, as an aside, there is evidence thats show that pulling a random resume, doing one phone screen and offering the job immediately is just as effective as doing 3+ interviews and challenges. So long as the random resume meets the minimum requirements (yoe, college degree, certs, licenses, etc). Employers that get super picky spend lots of time and money (probably more than the employee would get paid in the first year) doing so many interviews with basically no net benefit. When I did hiring once for an engineer, we got 30+ resumes in a day and stopped. Then spent a couple days doing phone screens, setup 4 interviews for the following week. We made the hire in less than 10 days of starting. That employee was great. These big companies that spend 4 months doing countless interviews makes no sense, it ends up being a big waste of time for everyone involved.
@@heyhoe168 Depends on the manager profile, if the guy became a manager through business school and never coded it's gonna be like that, in the opposite case if he is from an engineering background and has coded half of the codebase of the company then yeah gonna be good
No, being a corporate developer is being reduced to writing requirements docs and having to campaign them through your executives to maybe have your solutions prioritized because the actual development staff got outsourced to Indian contractors so your company doesn't have to pay onshore development rates.
@@esclavodeluna8000 He also put the name of the struct right after the word struct, rather than struct {} List; and then use a typedef to make the struct viewed as a type for the compilation unit,
@@markminch1906 It is not practical to use a typedef'd struct to create a linked list, because the struct must contain a pointer to the next node, but the typedef does not exist until after the closing brace of the struct. Therefore, the struct must have a tag, and you must actually use it at least once. Since you already have one name for the type that you must actually use, it is not wise to introduce a second name just to make it "look neat."
If he wants you to write in machine code, he has to give you which instruction set architecture (ISA) is used for the code. It could be a ARM architecture, a x86 architecture, or a RISC. Or even he has his own architecture. Otherwise, the interviewer has either no clue what he is asking for or he just dislike you in the first place.
@@jupahe6448 You are correct, ARM architecture is a RSIC. MIPS is also another example. Basically, there are CISC and RISC. The only CISC architecture I came to know of is intel x86. Most common civilian computation products use RISC.
I remember a live tech assessment for JP Morgan in 2021. The exercise was to write the Fibonacci sequence (plain, old Fibonacci). Those days are gone now, apparently.
My Coding assessment for Twitch was to write an efficient video streaming caching mechanism in C++. It wasn’t anything like an abstracted Leet Code problem. When I first started the assessment, I was greeted with 200 lines of already written code that I had to learn and correctly interface with. The video stream object they wanted me to work with was an extremely complex data structure that my caching system had to interpret, modify, and store in the correct way, based on the multiple levels of information within it. There was several pages of documentation that were necessary to read to even begin understanding the pre-written code, video stream data structure, and hidden apis. To submit the code, your caching mechanism had to pass a dozen tests that took a minute to run. They gave me 30 minutes. I read the documentation, thought about how I would implement it, ran the test cases to see an example of what they expected, and then closed the page with 15 minutes left. I have solved more than a 100 medium and 50 hard leet code problems, done CodeForces for 4 years, read and completed nearly the entire cracking the coding interview book, work for a big tech company, and even wrote my own efficient data structures library to implement pretty advanced algorithms in C++. I genuinely don’t understand how even a 30 year tech lead could have passed that assessment. There physically was not enough time to complete the task they provided me. Thanks for reading my trauma dump
I remember about someone giving an Amazon interview - asked Fibonacci (slightly fucked up at the end on follow up on complexity) still got the role. (2024 story)
Not new really, had that happened time over time 15 years ago. But the one company that rejected me (one out of 50 or so) actually sent me a good old-fashioned LETTER on paper. Still got it somewhere in my papers.
it was always the case. My friends from HR say that they do this to avoid conflicts. I have had several experiences where they told me that I had passed to the next stage and that they would contact me about the next stage and then I heard nothing from them. Once they even told me that they were hiring and would send details tomorrow, but the next day they simply sent me a text message saying that they had hired another candidate. Ghosting generally happens all the time.
This is why Im picking up other skills on top of software development. This market seems to be getting oversaturated and employers are getting picky, so it's good to have a backup plan.
As an older programmer. One, don't work for the big companies those jobs are miserable resume builders everyone leaves in 3mos those skills don't transfer they're a joke. Two, once you quit that awful job after this dehumanizing process. You have your pick of making 20% more at lots of places with half the workload. Or maybe the same money at a place where you barely even have to sign in to work most days and just randomly get crushed every few months. The whole industry is garbage. I hate it. But it makes money. Notice I haven't said a single word about like, helping people, or making a product. That's the worst part. The most helpful thing I've built in a decade was stuffing data into emails for pizza. If you can work in another industry, like you don't need money and you just want to farm or cut hair, just do that instead. Life will be better.
@@KevinJDildonik I'm programming since I was 15 (now ten years older) and it always was and will be my passion. But knowing how you don't even get to be a programmer doing a programming (duh) job is outrageous. It's just enslavement with extra steps, especially working for big industry. I got two chances of getting a pure coding job (no HR or meetings bullshit, just a B2B contract) in a fairly friendly environment of 10-15 people working as a contractor buy sadly nothing ever succeeded. Good thing I live in Europe where IT startups and less dense companies hire more actual entry-level developers but it's still very hard and I'm afraid I will just end in some pseudo-company that makes nothing just to fulfill the very suspicious demand.
The software engineer interviews are really broken, tipically: Interview: Solve problem with data structures, big o notation, algorithmic complexity, etc Job: Center a div
This reminds me how fortunate I am as a self-taught programmer (electrical engineering dropout). When interviewing for my current job (round of 3 + take home) it was a deep dive into signal based web frameworks, talking about programming at a high level, and addressing cultural fit for the startup. I work as a triage engineer (I'm the first contact for bug investigations and such) so my take home was a typescript project where I had to identify bugs. They were really clever because the code worked, but there were subtle bugs. Overall, I got really lucky, and my team is incredible. I'm sending you the best and hope you find a company that values you and gives you a fair shot.
@@carlosmspk like if they think youd get along with the team, not just as friendly people but your work habits. if you are someone who prefers to update your team once a week but your team is a startup that needs updates like two times a day, it just wont be a good fit. and then also things like asking for feedback or how good you would be giving feedback and collaborating with others. i think people also assess how you'd fit into a 'boring' company - if they see you've only worked at super exciting companies then suddenly want to work on the backend of an airport system in COBOL or at a bank, they would probably see that as a red flag IMO cus then they'd be suspicious for how long you'd actually stay around. it costs a lot to hire someone new
I've been trying since last month and out of my 100% applications, 10% of emails are rejection emails, barely 2-4% companies reply and the rest 86-88% straight up ignores the application. I don't understand why even bother posting a job when you are not planning to hire immediately.
@@anonimowelwiatko4455 IKR 🤣😭 Even I received a call from a recruiter and after the call she shared a prep deck with me which was a 6 page PDF mentioning there's gonna be 5 rounds, 1st two are gonna be DSA, 3rd gonna be of LLD, 4th will be HLD and finally 5th would be with Engineering Manager. I didn't reply afterwards. 😭
I actually had an interview that had question of reading machine code in it. Though it was not a junior position (15+ years required, anti-virus software)
@@mapron1There's no point making people read strings of binary. 00101011 is 2B and that's only part of an instruction or address, anything else is just hazing.
The first job is the hardest. I've been in the industry for 15 years and I haven't applied for any job except my first one. The rest of them were from my network. The best thing you can do is grow your portfolio, work on stuff you're passionate in, and go out and meet people in the industry. Don't look desperate and don't try to use them to get a job. We can smell that from a mile away. Just go nerd out.
Lol wtf 😂 Exactly opposite for me. Each year it's getting harder to get job. First two jobs were super easy to get. Now it's pretty much impossible. Nerd out? Gtfo... The best money was in the easiest jobs. Better to improve people/interview skill rather than "nerding out". Nothing good comes out of nerding out/ getting too "deep"
For everyone here dooming about getting a developer job, my recommendation is to try applying to your local government institutions. Most people don't even remember they exist or hire IT staff, so you'll have less competition. You'll also be helping maintain some kind of public research project or infrastructure, so you won't feel like you have a job that's not impactful or even actively harmful. They give good benefits and it's unlikely you'll be fired once you pass the initial settling-in period. The downside is that they're going to pay less. Also, the low likelihood of getting fired means that bad developers don't get kicked out and replaced. These places can't afford good developers, it's the whole reason they're easier to get into. You'll have to learn a lot by yourself, both because your agency will be understaffed and because many of your coworkers are doing things wrong. You may have to advocate for best practices by yourself.
Congratulations for passing your big O notation dynamic programming reverse binary tree test. For your first task you are gonna use axios to retrieve data from this web service and display it in a table. And tomorrow. And the next day. For the next year or so until we find someone cheaper than you.
As an experienced software developer with a deep and wide background, low and high level, coding interviews are getting more and more garbage everyday. The remote code screen is just the first phase after getting past the recruiter. Then you get to spend 6 or more hours onsite doing coding interviews in person. It’s nothing like doing actual work.
My lecturer once told me that couple years ago there was this one company that was hiring for a specific position where requirement was knowledge and experience of 7 years of a language (I don't remember which one it was) that was only 4-5 years old. lol it realy is tough nowadays.
HAHA I had an interview 10 years ago to write a method in JS to tell if a string is a palindrone which basically just used the reverse method to do all the work.
Seeing this I'm grateful for my job, but I also thrive for more, and its so annoying that I will have to take time out of my schedule just to learn stupid leetcode shit that I've not used once in my 3 years career as an engineer, its just stupid.
I got in 2022 and have been employed ever since. I remember watching such videos back then too. Seriously, even if you think you won't get it, you will. Just make a good project, and get some contacts. Hitting the apply button like a 1000 other people isn't going to make you stand out.
@@chavann I will follow up, I talked with an architect in my company, and he said that we are getting 400-500 CVs for a single intern position, and he just takes the top 100, and doesn't have time to read all of them, cause it would take too much time. The best way is to make contacts with people who already have a job, and get a referral, that is the new meta. I am Polish in a Polish company btw, so maybe it's better a bit in the US.
Good video, the value of pseudocode :) Some of these companies have 3+ interviews is honestly garbage for new people in the industry unless it's more mega bucks. I'd prefer someone who has actually built something, contributed or messed around in a lab compared to just grinding out leetcode that they will never even use outside of an interview. A big part of the job is communicating technical ideas, chat or plans to a non-technical audience and leetcode doesn't prepare anyone for that. As you get experienced it's 2 interviews max or you're just wasting my time.
It depends on the role / company. For smaller companies, hiring for roles with a narrow tech stack, asking candidates to talk about a project they made or contributed to, what their thought process was, if there's anything they'd do differently in retrospect, etc., often reveals a ton more than any other type of interview. When it comes to larger companies though, or companies who are hiring people who are expected to be able to jump across tech stacks and domains, the technical interviews are somewhat justified especially if the compensation matches. The problem is that small startups will put like a web dev candidate through 4 grueling rounds of interviews, where the people conducting the interviews clearly have no business doing so, will ask candidates to solve leetcode problems they will never encounter in their career as a web dev, and will offer compensation under $100K in CA. This is toxic and delusional.
So instead of memorizing the assembly instructions, you must memorize the op codes and convert them to binary manually (or just memorize them in binary in the first place 😅) which is of course architecture specific, not only that but you must learn the spec for the executable format of the target operating system so you can manually construct it, or read the data sheet for a target microprocessor if you are writing bare metal / embedded code. Why not take it a step further and have you mine the minerals (silicon, fosforus, boron, etc) so you can build your own transitors, build logic gates out of those transistors, and your own microprocessor out of those logic gates then design a ISA for it!
just write in assembly, swap out the assembly to binary instructions and values based on CPU architecture, and you're done! (this would be a nightmare lol)
i honestly cant remember more than one language at a time... the deeper I go the more i forget. im sure when i go back to something like python ill pick it up again quickly
Software jobs are insanely competitive nowadays. On the other hand, other fields are fine. I have 10 years in IT support and 3 in IT security and I get offers every now and then on LinkedIn from recruiters. Didn't like those so I applied to 2 different jobs in the past weeks in IT security and got a call both times, interviewing next week.
My last super interview was for a project management role. They gave me 15 minutes and told me to make a kick-off call with full sized 1 hour presentation for an imaginary client that need an AI application. Im pretty experienced guy and made a lot of kick-off calls, but how the hell i was able to prepare everything from my imagination for 15 minutes LoL
One of my friends went for one of these jobs circa 2010. The interviewer just barked at him "2 to the power 23" (which my friend knew if he had about 10 seconds to think about it, we all did C/C++ and bit-twiddling). My friend hesitated, the interviewer cut off the call. FUN TIMES
Could always join the singularity group that offers free plant based food and accommodation while volunteering on projects to do good in the world. They working on stuff like a mobile game, ai, etc.
i just interviewed as a qa intern and they asked me to build my own linked list class, reverse it, push it into a stack class (again, built myself), and then pop every 2nd, 3rd, 2nd, 3rd and so on. Oh and all of this in 15 minutes or less. No question about qa testing was asked. I mean i did it but it was insanity
i get rejected for an intership in a company in my country (Colombia), just because i used python besides Java to solve 4 hackerank medium level excercises, they never said it has to be solved in Java
I went to Developer in Test role and I had to write API first then Automation to test the API and it didnt work out. I DIDNT EVEN APPLY TO THEM. Later competitor firm hired me and they were probably shocked to see my linkedIn update LOL.
"Style this div using sheer quantum mechanic of electron movement between components of the server hardware, can you do this for me or we are done?" "No problem sir just give me a minute, I'll totally do that for you" This is not tech industry, this is service industry
It's wilder these days no doubt. But it wasn't easy 30 years ago either. The only advice I have I don't even know if it's relevant any more: when you find a good group of people stick with them. Most of my career I've worked with a core group of people that tend to move between companies in groups. If a company is going toxic the VP of dev will move to a new company, becoming their VP of dev (or similar title), then a couple more senior folk will wander over, then a few more. Pretty soon we've got pretty much the whole group. We're on our 4th company and it's been a fun and wild ride. But it's retirement time for me, even a good career gets old.
This year, I got a job as a PHP developer with six months of commercial experience (on a different stack) for a new job simply through HR screening, there wasn’t even any technical interview. Sometimes luck happens:)
If they ask you whether you can write machine code you tell then they're looking for a compiler not a developer. Hired on the spot for not trying to bullshit your way through an interview.
LMAO! “We’re done” is a phrase I am not afraid of telling interviewers. I had one once ask me to solve a Sudoko puzzle for him aloud, so he could see my thought process. I’m an Enterprise Technical Architect, so I laughed and said ‘good one’. Then he said, no really, to which I just stopped speaking for a few seconds, watching his facial expressed to determine his seriousness, then said “I think we’re done here; I don’t usually waste my time with puzzles that would never relate to a potential production problem.” …and then I disconnected from the video meeting, called the recruiter and ask him to remove my contact information from their database and forget my email address. 😂
You can tell when the interviewer just feels like every one is a waste of time. The fact that the interviewee here knew what a low level langauge was and that they started typing 0's and 1's was enough for them to be like "you beat everyone else. good job. holy crap someone teachable" A lot of companies are just in that desperate situation where interviews are eating up their entire week for no reason. it do be that way
This man asking you to write Machine Code without even first telling you the cpu architecture you will be writing for and and allowing you to pull up the instruction list and register id mapping, what kind of BS is that, you dodged a bullet on this one, that just an unrealistic expectations
@@randomps2gamer283Don’t doubt the stupidity of corporate. I remember there was a company that wanted 10 years of experience from a code that was invented 4 years ago (I read the article on 2021 and the code was invented at 2017 so there’s still no way to have 10 years on it)
Yeah im thankful I had a normal interview for my job, then again the engineering manager was there and he gave me a challenge that was pretty similar to the work they do in a day to day basis. Not some bs leetcode thing that only works for gatekeepers who have no interest in hiring someone
Hold up, you forgot the part where they accept you for the next few stages, including the on-site, and then they reject you for no given reason at the very last stage!!
I would have made a new list and filled it with the values of the original list, from end to beginning. Then return the new list. I also would have used pseudo code, because quickly being able to come up with a concept is more important than quickly writing runnable code.
C is low level enough that you could know which assembler code you get (if you have appropriate compiler) and you pay no attention which arch is used in this case.
The same idiots who think this is a "programming interview" also work at Apple and Microsoft, which is why basic things like the Bluetooth drivers and the Reminders program don't even work anymore.
I think writing straight out of machine code is impossible. Because don't forget compiler, compiler helps to avoid memory reading miss in pipeline stages by adjusting PC pointer to compile machine code implicitly.
"Please write low Level code". No further information, which architecture which system RIP... you have to invent a general machine code at first which runs on every architecture 😂
@@pilo11 😂but is it possible to make a All-in-One machine code? Every CPU/GPU in the market has different number of pipeline stages. That's why low-level engineers or programming language inventor has to deal with.
I remember interviewing a guy and i felt so bad for him, bro had 0 idea what he was doing. Talking about "lets debug this" and he started writing print statements 😭 When I was getting ready to leave tho i became really lenient 😂
@@PePe-kv2se it is but its not what you want to do in a 45 min multipart interview, you need to complete a minimum number of parts and this guy unfortunately wasted too much time starting and stopping to drop print statements and rerun the code
@@TerszelIn that case I guess it makes sense, but generally it's not like you have access to a debugger or repl when doing a code interview... Throwing print statements to step through execution should take a few seconds max lol
@@PePe-kv2se in our interviews you could use your own IDE and we also provide you with one (with built in debugger) if you dont have one. He really didnt know what he was doing and the problems he was having was not stuff he could fix just staring at the print statements. He was clueless to the execution of his own code, even tried giving him some hints. Seems he went in with hammer and thought the problem was a nail
@@Vishal-jq3fp Still interviewing, I got to talk to some pretty cool people for those mid interviews but there was no way I would get those anyway with my current experience. Still, there's a lot of job offers compared to last year so I'm hopeful, btw I'm not talking about USA/UK job market.
Software engineering jobs have turned into Database Administrator, Business Analyst, Project Manager, AI Prompter, Cloud Engineer and Technical Writer all in one. The reason the salary is so good you're doing 6+ jobs all in one and then some. Plus dealing with Karens all day.
I remember taking a module called Computer Systems & Architecture in my first year of studying for a BSc Honours in Computer Science at university. In this module, we did lab exercises in class where we solved problems and wrote code in assembly language, specifically for the Motorola 68000 chipset. I recall telling my lecturer how much I enjoyed learning assembly language coding. I said, "Assembly language is awesome! I'm really enjoying learning how to write code in this!" His response was, "Anyone still coding in assembly language in 2003 should be shot!" 😂 Sub'd
