Omar ElHawary — Content and Knowledge Strategist JD

Role: Content and Knowledge Strategist, MemberIntel
Incumbent: Omar ElHawary (internal promotion from the MemberPress support team, approved at the 2026-06-22 working session; role expanded to the hybrid curator + builder scope in the 2026-07-08 JD refresh, superseding the Brain Content Lead definition.)
Reports to: Seth Shoultes (Innovations Product Manager)
Works closely with: Russ Williams (Lead Designer — voice and style), Senior AI Engineer (owns the technical eval suite; you own the content-quality counterpart)
Status: Full-time on MemberIntel — operating standards apply from the start.
References: V1 spec §6 (the brain), V2 spec §6 (platform-tagged brain), arch-cross-pollination, Seth JD, Russ JD, Senior AI Engineer JD, privacy strategy for counsel

---

The role

This is a hybrid role. On one side you’re the domain expert and editor; on the other you’re a builder. You curate knowledge and write the software that manages it, using AI coding tools to ship the tooling and product features that support it. Both halves are the job, not one with the other bolted on.

You own the knowledge base (internally, the brain) that grounds MemberIntel’s AI: the curated playbooks that give the product its MemberPress-operator expertise. You author entries, review every entry promoted into the global knowledge base via the automated distillation pipeline (cross-pollination), operationalize the voice and style guide, and ensure the AI surfaces accurate, useful, well-bounded responses to real operator questions.

You also own the tooling. The Brain Editor Interface is the internal tool for authoring, reviewing, and publishing knowledge base entries — you design and ship it. The Content Eval Interface is the tooling behind monthly content quality audits — you design and ship that too. The AI Engineer owns the technical eval suite (prompt regression, citation accuracy, hallucination rate); you own the content-quality equivalent: is this entry grounded in real operator experience, is the advice sound, is the voice consistent, would a real MP operator trust it? The two halves connect through monthly paired reviews; neither ships without the other.

Taxonomy governance is also yours: the controlled vocabulary (categories, archetypes, industries, business models) that determines how entries are tagged, retrieved, and surfaced by the RAG pipeline. This is knowledge engineering work. A wrong tag silently fragments retrieval; a good structure makes the AI noticeably more useful.

You’re also the primary support person for MemberIntel. That puts you closest to real operator questions, which feeds directly back into where the knowledge base has gaps and what to author next. And you build: beyond the two interfaces, you ship product features using AI coding tools. You own your surface, and you’re trusted to move on it. You make the day-to-day calls and bring the bigger ones to Seth, with a bias toward keeping things ahead of schedule.

As the knowledge base scales past V1, this role grows into ownership of the knowledge-systems function: the taxonomy, the authoring and eval tooling, and the content-quality bar across the product as more people contribute to the brain. You’re the first owner of that surface, and you set the standard others work to as the team grows.

---

What you’ll do

