QA Engineer (REMOTE)

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

• Applying solid analytical and problem-solving skills to develop creative & thorough test cases

• Working & following Scrum / Agile software development methods

• Developing detailed test cases from functional requirements, technical specifications and application behavior/constraints, proven ability to develop test plans.

• Advantages – Proven knowledge and experience in the following subjects:

• Familiarity/fluency with commercial security applications/infrastructure products and experience with the monitoring/management/deployment of said products highly desirable.

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 minimal 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 produce a Jira artifact(s) with actual detailed steps. Submit these to the team for review and incorporate feedback.

• Create a XRay Test Plan for a test effort in Jira

• Have performed at least part of the actual story testing for a new or modified feature. Ask questions about anything when you have doubt! Our line of work does not allow guessing.

• Be able to describe in detail all of the purchased features (training calls them Modules). Understand the use cases which cause people to buy them and how to walk through the related workflows in-product.

• Be able to accurately and completely define all indexed object types (Identities, Roles, Access Profiles, Entitlements, Accounts, Events, Account Activity).

• Have a basic understanding of what our sister products do and what differentiates them from IDN. Including: Data Intelligence (IAI), IIQ, FAM, CAM, DAS.

• SDET: by end of 90 days, can review/write e2e tests for their team’s functional area, as well as able to investigate test failures in the build pipeline

After the first year, you will have:

• Yearly trainings as directed by the Cyber Security Team

• Any annual training programs related to this policy and procedure, and not tracked in our LMS system, will be logged in the QMS: Training Log.

SailPoint is an equal opportunity employer and we welcome everyone to our team.  All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or veteran status.