software engineering interviews in 2024 be like

390,369
0
Published 2024-01-21

All Comments (21)
  • Yet to hit my first dsa interview tho I already have a role atm. Earned a sub and good content.
  • @vertxi9934
    bro out here thinking i'm even getting to the interview stage💀
  • @ChimpanzeeUltra
    Entry-Junior level, full stack, $50K/year NET Responsibilities: make ChatGPT 5.0 without any library
  • @quackquack5396
    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.
  • @axiezimmah
    Always start with a 1. If they ask. Just say you trimmed the leading zeroes to save space.
  • @huh5950
    "You failed pretry hard.... but the other candidates failed harder, welcome to the team"
  • @enimal524
    Being a corporate developer is following the dumb request of someone ignorant about code
  • @AndyLin-ov8ey
    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.
  • @Mohamed.U3
    I mean you already lost in C the moment you wrote struct with a capital S.
  • @marianot9652
    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.
  • @PrinceOfOpinion
    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.
  • @axyLms
    The software engineer interviews are really broken, tipically: Interview: Solve problem with data structures, big o notation, algorithmic complexity, etc Job: Center a div
  • @CuriousWithOscar
    I'm lucky if I even get a rejection email lmao now a days they just ghost you
  • @ozzyfromspace
    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.
  • @jason_v12345
    I wouldn't even feel bad in an interview like this. I'd laugh my way out the door.
  • @msanterre
    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.
  • @Zeioth
    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.
  • @jonathanzieg7671
    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.