2

Remote Content Writing Jobs in Kansas (NOW HIRING)

Remote, U.S. - based Department: GTM Ops The Opportunity Agent Systems Engineer is what we call ... You write SQL fluently. You live in APIs. You've shipped production GTM automation that other ...

And we do it with a completely remote team. Imagine working alongside global innovators to build AI ... Create and shape thought leadership in collaboration with Content Marketing, including bylines, op ...

... showrooms, branded content, and more - generating $750M in revenue in 2025. Building the ... Our Ways of Working Babylist is remote-first with team members across the U.S. and Canada who move ...

next page

Showing results 1-20

Remote Content Writing information

See Kansas salary details

$12

$36

$88

How much do remote content writing jobs pay per hour?

As of Jun 26, 2026, the average hourly pay for remote content writing in Kansas is $36.08, according to ZipRecruiter salary data. Most workers in this role earn between $21.01 and $41.39 per hour, depending on experience, location, and employer.

What is a Remote Content Writing job?

A Remote Content Writing job involves creating written content such as articles, blogs, web copy, or marketing materials for clients or companies while working from a remote location. Writers may work as freelancers, full-time employees, or contractors. Strong writing skills, research abilities, and SEO knowledge are often required. This role offers flexibility in work hours and location, making it an attractive option for those who prefer remote work.

What are some common challenges faced by remote content writers and how can they be overcome?

Remote content writers often face challenges such as staying motivated without in-person supervision, managing multiple deadlines, and maintaining effective communication with editors and other team members. To overcome these, it’s important to establish a structured daily routine, regularly check in with your team via project management tools or video calls, and use productivity apps to track your progress. Actively seeking feedback and clarifying project expectations can also help prevent misunderstandings and improve the quality of your work. Successful remote writers develop strong self-discipline and prioritize continuous learning to adapt to changing content requirements.

What are the key skills and qualifications needed to thrive in the Remote Content Writing position, and why are they important?

To thrive as a Remote Content Writer, you should have excellent writing, research, and editing skills, often supported by a degree in English, journalism, or a related field. Familiarity with content management systems (such as WordPress), SEO tools, and basic image editing software is commonly expected. Strong self-motivation, time management, and communication skills help distinguish top performers in remote settings. These abilities are crucial for producing high-quality, engaging content while meeting deadlines and collaborating efficiently across distributed teams.

What are the most commonly searched types of Content Writing jobs in Kansas? The most popular types of Content Writing jobs in Kansas are:
What are popular job titles related to Remote Content Writing jobs in Kansas? For Remote Content Writing jobs in Kansas, the most frequently searched job titles are:
What cities in Kansas are hiring for Remote Content Writing jobs? Cities in Kansas with the most Remote Content Writing job openings:
Agent Systems Engineer, GTM & Internal Operations

Agent Systems Engineer, GTM & Internal Operations

Finite State

Remote

Other

Posted 25 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