Hi Team,
Please find the below Requirement.
Title - Software Testing Engineer - QA Engineer
Location - 250 E 500 S, Salt Lake City, Utah 84111 (Remote)
Note: Look for nearby Candidate within 50 to 60 miles from client location as the role requires once a month onsite)
Experience : 10 + years
Interview Mode: Web Cam
Must Have: .NET , Devops, Cloud experience is a plus
Summary:
The Utah State Board of Education (USBE) is seeking strong Software Testing Engineers to work on a new event driven microservices designed system which will impact every student and teacher in Utah. We are looking for highly motivated individuals experienced in secure coding practices, Test Driven Development, Domain Driven Design, event-driven microservices design, and with the ability to incorporate/integrate data visualization capabilities into web applications.
The Ideal Candidate:
The ideal candidate for this position has experience in Azure, Playwright, Selenium and SpecFlow, with advanced knowledge of event-driven microservices testing and containerization. They are an Automation Engineer with a passion for testing automation, failing fast, and making peoples' lives easier. They enjoy both philosophical discussions and deploying frameworks and are keen to experiment.
Principal Duties:
As a Software Testing Engineer, your responsibilities will include:
Develops and maintains automated integration test libraries to support the continuous integration pipeline this involves testing multiple event-driven microservices in containers with your knowledge of Git, Docker, Kubernetes, Selenium C#, SpecFlow, and Azure.
Collaborates with development and business to implement data-driven test strategies based on engineering and product goals.
Develops and maintains metrics and measures of testing performance, coverage, and efficacy.
Creates or consults on verification and validation of test plans, test reports, and matrices to incorporate the automated tests and then reviews with relevant stakeholders.
Develops and continuously improves a robust test automation framework which covers the needs of the domain.
Designs and tests quality measures and standards for new applications through development/product lifecycles which are engineered to enhance user experience.
Identifies and develops creative solutions to problems within the team domain.
Understands data collections and data flow and when and where to test within the pipeline.
Works within a cross-functional team to deliver on a common goal.
Other duties as assigned.
Requirements:
1. Degree Candidate must possess a bachelor's degree from an accredited college in Computer Science, Information Technology, Business, but may substitute equivalent experience.
2. Functional Experience Candidates must have 5+ years of QA automation experience.
3. Functional Experience Candidates must have 3+ years of development experience with C#, and .net technologies.
4. Functional Experience Candidates must have 3+ years' experience with Selenium with .Net and C# or Playwright with C#, or RestSharp and Playwright.
5. Functional Experience Candidates must have experience developing and maintaining testing metrics.
6. Functional Experience Candidates must have experience with multiple software testing methodologies.
7. Interpersonal Relationships Candidates must demonstrate the ability to work well with others of all personality types while demonstrating problem-solving and the ability to prioritize tasks.
8. Communication Candidates must demonstrate the ability to communicate in verbal and written form with both technical and non-technical personnel.
9. Initiative Candidates must demonstrate success as a self-starting, hardworking and inquisitive worker.
10. Teamwork Candidates must demonstrate the ability to work with cross-functional teams to deliver on a common goal.
11. Agile/Scrum Candidates must demonstrate experience in an agile product environment to include deep understanding and experience with agile methodologies.
Bonus skills:
12. Certifications Certified Ethical Hacker (CEH), ISTQB, CAST, etc.
13. Development Experience .NET, C#, CSS, Angular, Azure, etc.
14. Experience with container orchestration and building apps in containers.
15. Domain Driven Design Understanding and experience with Domain Driven Design
16. Financial or Education Domain experience
17. Penetration Testing, Security testing, experience with OWASP, etc.
What the USBE agrees to do:
1. The USBE PD Coordinator will direct all work of the vendor.
2. The USBE PD Coordinator will approve and sign weekly timesheets.
3. The USBE PD Coordinator will provide the vendor with an annual evaluation of the vendor's effectiveness in implementing the contract's scope of work.
Resources may have access to sensitive data, including student personally identifiable information (PII). Accordingly, resources must comply with applicable security measures, including possibly mandatory background and security checks. In addition to the terms of State of Utah Contract #IT2462, this engagement shall also be governed by the following terms and conditions regarding student data privacy.
1. GENERAL PROVISIONS:
a. USBE reserves all right, title, and interest, including all intellectual property and proprietary rights, in and to system data, Data, and all related data and content.
b. Contractor is hereby designated as an agent of USBE for the limited purpose of receiving PII to fulfill the purposes of this contract. Contractor may use the PII as provided herein but may not transfer or otherwise convey PII to any other person, persons or entities.
c. Contractor, as USBE's agent, shall comply with all applicable laws and regulations including but not limited to FERPA, the Utah Family Education Rights and Privacy Act, Utah Code 53E-9-2 ("UFERPA"), and the Individuals with Disabilities Educational Act, 30 1400 et seq. and 34 Part 300 ("IDEA").
d. Any terms that by their nature would survive the expiration of, completion, or termination of this Contract shall survive.
e. Contractor shall, upon written request, permit USBE or its designated representatives to perform an assessment, audit, examination, or review of all of Contractor's sites and environments in order to confirm Contractor's compliance with this Contract; associated Contractors or Scopes of Work; and applicable laws and regulations.
f. During the term of this Contract, if USBE requests the Destruction of PII collected, generated or inferred as a result of this Contract, Contractor shall Destroy the information within five (5) calendar days after the date of the request. Contractor shall provide USBE with written confirmation of the date the data was Destroyed.
g. USBE retains the right to use the established operational services to access and retrieve Data stored on Contractor's infrastructure at its sole discretion.
h. The USIMS project is comprised of professionals working in an environment supported by multiple vendors that provide contractor personnel. As a standard of workplace conduct, it is inappropriate for contractors to discuss individual hourly rate or contract rate information in the workplace with anyone other than the USIMS Project Manager or USBE Information Technology Leadership.
2. ACCESS TO DATA:
a. Contractor shall limit access to Data to Authorized Persons only and shall require a non-disclosure agreement be signed by all Authorized Persons prior to being granted access to Data.
b. Contractor shall maintain past and current lists of all Authorized Persons, maintain each non-disclosure agreement, and shall permit inspection of the same by USBE upon request.
c. Contractor shall maintain an audit trail for the duration of this Contract, which reflects the granting and revoking of access privileges to Authorized Persons. A copy of this audit trail may be requested by USBE from Contractor at any time and shall be provided within 10 days of the USBE request.
d. Contractor shall have strong access controls in place. Contractor shall disable and/or immediately delete unused and terminated Authorized Persons' accounts and shall periodically assess account inactivity for potential stale accounts.
e. Contractor shall provide annual, mandatory privacy and security awareness and training for all Authorized Persons, maintain past and current lists of Authorized Persons that have completed training, and permit inspection of the same by USBE upon request.
3. USE AND DISCLOSURE OF DATA:
a. Contractor shall not collect, use, or share Data beyond the purposes set forth as follows:
i. To carry out the Contractor's responsibilities listed in this Statement of Work.
b. Contractor shall share Data only for the purposes stated in Section 48.1 and only with the following entities:
i. Law enforcement agencies or individuals only as authorized by law or court order. Contractor receives such a request, Contractor shall notify USBE within two (2) business days of the receipt of the request, as permitted by law.
ii. Click here to list additional entities.
c. If Contractor seeks to publicly release Data, Contractor must aggregate the Data by totalling the Data and reporting it at the group, cohort, school, school district, region, or state level. Contractor shall, upon request of USBE, provide USBE with a document that lists the steps and methods the Contractor shall use to de-identify the information. Any aggregate data that is publicly released without being redacted using the methods in this section shall be considered an Incident. The following methods shall be used on any aggregated reports:
i. Aggregate data shall be reported publicly only if there is a sufficient number of individuals represented in any demographic or subgroup so that an individual cannot be identified.
ii. Aggregated reports shall be redacted using complementary suppression methods that remove the risk of Data being identifiable using simple mathematics or formulas.
iii. Aggregated reports shall be redacted to remove identifiability risks caused other prior releases of aggregate data by Contractor.
d. Contractor shall not use Data for the purposes of Targeted Advertising except under the following conditions:
i. For adaptive learning or customized student learning purposes.
ii. To market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product.
iii. To use a recommendation engine to recommend to a student (i) content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or (ii) services that relate to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party;
iv. To respond to a student request for information or feedback, if the content of the response is not motivated by payment or other consideration from another party.
v. To use Data to allow or improve operability and functionality of the third-party contractor's internal application.
e. Contractor shall not sell or otherwise monetize Data except Data transferred through the purchase of, merger with, or otherwise acquisition of Contractors provided that all parties remain in compliance with this Contract.