Software Developer in Test (SDET/QA)

A Software Development Engineer in Test (SDET) at Oblivious is primarily responsible for designing and implementing automated test frameworks, conducting various forms of testing such as integration, regression, and performance tests. Additionally, SDETs will be involved in API testing, exploratory testing, and engaging in security penetration testing. This multifaceted role ensures that our innovative technologies maintain exceptional quality and security standards.

To thrive as a Software Development Engineer in Test at Oblivious, candidates should have strong experience with testing tools like Selenium, Postman, and performance testing tools such as JMeter. Familiarity with AWS services, especially AWS Nitro Enclaves, as well as experience with Kubernetes deployment and management, is crucial. Furthermore, a solid understanding of networking concepts and programming proficiency in languages like Python or Rust would be advantageous.

Oblivious is dedicated to the growth of its team members and provides various opportunities for training and development. Employees benefit from workshops, online courses, and mentorship programs tailored to enhance their technical skills and professional growth in areas like quality assurance, automation, and security practices. We believe that investing in our team contributes to the success of our innovative projects.

As a Software Development Engineer in Test at Oblivious, you will work with a range of testing environments, including Kubernetes clusters and different operating systems like Windows, Linux, and Mac. Your role will require you to perform integration testing across multiple system components and ensure that tools function seamlessly across these various platforms.

Absolutely! At Oblivious, security is a top priority, and the Software Development Engineer in Test role includes engaging in security penetration testing to enhance our privacy-preserving technologies. Your insights will play a critical role in identifying potential security vulnerabilities and fortifying our solutions against threats, making a vital contribution to our mission.

When discussing your experience with automated test frameworks, be specific about the frameworks you've used and the projects where you've implemented them. Highlight any framework customization you performed and how it improved testing efficiency and productivity within the team.

When responding, emphasize your systematic approach to integration testing, such as understanding system requirements, writing comprehensive test cases, and collaborating with development teams to identify potential integration issues. Share a specific example where your testing led to enhanced system performance.

Focus on the tools you are familiar with, such as Postman or other popular choices. Explain your rationale, considering factors like ease of use, team collaboration features, and how those tools fit into the overall testing strategy. Share experiences where these tools helped uncover critical API issues.

Highlight your strategies for conducting regression testing effectively, such as maintaining a thorough test suite, automated test executions, and continuously updating tests to reflect the latest code changes. Mention how communication with development teams aids in identifying which areas need focus during regression testing.

When discussing performance and load testing, outline your experience with tools like JMeter or LoadRunner, explaining how you configure these tools, design scenarios, and analyze results to assess system performance under various loads. Provide insights into how this testing influenced product development decisions.

Talk about your hands-on experience with Kubernetes, detailing how you've managed container orchestration for testing purposes. Mention scenarios where Kubernetes enabled you to test deployments effectively and how you dealt with challenges related to updates or rollbacks.

Share a story about discovering a significant bug during your testing process. Explain the steps you took to replicate the issue, your communication with the development team to resolve it, and the impact this resolution had on the product quality.

When answering, mention resources like tech blogs, forums, webinars, and online courses that help you stay abreast of trends in testing practices. Discuss your commitment to continuous learning and how you apply new practices or tools to your work.

Discuss your approach to exploratory testing, including planning a testing charter to guide your exploration. Share examples of how this method helped uncover issues that scripted tests might have missed, emphasizing your intuition and analytical skills.

In your response, highlight the importance of clear, transparent communication with developers and stakeholders. Discuss how you ensure that your findings are communicated effectively, fostering collaboration while ensuring that quality remains a priority throughout the development process.