Ask Lemmy

Went in for an in-person prescreening with HR that turned into a surprise panel interview with the tech leadership, which sounds like a good thing, but I'm a severe introvert, so it tilted me to the point that I had a hard time regaining my internal composure.

Conversion was friendly and softball, and whiteboard was a super simple rdbms outer join scenario, but in the moment I couldn't really think straight, so I didn't see any of this.

I'd actually been practicing DSA so one of those problems might have actually been engaging enough to get me to focus.

One time I have applied for a role in one of the big companies. Microsoft/Apple/Google/Amazon like big (for the record, none of the above). The process took almost two months, I had 7 or 8 interviews with various department heads - HR, hardware and software engineers, support. I had to take an IQ test disguised as personality test, one more "soft" test, did the homework assignment based on sent requirements and docs. Now, the role I was applying for was a mix of sysops, devops and sys architect. I would be working with the bare metal. I was so deep in the sys/ops world I failed on fairly simple task. During the final interview I was tasked with a live coding problem - "using the language of your choice, write a program that calculates the fibonacci sequence". I was not prepared for that. Usually I could do this with my eyes closed after a night of heavy drinking but in this case I was so deep in systems architecture I totally blew it. Lesson I learned was to be prepared for most unusual tech questions. Ever since I always prepare for both, dev and ops parts even if it's strictly ops role.

When I was in Uni, we had the opportunity to apply for co-op at Black Berry when they still made phones with their own OS.

I was getting into mobile dev at this time and applied and got an interview.

I didn't know what I was expecting but what I got was a 10-20min sales pitch for their phone and I wasn't asked a question... I don't think. From what I gathered afterwards they just wanted to hire/rehire one guy and had to interview others to be in the co-op program.

Believe it or not I wasn't sold on black berry after that.

At university, a prof for theoretical CS (the kind of professor who thought CS students don't need computers) was looking for someone to program something for him. The requirements really showed that he had no clue about programming. His assistent, sitting beside him, obviously knew that, too.

I basically told that prof that he had no idea what he was talking about, and suggested that he should attend a basic programming course before I left.

I’m actually happy to say I haven’t necessarily had any bad programming related interviews. In fact, as someone with zero professional development experience but a healthy portfolio (side business for former employer, systems built for prior jobs not related to development) I’d say it was almost too easy to finally land a full time development job.