AI Developer (Automation Tester with Selenium, Python, and AI Experience)

DivIHN Integration

RemoteFull-timeMidPosted Jun 23, 2026

SeleniumPyTestPythonAzureCI/CD

Best fit for

This role is best for mid-level QA engineers with hands-on experience in Selenium, Robot Framework, Azure, Python who want a remote role.

Skills you need for this role

Detected from the job title, description, and tags.

Automation skills

Selenium — Still the most-asked browser automation framework in QA interviews and legacy suites.
Robot Framework — Keyword-driven testing framework common in enterprise QA teams.

CI/CD and DevOps

Azure — Common in enterprise / Microsoft-shop QA roles.

Programming languages

Python — Popular for API testing, data validation, and Playwright/Pytest suites.

Domain & process

AI in testing — Employers increasingly ask how you use AI copilots to speed up QA work.

Job description

AI Developer (Automation Tester with Selenium, Python, and AI Experience) Location: Washington, DC (primarily remote with potential interview requirements) Duration: 6 Months Only W2 candidates are eligible for this position. Description: This is not a traditional AI Engineer role, client is primarily looking for a strong Automation Engineer/SDET who has experience leveraging AI tools and LLMs to improve testing and automation processes. Task Overview

Design and develop test automation scripts using Selenium with Python, leveraging available AI models and LLMs to accelerate script creation, maintenance, and self-healing.
Build solutions using Visual Studio Code, Python, and related technologies to harness generative AI and LLMs (e.g., GitHub Copilot, Databricks).
Integrate the existing Python test automation framework with AI-based solutions to improve coverage, reliability, and efficiency.
Ensure all AI scripts and programs are fully executable on postal-issued laptops within approved security and environment constraints.
Train designated team members to execute, troubleshoot, and maintain the AI scripts and programs.
Develop comprehensive training materials and documentation to support knowledge transfer and long-term maintenance. Required Skills:
Selenium Automation Testing
Python Development
Test Automation Framework Development
Visual Studio Code
AI / Generative AI Experience
GitHub Copilot and/or Databricks experience
Experience integrating AI capabilities into automation solutions
Strong documentation and knowledge transfer skills Preferred Experience:
OpenAI or Azure OpenAI
LLMs and Prompt Engineering
AI-assisted test automation
Self-healing automation frameworks
API testing
CI/CD automation
PyTest, Robot Framework, or similar tools Required Experience: Minimum 2–3 years of specialized AI development experience in technology or software development using Visual Studio Code, Python, Selenium, Databricks, Co-pilot etc. Educational Requirements: A degree from an accredited college or university in a relevant field is preferred.

Job highlights

•Role: AI Developer (Automation Tester with Selenium, Python, and AI Experience)
•Company: DivIHN Integration
•Location: Remote
•Type: Full-time
•Experience: Mid
•Seniority: Mid
•Posted: Jun 23, 2026

Key skills: Selenium · PyTest · Python · Azure · CI/CD

How to prepare for this interview

A 5-step prep plan tailored to this job's stack.

1Revise Selenium deeply — locator strategy, waits, parallelisation, and how you'd structure the framework from scratch. Selenium interview Q&A →
2Read through the general QA/SDET interview prep guide to refresh core testing concepts. Job Interview Prep →
3Do at least one AI mock interview end-to-end so you're comfortable narrating your answers under time. AI Mock Interview →
4Run your CV through the ATS review so it clears keyword filters for this role before you apply. Resume ATS Review →

Likely interview questions for this role

Tuned to the stack we detected on this job.

Q1.Explain the Page Object Model and how you'd structure it in Selenium.
Q2.How do you handle dynamic waits without using Thread.sleep in Selenium?
Q3.Where do you use AI in your day-to-day QA workflow, and where do you avoid it?
Q4.Walk me through a bug you found that shipped anyway — how did you handle it?
Q5.How do you decide what to automate vs test manually for a new feature?