Growth Lead, Organic

We need to output HTML fragment with sections for headings present: About the role? Actually the posting includes "About Middesk" then "The Role" then "Hybrid" then "What You'll Do" then "What we're looking for:" then "Bonus points". According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map headings to those standard names? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those exact headings if they exist. But we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those headings for sections that match. The posting has sections: About Middesk (maybe not needed as heading? It's about company, could be omitted? 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 like About Middesk. But they gave examples of headings to use. Probably we should map content to those standard headings where appropriate: About the role (maybe corresponds to "The Role"), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (What we're looking for + Bonus points), Benefits (none), Pay (none), Schedule (Hybrid). Also we might include an "About Middesk" as a

maybe not a heading. But they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections to include. We have content: - About Middesk: description of company. Could be placed as a

before sections, not as heading? Might be okay as a

without heading. But they said use

for section headings (e.g. About the role...). They didn't forbid other headings, but they gave examples. Safer to follow their examples: Use headings only from that list if we have content. So we need to map: About the role: corresponds to "The Role" section. We'll put

About the role

and then content. Responsibilities: corresponds to "What You'll Do". We'll put

Responsibilities

with list. Requirements / Qualifications / Skills: Could combine into one section? They said prefer a few substantive sections over many thin ones. Could combine Requirements, Qualifications, Skills into one

Requirements

maybe. But we have "What we're looking for:" and "Bonus points". Both are about qualifications/skills. We'll combine them into a single

Requirements

(or maybe

Qualifications

). Choose one. Let's use

Qualifications

as it's in examples. Benefits: none -> omit. Pay: none -> omit. Schedule: Hybrid work model details -> we have schedule info. So

Schedule

with content. Also we might include an introductory paragraph about Middesk as

before headings. We must not include boilerplate like EEO etc. Not present. We must preserve all substantive information. So we need to include details from each section. Let's extract content. About Middesk paragraph: "Middesk is building the data and intelligence infrastructure that helps businesses work together with confidence. We started by creating a comprehensive platform for understanding businesses, bringing together authoritative and proprietary data to help customers verify business identities, onboard customers faster, and manage risk throughout the customer lifecycle. Today, Middesk is used by more than 700 banks and fintechs, and in 2025 we verified more than 7 million companies. We've also expanded beyond business verification to help companies form, register, manage, and maintain their businesses, supporting more than 50,000 companies in setting up over 100,000 accounts required to hire employees, run payroll, and stay compliant. Middesk came out of Y Combinator, and is backed by Sequoia Capital, Accel, Insight Partners, and Canapi. We're proud to be named on the Forbes Fintech 50 and Best Startup Employers lists." That's all. The Role section: "Enterprise go to market is consolidating around precision, and AI is accelerating that shift. Signal and intent data, automated research, and agentic outreach tooling are making it possible to build a real system around a defined set of accounts instead of running broader campaigns at more names, and the companies winning right now are the ones building that system first. This role owns that system at Middesk: the named enterprise and mid-market account list itself, the research and signal engine behind it, and every coordinated campaign, outbound, paid, SEO/AEO, and events, built around it. You will own the pipeline number this account list produces end to end, even though most of the people who execute against it, the AEs and SDRs, don't report to you. You will work closely with them, and you will set the standard, the research, and the operating rhythm the whole motion runs against." Hybrid: "We follow a hybrid work model, and for this role there is an expectation of 2- 3 days per week in our NYC or SF office. Candidates should be based within a commutable distance, as we believe in the value of in person collaboration and building strong team connections while also supporting flexibility where possible." What You'll Do: bullet list (each line starts with a verb). We need to convert to

