1

Content Developer Jobs in Minnesota (NOW HIRING)

Qualifications Ecommerce, web content writing experience a must and not multimedia/graphics/designing Additional Information All your information will be kept confidential according to EEO guidelines.

Java Developer

Minneapolis, MN · On-site

$53.25 - $69/hr

... Content Development, Software Debugging The position is Full-Time Permanent salaried with benefits. Our benefits include an attractive compensation package, bonus programs, health, and dental plans ...

next page

Showing results 1-20

Content Developer information

See Minnesota salary details

$28.9K

$114.2K

$126.3K

How much do content developer jobs pay per year?

As of Jul 13, 2026, the average yearly pay for content developer in Minnesota is $114,215.00, according to ZipRecruiter salary data. Most workers in this role earn between $120,500.00 and $125,400.00 per year, depending on experience, location, and employer.

What is the difference between Content Developer vs Content Writer?

AspectContent DeveloperContent Writer
CredentialsTypically requires a degree in communications, marketing, or related fields; may include certifications in content management or digital marketingOften requires a degree in English, journalism, or related fields; certifications are less common
Work EnvironmentCollaborates with designers, marketers, and developers in digital or print media projectsFocuses on writing articles, blogs, or scripts, often independently or with editors
Employer & Industry UsageUsed across marketing, advertising, media, and corporate sectorsCommon in publishing, media outlets, and online content platforms

While both roles involve creating content, a Content Developer typically manages the entire content creation process, including planning, designing, and implementing content strategies. A Content Writer primarily focuses on producing written material. Understanding these differences helps in choosing the right career path or job search focus.

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

To thrive as a Content Developer, you need strong writing, research, and editing skills, often supported by a degree in communications, English, or a related field. Familiarity with content management systems (CMS), SEO tools, and basic graphic design software is typically required. Creativity, attention to detail, and the ability to adapt tone and style for different audiences are valuable soft skills. These competencies ensure the creation of engaging, accurate, and effective content that meets organizational goals and audience expectations.

What does a Content Developer do?

A Content Developer is responsible for creating, editing, and managing written, visual, or multimedia content for websites, social media, e-learning platforms, or other digital channels. They work closely with subject matter experts and marketing teams to ensure the content is engaging, accurate, and aligned with brand messaging. Content Developers often use various tools and software to format and publish content, optimize it for search engines, and analyze its performance. Their goal is to attract, inform, and retain audiences by delivering valuable and high-quality content.

How does a Content Developer typically collaborate with subject matter experts and other team members?

Content Developers frequently work closely with subject matter experts (SMEs), designers, and marketing teams to ensure that content is both accurate and engaging. This collaboration often involves gathering detailed information from SMEs, participating in brainstorming sessions, and incorporating feedback during content revisions. Effective communication and a collaborative mindset are essential, as Content Developers are usually expected to manage multiple projects simultaneously while aligning with wider team goals and deadlines.

What Is a Content Developer?

A content developer creates information for web pages and online marketing. Job duties include the development and editing of articles, blogs, ad copy, and social media posts. A content developer may also create graphics, use photos, and work on web page layout. Qualifications for a content developer include strong writing skills and familiarity with web development software.

What are the most commonly searched types of Content Developer jobs in Minnesota? The most popular types of Content Developer jobs in Minnesota are:
What are popular job titles related to Content Developer jobs in Minnesota? For Content Developer jobs in Minnesota, the most frequently searched job titles are:
What are popular job titles related to Content Developer jobs in MN? For Content Developer jobs in MN, the most frequently searched job titles are:
Infographic showing various Content Developer job openings in Minnesota as of July 2026, with employment types broken down into 43% Full Time, 43% Part Time, and 14% Contract. Highlights an 71% In-person, and 29% Remote job distribution, with an average salary of $114,215 per year, or $54.9 per hour.
Staff Software Engineer - Search Platform, Ingestion & Indexing

Staff Software Engineer - Search Platform, Ingestion & Indexing

THOMSON REUTERS

Eagan, MN

Full-time

Re-posted 8 hours ago


Thomson Reuters rating

8.9

Company rating: 8.9 out of 10

Based on 19 frontline employees who took The Breakroom Quiz

25th of 449 rated business services


Job description

This posting is for proactive recruitment purposes and may be used to fill current openings or future vacancies within our organization.

Overview of the Role

Advanced Content Engineering (ACE) is seeking a Staff Software Engineer to serve as the technical anchor for the search platform's ingestion and indexing systems. The platform processes millions of documents across TR's legal, tax, and professional content corpora - parsing, chunking, enriching, embedding, and indexing them into a hybrid search engine that powers both human-facing search interfaces and autonomous AI agents. Getting this pipeline right, at scale, with zero-downtime operations and increasingly agentic retrieval patterns, is one of the platform's most consequential engineering challenges.

