Warner Bros. Discovery - Java Developers - JVM (2-4 yrs)

Role : Software Engineer

Roles & Responsibilities :

- 2+ Years of total exp and should have experience in Java and a few other languages.

- Proficient in Java or other JVM languages.

- Experience and deep understanding of Docker, Kubernetes, and AWS.

- Great understanding of distributed systems challenges, micro-service-based architectures, and asynchronized communication (e.g. using gRPC and Kafka).

- Ability to implement alerting, metrics, and logging using tools like Prometheus, CloudWatch, Kibana, PagerDuty.

- Practical knowledge of persistence and caching solutions such as PostgreSQL, Redis, ElasticSearch, Caffeine.

- Familiar with asynchronous, non-blocking, functional/reactive styles of programming.

- Hands-on experience with frameworks such as Spring WebFlux, Vert.x, Node.js.

The ideal candidate :

- You can work autonomously to design and develop functional changes to existing software systems. You require little or no guidance from team members. You still actively seek input where appropriate and engage your team to inform and share what you are doing.

- You can collaborate with other engineers assisting on features another engineer designed or taking the lead on feature design yourself. Your software contributions are demonstrated to work in production, and your team trusts your decisions, designs, and code.

- You are able to describe and defend your design and code decisions to other engineers, embrace constructive feedback, and adapt your approach to align with team and company standards and objectives.

- You consistently demonstrated good software ownership practices (e.g. code reviews, code comments, etc) in all of your contributions. Your code reviews are uneventful, you prepare documentation proactively, and you ensure proper monitoring for operational excellence in production.

- You offer enhancements to best practices, document, design, and architecture improvements, and as feedback through code reviews to other engineers without continuous prompting or recurring encouragement. Other engineers appreciate your feedback.

- You can troubleshoot a production issue by reviewing source code, logs, operational metrics, stack trace, etc to pinpoint a specific problem and then resolve it.

- Experience of building resilient, and scalable APIs for globally available consumer facing products that can sustain high load (thousands of RPS) with 4-5 lines of availability.