• Author the global knowledge base. Curated playbooks covering MemberPress-operator how-tos, pricing guidance, content-protection patterns, dunning playbooks, member-engagement plays, and churn-recovery tactics — the kind of advice an experienced MP operator would give another. Target: 200+ approved entries by months 2–3.
• Own the Brain Editor Interface. Design and ship the internal tool for authoring, reviewing, queuing, and publishing entries. Define the authoring workflow, review states, and what the interface exposes to internal reviewers. You build it; you’re also its primary user.
• Own the Content Eval Interface. Design and ship the tooling behind monthly content quality audits — the content-layer counterpart to the AI Engineer’s technical eval suite. You define the evaluation criteria (voice consistency, accuracy, entry usefulness), build the audit tooling, and run it. You design the process, not just execute it.
• Govern the taxonomy. Maintain and evolve the controlled vocabulary that governs how entries are tagged and retrieved. Propose changes as the knowledge base scales. Enforce consistency across all entries. This is the ontology layer of the product.
• Define retrieval quality criteria on the content side. Work with the AI Engineer on what good retrieval looks like from a content perspective: which entries should surface for which operator questions, how to identify gaps, how content structure affects what the AI surfaces. You own the content criteria; the AI Engineer owns the technical implementation.
• Review knowledge base entries from the distillation pipeline. Every entry promoted from a per-customer brain into the global knowledge base goes through you. The k-anonymity floor is enforced upstream; your job is the human judgment above the floor — is this generalizable, accurate, actually de-identified, and does it belong in the global knowledge base at all?
• Own and extend the voice and style guide. You authored it. Every entry is reviewed against it, and you keep it current as new cases come up, aligning with Russ and Santiago on anything that touches design and product voice.
• Run monthly content quality audits on accuracy, voice consistency, and entry usefulness — with paired monthly read-outs with engineering.
• Enforce sensitive-vertical exclusion. Medical, advocacy, and similar verticals are permanently excluded from the global knowledge base. The pipeline blocks the obvious cases; you catch the non-obvious ones. Zero leaks is the target.
• Close knowledge gaps surfaced by product feedback. Thumbs-down trends reveal where the knowledge base didn’t have the answer; you author the missing entries. Median turnaround: 14 days or less from signal to published entry.
• Author the BuddyBoss-flavored entries for V2. Community engagement, paid groups, member-to-member networking. Target: 30+ BB-tagged entries at V2 launch, 60+ within six months.
• Be the primary support person for MemberIntel. Front-line operator questions are yours. This isn’t a side duty — it’s your direct line to what the knowledge base is missing, and it feeds the authoring backlog.
• Ship product features with AI-coding tools. Beyond the Brain Editor and Content Eval interfaces, you build and ship product features, working in the same AI-assisted development loop as the rest of the team.

---

What the role needs

• Deep subject-matter expertise on MemberPress. You’ve worked closely with MP operators, you know what they’re trying to do, and you’ve seen what works and what doesn’t.
• Strong writing and editorial judgment. Each entry has to sound like one person wrote it — voice consistent across 200+ entries.
• Working familiarity with RAG and knowledge base systems — enough to understand how content decisions affect retrieval. You don’t build the pipeline, but you know why taxonomy choices and entry structure matter to what the AI surfaces.
• Willingness to build. You ship the Brain Editor and Content Eval interfaces yourself and write product features alongside the engineers, using AI-coding tools. Comfortable with code, breaking work down, and shipping without hand-holding.
• Product thinking. Owning two interfaces means defining what “done” looks like before anything gets built: user flows, edge cases, acceptance criteria.
• Standards-setting, not just standards-enforcement. You propose updates to the voice guide and taxonomy when they fall short, and define what quality means at the knowledge layer.
• Comfortable saying “no” or “not yet.” Sensitive verticals are a hard exclusion. Generic AI-shaped advice gets rewritten or killed. Voice drift gets corrected before it ships. The job rewards conservative calls.
• Operational rigor. Review SLOs, monthly audit cadence, two-week feedback turnaround (see Operating standards).
• Comfortable working alongside engineers and a designer without needing to be either. The backend pipeline isn’t your lane; voice and style direction comes from Russ and Santiago. But your tooling decisions have to support close collaboration with the AI Engineer.

---

Operating standards

Full-time on MemberIntel, so these apply from the start:

• 95% of distillation-pipeline entries reviewed within 7 days of staging.
• Monthly content quality audit with a paired engineering read-out.
• Thumbs-down-to-published-entry turnaround within two weeks.
• 200+ approved entries by months 2–3 of V1; 30+ BuddyBoss-tagged entries at V2 launch, 60+ within six months.

---

What this role does NOT own

• Core platform infrastructure. The distillation pipeline, API, and database are owned by the AI and Backend Engineers. You ship your own tooling and product features with AI-coding tools, but the underlying platform isn’t yours.
• UI and design work. Russ owns that.
• Marketing voice strategy. Blair and Santiago own external positioning. Your voice surface is the knowledge base itself.