Full Stack Engineer – Java, Kafka & AWS MSK Migration
Full Stack Engineer – Java, Kafka & AWS MSK Migration
Posted 2 days ago
SENIORITY
Lead
About the role
- Lead technical migration of self-managed/on-prem Kafka clusters to AWS MSK — cluster sizing, topic replication, cutover planning
- Design and implement Java-based microservices and APIs producing/consuming from Kafka topics
- Develop full-stack features (backend + UI integration) supporting event-driven architectures
- Re-architect/refactor producer/consumer applications for MSK compatibility (IAM auth, TLS, VPC connectivity, security groups)
- Implement monitoring/alerting/observability using CloudWatch, Prometheus/Grafana, or equivalent
- Define and execute data validation, dual-write/dual-read, and rollback strategies during cutover
- Optimize Kafka topic partitioning, replication factor, retention policies, and consumer group configurations
- Collaborate with DevOps/Infra teams on Terraform/CloudFormation-based MSK provisioning
- Ensure compliance with security, encryption (at-rest/in-transit), and access control standards (IAM, SASL/SCRAM, mTLS)
- Troubleshoot performance, latency, and throughput issues pre/post-migration
- Document migration runbooks, architecture decisions, and operational procedures
- Mentor junior engineers on Kafka/MSK best practices
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.
