Head of Integrated Communications

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "About Lightfield", "The role", "What you'll own", "Who you are", "Nice to have", "Benefits & Perks", "Compensation Range". According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to appropriate headings. The posting does not have explicit "Responsibilities" etc. We need to create sections only when posting has real specific content. We can use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we must not create headings without content. The posting includes narrative about role, what you'll own (responsibilities), who you are (requirements/qualifications/skills), nice to have (additional qualifications), benefits & perks, compensation range (pay). There's no schedule mentioned. So we should include sections: About the role (maybe summarizing the role description), Responsibilities (what you'll own), Requirements (who you are), Qualifications (maybe same as requirements?), Skills (maybe overlapping), Benefits, Pay. However we must avoid duplication and filler. The instruction: Prefer a few substantive sections over many thin ones. So we could combine some. But we need to follow the given heading list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose those that have content. So we can have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Qualifications/Skills but could be merged. We must not repeat the job title as a heading. The job title is "Head of Integrated Communications". Not to be used as heading. We must not put Job ID etc. We must remove boilerplate etc. We need to preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... description ...

Responsibilities

• ... each bullet ...

Requirements

• ... each bullet ...

Benefits

• ... each bullet ...

Pay

Compensation Range: $210K - $260K

We need to extract content. Let's parse the posting. About Lightfield: description of company. That could be part of About the role? Actually "About Lightfield" is company overview. Could be part of About the role? The instruction says About the role heading for section headings (e.g. About the role...). So we can put company overview under About the role? Might be better to have About the role include both company and role. But we could also have separate About the role (company) and Responsibilities etc. The instruction says use About the role for section headings (e.g. About the role, Responsibilities...). So we can have About the role as a section that includes company overview and role description. That seems okay. Thus About the role: include Lightfield description and the role overview (the paragraph starting "The role Our best growth channel..."). Responsibilities: "What you'll own" bullet list. Requirements: "Who you are" bullet list (essential qualifications). Also maybe "Nice to have" could be separate but we could incorporate into Requirements as optional? Better to have a separate section for Nice to have? But we have no heading for Nice to have; we could treat as part of Requirements or Skills. Since we want few sections, we could combine Requirements and Nice to have into Requirements (with maybe split). But we must preserve all info; we can list both required and nice-to-have under Requirements with indication. However the instruction says do not emit heading followed by filler/placeholder text. Not relevant. We could have Requirements (mandatory) and Skills (nice-to-have). But we have both. Let's decide: Use Requirements for mandatory qualifications (Who you are). Use Skills for nice-to-have (Nice to have). That seems reasonable. Thus:

About the role

Lightfield is an AI-native CRM that assembles itself from your email, calendar, and meetings. It captures every interaction and turns it into organized context: accounts, tasks, follow-ups, and insights, so nothing slips through the cracks. We’re rethinking CRM from first principles. Instead of forcing teams to maintain rigid systems, Lightfield learns from how companies actually work, adapting, automating, and surfacing the insight that drives growth. We’re building the CRM platform we always wished existed: fast, intelligent, and genuinely helpful. The market agrees. Over 5,000 companies have used Lightfield since we launched in November, making us the fastest-adopted product in our category. We raised a $47M Series A led by a16z, with Greylock, Lightspeed, Coatue, Maverick and Audacious participating, and our founders previously built Tome, a generative AI presentation product used by over 25 million people. Before Lightfield, our team worked on Llama, Instagram, Facebook Messenger, Pinterest, Google, and Salesforce. The role Our best growth channel is people telling other people about Lightfield, and most of them arrived through a founder's post, a customer's recommendation, or a story that traveled. That's not an accident, but it isn't yet a machine. We're hiring a Head of Integrated Communications to build that machine, and to make Lightfield the default answer when someone asks how modern GTM should work — whether they're asking a reporter, asking Google, or asking AI. Almost nobody owns all three yet. You would. Press and content are one function here, not two. The same point of view has to hold up in a founder's essay, a journalist's story, a customer's case study, and an AI answer that cites us. You'll own it end to end: the narrative, the founders' voices in market, earned media, customer stories, search and answer-engine presence, and the creator relationships that carry all of it. The old comms playbook — press releases, managed quotes, quarterly media cycles — was built for a world where information moved slowly and institutions conferred trust. We're looking for someone who knows that and has a point of view on what replaces it. This is a builder's role with a wide surface area. You'll work directly with the founders and hire the team as the function grows. Reports to our Head of GTM.

Then Responsibilities: from "What you'll own" list. We need to extract each bullet. The "What you'll own" section includes: - The narrative. Message architecture and audience-specific tracks — practitioners, GTM leaders, the AI community, press, recruits — each tuned without diluting the substance, and held consistent across a company that changes shape every quarter. - The founders' voices. Keith and Henri have earned real credibility building and selling AI products. You'll turn that into a consistent, high-signal presence across posts, essays, podcasts, talks, and video, with a process that makes it sustainable rather than dependent on inspiration striking. You know how to extract a point of view from a busy founder in twenty minutes. - Earned media and emerging media. Relationships with the journalists, newsletter writers, podcasters and creators shaping how people talk about AI and GTM — built on trust over time, not on a media list. Coverage in the places our buyers actually read, plus the placements that sit outside traditional press entirely. - Customer stories. A repeatable pipeline: sourcing, interviewing, writing, distributing across formats. Word-of-mouth is our strongest growth lever and it runs on stories worth retelling. - SEO and AEO. Traditional organic search, plus the newer discipline of getting Lightfield accurately represented in AI answers — structured content, citable source material, and the technical foundations behind both. - The creator program. Identify and partner with the creators, operators, and practitioners whose audiences trust them. Real relationships, not one-off sponsorships. - The operating system. Editorial calendar, briefs, standards, freelance and agency bench, distribution playbook, and the analytics to know what's working. You'll scale output through contractors and agencies while staying hands-on enough to write the piece that has to be perfect. - Reputation and judgment calls. Scenario planning, rapid response, and the judgment to make the right call under pressure when something matters. We need to turn each into

. Could combine sentences but keep substance. Then Requirements: "Who you are" bullet list. Extract: - You're an exceptional writer and editor with taste and standards. - You have range — a founder's LinkedIn post, a technical explainer, a customer story, a press statement, and a newsletter all sound right coming from you. - Your portfolio shows real artifacts, not decks about artifacts, and you'd rather ship less and have it matter. - You've ghostwritten for a strong voice before. - You can capture how someone thinks and sounds, and produce work they'd have written if they'd had the time. - You have real media relationships and a proactive news sense. - You've placed stories that mattered, and the people behind them take your call because of how you've worked with them before. - You understand distribution as well as creation. Publishing is the easy half. You have a point of view on how a story travels in 2026 — social, newsletters, communities, creators, search, and AI answers. - You're fluent in modern search. You've done serious SEO work and you're already thinking hard about how AI assistants surface and cite sources. - You can talk credibly about both, and you've shipped against both. - You're AI-native. You use AI throughout your workflow — research, drafting, repurposing, coverage tracking, competitive intelligence — while keeping a bar for quality that most AI-assisted content never clears. - You operate at early-stage pace. You've built a function without a calendar handed to you. Comfortable with ambiguity, high standards, and shipping daily. - You're passionate about startups and modern GTM. Genuinely curious about how AI is reshaping how teams sell, and you want to be documenting it from the inside. That's a lot. We'll list each as

. Then Skills (nice to have): - Nice to have 8+ years across content, communications, editorial, or journalism, with meaningful time at a high-growth technology company. - Experience at a technical product company, or in a developer/data/AI-adjacent space. - You've built or run a creator or influencer program in B2B. - You've run original research or a benchmark report that the market actually cited. - Video and short-form production experience, or comfort being on camera yourself. - You've published work you'd point to as an example of how AI answers should cite a source. We'll list each as

. Benefits: from "Benefits & Perks" section. Extract: - Competitive salary - Meaningful early equity - Health insurance (medical, dental, vision) - 3 weeks of PTO - 11 paid company holidays + we enjoy a winter holiday break - 3 months of paid family leave - Wednesdays work from home - Regular team dinners, events, offsites, and retreats - 401k plan - Other perks include: commuter and lunch stipend We'll list each as

. Pay: from "Compensation Range: $210K - $260K". We'll put in

. We must not include schedule heading as none. Now ensure we don't repeat any content inadvertently. We need to output only HTML fragment. Let's craft. Be careful to escape any HTML special characters? The text includes ampersands