Lead UX Content Designer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. So we should we include? It mentions Consilio’s True North Values but that's not benefits. No explicit benefits, pay, schedule. So we should not include those sections.
We need sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list maybe), Skills (maybe list of skills), maybe "Qualities we're looking for" could be part of Qualities or Qualities? Could be under Qualities. The posting repeats "Qualities we're looking for" twice; we can combine.
We need to preserve all substantive information, not invent.
Let's extract content:
Intro: "Consilio builds eDiscovery and legal technology solutions used by legal teams at major organizations. Our users make consequential decisions inside our products — often under deadline, always under scrutiny. And the language in those interfaces is how they understand what the system did, what it's asking of them, and what happens next. We're hiring our first dedicated content strategist to own that layer across a portfolio of enterprise products. You'll sit at the intersection of language, product strategy, system logic, and emerging technology, and you'll be the authority on what we call things and how we explain them. You'd join a User Experience team built deliberately as a strategic function — design, research, content, and design systems together. The problems are unglamorous in the best way: dense workflows, real consequences, users who notice when language is imprecise. How This Role Operates This is not a copywriting role or an embedded-writer role. Instead of writing every string yourself, you'll build the infrastructure that lets other people write well without you: terminology systems, voice & tone, content patterns, and guardrails that keep AI-assisted drafting on-voice. You'll own the logic, taxonomy, and rationale behind our hardest content problems and scale that intent across products and teams. Expect to oscillate. Some weeks you'll be deeply embedded in a single high-leverage initiative. Others you'll operate consultatively across several product teams at once, setting direction and auditing what ships. Both modes require you to be persuasive without formal authority."
That's the "About the role" prose.
Responsibilities: bullet list after "Responsibilities". Let's extract:
- Content systems and governance. Build, govern, and maintain our voice & tone, terminology standards, and content pattern libraries that span our portfolio. And drive their adoption across internal and partner teams.
- Content strategy for AI-assisted experiences. Our products increasingly incorporate AI-driven capabilities. Lead how our products explain what AI did, how confident it is, and where human judgment is required.
- Strategic content architecture. Drive complex initiatives from problem framing forward, owning content structure, hierarchy, and flow including onboarding and in-product guidance alongside design and product.
- Audit, gap analysis, and roadmap. Assess content quality across products, define the target state, and own the plan to close the gap.
- Design system partnership. Own the content layer of our design system — voice and tone, UI terminology, taxonomy, content components and patterns — documented for others to use independently.
- Enablement and practice maturation. Upskill product designers, PMs, and partner teams through documentation, workshops, and review mechanisms.
- Quality assurance across the journey. Serve as the standing check on narrative coherence across live experiences, so that teams building in parallel don't fragment the customer journey.
These are responsibilities.
Qualifications: bullet list after "Qualifications". Let's extract:
- 10+ years in content strategy or content design
- At least 4 years building, governing, or contributing to content systems, terminology standards, or design system content layers across multiple products
- Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to
- Demonstrated experience influencing product and content direction without formal authority
- Fluency in Figma and a working understanding of how content maps to components and tokens
- Strong presentation skills, with the ability to build a persuasive narrative for executive audiences
Note: The third bullet is incomplete: "Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to". It seems cut off but we must preserve as is.
Qualities we're looking for: repeated twice. Let's extract unique list:
- Undaunted by domain complexity — you'll learn a specialized professional field deeply enough to debate its vocabulary with practitioners, and you'll find that energizing rather than tedious
- A systems thinker who treats terminology and content patterns as infrastructure with dependencies and maintenance costs
- Comfortable making a decision and defending it.
- Extreme attention to detail alongside genuine tolerance for ambiguity and unfinished ground
- Portfolio: A strong portfolio demonstrating complex content strategy across multiple web-based enterprise products, showing the reasoning behind the words and not just the words
Also "Nice to have" items:
- Experience establishing a content design practice where none existed
- Experience with explainability, confidence and uncertainty, or human-in-the-loop review in AI or ML-driven features
- Prior experience with legal technology, compliance, financial services, or another regulated, high-consequence domain
We could treat "Nice to have" as part of Qualifications or Skills? The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Qualifications (maybe includes required qualifications). Skills could be separate for skills like Figma, presentation skills etc. But we already have those in qualifications list. Could separate: Qualifications (years experience, etc.) and Skills (Figma, presentation, influencing). However the posting lumps them together. To follow instruction, we could create a Skills section for items like "Fluency in Figma and a working understanding of how content maps to components and tokens", "Strong presentation skills, with the ability to build a persuasive narrative for executive audiences". Also maybe "Experience designing content for AI-driven features" could be skill. But we need to avoid duplication. Let's decide: Qualifications: experience requirements (10+ years, 4 years building systems, etc.). Skills: Figma, presentation, influencing without formal authority? Actually influencing is a quality. Hmm.
Better: Keep Qualifications as the list of bullet points under "Qualifications" heading (including experience, AI-driven, influencing, Figma, presentation). Then create a separate "Qualities" section for the qualities list. And maybe a "Nice to have" section? Not in allowed headings; but we could incorporate into Qualifications or Skills as a subsection? The instruction says use those headings only; we can add other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section like "Nice to have" if we want, but it's not in the examples. Safer to stick to the given headings. We can put nice-to-have items under Qualifications or Skills as additional bullets.
Thus sections: About the role (p), Responsibilities (ul), Qualifications (ul), Skills (ul), Qualities (ul). No Benefits/Pay/Schedule.
Now we need to ensure we don't repeat duplicated lines. The qualities list appears twice; we will include once.
Now produce HTML fragment:
About the role
... (the intro paragraph(s) combined). Need to ensure we keep all substantive info. Let's craft a single paragraph that captures all. Might be long but okay.
We need to preserve line breaks? Not required; just prose.
Let's combine:
Consilio builds eDiscovery and legal technology solutions used by legal teams at major organizations. Our users make consequential decisions inside our products — often under deadline, always under scrutiny. And the language in those interfaces is how they understand what the system did, what it's asking of them, and what happens next. We're hiring our first dedicated content strategist to own that layer across a portfolio of enterprise products. You'll sit at the intersection of language, product strategy, system logic, and emerging technology, and you'll be the authority on what we call things and how we explain them. You'd join a User Experience team built deliberately as a strategic function — design, research, content, and design systems together. The problems are unglamorous in the best way: dense workflows, real consequences, users who notice when language is imprecise. How This Role Operates This is not a copywriting role or an embedded-writer role. Instead of writing every string yourself, you'll build the infrastructure that lets other people write well without you: terminology systems, voice & tone, content patterns, and guardrails that keep AI-assisted drafting on-voice. You'll own the logic, taxonomy, and rationale behind our hardest content problems and scale that intent across products and teams. Expect to oscillate. Some weeks you'll be deeply embedded in a single high-leverage initiative. Others you'll operate consultatively across several product teams at once, setting direction and auditing what ships. Both modes require you to be persuasive without formal authority.
Now Responsibilities ul.
Then Qualifications ul: include:
- 10+ years in content strategy or content design
- At least 4 years building, governing, or contributing to content systems, terminology standards, or design system content layers across multiple products
- Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to
- Demonstrated experience influencing product and content direction without formal authority
- Fluency in Figma and a working understanding of how content maps to components and tokens
- Strong presentation skills, with the ability to build a persuasive narrative for executive audiences
Now Skills ul: maybe we could separate Figma and presentation as skills, but they are already in qualifications. To avoid duplication, maybe we move those to Skills and keep qualifications as experience years etc. Let's decide: Qualifications: experience years, AI-driven experience, influencing without authority. Skills: Figma, presentation. That seems reasonable.
Thus Qualifications:
- 10+ years in content strategy or content design
- At least 4 years building, governing, or contributing to content systems, terminology standards, or design system content layers across multiple products
- Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to
- Demonstrated experience influencing product and content direction without formal authority
Skills:
- Fluency in Figma and a working understanding of how content maps to components and tokens
- Strong presentation skills, with the ability to build a persuasive narrative for executive audiences
Now Qualities ul:
- Undaunted by domain complexity — you'll learn a specialized professional field deeply enough to debate its vocabulary with practitioners, and you'll find that energizing rather than tedious
- A systems thinker who treats terminology and content patterns as infrastructure with dependencies and maintenance costs
- Comfortable making a decision and defending it.
- Extreme attention to detail alongside genuine tolerance for ambiguity and unfinished ground
- Portfolio: A strong portfolio demonstrating complex content strategy across multiple web-based enterprise products, showing the reasoning behind the words and not just the words
Nice to have items: we could add as a separate section "Nice to have" but not in allowed headings. Could incorporate into Qualifications or Skills as extra bullets. Perhaps add under Qualifications as additional bullet points: "Nice to have: Experience establishing a content design practice where
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. So we should we include? It mentions Consilio’s True North Values but that's not benefits. No explicit benefits, pay, schedule. So we should not include those sections. We need sections: About the role (intro paragraph), Responsibilities (list), Qualifications (list maybe), Skills (maybe list of skills), maybe "Qualities we're looking for" could be part of Qualities or Qualities? Could be under Qualities. The posting repeats "Qualities we're looking for" twice; we can combine. We need to preserve all substantive information, not invent. Let's extract content: Intro: "Consilio builds eDiscovery and legal technology solutions used by legal teams at major organizations. Our users make consequential decisions inside our products — often under deadline, always under scrutiny. And the language in those interfaces is how they understand what the system did, what it's asking of them, and what happens next. We're hiring our first dedicated content strategist to own that layer across a portfolio of enterprise products. You'll sit at the intersection of language, product strategy, system logic, and emerging technology, and you'll be the authority on what we call things and how we explain them. You'd join a User Experience team built deliberately as a strategic function — design, research, content, and design systems together. The problems are unglamorous in the best way: dense workflows, real consequences, users who notice when language is imprecise. How This Role Operates This is not a copywriting role or an embedded-writer role. Instead of writing every string yourself, you'll build the infrastructure that lets other people write well without you: terminology systems, voice & tone, content patterns, and guardrails that keep AI-assisted drafting on-voice. You'll own the logic, taxonomy, and rationale behind our hardest content problems and scale that intent across products and teams. Expect to oscillate. Some weeks you'll be deeply embedded in a single high-leverage initiative. Others you'll operate consultatively across several product teams at once, setting direction and auditing what ships. Both modes require you to be persuasive without formal authority." That's the "About the role" prose. Responsibilities: bullet list after "Responsibilities". Let's extract: - Content systems and governance. Build, govern, and maintain our voice & tone, terminology standards, and content pattern libraries that span our portfolio. And drive their adoption across internal and partner teams. - Content strategy for AI-assisted experiences. Our products increasingly incorporate AI-driven capabilities. Lead how our products explain what AI did, how confident it is, and where human judgment is required. - Strategic content architecture. Drive complex initiatives from problem framing forward, owning content structure, hierarchy, and flow including onboarding and in-product guidance alongside design and product. - Audit, gap analysis, and roadmap. Assess content quality across products, define the target state, and own the plan to close the gap. - Design system partnership. Own the content layer of our design system — voice and tone, UI terminology, taxonomy, content components and patterns — documented for others to use independently. - Enablement and practice maturation. Upskill product designers, PMs, and partner teams through documentation, workshops, and review mechanisms. - Quality assurance across the journey. Serve as the standing check on narrative coherence across live experiences, so that teams building in parallel don't fragment the customer journey. These are responsibilities. Qualifications: bullet list after "Qualifications". Let's extract: - 10+ years in content strategy or content design - At least 4 years building, governing, or contributing to content systems, terminology standards, or design system content layers across multiple products - Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to - Demonstrated experience influencing product and content direction without formal authority - Fluency in Figma and a working understanding of how content maps to components and tokens - Strong presentation skills, with the ability to build a persuasive narrative for executive audiences Note: The third bullet is incomplete: "Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to". It seems cut off but we must preserve as is. Qualities we're looking for: repeated twice. Let's extract unique list: - Undaunted by domain complexity — you'll learn a specialized professional field deeply enough to debate its vocabulary with practitioners, and you'll find that energizing rather than tedious - A systems thinker who treats terminology and content patterns as infrastructure with dependencies and maintenance costs - Comfortable making a decision and defending it. - Extreme attention to detail alongside genuine tolerance for ambiguity and unfinished ground - Portfolio: A strong portfolio demonstrating complex content strategy across multiple web-based enterprise products, showing the reasoning behind the words and not just the words Also "Nice to have" items: - Experience establishing a content design practice where none existed - Experience with explainability, confidence and uncertainty, or human-in-the-loop review in AI or ML-driven features - Prior experience with legal technology, compliance, financial services, or another regulated, high-consequence domain We could treat "Nice to have" as part of Qualifications or Skills? The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Qualifications (maybe includes required qualifications). Skills could be separate for skills like Figma, presentation skills etc. But we already have those in qualifications list. Could separate: Qualifications (years experience, etc.) and Skills (Figma, presentation, influencing). However the posting lumps them together. To follow instruction, we could create a Skills section for items like "Fluency in Figma and a working understanding of how content maps to components and tokens", "Strong presentation skills, with the ability to build a persuasive narrative for executive audiences". Also maybe "Experience designing content for AI-driven features" could be skill. But we need to avoid duplication. Let's decide: Qualifications: experience requirements (10+ years, 4 years building systems, etc.). Skills: Figma, presentation, influencing without formal authority? Actually influencing is a quality. Hmm. Better: Keep Qualifications as the list of bullet points under "Qualifications" heading (including experience, AI-driven, influencing, Figma, presentation). Then create a separate "Qualities" section for the qualities list. And maybe a "Nice to have" section? Not in allowed headings; but we could incorporate into Qualifications or Skills as a subsection? The instruction says use those headings only; we can add other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section like "Nice to have" if we want, but it's not in the examples. Safer to stick to the given headings. We can put nice-to-have items under Qualifications or Skills as additional bullets.
Thus sections: About the role (p), Responsibilities (ul), Qualifications (ul), Skills (ul), Qualities (ul). No Benefits/Pay/Schedule.
Now we need to ensure we don't repeat duplicated lines. The qualities list appears twice; we will include once.
Now produce HTML fragment:
About the role
... (the intro paragraph(s) combined). Need to ensure we keep all substantive info. Let's craft a single paragraph that captures all. Might be long but okay. We need to preserve line breaks? Not required; just prose. Let's combine: Consilio builds eDiscovery and legal technology solutions used by legal teams at major organizations. Our users make consequential decisions inside our products — often under deadline, always under scrutiny. And the language in those interfaces is how they understand what the system did, what it's asking of them, and what happens next. We're hiring our first dedicated content strategist to own that layer across a portfolio of enterprise products. You'll sit at the intersection of language, product strategy, system logic, and emerging technology, and you'll be the authority on what we call things and how we explain them. You'd join a User Experience team built deliberately as a strategic function — design, research, content, and design systems together. The problems are unglamorous in the best way: dense workflows, real consequences, users who notice when language is imprecise. How This Role Operates This is not a copywriting role or an embedded-writer role. Instead of writing every string yourself, you'll build the infrastructure that lets other people write well without you: terminology systems, voice & tone, content patterns, and guardrails that keep AI-assisted drafting on-voice. You'll own the logic, taxonomy, and rationale behind our hardest content problems and scale that intent across products and teams. Expect to oscillate. Some weeks you'll be deeply embedded in a single high-leverage initiative. Others you'll operate consultatively across several product teams at once, setting direction and auditing what ships. Both modes require you to be persuasive without formal authority. Now Responsibilities ul. Then Qualifications ul: include: - 10+ years in content strategy or content design - At least 4 years building, governing, or contributing to content systems, terminology standards, or design system content layers across multiple products - Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to - Demonstrated experience influencing product and content direction without formal authority - Fluency in Figma and a working understanding of how content maps to components and tokens - Strong presentation skills, with the ability to build a persuasive narrative for executive audiences Now Skills ul: maybe we could separate Figma and presentation as skills, but they are already in qualifications. To avoid duplication, maybe we move those to Skills and keep qualifications as experience years etc. Let's decide: Qualifications: experience years, AI-driven experience, influencing without authority. Skills: Figma, presentation. That seems reasonable. Thus Qualifications: - 10+ years in content strategy or content design - At least 4 years building, governing, or contributing to content systems, terminology standards, or design system content layers across multiple products - Experience designing content for AI-driven features, or a clear, well-reasoned point of view on how to - Demonstrated experience influencing product and content direction without formal authority Skills: - Fluency in Figma and a working understanding of how content maps to components and tokens - Strong presentation skills, with the ability to build a persuasive narrative for executive audiences Now Qualities ul: - Undaunted by domain complexity — you'll learn a specialized professional field deeply enough to debate its vocabulary with practitioners, and you'll find that energizing rather than tedious - A systems thinker who treats terminology and content patterns as infrastructure with dependencies and maintenance costs - Comfortable making a decision and defending it. - Extreme attention to detail alongside genuine tolerance for ambiguity and unfinished ground - Portfolio: A strong portfolio demonstrating complex content strategy across multiple web-based enterprise products, showing the reasoning behind the words and not just the words Nice to have items: we could add as a separate section "Nice to have" but not in allowed headings. Could incorporate into Qualifications or Skills as extra bullets. Perhaps add under Qualifications as additional bullet points: "Nice to have: Experience establishing a content design practice where