1

Book Publishing Software Developer Jobs in Edmond, OK

... publishing of spatial data. Collaborate with land, operations, and engineering teams to ensure GIS ... software vendors to ensure quality and value. * GIS Strategy Partners with Technology and the ...

Licensed as a Professional Engineer (PE) * Six (8) to twelve (15) years of relevant experience ... Experience with Microstation, OpenRoads Designer or InRoads and/or other roadway design software

Licensed as a Professional Engineer (PE) * Six (8) to twelve (15) years of relevant experience ... Experience with Microstation, OpenRoads Designer or InRoads and/or other roadway design software

Are you an Engineering leader who is successfully delivering major Transportation projects for ... Green Book, the Roadside Design Guide, the Highway Capacity Manual (HCM), and the Manual Uniform ...

next page

Showing results 1-20

Book Publishing Software Developer information

See Edmond, OK salary details

$43.4K

$101.1K

$150K

How much do book publishing software developer jobs pay per year?

As of Jul 30, 2026, the average yearly pay for book publishing software developer in Edmond, OK is $101,053.00, according to ZipRecruiter salary data. Most workers in this role earn between $81,300.00 and $117,500.00 per year, depending on experience, location, and employer.

What is the difference between Book Publishing Software Developer vs Book Editor?

AspectBook Publishing Software DeveloperBook Editor
Primary RoleDevelops and maintains software tools for publishingReviews, revises, and improves written content
Skills RequiredProgramming, software engineering, knowledge of publishing workflowsEditing, language proficiency, content organization
Work EnvironmentTech companies, publishing software firms, remote or office-basedPublishing houses, freelance, editorial teams
Common Industry UsageTechnology-driven publishing projectsContent creation and quality control

The main difference is that Book Publishing Software Developers focus on creating and maintaining the digital tools used in publishing, while Book Editors concentrate on refining and improving the content itself. Both roles are essential in the publishing industry but serve different functions related to technology and content quality.

What are the key skills and qualifications needed to thrive as a Book Publishing Software Developer, and why are they important?

