eLearning Designer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Us (but we don't repeat job title; we can include About Us? The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid other headings, but we should follow the list. Likely we should include About the role (the description of role), Responsibilities (What You’ll Do), Requirements/Qualifications/Skills (What You Are), Compensation Range (Pay). Benefits not mentioned, Schedule not mentioned. Also maybe About Us could be omitted because not in list; but we could include as a paragraph? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; not required to only use those, but likely they expect those. We'll include About the role, Responsibilities, Requirements (or Qualifications?), Skills, Pay. We need to decide mapping. The posting: "About The Role" then description. Then "What You’ll Do" responsibilities. Then "What You Are" qualifications/skills. Then "Compensation Range: $105K - $120K". No benefits, schedule. Thus sections: About the role, Responsibilities, Qualifications (or Requirements), Skills, Pay. Could combine Requirements and Qualifications? The posting lists both requirements and skills in "What You Are". We could split: Requirements (years experience, preferred experience), Skills (visual design, authoring tools, etc). But we can also just have one section "Qualifications". However instruction says use headings for those categories; we can include multiple if content exists. Let's extract: About the role: paragraph describing Fieldguide University and role. Responsibilities: bullet list from "What You’ll Do". Each sentence could be a list item. Qualifications/Requirements: bullet list from "What You Are": 3+ years designing and developing eLearning courses, portfolio, strongly preferred: hands-on experience in audit, advisory, or accounting, familiarity with CPE requirements is a strong plus, nice to have – B2B SaaS or technical product context, experience building learning content for an AI-native product, comfort producing screen recordings and product screenshots from a live application, proficient in a major authoring tool (Articulate Storyline, Rise, Adobe Captivate, or similar), WorkRamp familiarity is a plus but learnable, General LMS experience is what matters, Strong visual design skills applied to learning, You work well with subject matter experts, Enough instructional design background to write learning objectives, build storyboards, and flag problems with content architecture. We could separate into Requirements (must-haves) and Skills (nice-to-haves). Must-haves: 3+ years designing and developing eLearning courses, portfolio showing production quality and visual design capability, Strong visual design skills applied to learning, You work well with subject matter experts, Enough instructional design background to write learning objectives, build storyboards, and flag problems with content architecture. Also proficient in a major authoring tool (maybe required). General LMS experience is what matters (maybe required). We'll decide. Skills: hands-on experience in audit/advisory/accounting (preferred), familiarity with CPE requirements (plus), B2B SaaS or technical product context, experience building learning content for AI-native product, comfort producing screen recordings/product screenshots, WorkRamp familiarity (plus). We'll put those under Skills. Pay: Compensation Range: $105K - $120K. We must not include boilerplate like About Us? Could include as a paragraph before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid other headings, but we should follow the pattern. I'd include a brief About Us paragraph as

before sections, not as heading. Thus output HTML fragment:

About Us Fieldguide is establishing a new state of trust for global commerce and capital markets. We enhance trust by augmenting the work of assurance and audit practitioners with AI agents. Put simply, we build software for the people who enable trust between businesses. We are based in San Francisco and built as a remote-first company. We have raised over $125M in venture funding from top investors including Goldman Sachs, Bessemer Venture Partners, 8VC, Floodgate, Y Combinator, Justin Kan, and Elad Gil. More than 50% of the top-100 CPA firms are customers, including several Big 4 firms, with an industry-leading NPS to match. We value diversity, both in backgrounds and in experiences. We need people from all backgrounds and walks of life to help build the future of audit and advisory. Fieldguide's team is inclusive, driven, humble and supportive.

Then sections. Make sure to use

for each section heading. Responsibilities:

• Own course production end to end. Take product documentation and subject matter expert input, and turn it into a visually polished, interactive, pedagogically sound course.
... etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet as close as possible. Let's list responsibilities exactly as in text: - Own course production end to end. Take product documentation and subject matter expert input, and turn it into a visually polished, interactive, pedagogically sound course. - You write the learning script, storyboard the screens, design the visuals, build the interactions, and publish in WorkRamp. - Write for learners, not readers. Shape technical documentation into on-screen copy with the right length, tone, and chunking. - Define measurable learning objectives for each module alongside the subject matter expert. - Build the interactive layer. Knowledge checks, scenario-based activities, and exercises that give each course a real balance of reading and doing. - Make sure every interaction serves the learning goal and works across delivery contexts. - Establish a visual design language for Fieldguide University. There is no design system for course content yet. Creating a reusable one is an explicit deliverable of the first engagement, not a nice-to-have. - Build and QA in the LMS. Structure course hierarchy, configure settings, produce landing pages and banners, and QA formatting, links, and presentation before publication. - Write assessments. Multiple-choice and other question types aligned to learning objectives, configured in WorkRamp with scoring and certification logic. - Push back. If a module is too long, a concept is unclear, or a proposed interaction does not serve the learner, say so. We want a peer collaborator, not an order-taker. We'll keep each as
• . Now Requirements (must-haves) and Skills (nice-to-haves). Let's extract must-haves from "What You Are": - 3+ years designing and developing eLearning courses, with a portfolio that shows production quality and visual design capability. - Strong visual design skills applied to learning. You understand how to design for on-screen reading, interaction, and learner attention. - You work well with subject matter experts. You can run an SME interview, synthesize documentation, and come back with a structure that holds up. - Enough instructional design background to write learning objectives, build storyboards, and flag problems with content architecture. - Proficient in a major authoring tool. Articulate Storyline, Articulate Rise, Adobe Captivate, or similar. WorkRamp familiarity is a plus but learnable. General LMS experience is what matters. We could treat "proficient in a major authoring tool" as requirement; WorkRamp familiarity as plus but learnable (maybe skill). General LMS experience is what matters (requirement). We'll keep as requirement. Now Skills (nice-to-haves / preferred): - Strongly preferred: hands-on experience in audit, advisory, or accounting, whether as a practitioner, a trainer or L&D specialist inside a firm. - Familiarity with CPE requirements is a strong plus. - Nice to have – B2B SaaS or technical product context, experience building learning content for an AI-native product, and comfort producing screen recordings and product screenshots from a live application. - WorkRamp familiarity is a plus but learnable (already mentioned). Could be under skills. We'll put these under Skills. Pay:

  Compensation Range: $105K - $120K

  maybe within a Pay section heading. Thus final HTML:

  About Us ...

  About the role

  Fieldguide University is our customer-facing learning platform. It is a product-adjacent learning system that reduces time to value, drives feature adoption, and removes preventable friction from the customer lifecycle. Courses are persona-driven, so an admin configuring frameworks and a first-year associate testing controls get different learning experiences, not the same product tour. We are looking for an eLearning Designer, who owns the production-heavy parts of course building including visual design, interactive elements, and multimedia. The remaining customer education team will continue to own product knowledge, learner personas, and course goals. It is a collaboration between domain experts and a learning production specialist.

  Responsibilities

  • Own course production end to end. Take product documentation and subject matter expert input, and turn it into a visually polished, interactive, pedagogically sound course.
  • You write the learning script, storyboard the screens, design the visuals, build the interactions, and publish in WorkRamp.
  • Write for learners, not readers. Shape technical documentation into on-screen copy with the right length, tone, and chunking.
  • Define measurable learning objectives for each module alongside the subject matter expert.
  • Build the interactive layer. Knowledge checks, scenario-based activities, and exercises that give each course a real balance of reading and doing.
  • Make sure every interaction serves the learning goal and works across delivery contexts.
  • Establish a visual design language for Fieldguide University. There is no design system for course content yet. Creating a reusable one is an explicit deliverable of the first engagement, not a nice-to-have.
  • Build and QA in the LMS. Structure course hierarchy, configure settings, produce landing pages and banners, and QA formatting, links, and presentation before publication.
  • Write assessments. Multiple-choice and other question types aligned to learning objectives, configured in WorkRamp with scoring and certification logic.
  • Push back. If a module is too long, a concept is unclear, or a proposed interaction does not serve the learner, say so. We want a peer collaborator, not an order-taker.

  Requirements

  • 3+ years designing and developing eLearning courses, with a portfolio that shows production quality and visual design capability.
  • Strong visual design skills applied to learning. You understand how to design for on-screen reading, interaction, and learner attention.
  • You work well with subject matter experts. You can run an SME interview, synthesize documentation, and come back with a structure that holds up.
  • Enough instructional design background to write learning objectives, build storyboards, and flag problems with content architecture.
  • Proficient in a major authoring tool (Articulate Storyline, Articulate Rise, Adobe Captivate, or similar). General LMS experience is what matters.

  Skills

  • Hands-on experience in audit, advisory, or accounting, whether as a practitioner, a trainer or L&D specialist inside a firm (strongly preferred).
  • Familiarity with CPE requirements (strong plus).
  • B2B SaaS or technical product context, experience building learning content for an AI-native product, and comfort producing screen recordings and product screens