Back
Metro location and common backend skillset increase competition, but senior Staff level reduces applicant density.
Core distributed ingestion skills transfer across industries, though compliance/telematics domain knowledge raises sensitivity.
Multiple mandatory technical requirements (Java, Spring, streaming, production experience) make filters strict.
Login to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Own architecture, design, and evolution of core backend services in the NELD (Native ELD) or Ingestion domain, shaping large-scale systems used by fleets and drivers.
Design and implement scalable, high-throughput ingestion pipelines and compliance workflows ensuring data correctness, reliability, and fault tolerance.
Provide technical leadership including mentorship, cross-team collaboration, and driving engineering standards across teams and product initiatives.
Strong backend development experience with Java and Spring Boot.
Solid understanding of distributed systems concepts including consistency, durability, retries, idempotency, backpressure, partitioning, and resilience.
Practical experience with messaging technologies such as Kafka, Kinesis, or Pulsar.
Work Experience Required: Not explicitly mentioned in the JD.
Experienced in owning and evolving large-scale distributed backend systems with strong domain ownership in ingestion or compliance workflows.
Skilled in designing data pipelines and storage solutions balancing scale, performance, and cost in production environments with incident management experience.
Capable of providing technical leadership in architecture, mentoring mid-to-senior engineers, and driving cross-team collaboration in compliance-heavy or regulated domains such as transportation or telematics.