I interviewed 17 senior engineers in 18 weeks – 7 just in April.
What do you wanna know? ama
#seniormindset
What do you wanna know? ama
#seniormindset
Most folks who thought they were senior evaluated at mid-level.
You’d trust them to write good code, but not to design solutions and component interfaces from scratch.
You’d trust them to write good code, but not to design solutions and component interfaces from scratch.
https://twitter.com/karnik_honza/status/1390330549064110082
My part of the interview is typically the React pair programming challenge. Feels like real world coding, shows how you approach a user story.
Best part is all the conversation it unlocks when you ask “Why’d you do it that way?”
Best part is all the conversation it unlocks when you ask “Why’d you do it that way?”
https://twitter.com/alex__luong/status/1390333441644777474
5 to 10 years of experience seems typical for senior candidates.
The ones who struggle most have 1 year of experience 10 times or a background in BigTech.
The ones who struggle most have 1 year of experience 10 times or a background in BigTech.
https://twitter.com/sultanB17/status/1390336812879687684
We have a couple pair coding challenges. Usually involves adding a new feature to existing code, reading an API doc, some googling.
Small feature you can build in 45min. If you read the full story in advance you can do it in 30min
Small feature you can build in 45min. If you read the full story in advance you can do it in 30min
https://twitter.com/alex__luong/status/1390352783073714186
I’m not personally involved in sending rejections and offers but our recruiting team is top notch and I doubt we leave anyone hanging.
We care a lot about creating a pleasant experience and positive environment as a culture
We care a lot about creating a pleasant experience and positive environment as a culture
https://twitter.com/capajj/status/1390354376733102080
Typical interview process is:
- recruiter chat
- 1h soft tech chat
- 1h technical screen
- 5 onsite interviews
Soft tech verifies you can talk about code, tech screen shows you can code. On-site is for culture, pair programming, and system design
- recruiter chat
- 1h soft tech chat
- 1h technical screen
- 5 onsite interviews
Soft tech verifies you can talk about code, tech screen shows you can code. On-site is for culture, pair programming, and system design
https://twitter.com/AndrejFodor/status/1390350626173988864
Job hopping doesn’t hurt you as much as getting stuck maintaining a unchanging system or working in a widget factory.
Typical failure mode is to become a growth or sales engineer. Many devrels fall into this trap too.
Typical failure mode is to become a growth or sales engineer. Many devrels fall into this trap too.
https://twitter.com/robcrock/status/1390366646863290368
Yep still hiring. We’re hoping to double the size of engineering this year.
And we’re starting to look for mid-level too. First juniors in Q4 maybe
👉 asktia.com/careers
And we’re starting to look for mid-level too. First juniors in Q4 maybe
👉 asktia.com/careers
https://twitter.com/Chad_R_Stewart/status/1390371167219982341
Meeting with 4 to 5 people over the course of a day is pretty typical for on-site. Hard to assess everything in 1 interview.
You show off your coding skills, system design skills, and chat about past experience. The last step is a sell from the founders
You show off your coding skills, system design skills, and chat about past experience. The last step is a sell from the founders
https://twitter.com/dutchmvp/status/1390386757741469696
You often get a feel for the candidate in the first 5 minutes. You have to ignore this feeling, it's wrong and full of bias.
Interviews are long so everyone gets a chance to shine. Even if they're nervous at first
Talking to 5+ folks helps with bias too
Interviews are long so everyone gets a chance to shine. Even if they're nervous at first
Talking to 5+ folks helps with bias too
https://twitter.com/MartinHN/status/1390355846861836292
My favorite answer to a question was “I haven’t done that before so any answer I can guess right now is bullshit, I’d have to research X, Y, and Z first”
We were talking about hypothetical scaling scenarios
We were talking about hypothetical scaling scenarios
https://twitter.com/vfdes/status/1390401444667281410
Best question you can ask a senior candidate is “Why did you solve it like that?”
Seniors have a reason, even if you disagree
Mid-level can’t explain or back up their choices
Can be as mundane as return null vs []
Seniors have a reason, even if you disagree
Mid-level can’t explain or back up their choices
Can be as mundane as return null vs []
https://twitter.com/SloanCam/status/1390420527429337093
Biggest surprise in interviewing seniors was how many of them have no idea how to build stuff.
They're so used to working in mature codebases they forget JS event bubbling, HTML form behavior, how to design a database schema, or make a tech decision
They're so used to working in mature codebases they forget JS event bubbling, HTML form behavior, how to design a database schema, or make a tech decision
https://twitter.com/TitPetric/status/1390367705526636544
• • •
Missing some Tweet in this thread? You can try to
force a refresh
