One of the worst places for a QA Selenium Automation Engineer to work as a contractor.
Contractors are taken for granted, and a high level of micromanaging exists.
There is no work-life balance, and it can be hard for non-Telugu speaking people to work in the automation team.
There are a few Telugu-speaking full-timers whose only aim is to make the life of contractors hell by squeezing out the best out of them.
Highly unprofessional Team Leads and Managers who are not at all technically qualified for their role.
Please hire managers not merely on the basis of looking at how many years they have spent as a contractor and giving them a full-time position and making them managers. Please hire professional managers who do not make the life of contractors hell.
The current (South Indian) manager who leads the QA Selenium automation team is only interested in receiving her pay cut for each and every contractor on an hourly basis through specific consultancies. I suggest my friends that given an opportunity to work as a QA Automation Engineer (Selenium) in the San Francisco, Wells Fargo team, think again!
There were 3 rounds. Be prepared. The first round was technical questions, followed up with a few behavioral and scenario-based questions. Also, be prepared to talk about why you want the role and what you can provide. They like hearing these things.
It’s just one round of technical round, starting with: Daily activities: * Technical questions related to UI automation with different situations. * Coding with Java. * Agile methodology and responsibility. * Difficulties in daily testing.
Lots of detailed questions, better not to go deep. Overall, a good experience. Tell me about your last project, your role in that project, and of course, your impact on the team and organization.
There were 3 rounds. Be prepared. The first round was technical questions, followed up with a few behavioral and scenario-based questions. Also, be prepared to talk about why you want the role and what you can provide. They like hearing these things.
It’s just one round of technical round, starting with: Daily activities: * Technical questions related to UI automation with different situations. * Coding with Java. * Agile methodology and responsibility. * Difficulties in daily testing.
Lots of detailed questions, better not to go deep. Overall, a good experience. Tell me about your last project, your role in that project, and of course, your impact on the team and organization.