2

Remote Windows Systems Engineer Jobs in Kansas (NOW HIRING)

Remote, U.S. - based Department: GTM Ops The Opportunity Agent Systems Engineer is what we call this role. You may know it as GTM Engineer, Revenue Systems Engineer, Growth Engineer, or internal ...

We are flexible on remote work from home if you are located in the USA and reside in one of the ... Proficiency in Windows environments (registry, services, performance troubleshooting)

We're looking for a Senior Systems Integrator (EMV) Location: United States - Field/Remote This ... Windows/Linux servers. * Competence in scripting/programming (PowerShell, Python, JavaScript, SQL ...

As a Remote Geotechnical Engineer, you will perform geotechnical engineering design, project ... bonus system that rewards performance. Olsson is an Equal Opportunity Employer. We encourage ...

Location - We are flexible on remote working from home, if you are located in the USA and reside in ... Windows, Mac, and Linux. * 3+ years of experience scripting in PowerShell (Bash or Python a plus)

Oracle Solutions Consultant

Topeka, KS · On-site +1

$59.75 - $75.25/hr

... and programming, software engineering, systems development, testing, integration, and ... Potential for remote work with travel for the right candidate. Required Qualifications: 4+ years of ...

$100K - $120K/yr

US, Canada (Remote) Employment Type: Full-time About Altera Altera, a member of the N. Harris ... Expert knowledge of Linux and Windows operating systems. * Experience in security engineering ...

$100K - $120K/yr

US, Canada (Remote) Employment Type: Full-time About Altera Altera, a member of the N. Harris ... Expert knowledge of Linux and Windows operating systems. * Experience in security engineering ...

next page

Showing results 1-20

Remote Windows Systems Engineer information

What are some common challenges faced by Remote Windows Systems Engineers, and how can they be effectively managed?

Remote Windows Systems Engineers often encounter challenges such as troubleshooting complex system issues without direct physical access, ensuring secure remote connectivity, and coordinating across distributed teams and time zones. Effective management of these challenges involves utilizing robust remote monitoring and management tools, maintaining clear and regular communication with colleagues, and following best practices for system security and documentation. Staying proactive with updates and leveraging collaboration platforms can significantly enhance productivity and reduce downtime.

What is the difference between Remote Windows Systems Engineer vs Remote Network Administrator?

AspectRemote Windows Systems EngineerRemote Network Administrator
CertificationsMicrosoft Certified: Windows Server, CompTIA Network+Cisco CCNA, CompTIA Network+
Work EnvironmentManaging Windows servers, troubleshooting OS issues, deploying updatesConfiguring and maintaining network infrastructure, monitoring network performance
Industry UsageIT, technology, enterprise environmentsIT, telecommunications, service providers
Search IntentFocus on Windows server management and supportFocus on network infrastructure and connectivity

The Remote Windows Systems Engineer primarily manages and supports Windows server environments, ensuring system stability and security. In contrast, the Remote Network Administrator focuses on maintaining network infrastructure, including routers, switches, and connectivity. While both roles require networking knowledge and certifications, their core responsibilities differ, with the Systems Engineer centered on Windows OS and server management, and the Network Administrator on network hardware and connectivity.

What does a Remote Windows Systems Engineer do?

A Remote Windows Systems Engineer is responsible for designing, implementing, and maintaining Windows-based server environments from a remote location. They manage tasks such as installing updates, configuring security settings, troubleshooting technical issues, and ensuring system performance and reliability. These engineers often work with cloud platforms, virtualization technologies, and collaborate with IT teams to support business operations. Their remote role allows them to provide support and maintenance without being physically present on-site.

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

To thrive as a Remote Windows Systems Engineer, you need expertise in Windows Server administration, system troubleshooting, and network protocols, often backed by a degree in IT or computer science and certifications like Microsoft Certified: Windows Server Hybrid Administrator Associate. Familiarity with tools such as Active Directory, PowerShell, virtualization platforms, and remote management software is essential. Strong problem-solving abilities, effective communication, and self-motivation are critical soft skills for managing systems and collaborating virtually. These skills ensure secure, reliable system operations and efficient remote support in distributed IT environments.
What are popular job titles related to Remote Windows Systems Engineer jobs in Kansas? For Remote Windows Systems Engineer jobs in Kansas, the most frequently searched job titles are:
What cities in Kansas are hiring for Remote Windows Systems Engineer jobs? Cities in Kansas with the most Remote Windows Systems Engineer job openings:
Agent Systems Engineer, GTM & Internal Operations

Agent Systems Engineer, GTM & Internal Operations

Finite State

Remote

Other

Re-posted 8 days ago


Job description

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

