Technical Education Specialist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - "Who We Are" description: Notion description. Could be considered "About the company"? Not requested heading. Not needed. - "About The Role": paragraph describing role. That's content for About the role. - "What You'll Achieve": bullet points (by day 90, by year one). That could be Responsibilities or maybe "What You'll Achieve" is like goals. Could map to Responsibilities. - "Skills You'll Need To Bring": list of skills. That's Skills section. - "Nice To Haves": list of nice-to-haves. Could be Qualifications? Or maybe Requirements? The posting includes "Skills You'll Need To Bring" and "Nice To Haves". Could treat Skills as Skills section, Nice To Haves as Qualifications or Requirements? Usually Requirements are must-haves, Nice To Haves are preferred. So we can put Skills You'll Need To Bring under Skills, and Nice To Haves under Qualifications (or Requirements). But we need to follow headings: Skills, Qualifications, Requirements. We have both Skills and Nice To Haves. We could put Skills under Skills, Nice To Haves under Qualifications (since they are preferred qualifications). Requirements maybe not present explicitly; we could omit Requirements if no specific content. But we could treat Skills You'll Need To Bring as Requirements? However they are labeled Skills. We'll follow the headings: Skills for the list under "Skills You'll Need To Bring". Qualifications for "Nice To Haves". Requirements maybe omitted. - Pay: The posting includes compensation: "For roles based in New York City, the estimated base salary range for this role is $118,000 - $147,000 per year." Also mentions equity and benefits but not specific. So we have Pay section with that range. - Benefits: The posting mentions "Notion is committed to providing highly competitive cash compensation, equity, and benefits." Not specific benefits listed. No detail. So we should not create Benefits section unless specific content. Since no specific benefits listed, we omit Benefits. - Schedule: The posting mentions "We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days)". That's schedule info. So we can create Schedule section with that. - About the role: we have paragraph. - Responsibilities: we have "What You'll Achieve" bullet points (by day 90, by year one). Those are achievements/goals; could be responsibilities. We'll put under Responsibilities. - Also there is "About The Role" heading already; we need to use

for section headings. So we will have

About the role

then paragraph. - Then

Responsibilities

with

