layiq

/la·yiq/adjective

worthy; deserving; fitting; suitable.

A role, opportunity, or path that merits attention, time, and pursuit.

Operating Memory Lead at Harper | LAYIQ

Capture tribal knowledge.
Embed with sales, intake, service, placements, and renewals. Sit with operators, shadow workflows, listen to calls, read transcripts, and document what people "just know."
Build operating memory.
Turn transcripts, Slack threads, Looms, and one-off explanations into source-of-truth docs, decision logs, playbooks, process maps, onboarding paths, and glossaries.
Use AI as a force multiplier.
Build repeatable workflows that turn raw context into decisions, owners, open loops, SOPs, training material, and product requirements.
Make meetings AI-legible.
Shape conversations in real time so they produce useful artifacts — decisions, owners, definitions, edge cases, unresolved questions, next steps. Ask the questions that turn a meeting into an artifact: who owns this, what's the exception, what's the source of truth, what would someone misread from the transcript alone.
Find the edge cases.
Document where workflows break — reworks, escalations, stale quotes, underwriter follow-ups, payment/binder gaps, COI delays, customer confusion.
Translate ops into product.
Sit between operators and engineering; capture what people do, where tools fail, what workarounds exist, what needs to be built.
Maintain the knowledge base.
Keep docs current, assign owners, kill stale guidance, make sure people know where the truth lives.
Turn repeated problems into systems.
If the same issue happens three times, it becomes a playbook, a QA check, a training artifact, or a product requirement.
Who you are
An exceptional writer and synthesizer who can turn a messy transcript into a clear operating doc the same day.
Genuinely
AI-native in practice
— not "I use ChatGPT," but you have taste for when an output is structurally wrong, not just stylistically off. You prompt for extraction (decisions, contradictions, owners, edge cases), not just summarization, and you know good output depends on good context you engineer upstream.
Curious about how organizations actually work, and you like sitting with operators.
You notice hidden assumptions, missing ownership, and contradictions other people walk past.
Structured but not bureaucratic; you care whether documentation changes behavior, not whether it looks polished.
Low-ego, persistent, and allergic to "someone should probably document that."

Operating Memory Lead

Employer job description

The role

What you'll do

Requirements:

Compensation & logistics

Salary:

Location:

Schedule:

Benefits:

About this listing