Loading…
Careers
WikiBusines runs an in-house editorial team — no marketplace freelancers, no manufactured coverage, paid-editing disclosure as a non-negotiable. Joining us means working on real Wikipedia projects, with senior editors who'll argue policy with you, and being measured on whether your published work survives — not on how busy you look.
Who we're looking for
Skills we can teach. These three are the ones we hire for — and the ones we can't onboard around.
We work in a market where shortcuts are normal — manufactured coverage, paid placements, citation laundering. We don't. The first thing we will check is how you read a source list, not how well you write a pitch.
Saying 'this won't pass notability' to a paying client is a skill. So is telling a senior editor the draft they handed you isn't ready. If 'no' costs you sleep, this is the wrong team.
Either is fine. What's not optional is fluency in WP:NCORP, WP:NPOV, WP:RS, and the actual etiquette of edit summaries, AfD discussions, and AfC reviewer feedback. We hire people who already live there.
Roles open right now
If you don't see the exact title you want but you read Wikipedia policy for fun, email us anyway — the team grows with the work.
Kyiv / Remote-EU
Full-time
Lead editor on English-language Wikipedia projects — from notability assessment through AfC submission, talk-page defence and post-publication monitoring.
What you'd own
You'll thrive here if
How we know it works
Onboarding is two weeks paired with a senior editor on real client work. Tooling — our internal source-vetting dashboard, edit-pacing tracker, and AfD-watch — is taught on day one. Escalation paths are documented: if a draft you wrote is challenged at AfD, the founder-editor pair joins the defence within 24 hours. You will never be alone on a contentious article.
Remote
Full-time or part-time
Native or near-native editors for the non-English Wikipedia editions we ship into. One language per role; multiple roles open across DE, FR, ES, IT, PL, UA.
What you'd own
You'll thrive here if
How we know it works
First two weeks: shadow a senior editor on the EN side to learn our source-vetting workflow, then take the lead on three small local-language projects with the EN senior reviewing source quality before submission. After month one you own your queue end-to-end. We share a weekly 30-minute call across all language-edition editors to compare policy interpretation drift.
Kyiv / Remote-EU
Full-time
The person who decides whether a subject is publishable before the editor writes a single line. Owns source-vetting, competitor audits and source-pack assembly.
What you'd own
You'll thrive here if
How we know it works
Onboarding is one week with the senior researcher walking you through 15-20 past source packs — both the ones we shipped and the ones we used to decline projects. Your first month is paired audits; from month two you own your own queue and the editor pod treats your verdict as authoritative. Escalation goes founder-direct when a sales call needs a notability ruling under deadline.
Kyiv / Remote-EU
Full-time
Source-pitch outreach to journalists at Tier-1 and Tier-2 outlets — not generic PR. The job is to help clients become coverage-worthy, not to spam editors.
What you'd own
You'll thrive here if
How we know it works
First two weeks: read the last 6 months of our outreach archive — wins and losses — and shadow the lead on three live campaigns. Tooling: our journalist relationship tracker (built in-house, no Meltwater) and the team-wide pitch library. Escalation is the founder for sensitive accounts; the editorial lead for notability-impact ambiguity.
Kyiv / Remote-EU
Full-time
End-to-end ownership of 5-10 enterprise client relationships — multi-language portfolios, annual-support tiers, multi-stakeholder approvals.
What you'd own
You'll thrive here if
How we know it works
First month: shadow the Head of Business Development on three existing enterprise accounts before being assigned your own. You inherit a starter portfolio of 3-4 accounts with documented histories; you grow to 5-10 over six months. The editorial leads and the researcher pod are 1:1 partners — not vendors you assign work to. Escalation is the founder for contract issues; the editorial lead for policy interpretation.
Kyiv / Remote-EU
Full-time
Monitors client brand presence across ChatGPT, Gemini, Perplexity and Google AI Overviews; builds source-recovery and source-strengthening plans tied to Wikipedia / Wikidata work.
What you'd own
You'll thrive here if
How we know it works
Onboarding pairs you with the Head of Digital for the first month — you'll learn the in-house monitoring stack (we built our own; vendor tools weren't honest enough) and read the past 12 weeks of client visibility reports. Escalation: founder for client-facing recommendations, Head of Digital for tooling questions. You'll publish a weekly internal note on what shifted across the LLM stack — this becomes a team artefact.
How we hire
We have one strong opinion about hiring: the people who can do the job and the people who interview well are not always the same set. Our process is built around that.
Email team@wikibusines.com with your CV, links to relevant work (portfolio, Wikipedia username if applicable, recent journalist contact list for PR roles), and a paragraph on what drew you to this work. We read every one.
A short call with the hiring lead for the role — not HR. We use it to confirm we understood your background and to answer your questions about how the team actually works.
A 2-4 hour realistic task — e.g. a source-quality audit on a sample subject for the Researcher role, or a Wikipedia draft against WP:NCORP for the Editor role. Paid at the role's pro-rated rate. You'll work with the same tooling you'd use on the team.
If it's a fit, we send the offer within 7 days of the trial. If it isn't, we send specific feedback within the same window — what worked, what didn't, where you'd be a better fit. We pay for trial work because we hire people who can do the job, not people who can interview well.
We pay for trial work because we hire people who can do the job, not people who can interview well.
Why work here
Every line below is something a team member could verify on day one. We don't write careers copy we'd be embarrassed to defend.
You work with senior Wikipedians and a researcher pod on the same payroll — not a marketplace of freelancers bidding on your draft. Reviews are conversations, not silent rejections.
Every editor on staff publishes under a disclosed paid-editing account per WP:PAID. You will never be asked to hide who you work for. The clients know that. The community knows that. It is non-negotiable.
Internal source-vetting dashboard, edit-pacing tracker, AfD-watch, LLM-visibility monitoring stack. We built our own because vendor tools weren't honest enough about source quality and we needed audit trails that survive client review.
Real volume, real ownership — you're not the eighth approver on someone else's draft. Once trusted, you own your queue end-to-end and we measure outcomes (survival, AfD defence rate), not activity.
Editors in DE, FR, ES, IT, PL, NL, UA work in their own time zones with weekly cross-language calls. You're not the only person who knows the policy backwards — there's always someone to argue an NCORP read with.
Our offer agreement includes a real refund clause for borderline work. That's not just client-protection — it's the reason we don't ship questionable pages. Your published Wikipedia URLs are evidence of competence, not embarrassment.
How to apply
No portal, no form, no third-party ATS. Email reaches a person on the team within one business day.
Send your application to team@wikibusines.com.
Suggested subject line
Application — [role title] — [your name]
Please include
We reply to every application we receive. If you don't hear back within five business days, please follow up — sometimes emails go missing.
Want to know who you'd be working with? Meet the team behind the work →
If you read Wikipedia talk pages for fun and you can't tell whether the Editor or Researcher path is right for you — write to us. We'll figure it out together on the screening call.