ECH Field Engineer

Description

The Field Engineer is accountable for implementing a 911 call handling system to the site design. That covers on‑site configuration, testing, cutover, and post‑cutover support.

This is a rotating‑project role. The engineer moves from site to site on a continual basis rather than staying on one long‑term project. The work is on live public safety systems where errors carry real consequences, so a methodical, communicative engineer matters more than any single technology.

Current focus is VESTA 911 (on‑prem). VESTA NXT (cloud) is a future direction, and cloud work today is limited.

Work Environment

Location:

Remote. Candidates can be located anywhere in the US. Regional coverage (east or west) and proximity to a major airport are preferred.

Travel:
More than 75%. Typically Monday to Friday, every week or every other week, with occasional Sunday travel. Sites range from standard to remote, for example Alaska.

Hours:

Hourly with overtime. Model at about 47 hours per week on average. Long days are normal, and some run until midnight when a cutover is urgent.

Site Duration: A full site configuration typically takes days to a full week, not a single day.

Work Setting:
Server rooms and customer sites, working alongside customers, channel partners, and the internal support team.

Site Access: A 7‑year CBG check is completed up front. Site‑specific checks and fingerprinting are handled locally, often through the local police department.

Reporting: ECH Field Engineer Manager, with a dotted line to a TGS Engagement Manager.

Key Responsibilities

System configuration for assigned ECH solutions:
Works through the site configuration checklist including servers (VMs on a hypervisor), Cisco switches, telephony gateways, and Windows 10/11 console positions. Must be hands‑on and independent, following the checklist and managing the process with support from internal configuration engineers and chat groups.

Site verification testing before cutover:
Checks system health and confirms connectivity between servers, console positions, and gateways. Validates the build against the design. Must be methodical and thorough and cannot skip steps on a live 911 system.

Gateway and telephony configuration:
Configures FXO/FXS and SIP gateways, with occasional PRI and T1. Requires working knowledge of VoIP/SIP and gateways, but not telephony architect‑level expertise.

Customer and channel partner support during deployment:
Checks in with the site contact, explains the work, and aligns on call flow and expectations as deployment progresses. Must be a confident, clear communicator who can engage customers and partners directly.

Documentation of all changes:
Updates the Post Sales Document (PSD) when the customer’s call‑flow needs differ from the original design and communicates changes to the team. Must be disciplined and consistent so changes can be traced and issues resolved quickly.

Resolve installation and quality issues:
Troubleshoots with Wireshark where possible and escalates to support teams and SMEs when needed. Requires systematic troubleshooting, knowing when to ask for help, and staying calm under pressure.

Methods of Procedure (MOP):
Contributes to MOPs for the VMware to Red Hat KVM migration and Windows Server refresh from 2019 to 2022. Expected to participate and execute. Authoring MOPs is not the expectation and should be validated.

Cloud connectivity and cloud‑native SME skills:
Cloud services connect into VESTA 911, but day‑to‑day cloud work is minimal. Awareness only is sufficient and can be taught on the job.

Skills

deployment, telephony, networking, windows servers, troubleshooting, sip, voip, layer 2, cisco, intergration, field engineering, customer facing, public service, ECH, Red Hat, KVM, PBX, Linus,…