Principal Engineer I
Skills
CommandContinuous ImprovementEvolutionGarbage CollectionMeshMotorsSales
What the job involves
The main requirements, responsibilities and hiring steps.
Requirements
- Proven ability to reason about distributed systems tradeoffs and make defensible design decisions under real constraints
- Proven experience writing production code and building high-traffic systems at scale
- Expertise in Java 17+ and the JVM including internals garbage collection and performance tuning
- Hands-on experience with a reactive non-blocking framework and asynchronous event-driven service design
- Deep experience with stream processing and event-driven architecture using Kafka Streams Apache Flink or equivalent
- Proven track record building high-throughput low-latency systems with tail latency backpressure and memory pressure concerns
- Strong command of gRPC and binary serialization formats such as FlatBuffers Avro or Protobuf with schema evolution
- Familiarity with Data-Oriented Design for cache-efficient throughput-oriented code
- Experience with compact search-oriented data structures for efficient large in-memory state
- Experience with search engines for discovery workloads is a plus
- Strong grasp of microservice design service mesh API contract evolution and backend-for-frontend patterns
- Hands-on experience with AWS EKS and cloud-native operations including Docker Kubernetes Helm Kustomize and Terraform
- Proficiency with caching strategies and their application to high-traffic systems
- Solid understanding of CI/CD pipelines and progressive deployment strategies
- Experience designing for high availability including multi-region architectures failover and disaster recovery
- Proficiency with AI/ML tools and techniques to accelerate engineering workflows
- Familiarity with observability tooling such as Grafana Splunk Prometheus or OpenTracing
- Strong understanding of security best practices including OAuth OIDC input validation and secrets management
- Track record of leading technical initiatives across multiple teams without direct authority
Nice to have
- Systems Thinking
- Technical Vision
- Domain Depth
- Ownership
- Influence Without Authority
- Communication
- Composure Under Pressure
- Continuous Improvement
Day to day
- Write production code daily and solve hard hands-on engineering problems.
- Lead platform modernization and design resilient event-driven systems for high-demand on-sales.
- Collaborate across teams on architectural decisions, observability, and reliability improvements.