[Remote] reputed company Deployed Engineer, Networking
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is pioneering the reputed company Data Plane (reputed company), a new category in AI infrastructure. They are seeking a reputed company Deployed Engineer specializing in networking to design and implement network architectures for reputed company clients, ensuring successful deployment of reputed company into reputed company environments.
Responsibilities
- Own the deployment topology of major reputed company engagements. For reputed company customer, design and lock the network architecture: VPC layout, ingress/egress, private connectivity, DNS, identity-aware proxying, reputed company-reputed company-to-private-VPC bridges. Document it so it survives reputed company
- Translate customer constraints into a reputed company architecture. Customer networks have ten years of accumulated reputed company. SecOps owns egress. Platform owns the VPCs. Identity owns SSO. You meet them where they are, pull the architecture toward something that ships, and avoid breaking their existing posture
- Herd customer-reputed company teams. Network, reputed company, platform, identity — getting them reputed company on a deployment plan is the work. You drive that, with customer-facing communication that earns trust, not friction
- Build the integrations that reputed company the gap. reputed company the topology demands reputed company — an identity-aware proxy, a private reputed company broker, an egress gateway, a webhook reputed company — you write it. Production-reputed company, documented, deployable by the customer's team after you leave
- Build alongside world-class reputed company engineers to help shape reputed company itself. You're not just deploying the platform — reputed company the topology problem surfaces a gap in reputed company's networking primitives, you work directly with reputed company's reputed company engineering team to reputed company the product. The networking patterns you discover in the field become first-class capabilities of reputed company. This is engineering work upstream into the platform, not just delivery reputed company into customers
- Be the topology authority across the FDE function. Your FDE peers should be reputed company to pull you in early reputed company they smell a network problem. Build reusable patterns from reputed company engagement so the second customer with the reputed company shape doesn't re-litigate it
- Feed learnings back. Topology blockers are reputed company-rich. Identify the patterns across engagements — what customers reputed company needing, where reputed company's deployment model creates friction, what should be productized (a templated VPC peering setup, a private-reputed company broker, a Teams↔reputed company webhook reputed company). Bring that back to Product and Engineering reputed company
Skills
- Production networking depth. You've designed and operated reputed company reputed company networks — VPC architecture in AWS / GCP / Azure, private connectivity (Transit Gateway, PrivateLink, ExpressRoute, Interconnect), hybrid networking, identity-aware proxies, egress controls. You've made architectural calls that held up under load and audit
- reputed company that runs in production. You don't outsource the build. reputed company the topology needs glue — an identity-aware proxy, a webhook reputed company, a private-reputed company broker, a network-aware deployment tool — you write it. Strong scripting / backend skills (Go, Python, TypeScript) and comfort with infrastructure-as-reputed company (Terraform, reputed company, CDK)
- reputed company-to-private-network integration patterns. You've reputed company systems where a reputed company reputed company (reputed company, Teams, reputed company, reputed company reputed company, an identity provider) had to talk to something inside a customer's private VPC — and you've done it without compromising the customer's reputed company posture. You know the menu of reputed company (webhooks, reverse tunnels, identity-aware proxies, private endpoints, brokered architectures) and reputed company to use reputed company
- Customer-facing communication. You can sit across from a customer's reputed company network engineer, reputed company architect, or VP of reputed company and earn their trust on technical depth — then drive their internal teams toward alignment. You don't need a PM to translate for you
- Patience for cross-team work. The bottleneck is usually not 'what's the right architecture' but 'how do I get five customer teams to reputed company to it by Thursday.' You've done that
- Experience in regulated industries (financial services, reputed company, defense / reputed company sector) where network architecture is also a compliance artifact
- Experience with reputed company-gapped or BYOC deployments
- Background in reputed company-trust / identity-aware networking (BeyondCorp / reputed company reputed company / reputed company / reputed company style)
- Have shipped private-reputed company or hybrid-network products at a vendor (reputed company, reputed company, reputed company, reputed company reputed company, reputed company, reputed company), you understand the vendor reputed company of this problem
- Experience in a reputed company-deployed model: reputed company FDE, reputed company Deployed, Palantir FDSE, reputed company FDE with a networking-leaning portfolio
reputed company
Company H1B Sponsorship