This role owns the design, implementation, and operational health of the document ingestion pipeline and search index management systems - from the Kafka-based streaming infrastructure that moves documents through processing stages, to the Vespa application architecture that stores and serves them. Staff Engineers on this team define, build, test, deploy, scale, and operate what they ship - full-stack ownership is not a principle we aspire to, it is the daily reality. AI-assisted development is the team norm, not the exception, and constant delivery to production is the expectation. This is a role for someone who sets architectural boundaries, not just executes within them

About the Role

In this position, you will focus on:

Ingestion Pipeline Architecture & Engineering

Plan, design, develop, and own the end-to-end document ingestion pipeline - a Kafka-based stream processing architecture that moves documents through parsing, chunking, enrichment (entity extraction, embedding generation, metadata enrichment), and indexing stages - including all fault tolerance, version ordering, and at-least-once delivery guarantees

Architect and implement pluggable, configurable pipeline components (parsers, chunkers, enrichers, indexers) that client teams can assemble into custom topologies via the platform's self-service APIs, while maintaining reliable, observable, and performant execution

Own the platform's Protobuf-based document schema and schema registry integration - establishing schema governance standards, enforcing backward-compatible evolution, and ensuring reliable serialization across all pipeline stages

Design and implement dual-flow ingestion: a high-throughput batch path for full reindexing and a low-latency incremental path for real-time document updates, with strong guarantees around document version ordering and idempotent processing

Lead the migration of ingestion infrastructure from OpenSearch to Vespa, including design of Vespa document processors, custom Kafka feeders, and application package architecture - resolving complex technical challenges that have little or no precedent within the team

Custom Model Operationalization

Own the end-to-end lifecycle for custom models integrated into the ingestion pipeline - re-ranking models, embedding models, and enrichment components - including inference serving behind a stable API surface, latency SLO management, hardware and runtime configuration (batching, quantization), and scaling

Build and operate the model promotion pipeline: the CI/CD workflow that moves a model artifact from the fine-tuning team through staging to production, including versioning, canary rollouts, and rollback mechanisms - ensuring the platform team can operate model updates independently without depending on the research team for production changes

Define and maintain integration contracts between custom models and downstream pipeline components - governing input/output schemas, compatibility requirements, and the governance process for model updates that ensures search pipeline consumers are not broken by changes upstream

Instrument model serving for production observability: latency distributions, throughput, error rates, and quality signals such as re-ranking score distributions - enabling the team to detect regressions or model drift without requiring the fine-tuning team's involvement

Search Engine & Index Management

Own the search engine layer end-to-end: design and operate Vespa (and OpenSearch during transition) index configurations, ranking profiles, schema definitions, and application package lifecycle management - applying architectural principles that scale to the platform's long-term content and tenancy goals

Build and operate zero-downtime index management: shadow indexing, blue/green index promotion, and rolling reindex workflows that keep the platform available during major infrastructure changes

Implement and maintain the Component Registry and Index Registry - the platform's catalog of reusable processing components and active index configurations - with a focus on correctness, observability, and safe concurrent modification

Develop the full-reindex and incremental-update orchestration logic, including change detection, document tracking, Kafka topic management, and DynamoDB-backed state management

Agentic Search Infrastructure

Design ingestion and indexing infrastructure with agentic retrieval patterns as a first-class concern - including explicit latency budgets per retrieval hop, chunking and result compression strategies optimized for token economy in context windows, and index boundary definitions that give agents clean, predictable tool contracts

Build trace-level observability into the retrieval stack that captures which tools were called, in what order, and with what inputs - enabling reliable diagnosis and reproduction of failures in non-deterministic agentic retrieval paths

Design session state and cache invalidation patterns for multi-turn agentic search: reasoning carefully about cache validity windows, session state scope (per-user, per-session, per-query), and mechanisms to prevent stale context from corrupting downstream agent responses

Evaluation & Search Quality

Build and own the integration between the ingestion pipeline and the platform's offline evaluation framework - ensuring that experiment runs produce query/result outputs that feed seamlessly into the search grading tool, supporting gold test set maintenance, LLM-as-judge evaluation, and side-by-side ranking comparison across pipeline versions

Instrument the query and retrieval stack for online analytics: real-time query latency and throughput monitoring, query log collection for session analysis, and the infrastructure to support A/B and interleaved ranking experiments in production - generating the signals that connect low-level search metrics to downstream product KPIs

Partner with TR Labs and research scientists to ensure that new search components can be evaluated in isolation - with automated offline evaluation on every build and a clear path from evaluation results to production promotion decisions

Reliability & Operational Ownership

Take full operational responsibility for ingestion and indexing infrastructure: define SLOs, set measurable goals and meet them, build and maintain CloudWatch dashboards and alarms, and participate in on-call rotations - you built it, you own it, you run it

Treat delivery friction as the enemy: identify and remove obstacles that slow the team's ability to ship ingestion and indexing changes to production safely and frequently - improving CI/CD pipelines, deployment automation, and local development workflows as a standing priority

Instrument pipeline components with distributed tracing, structured logging, and rich metrics - establishing documentation standards and knowledge

management practices so that the team and platform consumers can understand system behavior at all times

