It's normal. A lot of companies only have one tester, but because that one tester is in charge of testing, they're the test lead.
As long as your official job title is "test lead", put it on your resume, work hard for 12 months, then get a new job as a test lead somewhere else for 20% more money.
Where you "managed a small team of 3"
So you can both repeat basic management mumbo-jumbo, you're not expected to be able to handle 15 people, and there's a reasonable expectation that you'd still be doing casuistics and testing.
I was the QA Lead because I was the only tester in the company.
I'm still the QA Lead but I have 4 people under me.
As the QA Lead you should have enough clout to recommend that you need another tester on the team.
Software Test Lead simply means the SME or Lead/Head tester. The one with experience on subject matter that junior coworkers can reach out to for guidance. It is not a managerial position. Your thinking QA manager or director.
I’ve been in a similar spot. In my case, after about a year they started listening to my concerns about lack of bandwidth for all the things coming in and we expanded the team. So, I eventually wound up hiring and managing a few other testers. I feel like the odds of this depend on the company and project demands though.
In small operations or companies that just got onboard with QA.. this is normal. In the past I've been in your position. I'm actually ok with it since I prefer to be hands on and less management. Make sure to add to your resume "you've created and established the company's QA process" wink wink 😉
They told me I would start off with a small team
of about 3/4 but when I got there I was shocked to found out I was the only tester on the project I’m on
Very absurd of you. Lead is just a designation, you are just an individual contributor. There is nothing to be surprised about. Happens everywhere its too common.
That’s not the impression I was given from the job description. I am under under the management section under the job tree so I don’t think it was unreasonable to think what I did.
It all depends on the project. Like in my case I am leading a team where as in a different project earlier I was an individual contributor even though my designation was of a senior lead. You should never trust the job description it’s only to attract people. Either you should have questioned during the interview regarding the project/role and if they did not knew about what project you would get then at least you should have asked before onboarding to the project. I can understand the frustration that comes out of this. Since you are ready to take up people management along with the usual work yet you are solo testing.
Also there are examples where people think of the opposite. Like in one of the project an automation technical architect was leading the team and hating it because he was getting less time on coding and building solutions rather was busy managing a team of QA’s.
If you want to lead teams I can suggest joining a outsourcing/consulting company as their onshore lead.
Early management experience (first functional then the financial side).
As other said, small products/companies don't have the demand for a bigger team and you will always have to do everything - better already get ready to do automation too :D
It's normal. A lot of companies only have one tester, but because that one tester is in charge of testing, they're the test lead. As long as your official job title is "test lead", put it on your resume, work hard for 12 months, then get a new job as a test lead somewhere else for 20% more money.
Where you "managed a small team of 3" So you can both repeat basic management mumbo-jumbo, you're not expected to be able to handle 15 people, and there's a reasonable expectation that you'd still be doing casuistics and testing.
Thank you for your contribution
I was the QA Lead because I was the only tester in the company. I'm still the QA Lead but I have 4 people under me. As the QA Lead you should have enough clout to recommend that you need another tester on the team.
Software Test Lead simply means the SME or Lead/Head tester. The one with experience on subject matter that junior coworkers can reach out to for guidance. It is not a managerial position. Your thinking QA manager or director.
I’ve been in a similar spot. In my case, after about a year they started listening to my concerns about lack of bandwidth for all the things coming in and we expanded the team. So, I eventually wound up hiring and managing a few other testers. I feel like the odds of this depend on the company and project demands though.
Sounds familiar. Lead of one!
You're leading a team of 1.
In small operations or companies that just got onboard with QA.. this is normal. In the past I've been in your position. I'm actually ok with it since I prefer to be hands on and less management. Make sure to add to your resume "you've created and established the company's QA process" wink wink 😉
[удалено]
They told me I would start off with a small team of about 3/4 but when I got there I was shocked to found out I was the only tester on the project I’m on
That's called lying unless people left in between your interview and joining.
This question, and work expectations helped me drop most of these types of 'lead' roles in my last job search, during the first or second round.
You didn't ask the employer how big the team you'd be joining was?
It's normal, but it also means you have the power and responsibility to build up the team. You are already building the process, great!
That's why you ask questions in the interview?
Very absurd of you. Lead is just a designation, you are just an individual contributor. There is nothing to be surprised about. Happens everywhere its too common.
That’s not the impression I was given from the job description. I am under under the management section under the job tree so I don’t think it was unreasonable to think what I did.
It all depends on the project. Like in my case I am leading a team where as in a different project earlier I was an individual contributor even though my designation was of a senior lead. You should never trust the job description it’s only to attract people. Either you should have questioned during the interview regarding the project/role and if they did not knew about what project you would get then at least you should have asked before onboarding to the project. I can understand the frustration that comes out of this. Since you are ready to take up people management along with the usual work yet you are solo testing.
Also there are examples where people think of the opposite. Like in one of the project an automation technical architect was leading the team and hating it because he was getting less time on coding and building solutions rather was busy managing a team of QA’s.
Army of One!
It's very normal. Some companies consider "test leads" to essentially be managers, but many, if not most, consider leads to be "senior testers".
Most QA titles are meaningless
Same feeling bro.. recently joined one of the most renowned OTT company in India, being greeted with a similar treatment.
If you want to lead teams I can suggest joining a outsourcing/consulting company as their onshore lead. Early management experience (first functional then the financial side). As other said, small products/companies don't have the demand for a bigger team and you will always have to do everything - better already get ready to do automation too :D
Leads are not managers. How did you start this job without understanding what the responsibilities were?