Skip to main content

Java Developer (AWS, AI (Claude/Copilot), DevOps, Kafka).

Posted yesterday

iconmaPalo Alto (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Job Description: Our client, an IT Services and Consulting company, is looking for a Java Developer (AWS, AI (Claude/Copilot), DevOps, Kafka) for their Palo Alto, CA/ Plano, TX location.
Responsibilities: Leads end-to-end delivery of full stack solutions using Java Spring Boot, GraphQL/REST, and AWS-managed services, from design through production support. Drives architecture and design reviews, defining service boundaries, API contracts, data models, and integration patterns. Develops secure, high-quality, production-grade code; conducts thorough code reviews; sets and enforces engineering standards. Builds and maintains highly available and scalable services with strong operational excellence: reliability, performance, cost awareness, and maintainability. Implements and governs authentication/authorization using OIDC/OAuth2, token validation, scopes/claims, and service-to-service security patterns. Establishes robust observability practices (structured logging, metrics, tracing), incident response readiness (runbooks).Evaluates vendor and internal solutions (including architectural fit, security posture, scalability, and operability) and guides adoption decisions.
Requirements: Mandatory skills: Java (Spring Boot), Microservices, AWS, RestAPI, AI (Claude or Copilot), DevOps, Kafka Minimum 12+ years applied full stack engineering experience delivering and operating production systems; experience as a senior/lead capacity (technical leadership, design ownership).Java Spring Boot expertise: building APIs, dependency injection, validation, error handling, and performance tuning. GraphQL proficiency: schema design, resolvers, federation/composition patterns (where applicable), query performance (N+1 mitigation, caching), and API governance/versioning strategy. REST proficiency: OpenAPI-style contract design, pagination/filtering, idempotency, backward compatibility, and consumer-driven API evolution. OIDC/OAuth2: hands-on implementation with JWTs, refresh/access token flows, scopes/claims, secure session patterns, and least-privilege access control. AWS experience (hands-on): designing, deploying, and operating cloud-native applications; strong understanding of IAM, networking basics, and operational tooling (logs/metrics/alarms).Data layer expertise: · AWS Aurora PostgreSQL: advanced SQL, indexing, query optimization, migrations, and transactional design. AWS Neptune: gremlin, graph modeling, query patterns, and performance considerations for graph workloads. Event-driven systems: AWS Kafka (MSK): topics/partitions, consumer groups, schema evolution, ordering/at-least-once semantics, idempotency, retries/DLQs, and operational monitoring. CI/CD and quality: Strong Git practices, automated testing (unit/integration/contract/e2e), code quality gates, and release confidence practices (feature flags, progressive rollout where applicable).AI-assisted engineering (MUST):Demonstrated proficiency using Claude Code and/or GitHub Copilot to accelerate development, debugging, refactoring, test generation, and documentation—while ensuring correctness, security, and maintainability (e.g., validating outputs, avoiding sensitive data leakage, and adhering to team standards).
Years of experience: 14.00 Years of Experience Why Should You Apply? Health Benefits Referral Program Excellent growth and advancement opportunities

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this