> Markdown version of [/jobs/ext/3412187-senior-cloud-engineer](https://www.wearedevelopers.com/jobs/ext/3412187-senior-cloud-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Cloud Engineer - **Company:** Vervint, LLC - **Location:** Grand Rapids, MI, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Amazon Web Services, Amazon Cloudfront, Amazon S3, Apple Push Notification Service, Cloud Engineering, Data Structures, Amazon DynamoDB, Firmware, Protocol Buffers, Push Technology, Identity and Access Management, Mobile Application Software, Message Queuing Telemetry Transport (MQTT), Cloud Services, Prometheus, Runbook, Management of Software Versions, WebSocket, AWS Cdk, AWS Lambda, Backend, AWS Fargate, Database Replication, Api Gateway, Stream Processing, Serverless Computing - **Published:** September 16, 2026 - **Apply:** https://jobs.mitalent.org/job-seeker/job-details/JobCode/408783508 ## About the Role 6+ years building production backend services in the cloud, with strong hands-on Go experience, or deep experience in another statically typed language and a strong interest in writing Go. Deep AWS experience across serverless and container services, including Lambda, ECS and Fargate, API Gateway, DynamoDB, Kinesis, and S3, along with the judgment to choose between them. Strong data modeling instincts, including DynamoDB key and index design and the associated cost and consistency tradeoffs. Event-driven and stream processing experience, with an understanding of where pipelines can lose, reorder, or double-count data. A track record designing and versioning APIs and stored data structures that need to remain compatible with mobile clients that cannot be forced to upgrade. Infrastructure as code experience, with CDK preferred, plus IAM, KMS, and least-privilege access as part of your normal development practices. Strong testing discipline and the patience to learn a layered codebase before adding to it. Experience working on contract engagements, with the ability to ramp quickly, work within existing conventions, and scope your own work. A passion for connected consumer products and the curiosity to thrive alongside a high-performing engineering team. Preferred Qualifications Connected-device or IoT backend experience, including MQTT and IoT Core, device state, command and reply flows, provisioning, and OTA. Robotics, telemetry-heavy, or other high-volume device product experience, including large or binary payloads such as Protobuf. Real-time delivery to mobile clients, including WebSocket APIs, presence, reconnects, and fan-out. Experience with OpenSearch, push notification infrastructure such as APNs and FCM, or multi-region data replication. Observability and on-call experience, including Prometheus, Loki, OpenTelemetry, alarms, and runbooks. Experience using AI-assisted development tools and validating their output. ## Description We are looking for a Senior Cloud Engineer to join a backend platform team supporting a connected consumer robotics experience. In this contract engagement, you will own cloud services that power device state and missions, maps and zones, schedules, cleaning history, notifications, and the APIs consumed by a mobile application as the experience is built out on a next-generation platform. The platform is a Go and AWS CDK monorepo. Go services run on Fargate alongside Lambda functions, with chi HTTP APIs and a WebSocket API behind API Gateway, IoT Core MQTT feeding Kinesis, DynamoDB as the system of record, OpenSearch for activity search, S3 and CloudFront for content, and observability on Prometheus, Loki, and OpenTelemetry. What You'll Do Work alongside architects to implement the cloud services behind the connected robotics experience, owning features end to end from API contract through persistence and deployment. Implement the real-time path from device to app, including MQTT telemetry through the event pipeline to the WebSocket and REST surfaces the app consumes. Model device data for scale and cost, choosing appropriately between DynamoDB, S3, and the search index as payloads and query patterns grow. Design APIs the mobile team builds against and maintain backward compatibility for app versions already in consumers' hands. Extend notifications, history, and reporting so device events reach consumers reliably, once, and on time. Work directly with mobile and firmware teams to establish contracts and behavior before development begins, and document what you build., What the app shows accurately reflects what the device is doing, with reliable and timely history and notifications. Schema and API changes are implemented without breaking mobile versions already in the field. Services are observable, tested, and documented well enough for the permanent team to operate and extend them after the engagement ends. ## Related Videos - [Building Reliable Serverless Applications with AWS CDK and Testing](https://www.wearedevelopers.com/videos/812-building-reliable-serverless-applications-with-aws-cdk-and-testing) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Technical Documentation - How Can I Write Them Better and Why Should I Care?](https://www.wearedevelopers.com/videos/681-technical-documentation-how-can-i-write-them-better-and-why-should-i-care) - [Remote Driving on Plant Grounds with State-of-the-Art Cloud Technologies](https://www.wearedevelopers.com/videos/251-remote-driving-on-plant-grounds-with-state-of-the-art-cloud-technologies) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) - [Nest.js - TypeScript in the backend can also be clean](https://www.wearedevelopers.com/videos/1033-nest-js-typescript-in-the-backend-can-also-be-clean) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [7 Cloud Computing Trends Coming in 2025 for Developers](https://www.wearedevelopers.com/magazine/412-7-cloud-computing-trends-coming-in-2025-for-developers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [What Are The Top Skills Required For Azure Developers?](https://www.wearedevelopers.com/magazine/77-what-are-the-top-skills-required-for-azure-developers)