{"id":1965917,"url":"https://alion.io/job/stackyak-senior-network-engineer","title":"Senior Network Engineer","company":{"id":3905444,"name":"StackYak","domain":"stackyak.io","url":"https://alion.io/company/stackyak","size_band":null,"is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":null,"truth_index":null},"role":"Networking","role_family":"Networking","seniority":"senior","employment_type":"full_time","work_mode":"remote","remote_scope":"stated_countries","remote_scope_basis":"inferred_payroll_markers","remote_working_hours":null,"hiring_geo_confidence":"inferred","locations":[],"countries":[],"hiring_countries":["US"],"hiring_countries_total":1,"salary":null,"salary_estimate":{"min_usd":90000,"max_usd":187000,"period":"year","method":"global_role_seniority_cell","sample_n":490},"experience_years_min":null,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"BGP","optional":false},{"name":"HPC","optional":false},{"name":"Linux","optional":false},{"name":"Python","optional":false},{"name":"Terraform","optional":false}],"status":"live","first_seen_at":"2026-10-06T15:09:27Z","employer_posted_date":null,"last_verified_at":"2026-10-06T15:09:27Z","board_verified":false,"closed_at":null,"days_open":2,"trust":{"level":"not_scored","repost_count":null,"flags":[],"days_open":2},"description":"About StackYak\nStackYak is building the infrastructure layer for AI.\nWe are an early-stage, funded company building software that brings compute, GPU infrastructure, networking, and inference together into one product. The opportunity is large, the market is moving quickly, and we are building for real production workloads from the start.\nThis is not internal IT. This is not a slow-moving infrastructure team maintaining someone else's platform. The infrastructure is the product.\nWe are a small, senior team with very little bureaucracy. This is a founding role in its discipline. There is no network team to join and no inherited design to defend — the architecture, the automation, and the operational model are yours to set.\nTreat this document as a starting point rather than a boundary. The people who do well here take ground early and are not asked to give it back.\nWe move quickly. We do not have months for someone to learn the fundamentals of their discipline. You should already be very good at what you do, be able to ramp into adjacent areas quickly, and be comfortable operating without perfect requirements or neatly defined boundaries.\nThe RoleWe need someone who understands networks from Linux host to data-center fabric to carrier connectivity to cloud, and can automate the whole path.\nA customer's traffic has to reach a GPU workload, securely and reliably, over a path that no single party controls: their edge, a carrier, our side, a provider's side. Any hop on it can be the reason something is slow, unreachable, or leaking, and the answer is rarely in the place the symptom appeared.\nMaking one such path work is a good week for a competent network engineer. That is not this job. This job is the second path, and the fiftieth — how much of it can be made to provision itself, which parts genuinely have to stay bespoke, and how little a customer should have to do to get connectivity they would call enterprise-grade. Those questions are open here, and whoever takes the role is the one who closes them. That is why networking is part of the product rather than a support function beneath it.\nThis is not a traditional network-operations role. We do not need someone who waits for a change ticket to configure a switch. We need a network engineer who codes, debugs systems end to end, participates in architecture, and owns production outcomes.\nWhat You Will OwnNot tasks. Outcomes, and the authority that comes with them.\n\nThe whole path from a customer to their workload. Customer edge, carrier, our fabric, the overlay, the host — and the requirement that the next customer's path cost a fraction of the effort of the first.\n\nRouting and segmentation. BGP, VLANs, VRFs, firewalling, and policy, including what all of it does during a failure rather than on a diagram.\n\nTenant isolation, and the ability to define \"isolated\" precisely enough that it can go in a contract.\n\nSecure private access. WireGuard, IPsec, and overlays — where tunnels terminate, why there, and what happens when that site is unreachable.\n\nThe fabric inside our facilities, and how it meets the fabric belonging to people we do not control.\n\nCarrier and cloud connectivity. Cross-connects, transit, private circuits, and NaaS, including the commercial and lead-time realities that come with them.\n\nNetwork observability and incidents, including the ones that arrive disguised as an application problem.\n\nThe layer-boundary call. Host, overlay, cloud network, physical network, or carrier — you decide which, and you prove it instead of escalating it.\n\nTurning the above into product. Provisioning that runs without you, and connectivity patterns that engineers who are not you can deploy safely.\n\nWorking alongside the infrastructure and inference engineers on RDMA, multi-node GPU traffic, topology, and performance.\n\nWhat We NeedThe bar is what you have already done, not what you could learn. You should have done most of this:\n\nRun BGP in production, including on the day it did something you did not expect.\n\nDesigned and operated VLANs, VRFs, segmentation, and firewall policy at a scale where mistakes were expensive.\n\nTroubleshot Linux networking on hosts carrying real traffic.\n\nWorked inside a data-center network rather than only in front of one.\n\nOperated cloud networking in at least one major cloud.\n\nBuilt connectivity on IPsec and/or WireGuard that customers depended on being up.\n\nKept tenants apart from each other and been personally accountable for that claim.\n\nChased a packet flow across administrative domains you did not control until you found the truth.\n\nReplaced manually managed device configuration with automation that kept working while you were on holiday.\n\nWritten Python and Terraform that other people run in production.\n\nReasoned about how a networking decision would change the behaviour of the distributed system sitting on top of it.\n\nYou Will Be Especially Strong If\nYou have worked at a hyperscaler, neocloud, hosting provider, data-center operator, network provider, AI infrastructure company, or enterprise networking vendor.\n\nYou have designed or operated networks supporting GPU, HPC, storage, or other high-bandwidth distributed workloads.\n\nYou understand RDMA and the network requirements of multi-node GPU workloads.\n\nYou have experience with carrier connectivity, cross-connects, internet transit, private circuits, or NaaS platforms.\n\nYou have built network automation instead of relying on manually managed device configuration.\n\nYou have turned a connectivity pattern into something repeatable enough that non-network engineers could deploy it safely.\n\nYou are comfortable debugging from application symptoms down to packets and physical paths.\n\nYou run labs, write tools, or experiment with networking outside your assigned day-to-day work.\n\nThis Is Probably Not For You If\nYou primarily configure network devices through tickets and change windows.\n\nYou do not code.\n\nYou think the network ends at the top-of-rack switch.\n\nYou think cloud networking makes physical networking irrelevant.\n\nYou prefer architecture diagrams to implementation and debugging.\n\nYou want every customer connection to be a bespoke design you personally shepherd.\n\nYou have strong certification knowledge but limited experience owning real production networks.\n\nYou need networking to be your exclusive domain and do not want to touch systems, software, or adjacent infrastructure.\n\nWhat Success Looks LikeYou can take a requirement like:> A customer needs secure, private, reliable access from their environment to a workload running on GPUs in one of our facilities.\n…and design and implement the path from customer edge to workload — routing, isolation, security, observability, automation, failure handling — and then make the second customer's version of it take a fraction of the effort.\nYou will help us answer questions such as:\n\nWhen should we use an overlay versus native private connectivity?\n\nWhere should tunnels terminate?\n\nHow should tenants be isolated?\n\nWhat should the network look like inside our facilities?\n\nHow do we connect owned infrastructure with neocloud and public-cloud capacity?\n\nWhich network capabilities belong in the product rather than in an operator runbook?\n\nHow do we give customers enterprise-grade connectivity without making every deployment bespoke?\n\nHow We Work\nSmall, senior team with direct access to the founders.\n\nStrong opinions, loosely held.\n\nEveryone is expected to participate in technical decisions.\n\nEveryone shares responsibility for production and on-call.\n\nWe value people who can move between design, implementation, debugging, and operations.\n\nWe care much more about what you have built and operated than degrees, certifications, or academic credentials.\n\nWe expect people to leave ego at the door, argue the technical case, make a decision, and then execute.\n\nWe are remote and distributed across time zones. Whether a role is an employment or a contract engagement depends on where you are, and we work that out at offer.\n\nHiring here is a few real conversations with the people you would actually work with, not a recruiter screen followed by a panel of strangers.\n\nWe are hiring across inference, infrastructure, and networking. The boundaries between the three are blurry on purpose. If you sit between two of them, say so.\n\nThis is an early-stage startup. The pace is high, the problems are hard, and the scope will change as we grow.\n\nCompensationCompetitive compensation plus meaningful equity. Exact structure will depend on location, engagement model, and experience.\nA Note For AgenciesWe are not using external recruiters or agencies for this role, and we will not be persuaded otherwise by an email. We do not want your spam. We will not read the CVs you send, we will not reply to your follow-up, and no candidate you put in front of us creates a fee obligation of any kind. Do not contact us.\nOriginally posted on Himalayas","description_format":"text","description_chars":8934,"description_truncated":false,"requirements":{"experience_years_min":null,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":["Equity"],"hiring_locations":[{"name":"United States","iso":"US","kind":"country"}],"hiring_excludes":[],"relocation_offered":false,"industries":[],"lifecycle":[{"event":"open","at":"2026-10-06T17:28:00Z"}],"visa":[],"liveness":{"score":86,"band":"hot","label":"Hiring now","p_open":1,"p_active":0.86,"p_room":1,"age_days":1,"expected_fill_days":28,"reasons":["seen:1","win:early"],"computed_at":"2026-10-08T05:49:30Z"},"pay":null,"html_url":"https://alion.io/job/stackyak-senior-network-engineer","json_url":"https://alion.io/job/stackyak-senior-network-engineer.json","meta":{"generated_at":"2026-10-09T04:00:16Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"crawler","counted_by":"address","units_charged":1,"used_today":3365,"day_limit":5000,"remaining_today":1635,"minute_limit":60,"resets_at":"2026-10-10T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.02,"usd":0.002,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":3905444},"rest":"https://alion.io/mcp/rest/get_company?id=3905444"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Fstackyak-senior-network-engineer"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"live","price":{"credits":1,"usd":0.1},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Fstackyak-senior-network-engineer"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.02,"usd":0.002},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Fstackyak-senior-network-engineer"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/stackyak-senior-network-engineer\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Fstackyak-senior-network-engineer"}]}