Overview
Skills
Job Details
Job ID: H#12895 - UI Design System Documentation Specialist
PLEASE NOTE: This is a 3 month renewable contract and needs to meet Client full-time conversion policies. Those dependent on a work permit sponsor now or anytime in the future (ie H1B, OPT, CPT, etc) do not meet Client requirements for this opening.
Top 3 Must Haves:
1. Design system documentation writing (3-5 years)
2. Design token documentation writing (1-3 years)
3. Design system design & development (5-7 years)
What does the structure/makeup of the team currently look like?
- We have one UX team member dedicated to the design system and are looking for allocation to bring on a technical writer to assist with documentation writing
What will this contractor be accomplishing for your team? In what Capacity does this role integrate with other departments?
- Writing documentation for consumers of the design system to understand and implement the foundational styles and components appropriately and strategically
What will this contractor be working on / are there specific projects?
- The Hartford s enterprise design system, HUK
What makes this role stand out / what are some unique selling points?
- New and emerging design system based on design tokens; UX and Dev consumers will need to learn and understand the new styles and component configuration options
- Define best practices/standards, template, and format for our design system s documentation
Describe your expectations for training once a worker starts and expected ramp up.
- Will provide overview and location of resources where essential information and content for documentation can be found; expectation is they ll be able to hit the ground running drafting a content format then gathering and distilling information into separate stories that will be funneled into one of our existing design system docs sites
What tools or technologies do you want this contractor to have experience with/how will they be interacting with these tools in this role?
- Design Systems
- Design tokens
- Figma
- Fundamental understanding of front-end development
Are their certain KPI s or deliverables that will be expected by this candidate?
- Content pattern defined and documentation for foundational styles and core components written
What type of background should this contractor have in order to meet the needs of your team? Do they need to hold a specific degree or certification?
- Design systems
We re hiring a documentation specialist to help teams understand and implement the HUK design system effectively. This role focuses on writing clear, actionable documentation for design tokens, Web Components, and implementation guidance making it easier for designers, engineers, QA, and product partners to use HUK strategically and consistently.
HUK is a framework-agnostic web component library built on StencilJS, utilizing the Bootstrap5 framework with a custom foundational stylesheet. HUK has a companion Figma library that also houses the source of truth for all design tokens that connect design decisions to implementation.
Why This Role Matters Now: As we scale HUK v2.x (BS5), maintain high-quality Figma libraries, and drive token-based change management, clarity and consistency are critical. A dedicated documentation lead ensures our design system remains cohesive and actionable across disciplines.
Responsibilities:
- Create and maintain authoritative documentation that helps consumers of the design system understand what s available and how to use it:
- Foundational Styles: Document how to implement HUK s foundational styles colors, typography, spacing, etc. using CSS variables, SCSS tokens, and Bootstrap 5 classes.
- Figma Code Mapping: Clarify how Figma v2.x components relate to HUK tokens and components, including naming conventions, variants, and breakpoints.
- Designer-Facing Component Documentation: Document configuration and customization options, properties, usage guidance, accessibility notes for the components to inform designers on what's possible
- Design Tokens: Document token taxonomy, usage rules, and how tokens map to components and Figma assets.
- Implementation Guidance: Provide examples and best practices for integrating HUK components
- Accessibility Patterns: Document accessible usage patterns aligned to WCAG 2.x.
- Discoverability & IA: Organize documentation for easy navigation and search across SharePoint/Pages; define editorial style and templates.
- Training & Enablement: Create quick-start guides, onboarding checklists, and workshop materials for designers and developers.
Must-Have Qualifications:
- Hands-on experience with design systems (tokens, components, guidelines) and fluency in front-end code (TypeScript/JavaScript, HTML/CSS).
- Experience documenting Web Components or React/Angular APIs.
- Familiarity with Bootstrap 5 layout, grids, and breakpoints.
- Proven ability to write clear, concise component documentation and reference content.
- Strong grasp of design tokens and their role in implementation and change management.
- Excellent collaboration skills across UX, engineering, and QA.
- Working knowledge of accessibility standards (WCAG 2.x).
Nice to Have:
- Experience documenting Stencil components or similar compiler-based toolchains.
- Familiarity with large-scale Figma libraries (variants, theming, tokens).
- Exposure to migration documentation and change-management playbooks.
- Experience creating internal FAQs, knowledge bases, and release communications.
Key Deliverables:
- 1. Foundational Styles Documentation: Complete documentation for all Foundational styles - colors, typography, spacing, etc. using CSS variables, SCSS tokens, and Bootstrap 5 classes
- 2. Designer-Facing Component Doc: Complete documentation for existing component library (usage, props, events, accessibility, code samples)
- 3. Design Dev Bridge: Mapped guide from Figma v2.x components to HUK tokens and components.
- 4. Token Reference: Clear documentation of token taxonomy and usage rules.
- 5. Docs IA & Style Guide: Information architecture and editorial style for HUK docs
Success Metrics:
- Adoption & Satisfaction: Increased integration success and positive feedback from UX/Eng teams.
- Time-to-Integrate: Reduced time to implement HUK components and styles
- Doc Quality: Improved freshness, search success, and reduced unresolved questions.
- Migration Progress: % of target apps migrated from HUK1 to HUK2.x supported by your documentation