Agent Systems Engineer is what we call this role. You may know it as GTM Engineer, Revenue Systems Engineer, Growth Engineer, or internal Forward Deployed Engineer. The substance is the same. You're a deeply technical operator who embeds with revenue teams, learns how the business actually moves, and rebuilds workflows as governed, AI-augmented systems.

You write SQL fluently. You live in APIs. You've shipped production GTM automation that other people depend on. You know what good revenue data architecture looks like (warehouse as source of truth, modeled in dbt, activated into Salesforce and the rest of the stack via Reverse ETL) and you have opinions about why most companies get it wrong.

You also believe in practical AI. You've deployed LLMs against real GTM problems where the business value was concrete (account research, classification, enrichment, content generation), and you have honest views about what worked, what didn't, and where the hype outpaces reality.

Most companies treating AI as a productivity tool are pointing it at individual jobs. We think the bigger opportunity is rebuilding entire revenue processes around agents and modern data infrastructure. We sell that thesis to product security teams every day. Running our own GTM motion the same way is how we hold ourselves to the standard we're selling.

You'd be first in seat at Finite State, so you own the full motion: discovery with revenue leaders, system design, build, governance, evaluation, rollout, and the runbook so it survives you.

Responsibilities
  • Run discovery with revenue leaders before building. Sit in pipeline reviews. Watch a deal cycle end-to-end. Find the actual time sinks before designing a solution
  • Architect the GTM data layer: Snowflake (or equivalent) as source of truth, dbt for modeling, Reverse ETL (Hightouch, Census) for activation into Salesforce, HubSpot, Outreach, and the rest of the stack
  • Design and build AI agents and AI-augmented workflows for revenue-critical work: account research, ICP scoring, signal-based plays, outbound personalization, CRM enrichment, deal intelligence, churn risk, expansion triggers, lead routing
  • Deploy LLMs and agents where they add real business value, and skip them where they don't. We're not interested in AI for the sake of AI
  • Wire agents and systems together via APIs, webhooks, MCP servers, and lightweight code (Python, SQL, TypeScript). Use platforms like Clay, n8n, Workato, or Hightouch AI when they fit. Build custom when they don't
  • Build signal pipelines that capture buying intent (hiring patterns, funding events, security disclosures, product telemetry from our own platform) and trigger the right agent or action automatically
  • Stand up the governance layer for every agent you ship: 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
  • Codify recurring patterns as reusable skills so the next agent doesn't start from scratch
  • Document the architecture and write the runbook so the next person on the team can learn from your work
  • Expand into adjacent functions (Finance, People, Security ops) as the pattern proves out
Qualifications

Required

  • 5+ years in RevOps, Growth Ops, GTM Engineering, Sales Engineering, or Solutions Engineering, with production work that other people relied on
  • Strong technical chops: fluent SQL, comfortable in Python or TypeScript, lives in APIs and webhooks, reasons cleanly about data flow and auth
  • Modern data stack experience in production: warehouse (Snowflake, BigQuery), transformation (dbt), Reverse ETL (Hightouch, Census). You've shipped this, not just read about it
  • Deep Salesforce or HubSpot. Custom objects, schema design, sync logic, the limits and workarounds. You have battle scars
  • Working knowledge of the modern GTM stack: Outreach or Salesloft, Gong, ZoomInfo, Clay, Apollo, LinkedIn Sales Navigator, product analytics
  • Production experience deploying LLMs and AI agents in GTM workflows. You don't need to have built agent frameworks from scratch. You do need to have shipped something real and have informed views about what worked
  • Discovery instincts. You sit with the people doing the work before building. You ask the right questions and find the actual problem
  • Process thinking. You map full workflows including the messy human handoffs and have opinions about what should stay human
  • 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. This matters double at a product security company touching customer and prospect data
  • Self-directed. You can run a stakeholder conversation, define the process, and ship a v1 without a PM translating for you

Nice to have

  • Reverse ETL, CDP, or growth platform experience (Hightouch, Census, Segment, Rudderstack)
  • Hands-on experience with modern agent frameworks, MCP servers, evals, or current-generation agent SDKs
  • Prior work supporting a PLG motion or a sales-led-to-PLG transition
  • Public writing about your work (blog, Substack, talks). We value people who can explain their thinking
  • Familiarity with security buyer personas (CISOs, product security leaders, PSIRT teams)
Why This Role Matters

GTM teams across the industry are racing to bolt AI onto individual reps. We think the real unlock is engineering the revenue motion itself, with agents at the core and modern data infrastructure underneath. The people who can do that work, spanning technical depth, modern data fluency, and revenue process judgment, will be valuable for a long time.

You'd be the first inside Finite State.

Compensation
Our salary ranges are based on experience and geographic location:
  • $192,000 - $230,000Â