Software Engineer, Cloud

Staff Software Engineer, Cloud

Department: Interfaces

Employment Type: Full Time

Location: Minneapolis, MN

Reporting To: Deepti Gaonkar

We’re Smart Things, one of the leading IoT ecosystems in the world, creating the most effortless way for anyone to create a smart home. We're a wholly owned subsidiary of Samsung with corporate offices in Minneapolis and the Bay Area.

More than 430 million people worldwide use Smart Things to control and manage their connected life. Smart Things delivers simple, powerful experiences across Samsung’s leading portfolio of phones, TVs, and appliances. We also offer the most versatile smart home experience as an open platform with a rich partner ecosystem (think IKEA, SONOS, Honeywell, and so many more). As a founding member of Matter, we are a leader in the industry to help make smart homes more secure, reliable and seamless to use.

Come be a part of the leading edge of IoT innovation!

As a Staff Engineer on the Cloud-to-Cloud (C2C) team, you will be the architectural backbone of how Smart Things interacts with the global IoT ecosystem. You will lead the evolution of the Smart Things Schema, ensuring that our integrations—from voice assistants to third‑party smart home devices—are seamless, secure, and hyper‑scalable. This isn't just about making things work; it’s about defining how they work at a massive scale.

This position is a hybrid role, based onsite 3 days a week at our office in Minneapolis, MN.

In this role, your primary responsibilities will include the following:

• Lead the design and long‑term evolution of the C2C platform. You’ll ensure the Smart Things Schema remains flexible enough for tomorrow’s devices while maintaining the rock‑solid stability required for today’s users.
• Act as the subject matter expert for our AWS infrastructure. You will leverage deep hands‑on experience to build systems that aren't just "in the cloud," but are truly cloud‑native, prioritizing elastic scalability and zero‑trust security.
• Provide leadership through design reviews and mentorship. You will set the standard for AI‑assisted engineering best practices, ensuring that AI‑generated code meets our rigorous security, privacy, and performance benchmarks.
• Take ownership of the developer experience by integrating agentic coding tools (e.g., Claude, Cursor, Git Hub Copilot Agents) into the team’s daily workflow. Your goal is to move the team from "manual coding" to "architectural orchestration," significantly improving speed of delivery.
• Take end‑to‑end ownership of the technical stack. You will identify bottlenecks in our delivery pipeline and implement strategies to improve developer productivity, CI/CD speed, and overall engineering effectiveness. Use AI to automate the "boring" parts of the job—from generating unit tests and documentation to triaging complex incident logs across our C2C distributed systems.

Inclusive Hiring Practices

Don’t meet all desired requirements? Studies have shown that some people are less likely to apply to jobs unless they meet every single desired qualification. At Smart Things, we are dedicated to building a diverse, inclusive, and authentic workplace, so if you’re excited about this role but your past experience doesn’t align perfectly in the job description, we encourage you to apply anyway.

You may be just the right candidate for this or other roles.

• Bachelor's Degree in Computer Science, Engineering, or related field.
• 10+ years of software engineering experience, with a significant portion dedicated to distributed systems and high‑traffic cloud environments.
• Deep proficiency in AWS services like Lambda, Kinesis, DynamoDB, and API Gateway. You should be intimately familiar with the AWS Well‑Architected Framework.
• You understand the nuances of building public‑facing schemas and APIs that are intuitive for third‑party developers yet robust enough for enterprise partners.
• You have a proven track record of leading cross‑team initiatives. You know how to influence without authority and can translate complex technical trade‑offs for non‑technical…