Home / Careers / Senior Java Full Stack Engineer — Platform Engineering8+ yrs · Full-time
Senior Java Full Stack Engineer — Platform Engineering
Ship platform features from API and data model through the UI, with production experience on both Java/Spring Boot and React/TypeScript.
Apply for this roleJava · Spring Boot · React · Tailwind
Role summary
Reports to the team lead / tech lead. Interfaces with engineering leads, architecture, security, the program manager, and external partner teams. Scope covers UI development and backend development.
Own features end-to-end — from API and data model through the UI a customer touches. Measured on delivery throughput and code quality: how reliably features ship without rework, and how little other engineers wait on your APIs or components to build on top of.
Core responsibilities
- ✓Backend (Java/Spring Boot) — Design and build REST/service APIs in Spring Boot, own the data model (schema design, migrations, query performance) and integration points with downstream systems. Write code that is testable and observable by default — unit and integration test coverage, structured logging, metrics on the paths that matter. Participate in API contract design with frontend and other consuming teams before implementation starts.
- ✓Frontend (React/TypeScript/Tailwind) — Build UI components and flows in React and TypeScript, styled with Tailwind. Own component structure, state management, and the boundary between server data and client state. Keep the component library consistent — no one-off patterns duplicating what already exists.
Skills and experience
- ✓8+ years professional software engineering, with real production experience on both ends of the stack (not backend-primarily with some frontend exposure)
- ✓Backend: Java, Spring Boot (REST APIs, dependency injection, data access layer), relational database design and SQL (schema design, indexing, migrations)
- ✓Frontend: React, TypeScript, Tailwind CSS — component architecture, hooks, state management, working with a design system
- ✓Comfortable owning a feature’s API contract and its consuming UI in the same PR sequence
- ✓Git-based workflow, CI/CD-aware — writes code that passes pipeline gates
- ✓Writes tests as part of the work, not as an afterthought — unit tests minimum, integration tests for anything crossing a service boundary