2

Remote Textbook Publishing Jobs in California (NOW HIRING)

Remote Textbook Publishing information

What is remote textbook publishing?

Remote textbook publishing refers to the process of producing, editing, and distributing educational textbooks from a location outside of a traditional office or publishing house. Professionals in this field collaborate online to manage tasks such as manuscript review, layout design, copyediting, and digital distribution. Advances in technology have enabled publishers, editors, and authors to work together efficiently from anywhere, making remote textbook publishing increasingly popular. This approach offers flexibility, access to a global talent pool, and often faster turnaround times for educational materials.

What are the key skills and qualifications needed to thrive in remote textbook publishing?

To thrive in Remote Textbook Publishing, you need expertise in editorial processes, strong written communication, and familiarity with educational content standards, typically supported by a relevant degree in English, Education, or Publishing. Proficiency with publishing software (such as Adobe InDesign), content management systems, and digital collaboration tools is crucial. Attention to detail, time management, and the ability to work independently are standout soft skills in this role. These skills ensure the production of high-quality, accurate educational materials while meeting deadlines in a remote, collaborative environment.

What are some common challenges faced when working in remote textbook publishing, and how can they be addressed?

A common challenge in remote textbook publishing is ensuring clear and timely communication among editors, authors, and design teams who may be spread across different time zones. To address this, many teams rely on collaborative project management tools and regular virtual check-ins to stay aligned on deadlines and feedback. Additionally, maintaining version control for manuscripts and assets is crucial, so using cloud-based document management systems is highly recommended. Embracing these practices helps remote teams work efficiently and produce high-quality educational materials.

What is the difference between Remote Textbook Publishing vs Remote Educational Content Developer?

AspectRemote Textbook PublishingRemote Educational Content Developer
Primary FocusCreating, editing, and publishing textbooks for educational institutionsDesigning and developing various educational materials like online courses, modules, and multimedia content
Required SkillsWriting, editing, subject matter expertise, publishing toolsInstructional design, multimedia creation, curriculum development
Work EnvironmentTypically involves collaboration with authors, editors, and publishersOften works independently or with educational teams, using digital tools
Industry UsageUsed by academic publishers, universities, and educational institutionsUsed by e-learning companies, educational startups, and institutions

While both roles involve creating educational content, Remote Textbook Publishing focuses on producing traditional textbooks, whereas Remote Educational Content Developer emphasizes designing diverse digital learning materials. Understanding these differences helps job seekers target the right opportunities in the education publishing industry.

What job categories do people searching Remote Textbook Publishing jobs in California look for?

The top searched job categories for Remote Textbook Publishing jobs in California are:

What cities in California are hiring for Remote Textbook Publishing jobs?

Cities in California with the most Remote Textbook Publishing job openings:

Clinical Physician (Full-time or Part time)

Pear

San Francisco, CA • On-site, Remote

Part-time

Posted 2 days ago

New


Job description

About Optexity
Optexity is a product-driven research lab building clinical reasoning and computer use models on data no other lab can reach. We deploy directly inside clinics and hospitals - including systems with no APIs, using integration infrastructure we've built and open-sourced - and in return become their preferred partner. That gives us proprietary clinical reasoning trajectories from practicing physicians, and a feedback loop between real patient encounters, our models, and the products built on top of them.
We're a small, fast-moving founding team with multiple published papers in NeurIPS, ICML, CVPR and backgrounds from Apple, Amazon, Microsoft, CMU, and IIT.
We are backed by world-class investors and leaders including Jeff Dean, Neotribe VC, PearVC, Together Fund, and Zapier Fund.
How we work
  • Customer obsession - we start with the customer and work backwards
  • Intellectual honesty - ideas matter more than titles; we communicate directly and assume good intent, even in disagreement
  • Bias for action - we build and learn with customers rather than debate in the abstract
  • Extreme ownership - we own outcomes, not just tasks, and see problems through
Why this role exists
We're building a clinical AI assistant that sits inside real practices - surfacing care gaps, assembling pre-visit prep, flagging risk, and suggesting treatment plans. None of that works without physicians defining what "correct" means.
Most clinical advisor roles are a monthly call where someone reacts to a demo. This one isn't. You'll be in the product loop weekly: deciding what the assistant should flag, what a good summary actually looks like at 7:50am before a 15-minute visit, and grading where the model is wrong and why. Your judgment becomes our ground truth and our evaluation standard.
We're looking for physicians across internal medicine, cardiology, oncology, and other specialties - both to go deep in your own domain and to help us understand where workflows diverge across specialties.
What you'll do
  • Define what the assistant should surface. Which care gaps matter, which risk signals are worth an interruption, and which are noise that erodes trust. Translate clinical shorthand into precise, checkable criteria.
  • Shape the pre-visit summary. What belongs in it, in what order, at what length - and what a physician actually reads versus scrolls past.
  • Specify clinical search. What you'd want to pull from the chart before a visit, how you'd phrase it, and what a complete answer looks like.
  • Judge the AI. Review model-generated risk flags, differentials, and treatment plans against your own reasoning. Score them, explain the gap, and tell us whether a miss is dangerous or merely different.
  • Build ground truth. Help us construct real-case evaluation sets and rubrics that reflect actual standard of care, not textbook answers.
  • Pressure-test the product. Sit in on design decisions and tell us when something wouldn't survive contact with a real clinic day.
  • Contribute to publications. We publish benchmarks and technical reports; clinical co-authorship is available and encouraged.
Ideal candidate
  • MD or DO, board-certified or board-eligible
  • Currently practicing or recently practicing - active clinical context matters more than titles
  • Internal medicine, cardiology, oncology, or an adjacent specialty; primary care and multi-specialty experience especially welcome
  • Day-to-day fluency in an EMR (Epic, eClinicalWorks, Athena, ModMed, or similar) and an honest view of where it fails you
  • Opinionated about clinical workflow, and able to explain why something is right - not just that it is
  • Comfortable with ambiguity, direct feedback, and being asked "how do you actually know that?"
  • Genuinely interested in AI in medicine, including its failure modes
Nice to have
  • Clinical informatics training or CMIO-adjacent experience
  • Experience with quality measures and value-based care programs (HEDIS, MIPS, CPT Category II, HCC coding)
  • Prior work advising or building health tech products
  • Research or publication background
  • Experience training residents or fellows - the skill of articulating clinical reasoning out loud transfers directly
Commitment
  • Part-time: 5-15 hours/week, flexible around clinical schedules. Async-friendly, with a recurring weekly working session.
  • Full-time: for physicians ready to step into a founding clinical role and own clinical direction end to end.

Remote is fine. Occasional in-person time in San Francisco or at partner clinic sites is a plus.
What you get
  • Direct, daily work with the founders - no layers between your input and what ships
  • Real influence over a product that practicing physicians will use, not a pilot that dies in committee
  • Competitive hourly rate for part-time engagements; competitive salary and meaningful equity for full-time
  • Co-authorship on benchmarks and technical reports
  • Visa sponsorship available for full-time roles