Confirmed on the employer's own hiring board on Nov 17, 2026. First seen by Alion on Nov 17, 2026. Svitla Systems scores B on the Alion truth index.
Svitla Systems Inc. is looking for a Tech Lead, IoT Device-to-Cloud Platform for a full-time position (40 hours per week) in Argentina. Our client is a global technology company specializing in self-service payment solutions and digital customer engagement for the retail petroleum industry.
We are seeking a Tech Lead for our client’s Hub Device-to-Cloud team. The team builds the platforms that connect millions of devices and industrial assets to a global cloud ecosystem, ingesting, normalizing, distributing, analyzing, and serving telemetry from fueling stations, convenience retail environments, and other connected equipment.
This is a hands-on technical leadership role for someone who is comfortable designing systems that operate across unreliable networks, heterogeneous devices, multiple regions, high event volumes, and evolving data contracts. You will lead the technical direction for IoT and distributed-system capabilities while helping the team apply AI and machine learning safely and pragmatically to telemetry, asset health, predictive maintenance, and operational workflows.
Requirements
- Significant experience designing and operating distributed systems in production.
- Strong experience with IoT, telemetry, edge computing, industrial systems, or other unreliable-network environments.
- Demonstrated understanding of event-driven architecture and streaming systems.
- Experience with several of the following: Apache Kafka (including MSK and Confluent), NATS or another subject-based messaging system, MQTT or AWS IoT Core, Kubernetes and AWS/EKS, Go (ideally alongside Python or another production language), MongoDB or other operational data stores, and Snowflake or other analytical platforms.
- Strong understanding of distributed-system failure modes, including duplicate delivery, out-of-order events, consumer lag, replay, partial failure, network partition, and data convergence.
- Experience designing APIs and data contracts that support independent service ownership.
- Production experience with AI/ML systems, including at least some of the following: time-series modeling, anomaly detection, predictive maintenance, feature engineering, model serving, MLOps and model monitoring, and model or data drift management.
- Strong communication skills and the ability to explain complex technical trade-offs to engineers, product leaders, and non-technical stakeholders.
Will be a plus
- Experience with industrial automation, fuel retail, convenience retail, payments, logistics, manufacturing, or other operational technology domains.
- Experience with AWS IoT Core, MQTT, ATGs, device gateways, or edge agents.
- Experience with Go-based cloud services and shared platform libraries.
- Experience deploying models at the edge or designing low-latency inference services.
- Experience with multi-region architecture, data residency, federated APIs, or regional data stores.
- Experience modernizing legacy systems while maintaining backward compatibility and operational continuity.
- Familiarity with Temporal or other durable workflow orchestration platforms.
- Experience designing secure device identity, certificate rotation, mTLS, secrets management, and fleet provisioning.
Responsibilities
- Own the technical direction for end-to-end Device-to-Cloud flows, from edge devices and protocols through ingestion, processing, storage, APIs, and applications.
- Design robust architectures for devices that may be offline, intermittently connected, resource-constrained, or running different protocol versions.
- Establish patterns for supporting current and future device protocols without creating tightly coupled services.
- Design reliable event-driven systems using Kafka, NATS, and related technologies.
- Make deliberate decisions about delivery guarantees, ordering and partitioning, idempotency and deduplication, replay and recovery, backpressure and rate limiting, retry and dead-letter handling, schema evolution and compatibility, eventual consistency, and exactly-once versus at-least-once processing.
- Design for regional deployment, data residency, global aggregation, and graceful degradation.
- Help maintain a clear separation between device connectivity and fleet health, asset state and business meaning, telemetry processing, analytical workloads, and customer-facing APIs.
- Ensure that REST APIs and authoritative data stores remain the source of truth for domain objects.
- Use asynchronous messaging for notification, cache invalidation, fan-out, long-running processing, and workflow initiation, and not as an uncontrolled mechanism for duplicating authoritative data.
- Define ownership boundaries between device state, asset state, telemetry, analytical data, and derived predictions.
- Establish contracts that enable independent teams to evolve services safely.
- Identify valuable AI opportunities in device telemetry, including predictive maintenance, anomaly detection, failure prediction, sensor and data-quality monitoring, time-series forecasting, and operational decision support.
- Help design production-grade ML pipelines from raw telemetry through feature generation, training, validation, deployment, and monitoring.
- Guide decisions around batch, streaming, edge, and real-time inference.
- Establish standards for feature quality and freshness, model versioning and lineage, training/serving consistency, model drift and data drift, prediction confidence and fallback behavior, explainability and human review, and model rollback and safe deployment.
- Evaluate when traditional rules, statistical methods, machine learning, generative AI, or a hybrid approach is appropriate.
- Use AI coding and productivity tools responsibly, ensuring that generated code and designs are reviewed, tested, secure, and operationally supportable.
- Help the wider engineering team build practical AI capability rather than isolated prototypes.
- Turn ambiguous product and platform goals into clear technical approaches and incremental delivery plans.
- Lead solution design, architecture reviews, technical refinement, and risk identification.
- Ensure that non-functional requirements are explicit, including latency, throughput, availability, recovery, security, cost, and operability.
- Partner early with DevOps, SRE, security, data engineering, QA, and product teams.
- Support migrations from legacy polling, Elasticsearch, Oracle, and protocol-specific implementations toward modern Hub services and data flows.
- Ensure that systems are testable using realistic device simulators, contract tests, integration tests, load tests, and failure-injection scenarios.
- Participate in production support and incident response, using evidence from metrics, logs, traces, consumer lag, device health, and data-quality signals.
- Mentor engineers in distributed systems, IoT architecture, data engineering, AI/ML, and operational excellence.
- Create reusable patterns, reference architectures, and technical documentation.
- Spread knowledge rather than becoming the sole owner of critical design decisions.
- Raise technical risks early and challenge designs that compromise reliability, security, or long-term maintainability.
- Set a high quality bar while enabling the team to deliver iteratively.

