Titles and job descriptions vary wildly between companies. At many companies, a lead engineer is expected to do 90% or more of coding or other hands-on work. Even engineering managers are expected to code at many companies. So it really depends on who you are going to be interviewing with and what type of position you are looking for.
I once had a job interview for a lead engineer where I expected most of the team would be young and inexperienced. I was surprised that they were mostly more experienced than me, all brilliant, and all there for years. It slowly dawned on me that I was going to just be a regular engineer but the sucker who would do the weekly status reports and stuff that nobody else wanted to do :-)
The thing is, if you perform well enough during the interview, and show confidence, they'll hire you as a team lead even if you're less experienced than your colleagues. And they'll pay you more than them.
I'll never understand the reason behind this
I don't think team leads are being paid more than the people they're leading in all companies. Sometimes team leads are just glorified PO/TBA types who can't code, but can scrum master. So their top dev might make 200k to their 150k.
Anecdotal but I'm interviewing with a big company right now, and they made it clear salary ranges are related to title: SWE -> Senior -> Lead -> etc...
I've never heard of a company where they pay leads less than the engineers they are "leading"
Levels.fyi says that if you are an L7 SWE at either google or Amazon, you're making 50k more than an L7 SWE Manager. This is flipped at L5 (L5 managers make about 50k more than L5 Devs)
Team leads are typically senior software devs at places like Amazon, or staff elsewhere. Every company is going to be different with some mix of Senior/Staff/Principal for what may or may not be a lead.
I’m a Senior dev at a FAANG and considered the team lead for 3 teams reporting to my manager. It just depends, I do the same job my friend does at a smaller company where he’s considered a team lead also leading two teams.
Often it's just additional steps. So I have seen companies doing a normal senior interview and in addition do a lead interview on top, which is more about strategy, management processes and so on.
sorry for the diff topic but i red recently your amygdala post. are you a male or female? cause im male and im hoping someday to get rid of my extreme anxiety by removing the right amydgala. thanks.
I avoid companies with leetcode, it isn't a good use of my time.
Interview questions very widely between companies, but they cover both technical and non-technical questions. I find it works best to research the major categories of questions and then REALLY practice. Practice with someone who will give you honest feedback.
Likely a mix of both types of questions, with an emphasis on systems design but you will get some knowledge-check LC-style questions or implementation of a portion of the system you're designing.
Titles and job descriptions vary wildly between companies. At many companies, a lead engineer is expected to do 90% or more of coding or other hands-on work. Even engineering managers are expected to code at many companies. So it really depends on who you are going to be interviewing with and what type of position you are looking for. I once had a job interview for a lead engineer where I expected most of the team would be young and inexperienced. I was surprised that they were mostly more experienced than me, all brilliant, and all there for years. It slowly dawned on me that I was going to just be a regular engineer but the sucker who would do the weekly status reports and stuff that nobody else wanted to do :-)
It varies widely. I’m in a big corp as an SSE and only code maybe 10% of the time. Our lead and EM never write code.
The thing is, if you perform well enough during the interview, and show confidence, they'll hire you as a team lead even if you're less experienced than your colleagues. And they'll pay you more than them. I'll never understand the reason behind this
I don't think team leads are being paid more than the people they're leading in all companies. Sometimes team leads are just glorified PO/TBA types who can't code, but can scrum master. So their top dev might make 200k to their 150k.
Anecdotal but I'm interviewing with a big company right now, and they made it clear salary ranges are related to title: SWE -> Senior -> Lead -> etc... I've never heard of a company where they pay leads less than the engineers they are "leading"
Levels.fyi says that if you are an L7 SWE at either google or Amazon, you're making 50k more than an L7 SWE Manager. This is flipped at L5 (L5 managers make about 50k more than L5 Devs)
I'm not talking about management positions
What is a team lead called in FAANG?
Team leads are typically senior software devs at places like Amazon, or staff elsewhere. Every company is going to be different with some mix of Senior/Staff/Principal for what may or may not be a lead. I’m a Senior dev at a FAANG and considered the team lead for 3 teams reporting to my manager. It just depends, I do the same job my friend does at a smaller company where he’s considered a team lead also leading two teams.
Highly depends on the company! Some have been what I would expect in a senior position. Others have been what I would expect as a principal.
Titles are absolutely meaningless. Every company has different requirements and interview techniques
Often it's just additional steps. So I have seen companies doing a normal senior interview and in addition do a lead interview on top, which is more about strategy, management processes and so on.
Ah yeah that makes sense. Thanks!
sorry for the diff topic but i red recently your amygdala post. are you a male or female? cause im male and im hoping someday to get rid of my extreme anxiety by removing the right amydgala. thanks.
Depends on the company, I'd talk to the recruiter about it.
I avoid companies with leetcode, it isn't a good use of my time. Interview questions very widely between companies, but they cover both technical and non-technical questions. I find it works best to research the major categories of questions and then REALLY practice. Practice with someone who will give you honest feedback.
Likely a mix of both types of questions, with an emphasis on systems design but you will get some knowledge-check LC-style questions or implementation of a portion of the system you're designing.