Content Engineer

About QOVES

QOVES is on track to become the next consumer tech unicorn. With over 2.5 million followers across our platforms, we’ve built one of the largest global communities around beauty, aesthetics, and AI.

We pioneer AI-driven facial analysis technology and produce deeply researched educational content at the intersection of aesthetics, science, and technology.

QOVES writes long, heavily cited articles about facial aesthetics. We've built a content pipeline on top of Claude Code, including custom skills for image generation, chart rendering, corpus search, and CMS publishing, so one person can take an article from a literature search to a published page.

We’re hiring someone to run and improve that pipeline.

This is not a blogger job.

What You’ll Do

• Select and prioritize the next 5–10 articles from the SEO and concern roadmap using:
  • Ahrefs search volume
  • Corpus gaps
  • Brand priorities
• Run existing internal skills and workflows including:
  • /blog-build-measurement-page
  • /blog-build-concern-page
  • /blog-make-numerical-chart
  • /blog-make-flowchart
  • Severity strips
  • Before/after comparisons
• Edit and fact-check generated content against academic sources and internal corpuses
• Refine prose to match QOVES editorial voice
• Humanize alt text and remove AI-generated artifacts using internal tooling
• Build visuals and charts using:
  • Plotly
  • SVG workflows
  • Brand design systems
• Push and manage content in Payload CMS
• Verify rendering, publishing, and CDN delivery workflows
• Build new skills and tooling when required:
  • Python scripts
  • MCP servers
  • Image pipelines
  • Automation workflows
• Maintain corpus content-gap tracking for the academic team
• Run weekly SEO and LLM-citation audits and implement improvements

What We’re Looking For

• Comfortable in a terminal. You've shipped Python before. You can read a 500-line script, find the broken regex, and fix it.
• You know git well enough to keep a clean branch and PR history.
• You read a paper without flinching. You can tell a load-bearing citation from filler.
• You have editorial taste. You spot a flabby sentence, a buried lede, an over-italicised paragraph.
• You've used LLMs as tools, not just chat. Bonus if you know prompt caching, MCP, agent loops, or have written your own slash-commands.
• You'd rather publish 3–5 articles a week that hold up under scrutiny than 20 that don't.

You are NOT

• A traditional blogger who outsources research and only writes.
• A content marketer focused on growth-hacking and SEO clickbait.
• An engineer who doesn't care about prose.

Stack you'll inherit

Claude Code (CLI agent), Anthropic SDK, Python, Plotly, Payload CMS, AWS (S3 + CloudFront), Ahrefs, Google Search Console, Bing Webmaster, NCBI E-utilities, Gemini, BiRefNet, Moondream, and a private corpus RAG over indexed academic facial-aesthetics literature. Plus more than a dozen project skills already built in `.claude/skills/`, around 20 measurement articles drafted, 15 concern articles drafted, and drip-publish routines scheduled through July.

How to Apply

Send us the following:

1. A blog post or long essay you wrote, public somewhere. Ideally 1000+ words and citation-backed.
2. A GitHub link to anything you've shipped. Repo, Gist, one-file script, size doesn't matter.

3. Pick one of our published articles at qoves.com/insights. In under 200 words, tell us what you'd change and why. Could be the figures, the prose, the citation depth, anything that jumps out.

    

No cover letter. No "I'm passionate about beauty." Skip both, send the work.