Design and implement resilient fault tolerance mechanisms - dead-letter queues, retry strategies with exponential backoff, circuit breakers, consumer lag monitoring - that make the pipeline robust to downstream failures and transient errors

Drive system-level performance architecture: profiling ingestion throughput and indexing latency, identifying bottlenecks, and implementing optimizations that meet platform SLOs under peak load

Technical Leadership

Serve as the team's deepest technical authority on document processing pipelines and search engine internals - guiding architectural decisions, resolving technical ambiguity, and establishing cross-system design patterns that raise the quality bar across the team

Lead significant projects and initiatives that span multiple engineers and interact with other teams; determine work priorities based on strategic direction; recommend modifications to team operations and make needed adjustments to short-term priorities while maintaining strategic focus

Mentor and develop Senior and mid-level engineers - providing coaching, technical direction, and educational opportunities in modern distributed systems, stream processing, search infrastructure, and AI-assisted development practices

Collaborate closely with TR Labs and research scientists to integrate new chunking strategies, embedding models, and enrichment techniques into the pipeline in a safe, well-instrumented, and ethically responsible way

Deliver effective presentations on complex technical concepts to both technical and non-technical stakeholders; develop strategic plans for technology implementation that align with business objectives

About You

You're an ideal fit if you have:

Required Experience -

Bachelor's or Master's degree in Computer Science, Engineering, or a related field

8+ years of software engineering experience, with demonstrated progression to staff-level or equivalent technical leadership - including ownership of a functional area and leadership of significant cross-functional projects

Deep expertise in distributed stream processing: designing, building, and operating high-throughput, fault-tolerant event-driven pipelines using Kafka or equivalent technologies at production scale

Production experience with Vespa, OpenSearch, or Elasticsearch - including schema design, ranking profile configuration, and end-to-end application lifecycle management

Mastery of Python with strategic awareness of language and framework selection; strong software engineering fundamentals including test strategy, performance architecture, and system design

Proficiency with AWS cloud services used in data pipeline and search infrastructure (MSK, ECS, Lambda, DynamoDB, Step Functions, CloudWatch), with infrastructure-as-code experience (Terraform or AWS CDK)

Demonstrated ability to take full operational responsibility end-to-end - defining SLOs, building observability, running on-call, and driving systematic improvements from incident retrospectives - with a track record of shipping to production frequently and removing delivery friction proactively

Comfort and fluency with AI-assisted development tools; you use them to move faster and produce higher-quality work, not as a novelty

Track record of establishing architectural principles, cross-system design patterns, and documentation standards that improve the broader team's engineering quality

Preferred Experience -

Experience operationalizing ML models in production: inference serving, model promotion pipelines, canary rollouts, and production observability for model quality signals

Familiarity with agentic retrieval patterns - multi-hop retrieval, latency budget management across retrieval hops, context window optimization, and stateful session design

Experience with online search analytics: instrumenting systems for query performance monitoring, A/B or interleaved ranking experiments, and query log analysis to surface relevance gaps

Experience with embedding pipelines, vector indexing, and hybrid (dense + sparse) retrieval architectures in a production context

Familiarity with Protobuf schema design and schema registry governance patterns (Confluent Schema Registry or equivalent)

Experience building self-service or multi-tenant platform infrastructure where reliability and correctness directly affect multiple downstream teams

Background in AI ethics frameworks and responsible deployment of machine learning components in production pipelines

What Success Looks Like

In the first 90 days:

Develop a thorough understanding of the platform's current ingestion and indexing architecture, active technical debt, known reliability gaps, and the roadmap for Vespa adoption

Establish strong working relationships with the search platform team, TR Labs, and key client teams consuming the ingestion pipeline

Take on-call ownership for your functional area and deliver at least one meaningful improvement to pipeline reliability, observability, or delivery automation

In the first year:

Lead the architectural design and delivery of a major phase of the Vespa migration - including ingestion pipeline changes, schema migration, and zero-downtime index promotion - resolving novel technical challenges with minimal precedent

Establish robust SLO coverage and observability across ingestion components, with on-call playbooks, documented architectural decision records, and demonstrated improvement in incident response quality

Deliver a production-ready custom model operationalization framework: inference serving, promotion pipeline, and observability for at least one custom model integrated into the ingestion or query stack

Become the recognized technical authority for ingestion and indexing - the person the team and partner organizations turn to for architectural direction in this domain - with demonstrated influence on platform strategy.

#LI-TH1

What's in it For You?

  • Hybrid Work Model: We've adopted a flexible hybrid working environment (2-3 days a week in the office depending on the role) for our office-based roles while delivering a seamless experience that is digitally and physically connected.

  • Flexibility & Work-Life Balance: Flex My Way is a set of supportive workplace policies designed to help manage personal and professional responsibilities, whether caring for family, giving back to the community, or finding time to refresh and reset. This builds upon our flexible work arrangements, including work from anywhere for up to 8 weeks per year, empowering employees to achieve a better work-life b...


What Thomson Reuters employees say

Pay

Benefits

Hours and flexibility

Workplace

Get the full story on Breakroom