QA Automation Engineer

Role Overview

• Role: QA Engineer II / Mid-Level QA Automation Engineer
• Primary Focus: QA automation with an emphasis on Selenium, Java, and Adobe Tags/Tag Manager
• Contract Duration: Expected to run through the end of next year, with potential for continued opportunities depending on performance and business needs.
• Urgency: High priority. The team is targeting a candidate as soon as possible due to an upcoming fieldglasss cutover and hiring/funding timelines.
• Interview Process: One interview round with the engineering team.
• Onsite Requirement: Candidates are expected to work onsite in Phoenix Monday–Wednesday.

Primary Skills / Must-Haves

QA Automation

• Strong QA engineering background with hands-on automation testing experience.
• Strong Selenium experience is important.
• Candidate should be a solid QA engineer first.
• Experience level should generally be around 5–10 years, with a preference toward approximately 5–7 years.
• The hiring manager is specifically targeting a mid-level engineer, rather than a highly senior/10–20+ year QA professional.

Java

• Java is a core requirement.
• The team's APIs are primarily built in Java, so candidates need enough Java knowledge to understand and test the APIs/services.

Adobe Tags / Tag Manager

• The most important Adobe-related skill is Adobe Tags / Tag Manager.
• Candidates do not need to be Adobe experts.
• Hands-on experience is preferred, but exposure/familiarity is acceptable if the candidate demonstrates the ability and willingness to learn.
• The product is heavily related to tags and tracking user data for marketing purposes.

Preferred / Domain Experience

Adobe / Digital Experience

The hiring manager is particularly interested in candidates with exposure to:

• Adobe Tags / Tag Manager
• Digital tracking
• User-data tracking
• Marketing technology
• Digital experience platforms

Other Adobe technologies are beneficial but are not the primary focus.

Privacy & Compliance

Candidates should have at least a high-level understanding of:

• Privacy regulations
• Compliance
• Consent management
• Cookie preferences
• Cookie policies
• Customer data handling
• CCPA/CPRA and similar regulations

The hiring manager clarified that this knowledge does not need to be highly technical. Candidates should understand why these requirements exist and how they impact digital tracking and QA.

Industry Background

• Financial services experience is strongly preferred.
• The team operates in a highly regulated environment, and the company now has additional regulatory requirements associated with its banking operations.
• Candidates coming from finance/banking or another highly regulated environment may have an advantage because they are more likely to understand privacy, compliance, and customer-data requirements.
• Candidates from other industries can still be considered if they have strong QA skills and demonstrate an ability and willingness to learn the regulatory/domain requirements.

Ideal Candidate Profile

The ideal candidate is:

• Mid-level QA Automation Engineer
• Strong in Selenium
• Strong in Java
• Comfortable testing APIs
• Experienced with automation
• Familiar with Adobe Tags/Tag Manager
• Has some exposure to privacy/compliance/consent management
• Ideally comes from financial services or another regulated industry
• Willing and motivated to learn a new product/domain
• Able to ramp up quickly

The hiring manager emphasized learning agility and enthusiasm. They are looking for someone who wants to grow and learn the new product rather than someone who is simply relying on extensive years of experience.

Flexibility on Adobe Experience

The Adobe experience is a preferred skill rather than an absolute requirement.

The hiring manager is open to:

Strong QA + Selenium + Java candidate who does not have Adobe experience but is capable and willing to learn Adobe Tags/Tag Manager.

However, the candidate must already be a strong QA engineer. The team does not have the time to train someone from the ground up on QA.

Why the Adobe/Tagging Experience Matters

The team is currently moving from an in-house application toward an external application/product.

Because the future product is expected to be closely related to the team's current work around digital tracking and tags, the hiring manager wants someone who already understands, or can quickly learn:

• Adobe Tags
• Tag management
• User tracking
• Marketing-related tracking
• Privacy/consent considerations

This experience will help the team roadmap and support the product going into next year.