Software Engineer 4/5 - Content and Business Products Engineering

Netflix Netflix · Big Tech · Warsaw, Poland · Engineering

Software Engineer role focused on building and operating backend services for Netflix's Content and Business Products Engineering teams. This includes developing an internal search platform with AI-driven chat interfaces and semantic search capabilities, supporting various stages of content production and promotion.

What you'd actually do

  1. Work cross-functionally to build, test, deploy, and launch backend services that operationalize our workflows at scale.
  2. Participate in product reviews and team meetings, providing technical insight.
  3. Evaluate new technologies and approaches to streamline and improve our rapid application development tooling and conventions.
  4. Regularly learn and influence new systems and tools as the Netflix platform and ecosystem evolve.
  5. Participate in our on-call rotation and lead the incident reviews.

Skills

Required

  • architecting, building, and operating resilient, highly-available, high-scale, low-latency microservices
  • gRPC, GraphQL, or RESTful API design and implementation
  • relational and non-relational data stores
  • Java, C#, or other OO programming languages
  • OO design principles, concurrency, multi-threading, performance tuning, and observability
  • communication of complex technical concepts
  • ownership, independence, bias towards action, and collaboration

Nice to have

  • working full stack, with skills in frontend and backend development
  • creating platforms, tools, or infrastructure for engineers
  • storage or media processing domains
  • observability platforms
  • SRE experience
  • developing build tooling

What the JD emphasized

  • architecting, building, and operating resilient, highly-available, high-scale, low-latency microservices in production environments
  • ensuring high availability, fault tolerance, and performance
  • recent, proficient experience with Java, C#, or other OO programming languages
  • solid understanding of OO design principles, concurrency, multi-threading, performance tuning, and observability
  • proactively describe complex technical concepts to a variety of stakeholders
  • strong sense of ownership, independence, bias towards action, and inclination for collaboration
  • recognize, communicate, address and lead the technical improvements as part of the roadmap