2

Remote Ran Engineer Jobs in Kansas (NOW HIRING)

$59K - $80K/yr

Remote, U.S. - based Department: GTM Ops The Opportunity Most companies treating AI as a ... the agent ran * Expand into adjacent internal functions (Finance, People, Security ops) as the ...

Remote Ran Engineer information

What are some common challenges Remote RAN Engineers face when troubleshooting network issues from a distance?

Remote RAN Engineers often encounter challenges such as limited physical access to on-site equipment, relying heavily on remote diagnostic tools and clear communication with local technicians. Effective troubleshooting requires strong analytical skills and familiarity with remote monitoring platforms, as well as the ability to interpret alarms and logs without physical context. Building good relationships with on-site teams and maintaining detailed documentation can help overcome these hurdles and ensure efficient problem resolution.

What is a Remote RAN Engineer?

A Remote RAN Engineer is a telecommunications professional who manages, optimizes, and troubleshoots Radio Access Network (RAN) equipment and infrastructure from a remote location. They are responsible for ensuring reliable wireless connectivity, performing network upgrades, and resolving technical issues without being physically present at the network site. This role typically involves working with various network technologies, monitoring system performance, and collaborating with on-site teams to maintain optimal network operations.

What are the key skills and qualifications needed to thrive as a Remote RAN Engineer, and why are they important?

To thrive as a Remote RAN Engineer, you need a strong understanding of wireless communication principles, cellular network architecture, and a relevant degree in telecommunications or engineering. Familiarity with network management tools, RAN optimization software, and certifications such as CCNA or vendor-specific credentials (e.g., Nokia, Ericsson) are typically required. Excellent problem-solving, analytical thinking, and effective remote communication skills set top performers apart. These competencies are crucial for ensuring optimal network performance, prompt issue resolution, and seamless collaboration across geographically dispersed teams.

What is the difference between Remote Ran Engineer vs Radio Network Engineer?

AspectRemote Ran EngineerRadio Network Engineer
CredentialsTelecom certifications, LTE/5G knowledgeTelecom certifications, RF engineering background
Work EnvironmentRemote, field, or office-basedFieldwork, office, or remote depending on project
Industry UsageTelecom providers, network vendorsTelecom providers, network vendors
Common Search IntentRemote network setup, optimization, troubleshootingNetwork design, RF planning, site surveys

Remote Ran Engineers focus on configuring, optimizing, and troubleshooting RAN components remotely, often working with LTE and 5G networks. Radio Network Engineers typically handle RF planning, site surveys, and physical network deployment, often in the field. While both roles require telecom certifications and RF knowledge, Remote Ran Engineers are more likely to work remotely on network performance, whereas Radio Network Engineers are more involved in physical network setup and RF design.

What are popular job titles related to Remote Ran Engineer jobs in Kansas? For Remote Ran Engineer jobs in Kansas, the most frequently searched job titles are:
Agent Systems Engineer, GTM & Internal Operations

Agent Systems Engineer, GTM & Internal Operations

Finite State

Remote

$59K - $80K/yr

Other

Posted 4 days ago


Job description

Location: Remote, U.S. - based 
Department: 
GTM Ops
The Opportunity

Most companies treating AI as a productivity tool are pointing it at individual jobs. We think the bigger opportunity is rebuilding entire processes around agents, starting with the part of the business where it matters most: how we go to market.

This is an internal Forward Deployed Engineer role with a GTM focus. You'll embed with Sales, Marketing, RevOps, and Customer Success to learn how revenue actually moves through Finite State, then rebuild those workflows as governed AI agents wired into the tools your stakeholders already use.

You'll be first in the seat, so you own both halves of the job: the process side (sitting with revenue leaders, mapping how the work really happens) and the build side (writing the code, wiring the systems, standing up the agents).

Responsibilities
  • Embed with revenue leaders across Sales, Marketing, RevOps, and CS to map workflows end-to-end, including the messy parts and human handoffs
  • Design and build AI agents for revenue-critical workflows: ICP research, account scoring, signal-based plays, outbound personalization, CRM hygiene, deal intelligence, churn risk, expansion triggers, lead routing
  • Integrate agents with our GTM stack via APIs, MCP servers, and custom connectors: Salesforce, HubSpot, Clay, LinkedIn Sales Navigator, Slack, our own product telemetry amongst other tools
  • Build signal pipelines that capture buying intent (hiring patterns, funding events, security disclosures, product usage) and trigger the right action automatically
  • Codify recurring revenue motions as reusable skills so the next agent doesn't start from scratch
  • Stand up the governance layer: permissions, audit trails, access controls, sensitive data handling, and rollback paths
  • Build evaluation harnesses that measure real business outcomes (pipeline generated, deals accelerated, rep hours saved), not just whether the agent ran
  • Expand into adjacent internal functions (Finance, People, Security ops) as the pattern proves out
Qualifications

Requirements

  • Strong engineering background with production code, APIs, auth, and data flow fluency
  • Hands-on experience building with LLMs and agent frameworks: tool use, retrieval, evals, prompt engineering, MCP, current-generation agent SDKs
  • Deep familiarity with the modern GTM stack: Salesforce or HubSpot at minimum, plus working knowledge of outbound sequencers, conversation intelligence, enrichment platforms, and product analytics
  • Process thinking: you map full workflows, edge cases, and human handoffs, and you have opinions about what should stay human
  • Self-directed on the business side: you can run discovery with a VP of Sales, define the process yourself, and ship a working v1 without a PM translating
  • Judgment about revenue work: you can tell the difference between something that drives pipeline and something that just looks good in a dashboard
  • Strong sense for security, governance, and risk
  • Comfort with ambiguity and broad cross-functional scope
Preferred Experience
  • Prior FDE, GTM Engineer, RevOps Engineer, solutions engineering, or sales engineering experience
  • Hands-on Clay experience at a serious depth
  • Familiarity with security buyer personas (CISOs, product security leaders, PSIRT teams)
Why This Role Matters

We believe governed AI agents change how serious work gets done. We prove it daily for our customers. Running our own GTM motion the same way is how we hold ourselves to the standard we're selling.

Across the industry, GTM teams are racing to bolt AI onto individual reps. We think the real unlock is engineering the revenue motion itself. The people who can do that work, spanning technical depth and revenue process fluency, will be valuable for a long time. You'd be the first inside Finite State.