# Leaving a solo Dev/IT role for AWS Network Deployment Technician—sanity check from people who’ve made a similar move — retained record

> Retained reddit record from reddit:datacenter.

Canonical: https://highsignal.app/data/records/912c915176ced31d

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:datacenter)  published 2026-08-25 16:28 ingested 2026-08-25 22:46

[original source ↗](https://www.reddit.com/r/datacenter/comments/1vy4p2v/leaving_a_solo_devit_role_for_aws_network/)

## retained text



```
<!-- SC_OFF --><div class="md"><p><strong>TL;DR:</strong> I’m an early-career CS graduate and currently the only developer at a small non-tech company, with no engineering mentorship. I’ve been offered a direct AWS Network Deployment Technician position with better compensation in a substantially lower-cost area. However, it would move me away from daily coding and toward physical infrastructure. My long-term target is network automation, SysDev, infrastructure engineering, SRE, or network engineering—not product SWE. Is NDT a legitimate path toward those roles or a detour?<br /> <strong>Current role: Developer/IT generalist at a small company</strong><br /> Roughly two years of experience in Northern California<br /> Earn in the mid-$20s per hour<br /> Sole developer responsible for a customer-facing application, backend APIs, databases, deployment pipelines, and external integrations<br /> Also cover Microsoft 365, networking, servers, security, general IT, and support<br /> Compensation and technical advancement appear capped, with no engineering organization or senior developers to learn from<br /> <strong>AWS offer: Network Deployment Technician</strong><br /> Direct AWS position<br /> Low-to-mid $30s per hour, overtime eligible, benefits, and relocation assistance<br /> Requires moving to a substantially lower-cost area<br /> Work involves rack deployments, copper and fiber cabling, connection troubleshooting, site audits, and deployment coordination<br /> Primarily physical, on-site infrastructure work with little or no daily programming<br /> I prefer backend systems, databases, networking, automation, and infrastructure over front-end or product development. Long term, I’m targeting network automation, systems development, infrastructure engineering, SRE, or network engineering.<br /> I’m looking for firsthand answers:<br /> Has anyone actually moved from AWS NDT into Network Engineering, Systems Development, infrastructure engineering, or an automation-focused role? What did that path involve, and how long did it take?<br /> How much would moving from a developer/generalist position into Network Deployment Technician hurt if I later applied for coding-heavy backend or SWE roles?<br /> Does AWS infrastructure experience carry meaningful weight for future infrastructure, NetEng, or SRE positions when the role primarily involves physical-layer work rather than cloud configuration?<br /> What separates NDTs who advance into engineering roles from those who remain in physical deployment work?<br /> I’m leaning toward AWS because of the financial improvement, structured environment, and exposure to hyperscale infrastructure. However, I don’t want an answer based solely on the AWS name. I’m interested in what has actually happened to people who entered through this pipeline.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/BraveDog6540"> /u/BraveDog6540 </a> <br /> <span><a href="https://www.reddit.com/r/datacenter/comments/1vy4p2v/leaving_a_solo_devit_role_for_aws_network/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/datacenter/comments/1vy4p2v/leaving_a_solo_devit_role_for_aws_network/">[comments]</a></span>
```



document fetched 2026-08-26 05:41 · canonical https://reddit.com/r/datacenter/comments/1vy4p2v/leaving_a_solo_devit_role_for_aws_network
