Java / AWS Lead

Industry focus and Locals Only Job title- Technical Lead – Java / AWS Location: Chicago office is required - Hybrid: 3x days in office Duration: 12 months Position’s Contributions to Work Group: • The Lead Software Engineer will provide deep technical leadership for the design and implementation of Java‑based, cloud‑native systems on AWS, defining service architecture, data flows, and integration patterns to meet strict scalability, availability, and security requirements. This role will drive architectural decisions across microservices, event‑driven, and asynchronous processing patterns, ensuring clear service ownership and well‑defined contracts. • The position will lead development of core backend services using modern Java frameworks and AWS‑native patterns, including RESTful and event‑based APIs, message‑driven processing, and distributed data management. The Lead Engineer will guide adoption of AWS services such as managed compute, messaging, storage, and databases, and will define standards for infrastructure‑as‑code, resiliency, fault tolerance, and graceful degradation. • In addition, this role will establish technical best practices for CI/CD automation, observability, logging, metrics, and tracing to support reliable operation of distributed systems in production. By proactively identifying architectural bottlenecks, scalability constraints, and technical debt, the Lead Software Engineer will directly improve system performance, reliability, and long‑term maintainability while enabling the work group to scale features and throughput efficiently. Education & Experience Required: • NO Degree required • Must have 10+ years’ experience as a PM • At least 3+ years’ experience in leading a team is preferred. Required Technical Skills (Required) • Strong AWS expertise, including designing and operating cloud‑native, highly available distributed systems • Advanced Java and/or Kotlin in production environments • Spring Boot for building microservices and REST APIs (e.g., Spring Web/MVC, dependency injection, configuration, actuator/health checks) • Microservices architecture and distributed systems patterns (service boundaries, resiliency, fault tolerance) • RESTful API design & implementation, including documentation (OpenAPI/Swagger) • SQL + relational databases (data modeling, query tuning, performance) • NoSQL / non‑relational data stores (e.g., DynamoDB/MongoDB/Cassandra) • CI/CD and build/deploy automation (pipelines, quality gates, repeatable releases) • Data streaming / asynchronous messaging (event‑driven patterns; e.g., Kafka) • Observability & production troubleshooting (logging/metrics/tracing, incident investigation)