I FINALLY DID IT!! I landed a job!! I'm going to be a firmware engineer!! Woohoo!! 😁
It only took half a year, but I finally got one, and purely off my own merit. It feels damn good when you get the job with no references or connections, just your own skills.
After a highly successful on-site technical/whiteboard interview, I was 90% confident I'd get it. The fact that my job search is finally over, is such a fucking relief. Good riddance to endless interview prep, applications & rejections.
I start on Monday. Goodbye freedom >.<

No crazy prep, ever.

I always go in with a 'this is me, these are my skills, that's all you're going to get' mindset.

I of course do some research (about the company, their culture, technologies and stuff like that) but I find it kinda weird to spend a big amount of time on interview prep when there is a chance of rejection. (personal opinion)

Software engineers: "Maths is hard and scary!"

Also software engineers: "I've learnt to write a balanced binary search tree in c++ as interview prep!"

Mathematicians: "Have you guys heard of an AVL tree?"

Craziest prep for an interview?

Way back when I interviewed devs, I prepped a bank of Simpsons and Star Trek trivia questions if the candidate answered one of the softball questions ("What are your hobbies?", etc ) that related to either subject. On rare occasion a candidate claimed to be a big trekkie so I asked..

<Deep Space Nine was in it's 5th season>
Me: "What was the name of Captain Sisko's ship?"
C: "Sisko? Was he from the original series?"
Me: "No, Deep Space Nine"
<awkward silence>
C: "Is that the new series?"
Me: "Not really, but lets do an original series question. What does the middle initial 'T' stand for in James T Kirk?"
<awkward silence>
C: "I have no idea. I don't think it stands for anything."

He didn't make the cut.

My boss at the time said I should not document any of those questions/answers just in case we are sued for discrimination.

