How my mid-senior level software engineer interviews are going 😅

it’s super important to be able to have strong technical communication skills, I just wish I wasn’t so bad at it 😅 pls brain

System design, architecture is NOT a mid/senior level; writing performant, readable and testable code is. So the problem is not you, but companies that want a principal/architect engineer for the price of a senior.

I like those questions, it's much more representative how you would talk to your colleagues compared to "how to traverse a binary tree"

yeah to also add more context, coding here is talking about frontend lolol or even fullstack with like database modeling or writing api routes not really leetcode. but yeah i mean i just gotta get better at talking is what I'm learning lol

Everyone is like, “Yo you should be better at that,” after you just talked about how you wish you were better at it lol #thanksbro

Lmao yeah I just muted this thread 😅

If you’re applying for a senior engineer position and don’t know what websockets are or server sided events are and what polling is, that means I should be a principle engineer.

@Fred519622 ok fred let's see you get a principal engineer position

So many people in the comments missing that whats usually more important is the one’s ability to learn than retain! A lot of these interviews optimize for remembering things and knowing terms but not how well we understand general ideas and pick up new skills.

If you're using a framework/library but don't know why you're using it, maybe spend another year or 2 as a junior developer. People in mid-senior roles have a substantial input on tooling and should know what's on the market and if its a good fit or not.

I've literally been a mid level engineer at Square and Discord so I think I'm fine 😛