Hiring SDETs at TestVagrant

Source: https://www.google.com

“What would be my responsibilities once I join?”

“What technologies your organisation work on?”

“How many rounds would I have to go through during my recruitment process?”

Sounds familiar, isn’t it?

For talent acquisition folks and interview panellists, these questions are an everyday affair. Aspiring candidates have a lot of curiosity around the offered role, the time it would take to get through the recruitment process, skillset requirement, and post-selection responsibilities. The nerves get high with a black-box built around these curiosities and it gets tough for the right people to meet the right companies.

Keep calm & get hired at TestVagrant!

TestVagrant(aka TV) believes in keeping its recruitment process transparent and candidate-friendly. We understand that it takes a good amount of commitment & time for the candidates to go through the recruitment process and we want it to be as open and informative as it can be.

We bring to you this blog that intends to answer the big question—“What it takes to join the engineering team at TestVagrant”.

Minimum Requirements

So, when you apply at the TV, be watchful of certain minimum requirements we have for our SDET roles:

1. Extensive experience in testing & automation at any of the product layers, i.e. Web, Mobile or API (as we move up the SDET ladder, versatility plays a vital role)
2. Good experience with handling testing work within a microservices architecture
3. Strong object-oriented programming fundamentals
4. Expertise in source control management
5. Very good consulting skills (focussed on attributes like communication, assertiveness, project driving capability, vision etc.)
6. Experience of working in an agile workplace

Responsibilities of an SDET

At TestVagrant, we strive for excellence in providing effective testing and automation strategies to our clients while contributing to their success and growth. Our SDETs are champions at test consulting, problem-solving, test life cycle management, developing automated test solutions, and decision making. As part of the engineering team at TestVagrant, you get an opportunity to:

1. Learn and experiment with latest and upcoming testing tools & practices
2. Demonstrate high standards of programming skills to solve interesting test automation challenges at various levels of the testing pyramid
3. Work in collaboration with application developers to implement & test cutting edge technologies for delivering a world-class product
4. Do thorough test consulting for our clients to improve their testing efficiency and speed of development
5. Embrace core agile principles for achieving continuous progress and delivering incremental value
6. Contribute as a key player in cross-functional teams¹
7. Build scalable test automation frameworks from ground-up²

Technology Focus at TestVagrant

TestVagrant encourages test engineers to be self-motivated and change drivers. The passion of consistently growing and going beyond expectations keep our SDETs ahead of their industry peers. Based on requirements from our clients & prevalent industry standards, you work on following tools & technologies:

1. Variety of programming languages like Java, C#, Javascript, Python (language is no bar in terms of hiring for TV — grasp on any 1 object-oriented language is good enough)
2. Postman, Rest Assured, OkHttp or similar RESTFul/GraphQL/gRPC clients for API testing & automation
3. TestNG, JUnit, Mocha or similar testing frameworks
4. Gradle, Maven or similar build tools
5. Git for source control management
6. Gitlab, Jenkins, Bamboo or similar CI infrastructure
7. Wiremock, Mockito or similar Mocking techniques
8. Appium, Espresso or similar mobile automation tools
9. Selenium, Cypress, WebDriver IO or similar web automation tools
10. Docker, Kubernetes or similar containerisation & orchestration technologies

Additionally, you also get opportunities to get involved in:

• Non-functional testing based on product requirements
• Test Planning
• Exploring tools that improve testing efficiency over time
• Identifying potential risks and loopholes in the existing delivery process
• Implementing strategies for constantly boosting the testing turnaround time

Hiring Process

Step 1: Screening of the profiles based on our minimum requirements

Step 2: Reaching out to candidates and sharing a time-bound coding assignment with them

Step 3: Evaluation of the submitted assignment

Step 4: If the candidate passed step 3, we schedule a technical interview round³

Step 5: If the candidate passed step 4, we set up a final discussion round to talk more about expectations, testing abilities and prospective growth

Step 6: Hire!

Conclusion

TestVagrant is growing leaps and bounds with every new client we work with and every new engineer that joins us. We have a never-ending appetite to become thought leaders in the testing space and continue providing intelligent test solutions. We aim to extend our strong community of QA engineers willing to make an impact and contribute to our vision.

WE ARE HIRING!!!

If you’re interested in joining us, please send an email with your updated profile at careers@testvagrant.com

Notes:

[1] Role in a cross-functional team would include

*. Building & maintaining the quality-first culture

*. Managing test artefacts & making them useful assets for the team

*. Taking product & release ownerships

*. Making effective use of test automation on delivery pipelines

*. Assisting Product Managers in creating comprehensive stories for the team

*. Managing test cycles through project management tools

[2] Frameworks shall follow principles like

*. High readability & maintainability

*. Layered & data-driven architectures

*. Support for CI execution

*. Rich reporting mechanism

*. Minimum boilerplate coding

*. Minimum possible test execution time

[3] Focus areas during a technical interview

*. Code pairing for the assignment submission

*. Questions around programming knowledge, language structs, logic building & problem-solving

*. Discussion around technical know-how of the current project

*. Discussion around the expertise level of the candidate w.r.t. test automation tools they have worked on