Accelerated Growth Lead
NewtonX · United States · 4 wk ago
RemoteRemoteMarketing$47/hrFull-time
We need to produce HTML fragment with sections: About the role? Actually the posting includes "About NewtonX" (company description) then "About The Role". We should not repeat job title as heading. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About NewtonX (company description) - maybe we can put under
under
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About NewtonX (company description) - maybe we can put under About the company
but not listed. The allowed headings are limited to those specific ones. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should use those headings when appropriate. Probably we should include sections: About the role (maybe includes description of role), Responsibilities (list of duties), Requirements/Qualifications/Skills (maybe combine), Benefits, etc.
We need to preserve all substantive information, remove boilerplate (EEO, etc). Also remove navigation, cookie, legal, duplicated lines, application instructions.
We need to output only HTML fragment, no /, no markdown fences.
Let's parse content.
Company description: "About NewtonX NewtonX is a B2B insights company trusted by the world's most innovative companies to make high-stakes decisions with confidence. We combine a verified network of business professionals with AI-powered research tools to deliver research intelligence faster, more precise, and more defensible than traditional methods. Our clients include Google, Microsoft, TikTok, DoorDash, Stripe, and Coinbase. Our research has been cited by Fortune, Forbes, TechCrunch, Adweek, and the Wall Street Journal. NewtonX has raised $47M from investors including Two Sigma Ventures, Third Prime, XFund, and Citi Ventures."
That's substantive; we could put under About the company
but not in list. Maybe we can treat as part of "About the role"? Actually "About The Role" heading appears later. The company description could be placed under a heading like "About NewtonX". Since not in allowed list, maybe we can still use About NewtonX
. The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests to use those. Safer to stick to those headings. However we need to convey company info; we could embed it in a
About the company
but not in list. Maybe we can treat as part of "About the role"? Actually "About The Role" heading appears later. The company description could be placed under a heading like "About NewtonX". Since not in allowed list, maybe we can still useAbout NewtonX
. The instruction says usefor section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests to use those. Safer to stick to those headings. However we need to convey company info; we could embed it in a
before any heading, as introductory paragraph. That's allowed: we can have prose before headings. Thus output:
About NewtonX ...
thenAbout the role
with description of role (the paragraph after "About The Role"). Then responsibilities: list of duties under "In This Role, You Will". Those are bullet points (starting with Carry and deliver..., Manage..., Own..., Build..., Partner..., Manage..., Own..., Recruit..., Act as...). We'll put each as- .
Then "What Success Looks Like" could be considered responsibilities or maybe a separate section like "Success metrics". Could be under
Success metrics
but not in list. Maybe we can treat as part of responsibilities or as a separate section "Performance expectations". Since not in list, maybe we can incorporate into responsibilities as a- as well. But we need to preserve all substantive info; we can create a section
Success metrics
even if not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)" implying those are typical. It might be okay to add other headings as long as they are . Safer to stick to given ones. However we need to represent success metrics; we could put them under Responsibilities as well, but they are outcomes not duties. Could also put under a section "What Success Looks Like" as Success metrics
. I'd argue it's acceptable.
Then "What You Have" includes qualifications/requirements/skills. We can split into Requirements (experience), Qualifications (maybe same), Skills (list). We'll create sections: Requirements
with bullet points of experience etc. Skills
with bullet points of skills.
Then "What We Offer" includes benefits: compensation, career advancement, insurance, 401k, HSA/FSA, commuter benefits, PTO, culture, good vibes. We'll create Benefits
with bullet list.
Pay and Schedule: not explicitly mentioned; compensation mentioned but not specific numbers, so we should not create Pay section because it would be filler like "Competitive compensation — base salary, uncapped commission, and participation in our employee equity plan." That's actually substantive: they mention compensation details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state compensation: "Competitive compensation — base salary, uncapped commission, and participation in our employee equity plan." That's compensation info, so we could create a Pay section with that detail. However they also mention benefits separately. Could combine compensation into Benefits or have Pay section. Since they explicitly mention compensation, we can create Pay
with that sentence. But they also mention base salary, uncapped commission, equity. That's specific enough.
Schedule: not mentioned, so omit.
Thus sections:
-
. Safer to stick to given ones. However we need to represent success metrics; we could put them under Responsibilities as well, but they are outcomes not duties. Could also put under a section "What Success Looks Like" as Success metrics
. I'd argue it's acceptable.
Then "What You Have" includes qualifications/requirements/skills. We can split into Requirements (experience), Qualifications (maybe same), Skills (list). We'll create sections: Requirements
with bullet points of experience etc. Skills
with bullet points of skills.
Then "What We Offer" includes benefits: compensation, career advancement, insurance, 401k, HSA/FSA, commuter benefits, PTO, culture, good vibes. We'll create Benefits
with bullet list.
Pay and Schedule: not explicitly mentioned; compensation mentioned but not specific numbers, so we should not create Pay section because it would be filler like "Competitive compensation — base salary, uncapped commission, and participation in our employee equity plan." That's actually substantive: they mention compensation details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state compensation: "Competitive compensation — base salary, uncapped commission, and participation in our employee equity plan." That's compensation info, so we could create a Pay section with that detail. However they also mention benefits separately. Could combine compensation into Benefits or have Pay section. Since they explicitly mention compensation, we can create Pay
with that sentence. But they also mention base salary, uncapped commission, equity. That's specific enough.
Schedule: not mentioned, so omit.
Thus sections:
-
About NewtonX ...
-About the role
...
-Responsibilities
- ...
Success metrics
- ...
Requirements
- ...
Skills
- ...
Pay
Competitive compensation — base salary, uncapped commission, and participation in our employee equity plan.
-Benefits
- ...