> Markdown version of [/jobs/ext/3948584-software-development-engineer-building-connectivity-engineering](https://www.wearedevelopers.com/jobs/ext/3948584-software-development-engineer-building-connectivity-engineering). 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).

---

# Software Development Engineer, Building Connectivity Engineering

- **Company:** Amazon.com, Inc.
- **Location:** Seattle, WA, United States
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Software Design Documents, Amazon DynamoDB, IP Address Management, Network Architecture, Runbook, Software Engineering, Computer Network Operations, Build Management
- **Published:** October 27, 2026
- **Apply:** https://www.careerbuilder.com/job-details/software-development-engineer-building-connectivity-engineering-seattle-wa--45e6beb6-b4b5-45a6-a778-596f9a06d435

## About the Role

Software Development, Software Engineering, Network Operations Center, Vehicle Fleets, Building Systems, Amazon Web Services (AWS), Financial Control, Network Architecture/Engineering, Software Development, Design Document

## Description

* Design and build services in AWS (Lambda, Step Functions, DynamoDB, EventBridge, CDK), modeled with Smithy and deployed through pipelines you own.
 * Write the design document for what you build. Every engineer on this team writes designs; it is a core part of the job, and seniority is not the gate.
 * Integrate with the systems of record in AWS Networking (IP address management, device registry, routing-policy store, configuration store and release, deployment, cabling plans), and find out what each contract actually does, against the real service, before committing to a date.
 * Prove correctness in shadow mode: compute what the automation would do for a site, diff it against what engineers did by hand, and get to zero discrepancies before any cutover.
 * Own what you ship in production: metrics, alarms, runbooks, and a turn in the team"s on-call rotation, which covers the new services and the ones the team inherited.
 * Keep fabric knowledge out of the code. New fabrics, site types and rack types arrive as models the network engineers author; your job is to make the second one cost a configuration change.
 * Estimate honestly: size work by how novel it is and how many systems outside the team it touches, raise partner asks early, and say what is unknown.