An Engineering Manager Challenge
- Ted Neward tl;dr: Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"featured in #567
Salary Expectations Questions - How Should You Answer Them?
- Josh Doody tl;dr: “Your salary expectations are one of the few things you know that the company doesn’t. That makes them extremely valuable and sharing them can make your salary negotiations very difficult and even cost you a lot of money.”featured in #565
featured in #549
How SQL Query Works? SQL Query Execution Order For Tech Interview
tl;dr: “While SQL queries are written in a declarative, human-readable format, there is a complex process that occurs behind the scenes to execute these queries and retrieve the desired results. In this article, we'll delve into the inner workings of SQL queries, breaking down the process step by step.”featured in #529
An Engineering Manager Challenge
- Ted Neward tl;dr: Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"featured in #518
An Engineering Manager Challenge
- Ted Neward tl;dr: Ted shares his answer to the following interview question: "You're the tech lead and your team is getting stretched thin. You decide to add resources but you can afford 1 senior full-stack developer or 2 junior full-stack devs. Which do you choose and why?"featured in #517
How Hard Is It To Cheat In Technical Interviews With ChatGPT? We Ran An Experiment
- Michael Mroczka tl;dr: "Does ChatGPT make it easy to cheat in technical interviews? To find out, we ran an experiment where we instructed interviewees on our platform to use ChatGPT in their interviews, unbeknownst to their interviewers. The results were surprising, but as a preview, know this: companies need to change the types of interview questions they are asking — immediately."featured in #485
My Approach To Coding Interviews: Optimize For Iteration
tl;dr: “I didn’t encounter this question in an interview personally. I’ll be pretending to go through a ~60 minute interview with an imaginary interviewer. And what you will read here is how I would tackle this question and how I predict the interview would go, informed by my experience in interviews. While reading all of this, it’s important to remember that the most important part of an interview is communication. Keep your interviewer in the loop! Not only tell them what you are currently doing, but also what you are working towards. Think out loud and describe what your ideas are and how you plan to implement them. Most interviewers want to help and will reinforce good ideas and try and prevent you from going down the wrong path. A coder that can’t articulate what they are doing is likely not going to do well in a team environment.”featured in #449
How To Sabotage Your Salary Negotiations Efforts Before You Even Start
- Aline Lerner tl;dr: Common mistakes people make during salary negotiations, focusing on two key errors: revealing information too early and negotiating before being ready. Aline emphasizes that recruiters are not your friends; they work for the company and are incentivized differently. Revealing information like your current salary, expectations, or other job interviews can be used against you. The article advises being in "passive information gathering" mode during interactions with recruiters. It also stresses the importance of timing in negotiations. “Only when you have all the necessary information should you begin to negotiate.”featured in #444
featured in #412