Network engineering for MSPs

Hire Remote Network Engineers for Client Cutovers and Firewall Work

A new client's cutover has a date, a change window and an ISP that may or may not show up. A remote network engineer, placed through Dokimo, builds and stages the configs, runs the window from a laptop and hands your on-site tech a clear list. The rack, the cable and the closet stay with a local person.

Tell us what you need

The half of a site cutover that never needs a truck

A network cutover is mostly paperwork and configuration long before anyone drives to the site. The firewall policy gets built and reviewed. The switch port map is written, the VLANs are agreed, the VPN peers and SD-WAN policies are staged, and a rollback plan exists in a form someone else could run at midnight. A remote network engineer does that half from a laptop, well before the window, and records it on the change ticket in your PSA.

During the window the engineer works the change remotely while your on-site tech, or a contact at the client, handles whatever needs hands: plugging in the staged firewall, moving a patch cable, reading the lights on a switch. The engineer stays on the console, watches the tunnels come up and runs the checks. Afterward the same person owns the cleanup: carrier tickets chased to a close, monitoring that someone reads, and diagrams that match what's actually on the wall.

The rack, the closet and the short spike: where this is the wrong answer

Anything physical stays local. Nobody remote is racking a firewall, running cable, swapping a failed transceiver, staging an appliance at a branch, or standing in a wiring closet at 2am. When a change needs a body in the room, the engineer directs a smart hands vendor, your on-site tech or a client contact, and doesn't do the work. If you have nobody local for those hours and no plan to get someone, fix that before you add a seat.

It's also the wrong answer for one-off projects. If you need someone for a campus rollout and then nothing, a project vendor is the better buy. The seat suits an MSP whose network work turns up every week: change requests, circuit turn-ups, VPN tickets, new clients to bring onto your standard. A seat takes time to recruit and ramp, so it doesn't suit a short spike.

Then there are the clients you keep with US staff. Whether a remote engineer may touch a client's network depends on that client's contract and data. You decide, with your counsel, and Dokimo fits the seat to your answer. A few environments are closed to anyone outside the US in practice, and Dokimo won't place an engineer on them: export-controlled defense data and criminal justice systems. Other limits are contract or insurance terms that vary.

Firewall admin is sensitive, so treat it that way

A firewall admin login is one of the most consequential accounts you hand out, and the decision about who gets it is yours, not Dokimo's. The safer pattern is a named account for the engineer, MFA, credentials held in your vault, session logging you can replay, and every change on your normal change record. Some clients restrict who can administer their perimeter, so read their agreements before the seat starts, and start on client sites you have already cleared.

Much of the seat suits remote work well: configuration review, rule cleanup, change planning, monitoring triage, wireless and site-to-site VPN design, and documentation. Keep the client-facing side with your US team, meaning the conversation about a client's risk, anything that needs a signature, and any network you keep US-only. Write that split down, so the engineer knows which changes to make and which to hand to you.

How a network seat is priced and tested

Network seats are priced by country and level: seats run from $3,100 a month in the Philippines and from $3,900 a month in Mexico, and the calculator on the pricing page shows the price for each level. The price pays the engineer and the employer costs local law requires, year-end pay included. Your MSP provides the licenses, as it does for its own techs. The skills test is real network work: a config to review for holes, a change to plan with a rollback, or an outage ticket to troubleshoot from a config export and logs.

Every candidate is tested on the real work before you meet them, which makes Dokimo slower than a firm that forwards resumes. That's deliberate, because the people you interview have already worked real network problems in a test. Dokimo won't quote a time to shortlist. The platforms, the hours and how narrow the skill list is decide it, and an invented date is a missed date later.

Month to month, with no long-term contract. One monthly invoice also covers the search and screening and the cost of employing the engineer in their own country through Dokimo's employer of record (EOR) partner, payroll included.

What you get

What the engagement covers, and what is optional

Firewalls, switching, wireless, VPN and SD-WAN

Rule hygiene, change planning and remote execution, site-to-site and remote-access VPN, SD-WAN policy and failover testing, and wireless design, all inside the platforms you run.

Cutover staging and remote change windows

Configs built and reviewed before the site visit, the window run from the console, and a clear handoff list for your on-site tech.

Carrier tickets and current diagrams

Circuit and ISP tickets chased to a close, monitoring triage, and network documentation kept current in your documentation platform.

Direction for the hands, not the hands

The engineer directs your on-site tech or a local vendor. Racking, cabling and device swaps stay with a person in the room.

Optional Productivity and Security Suite

An optional extra at $399 a month per person: a secure, US-hosted Microsoft Azure environment the person works inside, productivity monitoring that shows whether they are working at their station through the day (disclosed to the person and written into their agreement), security and onboarding for the digital workstation, and your reports in our client portal.

Questions

Frequently asked

Can a remote network engineer run a client site cutover?

The configuration and the change window, yes. The physical steps, no. A remote engineer builds and reviews the configs, runs the change from the console and tests the tunnels and failover. Someone on site has to plug in the appliance, run the cable and swap hardware, whether that's your on-site tech, a smart hands vendor or a contact at the client. Dokimo fits the seat to that split up front.

Which client firewalls can a remote network engineer administer?

That's your decision, set by your own agreements and your counsel, and it depends on each client's contract and data. Networks holding export-controlled defense data, and criminal justice systems, are effectively closed to an engineer outside the US, and Dokimo won't place one there. Most other limits are contract or insurance terms that vary, and some clients restrict sign-ins from outside the US. HIPAA doesn't itself ban work from outside the US, but health data brings agreements and a risk analysis. Nothing here is legal advice.

How is a network engineer tested before I interview them?

Every candidate is tested on the real work before you meet them. For network seats the test is a live piece of work, such as a firewall config to review or a cutover to plan with a rollback. Dokimo won't quote a time to shortlist, because the stack and the seat decide it.

Can I hire the network engineer directly later?

Yes, for a Tier 3 seat. Contract to hire and direct placement are available for Tier 3 technical and technical management seats only, so a Tier 3 network engineer can qualify. Either route ends with the person hired directly by your MSP. Ask us for direct placement terms, and raise it up front so your agreement reflects it.

Tell us what your clients' networks run on

Tell us the seat, the hours you need covered and the tools you run. We'll reply with questions and the next steps, not a pitch deck.