Skip to main content

PlayStation Global

Data Engineer II

United States, Aliso Viejo, CAFrom $225.1kmidAdded today

About this role

Sony Interactive Entertainment seeks a Data Engineer II to design and maintain scalable data platforms powering PlayStation's Cloud Streaming service. You'll develop JVM-based applications, Flink stream processing jobs, and APIs to deliver real-time data insights across a geographically distributed infrastructure, collaborating with BI and product teams to drive data-informed decisions.

What you'll do

  • Design and implement middleware and backend systems handling high throughput and load
  • Develop and maintain stream processing jobs using Apache Flink with stateful and stateless operations
  • Optimize performance, reliability, and monitoring across the data pipeline stack
  • Support migration of on-premises Kafka infrastructure to cloud technologies
  • Analyze functional and business requirements to inform architectural decisions
  • Partner with BI and product teams to translate data into actionable business insights

What they're looking for

  • JVM languages (Kotlin, Scala, Java)
  • Python
  • Apache Kafka and Flink
  • Apache Spark and SQL
  • REST, gRPC, JSON, WebSockets
  • Data structures (Avro, Protobuf)
  • Functional and object-oriented programming
  • High-throughput distributed systems design
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 high-throughput, fault-tolerant systems. What challenges did you encounter and how did you address them?
  • Walk us through a complex Flink job you've implemented. How did you handle state management and exactly-once semantics?