• items. - Then

  Skills

  with list. - Then

  Qualifications

  with list (Nice To Haves). - Then

  Pay

  with paragraph (salary range). - Then

  Schedule

  with paragraph (office days). We must not include sections with filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove all that. We must preserve all substantive information: ensure we keep all details from sections we include. Let's extract exact text. About The Role paragraph: "As Notion’s product surface expands, we need a builder-teacher who can turn new capabilities into technically accurate education that helps customers confidently build with Notion. In this role, you’ll explore Notion’s newest capabilities, teach by showing, and ship as the product evolves. You’ll be the technical face of Notion Academy: leading workshops, recording walkthroughs, and building implementation guides. This role is based in New York City. We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days) because we do our best thinking and building together in person. We’re looking for someone who’s excited to work alongside the team during those days." Note: The schedule sentence appears also in this paragraph. But we will also have Schedule section; we might duplicate if we keep schedule sentence in About the role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we move schedule sentence to Schedule section, we should remove it from About the role to avoid duplication? The instruction says preserve all substantive information; duplication is okay? It says remove duplicated lines. So we should avoid duplicated lines. The schedule sentence appears in About The Role paragraph; we also have a Schedule section. To avoid duplication, we could keep schedule sentence only in Schedule section and remove from About the role. However the About the role paragraph also includes location (New York City) and the anchor days. If we remove schedule sentence, we lose mention of Anchor Days and location? Location is also in that sentence: "This role is based in New York City." We could keep location in About the role and move schedule details to Schedule section. Let's see: The sentence: "This role is based in New York City. We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days) because we do our best thinking and building together in person. We’re looking for someone who’s excited to work alongside the team during those days." We could split: Keep "This role is based in New York City." in About the role. Move the schedule sentence to Schedule section. The last sentence about excitement could be kept in About the role or maybe also schedule? It's about excitement to work alongside the team during those days; it's related to schedule. Might be okay to keep in About the role as motivational. But to avoid duplication, we could keep it in About the role as it's not duplicated elsewhere. However the phrase "during those days" refers to Anchor Days; if we move Anchor Days to Schedule, the reference may be unclear. But we can keep it. Better: Keep About the role paragraph as is, and also have Schedule section with the same info? That would duplicate the schedule sentence. The instruction says remove duplicated lines. So we should not duplicate. So we need to decide where to place schedule info. Since Schedule section is explicitly requested, we should put schedule details there, and adjust About the role to not include schedule details. We can keep location and maybe the excitement sentence but rephrase to avoid referencing days? Could keep excitement sentence but change "those days" to "the team"? Might be altering meaning. Better to keep About the role as original but then not have Schedule section? But we have schedule info, so we should include Schedule section. The instruction: "include a section ONLY when the posting has real, specific content for it". It does not forbid duplication, but earlier says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we must remove duplicated lines. So we cannot have the same sentence appear twice. So we need to split. Thus we will edit About the role to remove the schedule sentences, but keep location and maybe excitement? Let's see: The excitement sentence: "We’re looking for someone who’s excited to work alongside the team during those days." This also references days. If we remove schedule, this sentence becomes odd. Could we keep it but change to "We’re looking for someone who’s excited to work alongside the team." That's a slight change but preserves meaning? It removes reference to days, but still conveys excitement. Might be considered altering content. However we could keep it as is and still have Schedule section with the schedule details; duplication of "We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days)" would be duplicated, but the excitement sentence is not duplicated. The duplication would be only the schedule sentence. So we could keep About the role as is, and Schedule section just contain the schedule sentence (maybe shortened). That would duplicate the schedule sentence exactly. That's not allowed. Thus we need to avoid duplication. Let's decide to put schedule info in Schedule section, and adjust About the role to exclude the schedule sentences but keep location and maybe excitement rephrased without referencing days. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Changing wording could be considered summarizing or altering. But we could keep the excitement sentence as is, but it's okay if it references days even if we moved schedule details elsewhere; it's not duplicated, just referencing. The schedule details are elsewhere; the excitement sentence still makes sense if the reader knows about Anchor Days from Schedule section. It's not duplicated. So we can keep About the role paragraph unchanged, and Schedule section just contain the schedule sentence? That would duplicate the schedule sentence exactly as it appears in About the role. Actually the schedule sentence is: "We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days) because we do our best thinking and building together in person." If we keep that sentence in About the role, and also put it in Schedule section, that's duplication. So we need to avoid that duplication. We could keep the sentence in About the role and not have a separate Schedule section, but we have schedule info, so we need Schedule section. Could we put schedule info in Schedule section but not duplicate the exact sentence, maybe rephrase? The instruction says do not invent or summarize away detail. Rephrasing could be considered summarizing but maybe acceptable if we keep all detail. For example, Schedule section could say: "Office work required on Mondays, Tuesdays, and Thursdays (Anchor Days)." That retains the detail but is not identical sentence. It's a summary but retains all detail (days, Anchor Days). It's not inventing. It's a concise representation. I think that's acceptable. Thus we will have About the role paragraph as original (including location and excitement). Schedule section will have a concise statement: "Office work required on Mondays, Tuesdays, and Thursdays (Anchor Days)." That captures the detail. Now let's extract other sections. What You'll Achieve: Bullet points: - By day 90: Expand Notion’s technical education library. Author technically rigorous Academy content, implementation guides, and Help Center resources that make our most complex capabilities easier to understand and adopt. - By day 90: Become a trusted voice for Notion Academy. Teach customers through video, live webinars, and workshops, demonstrating real workflows and solving problems in real time. - By day 90: Build with Notion’s newest capabilities. Get hands-on with new product features, use customer insights to identify high-value use cases, and determine top priority workflows for education to focus on. - By year one: Reimagine learning with AI. Experiment with adaptive, contextual learning experiences that respond to what customers are trying to build and where they need help. - By year one: Prove and scale the impact of technical education. Use product adoption signals to measure impact and improve what we teach, then build reusable standards to help the team deliver effective technical learning faster. We need to put these under Responsibilities as
  • . Skills You'll Need To Bring list: - Builder mindset: You learn new product features by getting hands-on, experimenting, and building until you understand. - Comfort navigating technical content: you don’t need to write code, but you can read a technical architecture doc, identify what’s outdated, and work with engineers to fix it. - Customer-facing credibility: You’re comfortable teaching, building, and troubleshooting in front of customers. - AI experimentation: You actively use AI to build, learn, and teach technical proficiency. - Product expertise: You can quickly understand a new feature, identify where it creates meaningful customer value, and turn that into practical use cases. We'll put under Skills. Nice To Haves: - Notion product expertise - Experience in a customer-facing technical role, such as solutions