Skip to main content

About the role

Job Title: Java Full Stack ArchitectLocation: Austin, TX / Cupertino, CAFull TimeJob DescriptionMust Have Technical/Functional Skills
  • Own end-to-end solution architecture - microservices, APIs, event-driven systems, andfront-endProduce HLD, LLD, ADRs, and architecture diagrams; lead design and code reviewsDesign cloud-native solutions on AWS (ECS/EKS, Lambda, RDS, SQS, API Gateway, CDK) Provide hands-on guidance across Java back-end, JavaScript/TypeScript front-end, andPython services
  • Act as primary liaison with Apple DRIs - translate platform standards into actionableengineering
  • Lead and attend daily offshore calls; mentor distributed teams and ensure architecturalconsistencyDrive DevSecOps, CI/CD, IaC (Terraform/CDK), observability, and NFR adherenceEvaluate and integrate AI/LLM tools (Claude, Copilot) into development workflowsMust-Have 12-15 years of engineering experience; 5+ years as Architect - still actively codingDeep hands-on Java (17/21), Spring Boot 3.x, Spring Cloud, microservicesStrong AWS expertise (multi-service, production-grade)
Strong proficiency in Angular, JavaScript/TypeScript, and Python for full-stack developmentSolid grasp of distributed systems, Kafka/SQS/SNS, REST/GraphQL/gRPCProven stakeholder liaison experience at DRI / senior leadership levelComfortable with offshore collaboration across time zonesFluent with AI-assisted development - Claude (Anthropic), GitHub Copilot; can review, validate, and extend AI-generated codePreferredPrior experience with Apple engineering teams or DRI-driven delivery modelsAWS certification - Solutions Architect Professional or DevOps EngineerHands-on with Claude API / LLM integration - RAG, prompt engineering, agentic workflowsExperience with Kubernetes (EKS), Istio, and container orchestrationData architecture - Redshift, Glue, Athena, DynamoDB, SnowflakeConsulting / vendor delivery experience at enterprise scaleTech StackBack-End → Java 17/21, Spring Boot 3.x, Spring Cloud, HibernateFront-End → Angular, TypeScript, JavaScript, Node.jsPython → FastAPI, Pandas, LangChainCloud → AWS (ECS/EKS, Lambda, RDS/Aurora, S3, VPC, IAM, CDK) Messaging → Kafka, SQS/SNS, EventBridgeAI / LLM → Claude (Anthropic), LangChain, RAG pipelinesData → MongoDB, PostgreSQL, Redis, DynamoDBDevOps → GitHub, GitHub Actions, Docker, Terraform, ArgoCD

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