I've been appointed lately to a "Test automation team technical lead" position. This is my first leading role. I have automation experience.

The team has 4 QA engineers, most of them has basic Java and Python knowledge and experience.

The team need to automate tests for a micro-services based solution. There should be both browser and REST tests. They already have a starter project, based on Selenium, Cucumber and more tools and solutions.

I have first meeting with them next week.

How would you prepare for that meeting? What would you present and ask in the meeting? What should be my goals?


New contributor
dushkin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

put on hold as too broad by João Farias, Nitin Rastogi, Milin Patel, Bharat Mane, dzieciou Jun 12 at 17:32

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    As I said, I have automation and development experience in contrast to the team members – dushkin Jun 11 at 14:46
  • 1
    That really depends on the project, on the team. Are you new to the project? Is the rest of the team new to the project? Do they have more domain knowledge or knowledge about the project? Who they are? How do you understand technical leading in a project? Will you be a proxy between your team or other stakeholders? How do you want to organize the work? What are the expectations of your team? What skills the project requires? What skills your team has? Do you have a test plan or you want to involve your team in planning as well? First meeting is to get to know each other. – dzieciou Jun 11 at 14:54
  • 1
    Read similar questions on QA leads: sqa.stackexchange.com/questions/6454/tips-for-qa-lead – dzieciou Jun 11 at 15:07
  • 1
    I'd probably take a portion of the meeting to talk about the way the team will follow best practices and make decisions on issues that come up. And when there isn't consensus, following the principal of disagree and commit (amazon). Take some time to make it clear and discuss what people's role and expectations are including your own. – mrfreester Jun 11 at 16:01
  • 2
    Needs assessment and inventory - Figure out what they're doing/what exists now, and where they think they want to be in 3 months, a year, etc. After that, figure out what seems reasonable, what the skills are, and how the team can get to the future . . . – ernie Jun 11 at 17:40