12 ago
|
Sailpoint
|
México
SailPoint is the leader in identity security for the cloud enterprise. Our identity security solutions secure and enable thousands of companies worldwide, giving our customers unmatched visibility into the entirety of their digital workforce, ensuring workers have the right access to do their job - no more, no less.
SailPoint is seeking a QA Engineer to remotely join our team in Mexico.
The QA Engineer is responsible for:
- Characterizing the technical quality of the SailPoint product.- Development, maintenance, and execution of tests and test harnesses- Creating detailed, comprehensive and well-structured test plans and test cases- Estimating, prioritizing, planning, and coordinating testing activities- Debug and solve the configuration problem in product environment.- Hands-on experience with automated testing tools- Planning and executing functional, regression and system level tests-
- Working & following Scrum / Agile software development methods- Work experience:
- 2 to 4 years of professional experience creating and executing test plans and test cases- Experience with both manual and automated testing- Experience with Java and / or GoLang- Experience with AWS or other cloud environment- Should have hands on experience on Windows, UNIX/LINUX OS- Experience working with SaaS products- Skills in reviewing technical documentation for accuracy and thoroughness- Should have assertive, analytical yet practical approach- Experience with Security testing is plus- Experience working with distributed team with regular interactions- Excellent written and verbal communications skills- Detail oriented with strong organizational skills and able to work independently on multiple tasks under mínimal supervision- Should have good diagnostic skills.- Should be able to adjust working schedule when necessary to communicate and work with SailPoint offices in US.
Preferred:
- Experience working with Karate Tests or Neuman Tests- Experience with Cypress, Jasmine, or Selenium is a plus- Familiarity with following technologies:
- Software-based testing (including unit testing, _automation_, performance testing)- Server virtualization
Education:
- University degree a Computer Sciences or equivalent professional experience- Good to have diploma in software testing
The first week you will:
- Attend new hire orientation day, typically the new employee's entire first day.- Obtain any desired supplies, get monitors setup, be able to login to laptop and connect to VPN.- Ensure access to Slack.- Confirm that you have access to Outlook. Accept any meeting invites in your Inbox. In your Calendar, add the Shared #IDN-Team-Calendar team calendar where we document absences.- Familiarize yourself with the look-and-feel of Toolbox, a collection of apps and tools used by SaaS devs and testers.- Register for the online class Introduction to Identity Security with SailPoint and watch it.- For SDET: Refer to Saas Engineering Developer Onboarding Guide and setup your environment as needed- Review the contents in ISC Product Quality.- Review the policy and procedure documents
In the first 30 days you will:
- Have created your own IDN test org (tenant). Using Toolbox’s Org _Data_ Service may be the easiest route. This will add basic _data_ you need to begin using IDN functionality.- Perform some basic exercises in your new tenant. This includes things like adding a virtual appliance, adding sources and aggregating _data_, add identity profiles to create identities,
inviting and registering users, etc.- Understand these concepts: Authoritative Source, Aggregation, Correlation- Learn something about each of the purchasable features e.g. Password Management (training refers to them as Modules), such that you can at least define what they're for. Learn how to know which if these exist in an org.- Have attended weekly team meetings.
In the first 60 days you will:
- Understand these concepts: APIs and REST, microservices, _Kafka_, queues, scheduling, feature flags, database migrations, rollbacks (note: we will not be conducting the rollbacks).- Review the pages in General Testing Tips and Info: General Testing Tips and Info Star this folder of sorts in Confluence for future reference. Below are a couple docs in that folder that are a good place to start.- Review what to include in a test brainstorm- Review what to include in a test plan- Have sat with someone and talked about how they actually perform testing.- Have been introduced to the Support team and the Triage team.- Get familiar with using XRay. XRay should be used to create Test Plans and Test Cases.- SDET: by end of 60 days, ensure you can use Kibana to see the log of the e2e test executed- SDET: by end of 60 days, know which e2e tests belong to their scrum team
In the first 90 days you will:
- Have single-handedly completed a test brainstorming exercise. This can be done in confluence doc. Have it reviewed, naturally.- Take the output of a test brainstorm (someone else's is fine) and
📌 QA Engineer (Remote) (México)
🏢 Sailpoint
📍 México