Technical Content Writer

Looking for 3 contract writers for Intellum!

1️⃣ B2B SaaS Comparison & AEO/SEO Content Writer

2️⃣ B2B Thought Leadership Writer, Customer Education / L&D

3️⃣ Technical Content Writer, SaaS Use-Cases and Product Explainers

These are all posted through Upwork. Linking to each role in the description. Please take a look and/or tag a friend! :)

Posted by: Shannon Howard

---

Summary

We're Intellum, a 25-year LMS used by Google, Amazon, Meta, and Stripe, and we're AI-native in a category full of bolted-on AI. We're hiring a contract writer to own our use-case and technical-explainer content: the pieces that connect a real problem to a product capability to an outcome, and the explainers that make our architecture make sense. You'll write accurately about AI and integration topics without a product manager rewriting every paragraph. There's a paid test, and we pay for it.

What you'll write

• Use-case and how-to content (for example, building a certification program, onboarding at scale, or measuring time-to-value)
• Technical explainers (for example, how agentic learning works, or what an AI-native learning platform does differently)
• Content built from interviews with our product, customer experience, and customer teams

What you need to be good at

• Enough technical literacy to write accurately about AI and integration architecture on your own
• The instructional instinct to turn a capability into a clear "here's how you'd actually do this" walkthrough
• Sourcing product claims to the reference material we provide, flagging what you're unsure of, and never filling a gap with a plausible guess
• Structuring for long-tail use-case queries and question-format prompts, with the goal of ranking in traditional search and earning AI citations, and building a brief from intent research in SEMrush and Search Console to pursue both
• Lived specificity: real workflows, real numbers, real edge cases

Nice to have

Background in instructional design, customer education, or technical/integration writing Comfort working from a product spec as source material

What "done" looks like (every piece)

Every deliverable lands as a Google Doc with a clear heading hierarchy, a meta title (under 60 characters) and meta description (under 155), a proposed URL slug, the target query noted at the top, two to four internal link suggestions, image specs with alt text, and a sourcing appendix tying every product claim to the reference we gave you. You spec the screenshots and diagrams and mark exactly what to capture; we produce them. Two rounds of revision are included.

How we work, and what you get from us

We give you a product-validated reference source, product environment access, and interviews with the people who built the thing, so you can write accurately instead of guessing. We don't pay by the word. Use-case walkthroughs usually run 1,200 to 2,000 words.

On AI tools and our bar Use AI tools for research and speed if you like. Every piece still passes a strict editorial and anti-slop check before it publishes, the final has to be original, and we may run AI-detection. Accuracy is the whole job here, so a confident-sounding claim that turns out wrong is worse than a flagged unknown. Recycled or plagiarized work ends the contract.

The details

Ongoing contract, roughly 10 to 15 hours a week to start (around two use-case pieces weekly), 3-month initial term with strong potential to continue.