2

Remote Feature Producer Jobs in California (NOW HIRING)

If remote, travel to the headquarters in San Diego, CA will be required at least quarterly ... feature work, and code reviews. * Own and maintain build configuration, CI/CD pipelines, and ...

If remote, travel to the headquarters in San Diego, CA will be required at least quarterly ... feature work, and code reviews. * Own and maintain build configuration, CI/CD pipelines, and ...

Sr. Product Manager, TwoTwenty

San Francisco, CA · On-site +1

$149K - $196K/yr

At Pinterest, AI isn't just a feature, it's a powerful partner that augments our creativity and ... Run experiments that answer real questions, not experiments that produce metrics. You'll decide ...

Sr. Product Manager, TwoTwenty

San Francisco, CA · On-site +1

$149K - $196K/yr

Run experiments that answer real questions, not experiments that produce metrics. You'll decide ... Experience saying no to a well-liked feature request from an executive and holding the line on ...

Senior Designer, Creative

Long Beach, CA · On-site +1

$70K - $110K/yr

Remote- Eligible US Locations About the role and about You: At Zwift, our Creative team brings ... One week you might be developing a campaign for a new feature launch, the next designing an ...

New

Software Architect (Java)

El Segundo, CA · On-site +1

$67 - $90.50/hr

About This role is remote from anywhere in the US and Canada. NEOGOV is a proud AI-Enabled SaaS ... Produce high-level designs (HLD), sequence diagrams, and interface definitions that guide your five ...

Content Marketing Lead

San Francisco, CA · On-site +1

$120K - $140K/yr

New feature going live? Fun fact from a factory floor? You'll be continuously gathering inspiration ... You'll help Squint execs produce social content, longform posts, and talktracks for speaking ...

Showing results 21-40

Remote Feature Producer information

How does a remote feature producer effectively manage collaboration and communication with distributed teams?

As a Remote Feature Producer, seamless collaboration with cross-functional teams—such as designers, developers, and stakeholders—is essential. This is typically achieved through regular virtual meetings, clear project documentation, and the use of collaborative tools like Slack, Jira, or Trello to track progress and feedback. Proactive communication, time zone awareness, and establishing clear milestones help ensure everyone stays aligned and project timelines are met. Building strong relationships remotely can be challenging, but frequent check-ins and transparent updates foster trust and accountability.

What is the difference between Remote Feature Producer vs Remote Content Coordinator?

AspectRemote Feature ProducerRemote Content Coordinator
Required CredentialsExperience in media production, storytelling, and project managementExperience in content management, editing, and communication
Work EnvironmentCollaborates with creative teams, manages production schedules remotelyCoordinates content workflows, liaises with writers and editors remotely
Industry UsageUsed in media, entertainment, and digital content industriesCommon in marketing, publishing, and digital media sectors

The Remote Feature Producer focuses on creating and managing media features, requiring storytelling and production skills. In contrast, the Remote Content Coordinator handles content organization and workflow coordination. Both roles often work remotely within media and digital industries but differ in their core responsibilities and skill sets.

What are the key skills and qualifications needed to thrive as a remote feature producer, and why are they important?

To excel as a Remote Feature Producer, you need expertise in project management, content development, and storytelling, often backed by experience in media production or a related degree. Familiarity with digital collaboration tools such as Slack, Trello, and cloud-based editing software is typically required. Exceptional communication, time management, and problem-solving abilities help you coordinate with dispersed teams and adapt to shifting priorities. These skills ensure high-quality feature delivery on time and foster seamless teamwork in a virtual environment.

What is a remote feature producer?

A Remote Feature Producer is a professional responsible for overseeing the planning, coordination, and execution of feature-length content, such as films, documentaries, or special segments, while working remotely. They manage creative teams, budgets, schedules, and communications, ensuring the project meets its goals without being physically present at a central location. This role often involves collaborating with writers, directors, editors, and other stakeholders through digital tools and virtual meetings. Remote Feature Producers need strong organizational and leadership skills, as well as proficiency with project management and communication technologies.

What are the most commonly searched types of Feature Producer jobs in California?

The most popular types of Feature Producer jobs in California are:

What are popular job titles related to Remote Feature Producer jobs in California?

For Remote Feature Producer jobs in California, the most frequently searched job titles are:

What job categories do people searching Remote Feature Producer jobs in California look for?

The top searched job categories for Remote Feature Producer jobs in California are:

What cities in California are hiring for Remote Feature Producer jobs?

Cities in California with the most Remote Feature Producer job openings:

Infographic showing various Remote Feature Producer job openings in California as of August 2026, with employment types broken down into 80% Full Time, 9% Part Time, and 11% Contract. Highlights an 87% Physical, 3% Hybrid, and 10% Remote job distribution.

Software Engineer - AI-Native Full Stack

Bolo AI

Lake City, CA • On-site, Remote

Full-time

PTO

Re-posted 5 days ago


Job description

