2

Remote Next Js Developer Jobs in Kansas (NOW HIRING)

Remote, U.S. - based Department: GTM Ops The Opportunity Agent Systems Engineer is what we call ... Codify recurring patterns as reusable skills so the next agent doesn't start from scratch

... our next generation of AI-driven security products. This role requires significant hands-on ... You will champion engineering excellence, focusing on shipping fast, writing elegant, high-quality ...

... next success story. Lochner - learn more about us Your Impact: * Design of airport engineering ... Flexible Work Schedules (Hybrid or Remote, when possible) * Wellness Program for Physical and ...

Fully Remote* *Candidates can be located anywhere in the U.S* Job Summary: The Designer should have ... Modify drawings as directed by Design Coordinator, Engineer, or Designer What We Offer: * A ...

Location: Remote (U.S. or Canada) Type: US Applicants - Full-Time; Canadian Applicants ... next chapter of growth. We are a company of doers. Leaders roll up their sleeves, teams work flat ...

Mad Science Performer SWMO

Lenexa, KS · On-site +1

$30 - $45/hr

Driver's License and access to your own vehicle (Required) This is a remote position. Compensation ... Become part of our team and help us inspire the next generation of scientists and engineers. Our ...

Sr Electrical Designer

Lenexa, KS · Remote

$40 - $73/hr

Fully Remote Contract to hire position $40-$73/hr. DOE Experience working on duct banks, cable ... Responsibilities Utilize applicable engineering national and local codes Design duct bank, embedded ...

Roadway Design Engineer - Kansas City, KS

Lenexa, KS · On-site +1

$72K - $88K/yr

... next success story. Lochner - learn more about us Your impact: * Experienced in the design of ... Flexible Work Schedules (Hybrid or Remote, when possible) * Wellness Program for Physical and ...

next page

Showing results 1-20

Remote Next Js Developer information

What is the difference between Remote Next Js Developer vs Remote React Developer?

AspectRemote Next Js DeveloperRemote React Developer
Required SkillsNext.js, React, JavaScript, HTML, CSS, API integrationReact, JavaScript, HTML, CSS, API integration
Work EnvironmentRemote, collaborative teams, web development projectsRemote, web development teams, UI/UX focus
Industry UsageWeb applications, server-side rendering, static site generationSingle-page applications, UI components, client-side rendering

Remote Next Js Developers specialize in server-side rendering and static site generation using Next.js, while Remote React Developers focus on building interactive UI components with React. Both roles often share skills like JavaScript and API integration, but Next.js developers typically work on more SEO-friendly, performance-optimized websites. The choice depends on whether the project requires server-side rendering or client-side UI development.

What are the key skills and qualifications needed to thrive as a Remote Next Js Developer, and why are they important?

To thrive as a Remote Next Js Developer, you need strong proficiency in JavaScript, React, and Next.js, usually backed by a degree in computer science or relevant experience. Familiarity with version control systems like Git, cloud services such as Vercel or AWS, and testing frameworks is typically required. Excellent problem-solving, self-motivation, and clear communication skills help remote developers collaborate and deliver high-quality solutions independently. These skills ensure efficient project delivery, maintainable code, and effective teamwork in a distributed work environment.

What is a Remote Next.js Developer?

A Remote Next.js Developer is a software engineer who specializes in building web applications using the Next.js framework, typically working from a location outside of a traditional office environment. Next.js is a popular React framework that enables server-side rendering, static site generation, and other advanced features for creating fast and scalable web applications. Remote developers in this role collaborate with teams via online tools, write and maintain code, troubleshoot issues, and implement new features. This position allows professionals to work for companies worldwide without needing to relocate, offering flexibility and a better work-life balance.

How do Remote Next.js Developers typically collaborate with team members on projects?

Remote Next.js Developers commonly collaborate using a mix of asynchronous and real-time tools such as Slack, Jira, and GitHub. Daily stand-ups or weekly sprint meetings over video calls help align priorities and clarify any blockers. Code reviews and pull requests are essential for maintaining code quality and fostering team learning. Effective written communication and proactive status updates are crucial since the team is distributed, ensuring everyone stays on the same page and project timelines are met.
What are the most commonly searched types of Next Js Developer jobs in Kansas? The most popular types of Next Js Developer jobs in Kansas are:
What are popular job titles related to Remote Next Js Developer jobs in Kansas? For Remote Next Js Developer jobs in Kansas, the most frequently searched job titles are:
What job categories do people searching Remote Next Js Developer jobs in Kansas look for? The top searched job categories for Remote Next Js Developer jobs in Kansas are:
What cities in Kansas are hiring for Remote Next Js Developer jobs? Cities in Kansas with the most Remote Next Js Developer job openings:
Agent Systems Engineer, GTM & Internal Operations

Agent Systems Engineer, GTM & Internal Operations

Finite State

Remote

Other

Posted 21 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Â