Senior Cloud Engineer - IoT Data Plan

SJE Inc.•Chesterfield, MO

6d•Remote

About The Position

We are looking for a Senior Cloud Engineer – IoT Data Plane to help build the next generation engineering team for our AMI Global brand. AMI Global is a leading IoT connectivity solution for equipment via hardware, SaaS, and software. Its gateways and cloud connected solutions enable real-time monitoring, control, analytics, and commercialization support. We provide integration, development, and go-to-market services. The company defaults to managed and serverless infrastructure, preferring to pay AWS for services rather than hire operations headcount. Industry-standard protocols and formats are the default. Tests gate every merge, aiming for boring releases. GitHub is the source of truth, and deployments go out in waves. AI tooling is integrated into the workflow for pair programming, code generation, and test scaffolding. On-call duties are limited to business hours during the initial rollout phases.

Requirements

Experience building production cloud systems on AWS (7+ years), with deep IoT or large-scale streaming experience.
Experience operating a MQTT-based device fleet at 100k devices, or a comparable ingest-heavy streaming workload (Kinesis, MSK, Kafka, etc.) at similar scale.
Experience making strong opinions on time-series storage trade-offs, based on actual operational experience.
Experience writing design documents.
Fluency in Infrastructure as Code (IaC) using Terraform or CDK.
Fluency in CI/CD practices.
Experience talking directly to customer engineering teams.
A 4-year degree in Computer Engineering, Computer Science, Electrical Engineering or equivalent degree.
7-10 years of experience.

Nice To Haves

Industrial IoT or critical-infrastructure background (water, energy, manufacturing, building automation).
Modbus or other industrial-protocol exposure.
ISO 27001 or SOC 2 platform experience.
Multi-account AWS Organizations / Control Tower experience.

Responsibilities

Own the data plane end-to-end, including MQTT broker selection, telemetry ingestion at fleet scale, semantic data modeling, time-series storage, and public API contract.
Select an MQTT broker (AWS IoT Core, self-hosted, or managed third-party) and write the corresponding Architecture Decision Record (ADR).
Ensure telemetry ingestion can handle backpressure, validation, dead-letter handling, and occasional poison-pill payloads without system failure.
Design and implement a semantic data model where raw Modbus telemetry is normalized against a versioned, device-type-aware mapping.
Choose a time-series storage engine (e.g., Timestream, Influx, ClickHouse), and define partitioning, retention, and query patterns.
Co-design a versioned, OpenAPI-described semantic public API contract with the launch customer.
Instrument cost per device and cost per tenant early in the design phase to identify potential serverless cost issues at IoT volumes.