JOBSEARCHER

Technical SEO Content Engineer (SaaS / Developer Docs) REMOTE

ARCHIVED
NalpeironBoulder, CORemoteL5 SeniorApril 9th, 2026

We can't find an active application page for this role right now. It may reopen or be listed elsewhere. Use Next Steps to search for an active apply link and similar live jobs.

OverviewWe are looking for a remote contractor to transform our technical documentation, written in GitBook (https://docs.nalpeiron.com), into a high-performing SEO acquisition channel.This is not a traditional writing role — it requires structuring, optimizing, and expanding technical content to rank in search and AI-driven discovery (ChatGPT, Google SGE).It will require the use of AI tooling and the latest techniques to speed up the process and get better results.This is a core role for us - you will be our Docs Growth Owner , not just a technical writer.You will own:KPI: organic traffic + rankingsOwnership of docs, SEO, and content >page 1Ownership of AI placement, so the docs pages are recommended in all AI enginesBacklinking strategy between various propertiesOpportunity to own our full docs process if this project is successful, i.e., technical writing and doc productionWe will filter candidates by:Thinking quality and use of AI toolsetStructure and quality output (not just AI B.S. blurb)Technical understanding of the messaging and ability to communicate technical conceptsAbout Us (nalpeiron)Nalpeiron provides enterprise-grade software monetization infrastructure (entitlements, licensing, usage analytics). Our platform sits at the core of modern SaaS and IoT monetization architectures. We are 21 years old, stable, profitable, and a key player in our industry.Responsibilities1. Documentation SEO OptimizationRewrite existing docs pages to align with high-intent search queriesImprove titles, headings, and on-page keyword targetingAdd contextual introductions and use cases to technical pagesWork with colleagues to generate content (you are not alone)Ensure our content remains high quality, detailed, useful, and of value to developers2. Pillar Content CreationCreate 5–10 long-form "pillar" technical guides (2,000–4,000 words)Example topics:Entitlement Management ArchitectureUsage-Based Licensing ImplementationSoftware Licensing System DesignHybrid Monetization Models3. Internal Linking & Topic ClustersBuild structured internal linking across docs and marketing pages (working with marketing team)Recycle video and training content into the docs from the university and other sourcesCreate topic clusters (licensing, entitlements, usage, APIs)4. Technical Content EnhancementAdd/create:Architecture diagrams (can be simple)API examplesStep-by-step implementation flowsVideo contentUse cases5. Schema & AI OptimizationImplement FAQ, HowTo, and TechArticle schemaStructure content for AI search visibility (clear definitions, summaries)6. Ongoing Content & MaintenanceContinuously expand docs with new SEO-driven pagesMonitor rankings and iterate on content monthlyProduce a monthly report on progress and rankings vs competitionRequirementsProven experience with:SaaS, APIs, or developer documentationTechnical SEO (not just blog SEO)Strong understanding of:Software architecture concepts (APIs, licensing, usage tracking)Search intent and keyword mappingAbility to turn fragmented docs into structured, ranking contentFluent written English (native or near-native)Strong use of the latest AI tooling (we will buy as required)BonusExperience with:Monetization, billing, or licensing systems/software development (SDLC), etcTools like Ahrefs, SEMrush, SurferSEOMarkdown-based documentation systemsDeliverables (First 60 Days)Audit of existing docs and their rank in key AI/search queriesUnderstanding of our keyword/ranking strategyOptimization of the top 50 pages5-10 pillar pages with associated child pages createdInternal linking structure implementedMeasurable increase in indexed pages and impressionsEngagement ModelInitial project: 4–8 weeksRemote, async-friendlyHow to ApplyPlease include:Examples of technical content you've written (docs, APIs, or SaaS)Before/after SEO improvements you've deliveredTools and processes you use for SEO + content structuring#J-18808-Ljbffr