Software Engineer - AI-Native Full Stack
Bolo AI
Bay Area (Hybrid) | Salt Lake City Area (Remote) | Full-Time Senior Engineer
The Role Has Changed
Three person engineering teams are building what used to take thirty. Not by working harder, but by working differently. The engineers shipping at this pace don't write code. They write specs precise enough that agents implement them correctly. They build harnesses. CI gates, structural tests, linting rules, and architectural enforcement that mechanically prevent entire classes of agent mistakes. They design validation systems where agents write the tests and humans verify that features actually work from the user's perspective.
The code is a generated artifact. The spec, the harness, and the validation infrastructure are what engineers maintain.
This is how we work at Bolo.ai. We're hiring engineers who already work this way, or who have the depth to start.
The Company
Bolo AI is building the AI company for heavy industry.
These are the sectors the world depends on: energy, utilities, manufacturing, and industrial operations. They have been underserved by modern software and AI for too long. We are changing that with AI built for their messy, high-stakes operational reality.
Customers are already using Bolo to catch critical equipment failures, recover hidden cost impact, automate operational workflows, and put decades of industrial data to work.
Backed by True Ventures, Benchstrength, Accomplice, Analog Ventures, and Beat Ventures, we are a small, AI-native team working close to the customer to make their daily work faster, safer, and better.
The Work
You'll spend your time on four things:
  • Specifications. You write behavioral specs, architectural constraints, and feature requirements that agents implement against. When agent output misses the mark, you tighten the spec. Not by adding more words, but by being more precise about what "correct" means. This requires understanding the system deeply enough to define its behavior at every layer.
  • Harness. You build and maintain the infrastructure that keeps agents producing reliable code. Structural tests that enforce architectural boundaries. Linting rules where every failure message teaches the agent what went wrong. CI gates that reject drift. Structured knowledge bases agents can navigate. The principle: every class of agent mistake gets a mechanical fix so it never recurs.
  • Validation. Agents write the code. Agents write the tests. You verify that features work from the user's perspective, under real deployment conditions, against edge cases that matter in production. You define scenarios and acceptance criteria. You build the end-to-end checks, behavioral verification, and automation that make this trustworthy at scale. When something breaks, your job is diagnosing whether the failure is in the spec, the harness, or the agent's implementation, and fixing the right layer.
  • Architecture and operations. Our systems run across cloud providers and on-premises environments. You design modular abstractions, clean interfaces where deployment targets don't leak into application logic. You own production systems used by energy companies in regulated environments where failures have real consequences. Reliability, observability, and graceful degradation matter here.
What Makes Someone Good at This
7+ years of engineering experience, applied at a higher altitude. You need years of building and debugging production systems. Not because you'll write every line, but because you can't design a harness that catches real failures, write a spec that anticipates edge cases, or diagnose a broken feature across the full stack without that foundation. The depth serves the abstraction.
Systems thinking over code fluency. How components interact. Where failures cascade. What breaks when requirements change. What to anticipate before it happens. This is what agents are worst at and what matters most.
An agent-driven workflow. You already direct AI agents (Claude Code, Codex, Cursor, or similar) to handle implementation while you focus on architecture, specification, and validation. Or you have the engineering judgment to make that transition and the motivation to do it now.
Experience building the infrastructure around agents. CI enforcement, scenario-based testing, documentation systems agents can consume, structured knowledge bases - you've built some of this, or you have specific ideas about how and why.
Comfort making decisions with incomplete information. Startup. Requirements shift. The right approach isn't always obvious. You move forward, and you know when to ask versus when to make a call.
Direct communication. You give and receive honest feedback. You can disagree with a decision, say so clearly, and still commit to the outcome. We care about getting it right more than being right.
Enthusiasm for a field that reinvents itself quarterly. Tools change. Workflows get replaced. Best practices from three months ago become obsolete. You're energized by that. You see this as the most interesting period in the history of software.
About Us
Small, senior-leaning engineering team. Real ownership, direct impact, no layers between you and the work. We expect a lot from each other and give each other the room to deliver.
Sustainable pace over heroic sprints.
What We Offer
Bolo AI is headquartered in Palo Alto, backed by True Ventures, Benchstrength, Accomplice, J Ventures, and Beat Ventures.
  • Competitive compensation with equity so you share in what we build together.
  • Hybrid flexibility - in-person collaboration in Palo Alto with room to work how you're most productive.
  • Early-stage ownership - join at a stage where your decisions shape the product, the architecture, and the engineering culture.
  • Generous PTO and flexible working hours.

Hiring Process
We evaluate how you work in an AI-native workflow. AI tool usage is expected, not just permitted. We're looking at engineering judgment. Can you write specs agents execute well against, build systems that catch real failures, and reason about problems across the full stack.
We'll be straightforward about our process, give you real information to evaluate us, and give you feedback regardless of outcome.
If this sounds like what you're already building toward, we'd like to talk.