Skip to main content

PlayStation Global

Software Development Engineer in Test

United States, San Diego, CAcontractmidAdded today

About this role

Sony Interactive Entertainment seeks a Software Development Engineer in Test to join the Client QA team for a 12-month contract role. You'll design and execute comprehensive testing strategies, build automation frameworks, and ensure quality across multiple PlayStation platforms and devices.

What you'll do

  • Analyze product requirements and design documents to develop effective testing strategies
  • Create detailed test plans, write test cases, and execute them to validate feature quality
  • Build and maintain test automation scripts using tools like Selenium or Appium to expand coverage
  • Develop and improve the test automation framework
  • Log, track, and verify defects while monitoring automation job execution
  • Collaborate with infrastructure teams to maintain CI/CD pipelines and provide status reports to leadership

What they're looking for

  • UI automation (Selenium, Appium)
  • Python or other programming/scripting languages
  • Software testing life cycle methodology
  • Version control systems (Git, SVN)
  • CI/CD systems (Jenkins)
  • Test case design and execution
  • Multi-platform testing (web, mobile, gaming)
  • Agile development practices
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

PlayStation Global

PlayStation Global builds gaming platforms and backend systems for PlayStation products, including console and mobile applications. The company is hiring software engineers across backend, frontend, testing, and systems infrastructure roles to support large-scale services and player experiences.

View all jobs at PlayStation Global

Likely interview questions

  • Describe your experience building and maintaining test automation frameworks—what challenges did you face and how did you overcome them?
  • Tell us about a time you identified a critical defect early in the testing cycle. How did you communicate this to stakeholders?