To thrive as a Book Publishing Software Developer, you need strong programming skills (such as Python, Java, or C#), experience in software development, and often a degree in computer science or a related field. Familiarity with publishing-specific tools like Adobe InDesign, XML workflows, content management systems (CMS), and version control systems (e.g., Git) is typically required. Excellent problem-solving, collaboration, and communication skills help developers understand publisher needs and work effectively with cross-functional teams. These skills ensure the creation of robust, user-friendly software that streamlines the publishing process and meets industry standards.

What are Book Publishing Software Developers?

Book Publishing Software Developers are professionals who design, develop, and maintain software applications specifically for the book publishing industry. They create tools that help publishers manage manuscripts, automate workflows, format content for print and digital platforms, and track sales or distribution. These developers often work with publishing standards like EPUB, PDF, and XML, and collaborate with editors, designers, and production teams to streamline the publication process. Their work ensures that publishers can efficiently produce and distribute books in various formats while maintaining high quality.

How do Book Publishing Software Developers typically collaborate with editors and designers during the development process?

Book Publishing Software Developers frequently work closely with editors and designers to understand workflow requirements, digital formatting standards, and user-interface needs. This collaboration often involves gathering feedback on prototypes, troubleshooting layout or conversion issues, and integrating editorial tools that streamline content management. Effective communication and agile development practices are essential, as developers must adapt to changing publishing trends and ensure the software supports both creative and production teams efficiently. Regular cross-functional meetings and iterative feedback loops help ensure the final product aligns with the needs of all stakeholders.
What are popular job titles related to Book Publishing Software Developer jobs in Edmond, OK? For Book Publishing Software Developer jobs in Edmond, OK, the most frequently searched job titles are:
Infographic showing various Book Publishing Software Developer job openings in Edmond, OK as of July 2026, with employment types broken down into 74% Full Time, 11% Part Time, 3% Temporary, and 12% Contract. Highlights an 91% In-person, 3% Hybrid, and 6% Remote job distribution, with an average salary of $101,053 per year, or $48.6 per hour.

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Oklahoma City, OK โ€ข Remote

$99K - $130K/yr

Full-time

Posted 15 days ago


Job description

Senior Software Engineer: Applied AI (Voice Agents & ML Systems)

AMC Health ยท Remote (US) ยท Full-time

The pitch

We build and operate production AI voice agents that hold real phone conversations in a regulated healthcare setting, plus the machine learning and LLM pipelines around them. This is one seat that spans four disciplines that rarely come together: real-time systems, LLM engineering, traditional machine learning, and serious cloud infrastructure, all in production, all with real consequences. If you are the kind of engineer who gets restless doing one thing, this role is the opposite problem.

What you'll work across

Real-time voice AI

  • Streaming, low-latency speech-to-speech systems built on modern LLMs
  • Telephony and real-time media (call control, live audio streaming)
  • Audio handling and the quirks of real human conversation (interruptions, timing, noise)
  • Concurrency on a latency-sensitive path, where p99 matters and a stall is something a caller hears

LLM engineering

  • Wrapping nondeterministic models in deterministic control so they behave reliably in production
  • Multi-model pipelines, prompt design, and cost/latency budgeting
  • Evaluation harnesses, including LLM-as-judge and automated agent-tests-agent approaches
  • Agentic tooling that gives AI systems safe, structured access to infrastructure

Traditional (non-LLM) machine learning

  • End-to-end ML pipelines: feature engineering, model training, and scheduled inference
  • Imbalanced, messy real-world data; calibration and explainability for non-technical consumers
  • Turning research notebooks into reproducible, auditable production pipelines

Cloud and infrastructure

  • Infrastructure as code across multiple environments (we run on AWS)
  • Managed compute, data, streaming, and orchestration services
  • Security engineering in a regulated setting: encryption, least-privilege access, strict data-handling discipline
  • Observability and telemetry-driven debugging, tracing a production issue from a metric anomaly to root cause

Plus occasional full-stack work on internal tools, and an engineering workflow that leans heavily on AI coding assistants, with human accountability for every change.

What you'll actually do

  • Ship and debug code on a live, real-time voice pipeline where latency and correctness are user-facing
  • Design control systems around LLMs: guardrails, budgets, watchdogs, safe fallbacks
  • Build and operate LLM evaluation and batch-analysis pipelines
  • Own traditional ML workflows from data to scheduled production inference
  • Trace production issues from a metric anomaly to root cause, including building the evidence when the cause is a vendor

Must-haves

  • 7+ years building and operating production backend systems, with strong general-purpose programming skills (we work primarily in Python)
  • Experience running distributed systems in the cloud; comfortable debugging from telemetry to root cause
  • Hands-on production experience with LLMs or generative AI (any provider or framework), plus the judgment to know when not to use a model
  • Working fluency across the traditional machine learning lifecycle (you productionize; you do not need to publish)
  • Disciplined in a regulated environment: small, reviewable changes and careful handling of sensitive data

Nice-to-haves

  • Real-time media or telephony experience
  • Front-end / full-stack ability
  • ML pipeline experience, vector search, or embeddings
  • Fluency with AI coding assistants (our workflows assume them, with human accountability for every change)

How we work

Smallest correct change wins. Every behavior change is validated against the live system. Evidence over opinion in debugging. Code review is rigorous. Safety and privacy gate everything.

Work authorization (no exceptions)

This role is open only to US citizens and lawful permanent residents (Green Card holders). We cannot consider candidates who require visa sponsorship now or in the future, and we are unable to make exceptions of any kind.

How to apply

Please submit both of the following:

  • Your LinkedIn profile URL
  • A phone number where we can reach you

A resume is welcome but optional; the two items above are required.