A connection was looking for a developer in the city my brother-in-law recently moved to (for my sister's career), so I connected them. They exchanged a couple of emails, and he has an on-site interview tomorrow!

He and I are both .Net developers, and I'm older/more experienced, so I offered to rearrange my schedule to help him with some interview prep tonight.

He said no, that he's pretty confident about things, that he'll do some studying and research on his own.

Good for him and his confidence, but I'm kinda salty that he didn't take me up on my offer. I'm pretty damn clever. How dare someone reject my offer for assistance?? I hope the interview goes well of course but if it doesn't I'm very much going to feel some silent "I told you so!"

So I'm called down to the office the other day for a meeting, I get there and my boss says "hi this is John Doe he has applied for the developer role, can you give him the technical interview" had no time to prep, my boss didn't even give me a copy of his CV

Still looking for my first full-time dev role. After being endlessly rejected from every dev job I've applied for, it starts to eat away at your confidence. Makes me wonder if I'm not as competent as I believe I am. :/

Fortunately, I landed a coding interview with Google! It is my dream job to work at Google, so the fact that they even acknowledged me & my skillset makes me so happy and reaffirms my belief in my capabilities. :D

It's pretty odd, that after applying to 20+ open Google positions relevant to my skill level & location and often with references included, then having been rejected from all of them, that I finally got a chance with them when one of their recruiters found me on LinkedIn and liked what she saw. I cleared the screening call, and made it to the first coding interview.

Of course, even with all the interview prep I've done, it was all practically for naught since they caught me off guard with a crazy conceptual problem anyway. (Well, actually, was I 'caught off guard' if I was already expecting to be caught off guard? o.0) I struggled heavily in the first half of the interview, but found my footing towards the end. So I knew I screwed up and that it was highly unlikely for me to get the job.

Nonetheless, Google had the decency to reject me not via an automated email, but through an actual direct phone call with my recruiter. (The cruelty of the automated application rejection system in our society is a whole rant of its own, for another time.) My recruiter told me that they felt I wasn't ready but they liked what they saw, so they will be revisiting me in exactly a year to reconsider me.

To know that I wasn't fully rejected, and that my dream company Google sees real potential in me, is highly reassuring. It means I'm not a lost cause; I simply need to keep looking. Google will want me more strongly once I have the experience that comes from a fresh grad's first full-time job.

Got hit up by a FANG recruiter on LinkedIn. Almost went for it, but then I remembered I'd have to spend 3 months prepping for it, since it's been 5 years since I've manually reversed a linked list, back when we did that for funsies in college...

Plus how do you tell your manager you're quitting to "prep" for an interview...and moreover, how do you go back and sheepishly tell them you didn't make it...

Like, that one simple LinkedIn message caused me to re-evaluate my life and seriously consider leaving my comfy job to do something insane like try to work at <insert FANG company here>. And I wasn't going to quit until I had made it.

Working on individual projects is a million times more fun than interview prep / doing Leetcode problems.

I wish companies looked at my few years of experience and personal projects rather than testing my knowledge by asking me some random "Hard level" Leetcode question.

My craziest interview prep was for the role I just started last week. I applied to AWS and forgot about it, a month later I got invited to do a phone interview followed by a 5 hour on-site loop

I had just 4 days to prepare while already working full-time so I basically didn’t do anything after work for those few days other than cramming through over 50 hours of content on ds & algo, linux, networking and scalable system designs.

It helped that I’ve been working as a software engineer for many years so I just needed to review what I already knew

**random rant**

So next week I have a technical interview with TripleByte and I'm supposed to spent the next 2 days sorta preparing. Just woke up and had this thought tho:

What's the point? Yes I think I could try to get a better job but been trying for years (banking tech area) but now it feels like I'm at a "local optimum" sort of a sweet spot. Team/company could be smarter/more efficient but...

I've got my own place in a city that's also near NYC. It takes me 20 minutes to get to my current office, fairly flexible with the 9-5 work day, I can work remotely. I get enough money.

And then finding a new job === technical interviews about stuff you will rarely use and usually with no feedback like a pass-fail test where they only tell you if you pass or fail (and for me it always feels skewed towards fail the moment i walk since I'm deaf).

But at this point, I feel more like "you need to convince me to work for you". In my head, the plan is mostly to just have a nice chat and wing the technical questions just to see how good i am without any prep (i.e. poring thru Cracking the Coding Interview or Big O concepts, sorting...).

I've been doing interview prep for almost two months now (off and on). Doing this course online to better understand algorithms and doing Leetcode problems here and there. Definitely not putting in 6 or even 8 hours a day into studying since I'm working, but fuck I feel so discouraged when I'm not even able to get an "easy" problem.

I really want to get better, and I know it takes a lot of patient and practice when it comes to problems. I try my best to tell myself "you haven't learned this yet" or "you'll get it soon", but in the end I just feel so discouraged that I want to quit practicing for interviews.

I hate that this profession requires people to spend X months or even years studying for an interview. That the 3-5 years of relative and good work experience means nothing more than passing a resume screening to get to a coding interview where they ask you a problem you'll never face in your career at X company.

Do I hate the process because I'm just bad at algorithms I don't use often? Or would I feel like it's just and fair if I understood things easier and were able to land jobs easily because I get all the algorithms?

I just want to be better.

My goal is to study for 300 hours (coding problems, behavioral, and system design combined) before I start applying for companies.

Is this overkill? Is it enough?

I put a "stop" on my studying since I know there will always be a question that's a "got-ya" or some extremely hard Leetcode question that require some obscure algorithm from college that had 1 figure about it.

Is interview preparation and competitive programming the same thing? If they are different which one should one focus on?
🤔🤔🤔

!rant

Interview prep question. My understanding now is, at least in theory is: always use SOLID. I've never really understood it explicitly though I think I follow it a lot in practice, just naturally...

But when I usually program I'm kinda of in between... I don't automatically default to it.

Particularly, I don't always create interfaces, at least not in the first pass unless I know or expect many different implementations of a certain component... Or just because I need some class that does X but haven't quite thought of the implementation.

But I have never created an interface with like only 1 property or method... Kinda feel that's overkill...

I tend to follow DRY more I guess...

What's everyone thoughts on this stuff?

Happy to share that I got my first ever internship offer from Credit Suisse! All the interview prep paid off!

so which company is the new faang among developers? you know, the one where there is a good WLB, nice pay , 5-7 hr work/day and other benefits , but with a high entry barrier?

I am thinking of starting to revise DS/Algo for some interview prep

I have several tasks in my job. Not all of them are straight up dev, some are also student related. Since my coworker left I was rediculously overbudened, simply because the tasks I have to do are sooo far appart from one anothet. After talking to my boss, we get to hire some people to help (big yay!) But now it is upon me to write the recruitment adds so to speak and also talk to the people and interview them. What the heck I have no clue about this whatsoever xD i mean, i kinda feel honoured that my boss trusts me enough to do a pre selection for her. But damn. .-. I'm barely older then the applicants (it's all at uni and I'm a student and so are they)
Anyone got tips for interviews? I dont need them to do dev work. More like working with kids and presentation prep and support.

Never did a prep for before interview when I was the candidate... that's until lately, when I was told I need to interview some candidates. I really had no clue on what to ask...

Craziest prep for interview :

Step 1 : Given sufficient time for the scheduled interview by any company, start by searching "How to prepare for Google interviews". Awe at the information before you and get all pumped up to jump in.

Step 2 : Starting with Algorithms, study each one and try not to mix any of them in confusion. In case you are stuck in whiteboard coding, close your eyes, take deep breath and visualize Don Kunth. If that doesn't help, well you are ruined anyway.

Step 3: Practice coding without internet connection, till you are able to write code while you talk about how the weather is really great today. Libraries and methods should flow like poetry. SO is sin.

Step 4: The X programming language which you added to your resume because you can write Hello World, head over to Wikipedia and read more about it just in case.

Step 5: Read some xkcd comics so you can impress the interviewer with some humor. You can try Dilbert too.

Job Interview Help!

Hi Devs! Applying for a junior front end developer job here and have been called by a recruiter. He's explained he will:

"be asking some technical questions, so it might be worth a quick bit of revision on your JavaScript knowledge and terms!"

Has anyone come across these before and what level of knowledge would I be expected to know for a junior role?

I'm going to do the test either way as it'll be great experience but a bit of prep is always good!

If you're a web developer OR python developer, what are the top 3 concepts you should understand like the back of your hand?

It started when life caught me off guard. It was one of those transition moment when you realized you are no longer a college student and you need to get a job.

I was clueless that time (still clueless - smh) that I didn't prepare my CV nor interviews. I got into panic mode and ask help from career service in my college (I rarely ask for help, and when I did that, I am really desperate).

Long story short, I got a job from the career service's connection. I don't think I did well in both the interview and technical test (of course, no prep or whatsoever, what do you expect?) but seems like we both in need of each other (maybe because my grades when I was in college is good... and maybe because my starting salary is low enough... and maybe because there was no better candidate at that moment) that I get picked.

How many of you have formalized knowledge in computer science theory? Do you find yourself using that knowledge in your daily engineering life? For example, knowing random search algorithms, or obscure data structures. I ask this because of the modern "technical interview" trending towards discrete math instead of actual programming ability. Instead of coding projects I care about or reading research papers, I'm just doing discrete math problems to prep for recruiting. While it's not the worst thing to do I just wish there was a more direct way of interviewing a person's engineering abilities.

My roommate's new cat... Cats already own the internet why must she impend my interview prep for rubs T.T

Was solving algo problems for the last few hours again. It's for technical interview prep but what I realized was...

If I just see them as puzzles rather than a pointless barrier to me getting a better job... they actually become fun...

That and maybe I'm bored at work, need something intellectually challenging/requires thinking, and out of ideas for personal projects I want to build.