• . List items: - Own Middesk's qualified new logo pipeline number across enterprise and mid-market named accounts, end to end - Build and maintain a documented named account list by segment, with clear criteria, a re-audit cadence, and refresh as deals close - Stand up account enrichment and research: AI-enabled signal and intent data, automated research, investor and network mapping, contact enrichment - Build scalable, coordinated outreach systems across email, cold calling, LinkedIn, and every other channel that reaches these accounts - Orchestrate ads, SEO/AEO, and targeted events around named accounts so every channel reinforces outreach rather than running in isolation - Design AI-enabled, trigger based automated workflows, event and intent triggers, follow up cadences, paid ads tied to SDR outreach, so channels work together instead of as one off campaigns - Write the coverage standard AEs and SDRs work against, and run the weekly rhythm that holds the team to it What we're looking for: paragraph then bullet list? Actually it's a paragraph then bullet list? The text: "What we're looking for: A strategic thinker who can see the whole account motion, the list, the research, the outreach, and the campaigns, and build one coordinated system rather than run a single channel of campaigns against the listA track record of personally owning a number end to end in a high-growth environment, whether that's sales, pipeline, marketing, or account management, including when the people who drive that number don't report to youA strong executor as well as a strategist. You will build the plan and also do real work yourself, the list, the research, the first campaignsComfortable working directly with sales leaders and reps, and confident enough to hold a peer AE and SDR team to a standard you set, without managing themComfortable using AI tools to build and scale research, enrichment, and outreach systems, not just to write copy fasterA background like management consulting, or an early operating role at a high growth startup, is common but not requiredDoes not need to come from a narrow ABM campaign background. This role is about owning the whole coverage system and the sales relationship that runs on it, not running campaigns at a distance from sales" It seems missing punctuation and line breaks. We need to parse into bullet points? The original likely had bullet points but got merged. We'll need to split into sensible bullet points. Let's try to identify separate clauses: - A strategic thinker who can see the whole account motion, the list, the research, the outreach, and the campaigns, and build one coordinated system rather than run a single channel of campaigns against the list - A track record of personally owning a number end to end in a high-growth environment, whether that's sales, pipeline, marketing, or account management, including when the people who drive that number don't report to you - A strong executor as well as a strategist. You will build the plan and also do real work yourself, the list, the research, the first campaigns - Comfortable working directly with sales leaders and reps, and confident enough to hold a peer AE and SDR team to a standard you set, without managing them - Comfortable using AI tools to build and scale research, enrichment, and outreach systems, not just to write copy faster - A background like management consulting, or an early operating role at a high growth startup, is common but not required - Does not need to come from a narrow ABM campaign background. This role is about owning the whole coverage system and the sales relationship that runs on it, not running campaigns at a distance from sales We'll make
  • for each. Bonus points: "Bonus points Experience owning or building a named account or ABM motion at a B2B SaaS or fintech companyExperience orchestrating multi channel account based outreach (executive outbound, targeted events, paid, SEO/AEO) as one coordinated systemFamiliarity with modern outbound and signal or intent tooling (Clay, Apollo, or equivalent), and a point of view on where AI can replace manual research and enrichment work" Again missing punctuation. We'll split: - Experience owning or building a named account or ABM motion at a B2B SaaS or fintech company - Experience orchestrating multi channel account based outreach (executive outbound, targeted events, paid, SEO/AEO) as one coordinated system - Familiarity with modern outbound and signal or intent tooling (Clay, Apollo, or equivalent), and a point of view on where AI can replace manual research and enrichment work We'll include these under Qualifications section maybe as part of same list? Could combine with What we're looking for. But to avoid too many sections, we can have one Qualifications section containing both lists (maybe separate subheadings? Not allowed). We'll just combine all bullet points into one
    • list under Qualifications. But we need to preserve all info; we can have two separate
      under same heading? That's okay. We'll output:

      About Middesk: ...

      About the role

      Enterprise go to market is consolidating around precision, and AI is accelerating that shift. Signal and intent data, automated research, and agentic outreach tooling are making it possible to build a real system around a defined set of accounts instead of running broader campaigns at more names, and the companies winning right now are the ones building that system first. This role owns that system at Middesk: the named enterprise and mid-market account list itself, the research and signal engine behind it, and every coordinated campaign, outbound, paid, SEO/AEO, and events, built around it. You will own the pipeline number this account list produces end to end, even though most of the people who execute against it, the AEs and SDRs, don't report to you. You will work closely with them, and you will set the standard, the research, and the operating rhythm the whole motion runs against.

      Responsibilities

      • Own Middesk's qualified new logo pipeline number across enterprise and mid-market named accounts, end to end