B2B Content Editor — Cybersecurity / SaaS (Contract, Hourly)

🚫 Please do not contact our company directly, although you can check us out at www.o8.agency. All applications must go through Upwork. Messages sent outside of Upwork will be ignored and your application will be rejected. ‼️ 🚫 🕐 Time Zone Requirement This is an asynchronous role. You must have reliable overlap with US Central Time business hours for occasional questions and handoffs, and be able to return edits within 48–72 hours. 📋 About the Role O8 is a digital marketing agency seeking a domain-credible B2B Content Editor for research-backed cybersecurity SaaS content. The work serves vendor and third-party risk management audiences, including readers responsible for GRC, zero trust, IT risk, procurement, and enterprise security decisions. This is an hourly editing and technical-quality-review role, not a per-piece writing assignment. You will receive research-backed, SEO-structured first drafts, generally 1,000–2,000 words, and make them more technically sound, useful, readable, and credible before client review. We need an editor who can tell the difference between content that merely sounds plausible and content that holds up under scrutiny from informed technical buyers. 🔑 Key Responsibilities - Edit 1,000–2,000-word cybersecurity SaaS drafts for clarity, structure, B2B SaaS voice, and relevance to CISO, CIO, security, risk, and procurement audiences. - Fact-check subject-matter claims and flag statements that are unsupported, overstated, vague, or technically imprecise. - Strengthen accuracy and buyer relevance across vendor risk management (VRM/TPRM), GRC, zero trust, compliance, and adjacent enterprise-security topics. - Preserve a sound research and SEO structure while making substantive editorial improvements; this is not a full-rewrite assignment. - Return edits with concise rationale within 48–72 hours and coordinate asynchronously with our delivery team as needed. ✨ We're looking for someone who: - Has 4+ years of editing or senior content experience in B2B technology, cybersecurity SaaS, IT security, GRC, compliance, or a comparable technical field. - Can show work where they improved technical accuracy, buyer relevance, and credibility—not only grammar and style. - Understands how CISOs, CIOs, security leaders, risk teams, and procurement evaluate claims, and can distinguish evidence from marketing language. - Is comfortable technically QA-ing research-backed first drafts created from a structured research and SEO brief. - Is reliable, detail-oriented, and able to work independently in Notion, Google Docs, or similar collaborative tools. 💡 Nice-to-haves: - Practitioner background in cybersecurity, security engineering, GRC, IT risk, compliance, privacy, enterprise software, or technical product marketing. - Experience with vendor risk management (VRM), third-party risk management (TPRM), zero trust, SOC 2, ISO 27001, or related enterprise-security concepts. - Agency editorial experience across multiple B2B technology clients. 🌎 Why Join O8? - Work with a collaborative, supportive team dedicated to helping clients achieve measurable growth. - Enjoy a flexible, remote-friendly work environment that values work-life balance, cultural exploration, diversity, travel, and being a good human. - Grow your career in a company committed to transparency, agility, and innovation. 🤝 Equal Opportunity Employer At O8, we celebrate diversity and are committed to creating an inclusive environment for all employees. 🚫 Please do not contact our company directly. All applications must go through Upwork. Messages sent outside of Upwork will be ignored and your application will be rejected. ‼️ 🚫 📊 ADDITIONAL DETAILS: Suggested Hourly Rate: $35–60 USD, based on experience and technical depth Estimated Hours: Approximately 8–16 hours per month to start; roughly 2–4 hours per 1,000–2,000-word draft Project Length: Ongoing contract; volume may grow with strong performance ✅ UPWORK SCREENING QUESTIONS 1. Share one B2B cybersecurity, GRC, or SaaS piece you edited. What was materially wrong or weak in the original, what did you change, and why? 2. Describe a time you challenged, removed, or rewrote a client-facing technical claim because it was unsupported, misleading, or technically imprecise. What was the topic, your evidence, and the outcome? 3. Which cybersecurity audiences and subject areas do you edit most often? Include specific examples involving vendor/third-party risk, GRC, zero trust, security, compliance, or enterprise procurement where relevant. 4. What is your hourly rate, weekly availability, US Central overlap, and typical turnaround for a 1,000–2,000-word technical edit?