Software Platform Engineer II | Apply Now
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Job Description
Description and Requirements
Role Value Proposition
We are seeking a Full Stack Engineer who is passionate about building scalable, cloud-native, and API-driven digital experiences. The ideal candidate will have strong hands-on expertise in React, Java, and Spring Boot, with a proven ability to develop responsive, accessible, and high-performance web applications. This role requires a focus on delivering secure, high-quality solutions that seamlessly integrate modern user interfaces with robust backend services and microservices.
Key Responsibility
- Design, develop, and maintain modern React-based web applications and Java/Spring Boot backend services.
- Build and integrate secure, well-designed REST APIs and microservices.
- Ensure the development of secure, high-quality code across UI and backend components while adhering to enterprise engineering standards, coding best practices, and security guidelines.
- Develop responsive, accessible, and high-performance digital experiences.
- Collaborate with cross-functional teams to deliver scalable and cloud-native solutions.
Technical
- 5-7 years of experience in Full Stack development with expertise in React JS, Java, Spring Boot, and RESTful APIs.
- Strong understanding of microservices architecture and cloud-native application development.
- Experience with frontend performance optimization, accessibility, and responsive design.
- Knowledge of secure coding practices, testing frameworks, CI/CD pipelines, and enterprise engineering standards.
- Proficiency with databases and modern development tools
Audit details(provenance, verification trail, raw fields)
Core fields
metlife:20490Provenance
www.metlifecareers.com|/en_US/ml/SearchJobsVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.