Cloud Engineer

• Lead project scoping and qualification for delivery
• Provide technical leadership to project teams
• Design and implement cloud application platform solutions

Cloud Architect – OpenShift, AI

• Take ownership of the IoT cloud perimeter
• Get hands-on with FleetAPI, AWS Step Functions provisioning, RMS, and the Retool layer - operating 50% of the perimeter autonomously within three months, 100% within six.
• Document the stack as you go. The goal isn't a wiki - it's that the team's knowledge becomes shared infrastructure, not tribal memory.
• Make the cloud foundations resilient enough that scaling the fleet doesn't put pressure on a single person.
• Own AWS architecture and infrastructure-as-code
• Design and evolve compute (Lambda, ECS, Batch), networking, storage and IAM across the DLM perimeter.
• Bring the full stack under CDK - no manual AWS console clicks to ship a critical infra change.
• Make trade-offs (serverless vs container, RDS vs DynamoDB, push vs pull) and explain them to the team without dogmatism.
• Drive observability and reliability
• Instrument logs, metrics, alerting that ops and engineers can act on.
• Run on-call rotation, write post-mortems, keep runbooks current.
• Move MTTR down quarter after quarter, with the numbers to prove it.
• Ship backend services
• Build and maintain backend services in Node.js / TypeScript (Python where it makes sense), at production grade.
• Pair with the Tech Lead and the full-stack IC on infra-aware design from the spec stage - so trade-offs are made before the code, not discovered at review.
• Become the cloud referent across teams
• Within 12 months, represent CIOT-DLM in cross-team architectural discussions (Platform, Data Platform, NetSec, AI).
• Take ownership of one major vertical at six months - provisioning, fleet drift detection, or RMS - and ship a measurable improvement on reliability or manual correction.

See all jobs on JobTailor

Cloud Architect – OpenShift, AI

Senior Backend, Cloud Engineer