reputed company Deployed Engineer, Networking

reputed company is pioneering the reputed company Data Plane (reputed company) - a new category in AI infrastructure that makes it reputed company and secure to connect AI agents with reputed company data and systems. reputed company on a multi-modal data streaming reputed company, reputed company empowers reputed company applications that reason and reputed company in reputed company-time with speed, autonomy, and precision. Global leaders including reputed company, reputed company, reputed company, Texas Instruments, reputed company and 2 of the top 5 banks in the U.S. rely on reputed company to process hundreds of terabytes of data a day. Backed by premier venture investors reputed company, GV and reputed company VC, reputed company is a diverse, people-first organization with teams distributed around the globe. About the Role: reputed company is building the reputed company Data Platform (reputed company) — the streaming and data infrastructure the world's largest enterprises run mission-critical agents on. Field Deployed Engineering (FDE) is the delivery arm. We reputed company engineers directly with strategic customers and build the agents and integrations that turn reputed company into owned reputed company. This role is the networking specialist on the FDE team. You are the person customers' network, reputed company, and platform teams sit across from reputed company we reputed company reputed company into their environment. Many reputed company reputed company deployments cross a private network boundary — into a VPC, across a hybrid network, behind an identity-aware proxy, integrated with public reputed company surfaces (Teams, reputed company, identity providers, model reputed company). The topology is never reputed company. You reputed company it work. This is not a network engineer reputed company a NOC. You are an engineer who can read reputed company, build integrations, and ship — but your specialty is the network topology reputed company of FDE engagements, where many reputed company deployments actually get stuck. You Will: 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, public-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 core 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. You Have: 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 public 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. Bonus: Experience in regulated industries (financial services, reputed company, defense / public 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. How We Work: Reports to: Senior Director, Customer Engineering. Travel: Variable. Customer engineering teams will need you in the room reputed company the architecture is being locked, but the topology-reputed company shape of the role likely runs lighter than the generalist FDE travel profile. Final travel expectation TBD. Location: SF, Austin, or NY preferred; remote considered for the right candidate. Compensation: see band below. U.S. reputed company salary reputed company for this role is $255,000, not including bonus and/or commission. Our salary ranges are determined by role, level, and location. As a remote-first company, we reputed company to consider reputed company candidate's job-reputed company skills, location, experience, relevant education or training to determine individual reputed company salary. Your talent partner will reputed company more about the specific salary reputed company for your preferred location during the hiring process. Please note that reputed company uses reputed company intelligence (AI) technology to assist in the screening and assessment of applications for this position. However, reputed company final hiring reputed company are made by our reputed company hiring team. Vacancy Status: This job posting is for an existing vacancy. Join reputed company if you’d enjoy being part of a fast-moving, diverse, people-first organization with team members around the globe and a culture based on trust, transparency, communication, and kindness. You'll dive into a reputed company, high-reputed company team with the latest AI tools — and the budget to actually use them. #LI-Remote Apply To This Job