GTM Engineer
for headings. Use - for lists,
for prose. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- The Role: description paragraph.
- What You'll Do: list of duties.
- Who you are: bullet list of traits.
- Bonus points: bullet list.
- About Forgepoint: description.
- Our Founders: bios.
- How We Work: bullet points.
- Our Values: bullet list.
- Comp & Benefits: base salary range, equity, healthcare, dinner, unlimited Celsius.
- Location: NYC office five days a week.
- Compensation Range: repeated.
We need to map to sections: About the role (maybe the initial paragraph). Responsibilities (What You'll Do). Requirements (maybe Who you are? Actually requirements are qualifications). Qualifications (maybe Bonus points? Or we can combine). Skills (maybe technical stack). Benefits (healthcare, dinner, unlimited Celsius). Pay (salary range + equity). Schedule (in-person 5 days a week). Also maybe About the company? Not required but could be included as About the role? Actually "About the role" is separate from company description. We could include a section "About the company" but not in list; but we can include only those headings from list. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if we have content. We can also include other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should stick to them. So we need to map content to those.
Thus:
- About the role: The Role paragraph + maybe About Forgepoint? Actually About the role is about the role itself, not company. So we can put the initial paragraph "The Role This is a true 0→1 role..." as About the role.
- Responsibilities: What You'll Do list.
- Requirements: Who you are bullet list (technical enough, product sense, etc.)
- Qualifications: Bonus points bullet list (built GTM automations, background blending engineering with sales/marketing ops, shipped internal AI tools, familiarity with stack).
- Skills: maybe technical stack: TypeScript/NodeJS/PostgreSQL, APIs, scripts, LLMs, AI tooling. Could also include "fluent with AI and LLM tooling". We'll list.
- Benefits: healthcare coverage, dinner provided at the office, unlimited Celsius.
- Pay: Base salary $160,000-$200,000 depending on level and experience, plus opportunity to receive meaningful early-stage equity ($45,000-$100,000 per year).
- Schedule: You'll be in our NYC office five days a week. Also "In person every day in NYC for high-bandwidth collaboration" from How We Work. So schedule: in-person 5 days a week.
We should also maybe include "How We Work" and "Our Values" but those are not in allowed headings; we could drop them as they are not required headings. However they contain substantive info; but instruction says we should only include sections when posting has real, specific content for it, and we should prefer a few substantive sections over many thin ones. It didn't forbid adding other headings, but gave examples. Safer to stick to those headings and incorporate other info into those sections where appropriate. For example, "How We Work" could be part of About the role or Responsibilities? Might be better to include as part of About the role or maybe as a separate section not in list? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add other headings if we have content. But to be safe, we can include those headings plus maybe "About the company" etc. However the instruction says "Prefer a few substantive sections over many thin ones." So we should combine.
Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure we don't repeat job title as heading. Not needed.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive information. Let's extract.
About the role paragraph:
"The Role This is a true 0→1 role at the intersection of engineering and go-to-market. You'll be the technical builder behind our GTM motion, building the automations and tooling that make sales and marketing fast and scalable. That means outbound and enrichment pipelines, CRM and data plumbing, and internal AI tools that give the whole GTM team leverage. You'll work shoulder-to-shoulder with our founder and sales and marketing leaders, spot the bottlenecks that slow them down, and build the systems that remove them. Expect hands-on work with APIs, scripts, and LLMs every day, and tight feedback loops with the people using what you build. If you love the idea of engineering being a force multiplier for revenue, this is the job for you."
We'll put that in
.
Responsibilities: list from "What You'll Do":
- Build and own outbound systems, from account sourcing and enrichment through personalized outreach, routing, and follow-up.
- Keep our GTM data foundation trustworthy by connecting the CRM, enrichment tools, and internal systems; automate deduplication, lifecycle updates, and pipeline reporting.
- Turn founder-led sales workflows into repeatable systems for account research, call preparation, follow-ups, proposals, and pipeline reviews.
- Build AI-powered tools and agents that make sales and marketing faster, more informed, and more personalized.
- Partner directly with sales and marketing to find bottlenecks, run experiments, measure conversion, and ship improvements quickly.
- Own what you build in production: integrate APIs, handle edge cases, monitor reliability, document the system, and keep it running.
Make
- .
Requirements: "Who you are" bullet list:
- You're technical enough to script, call APIs, and wire tools together into reliable systems
- You have product sense for what actually moves pipeline, not just what looks cool
- You're comfortable owning systems end-to-end, from idea to running in production
- You're fast, experimental, and obsessed with leverage
- You're fluent with AI and LLM tooling and constantly finding new ways to apply it
- You care about our mission, and you want to see the American manufacturing base get stronger
- You're excited to work in person 5 days a week in our NYC office, with a founder and growth mindset
Make list.
Qualifications: "Bonus points":
- You've built GTM automations with tools like Clay, Apollo, enrichment providers, or CRM APIs
- A background that blends engineering with sales or marketing operations
- You've shipped internal AI tools that a team actually adopted
- Familiarity with our stack: TypeScript / NodeJS / PostgreSQL
Make list.
Skills: Could combine technical skills: APIs, scripts, LLMs, AI tooling, TypeScript, NodeJS, PostgreSQL, maybe also mention "outbound and enrichment pipelines, CRM and data plumbing". We'll list.
Make list.
Benefits: "great healthcare coverage, dinner provided at the office, and unlimited Celsius." Also maybe "opportunity to receive meaningful early-stage equity" is pay not benefit. So benefits: healthcare, dinner, unlimited Celsius.
Make list.
Pay: Base salary $160,000-$200,000 depending on level and experience, plus the opportunity to receive meaningful early-stage equity ($45,000-$100,000 per year). Also maybe mention "Comp & Benefits Base salary..." We'll put that.
Make
maybe.
Schedule: "You'll be in our NYC office five days a week." Also "In person every day in NYC for high-bandwidth collaboration" from How We Work. So schedule: in-person 5 days a week.
Make
.
We should also maybe include "How We Work" and "Our Values" content somewhere? Could incorporate into About the role or Responsibilities as extra bullets? But we already have responsibilities covering many aspects. The "How We Work" includes: In person every day in NYC for high-bandwidth collaboration, Talk to users constantly: we build with manufacturers, not for them, Own outcomes end-to-end and drive solutions without waiting for permission. These are cultural aspects; could be added to About the role or maybe as a separate section not in list but we risk many thin sections. Could add a short paragraph under About the role after the initial paragraph describing work style. That would preserve info.
Similarly "Our Values" list: We're Here to Win, There's Always a Way, Truth Over Comfort, Act Now, Step Up, The Team. The Team. The Team.: We put the team first, push and support each other, share wins, and own failures together. Could be added as a paragraph under About the role or maybe as a separate "Values" section but not in allowed headings. Since we prefer few sections, we can incorporate into About the role as a paragraph.
Thus About the role will be longer: include role description, work style, values.
Let's craft About the role paragraph(s). We'll have maybe two
elements: first paragraph role description, second paragraph work style and values.
But we must not create filler. Ensure we have substantive content.
Now produce HTML.
We'll output:
About the role
...
...
Responsibilities
...
Requirements
...
Qualifications
...
Skills
...
Benefits
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine.
Now craft content.
About the role first paragraph: as given.
Second paragraph: combine How We Work and Our Values.
How We Work: "In person every day in NYC for high-bandwidth collaboration Talk to users constantly: we build with manufacturers, not for them Own outcomes end-to-end and drive solutions without waiting for permission"
Our Values: list: "We're Here to Win: We are building to help American manufacturers, our customers, our company, and our teammates win at the highest level. There's Always a Way: We are relentlessly resourceful, take ownership of constraints, and find a path forward when others stop. Truth Over Comfort: We choose honesty over ego, surface reality quickly, and change course when the facts demand it. Act Now: We move fast, trust our instincts, and correct course as we go. Step Up: We act like founders, fill gaps, fix problems, and follow through until the work is done. The Team. The Team. The Team.: We put the team first, push and support each other, share wins, and own failures together."
We'll combine into a paragraph.
Now Responsibilities list as above.
Requirements list as above.
Qualifications list as above.
Skills list: maybe: "APIs, scripts, LLMs, AI tooling, TypeScript, NodeJS, PostgreSQL, outbound and enrichment pipelines, CRM and data plumbing". We'll list.
Benefits list: "Great healthcare coverage", "Dinner provided at the office", "Unlimited Celsius".
Pay paragraph: "Base salary $160
for prose. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - The Role: description paragraph. - What You'll Do: list of duties. - Who you are: bullet list of traits. - Bonus points: bullet list. - About Forgepoint: description. - Our Founders: bios. - How We Work: bullet points. - Our Values: bullet list. - Comp & Benefits: base salary range, equity, healthcare, dinner, unlimited Celsius. - Location: NYC office five days a week. - Compensation Range: repeated. We need to map to sections: About the role (maybe the initial paragraph). Responsibilities (What You'll Do). Requirements (maybe Who you are? Actually requirements are qualifications). Qualifications (maybe Bonus points? Or we can combine). Skills (maybe technical stack). Benefits (healthcare, dinner, unlimited Celsius). Pay (salary range + equity). Schedule (in-person 5 days a week). Also maybe About the company? Not required but could be included as About the role? Actually "About the role" is separate from company description. We could include a section "About the company" but not in list; but we can include only those headings from list. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if we have content. We can also include other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should stick to them. So we need to map content to those.
Thus:
- About the role: The Role paragraph + maybe About Forgepoint? Actually About the role is about the role itself, not company. So we can put the initial paragraph "The Role This is a true 0→1 role..." as About the role.
- Responsibilities: What You'll Do list.
- Requirements: Who you are bullet list (technical enough, product sense, etc.)
- Qualifications: Bonus points bullet list (built GTM automations, background blending engineering with sales/marketing ops, shipped internal AI tools, familiarity with stack).
- Skills: maybe technical stack: TypeScript/NodeJS/PostgreSQL, APIs, scripts, LLMs, AI tooling. Could also include "fluent with AI and LLM tooling". We'll list.
- Benefits: healthcare coverage, dinner provided at the office, unlimited Celsius.
- Pay: Base salary $160,000-$200,000 depending on level and experience, plus opportunity to receive meaningful early-stage equity ($45,000-$100,000 per year).
- Schedule: You'll be in our NYC office five days a week. Also "In person every day in NYC for high-bandwidth collaboration" from How We Work. So schedule: in-person 5 days a week.
We should also maybe include "How We Work" and "Our Values" but those are not in allowed headings; we could drop them as they are not required headings. However they contain substantive info; but instruction says we should only include sections when posting has real, specific content for it, and we should prefer a few substantive sections over many thin ones. It didn't forbid adding other headings, but gave examples. Safer to stick to those headings and incorporate other info into those sections where appropriate. For example, "How We Work" could be part of About the role or Responsibilities? Might be better to include as part of About the role or maybe as a separate section not in list? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add other headings if we have content. But to be safe, we can include those headings plus maybe "About the company" etc. However the instruction says "Prefer a few substantive sections over many thin ones." So we should combine.
Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure we don't repeat job title as heading. Not needed.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive information. Let's extract.
About the role paragraph:
"The Role This is a true 0→1 role at the intersection of engineering and go-to-market. You'll be the technical builder behind our GTM motion, building the automations and tooling that make sales and marketing fast and scalable. That means outbound and enrichment pipelines, CRM and data plumbing, and internal AI tools that give the whole GTM team leverage. You'll work shoulder-to-shoulder with our founder and sales and marketing leaders, spot the bottlenecks that slow them down, and build the systems that remove them. Expect hands-on work with APIs, scripts, and LLMs every day, and tight feedback loops with the people using what you build. If you love the idea of engineering being a force multiplier for revenue, this is the job for you."
We'll put that in
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add other headings if we have content. But to be safe, we can include those headings plus maybe "About the company" etc. However the instruction says "Prefer a few substantive sections over many thin ones." So we should combine. Thus we will produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure we don't repeat job title as heading. Not needed. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive information. Let's extract. About the role paragraph: "The Role This is a true 0→1 role at the intersection of engineering and go-to-market. You'll be the technical builder behind our GTM motion, building the automations and tooling that make sales and marketing fast and scalable. That means outbound and enrichment pipelines, CRM and data plumbing, and internal AI tools that give the whole GTM team leverage. You'll work shoulder-to-shoulder with our founder and sales and marketing leaders, spot the bottlenecks that slow them down, and build the systems that remove them. Expect hands-on work with APIs, scripts, and LLMs every day, and tight feedback loops with the people using what you build. If you love the idea of engineering being a force multiplier for revenue, this is the job for you." We'll put that in
. Responsibilities: list from "What You'll Do": - Build and own outbound systems, from account sourcing and enrichment through personalized outreach, routing, and follow-up. - Keep our GTM data foundation trustworthy by connecting the CRM, enrichment tools, and internal systems; automate deduplication, lifecycle updates, and pipeline reporting. - Turn founder-led sales workflows into repeatable systems for account research, call preparation, follow-ups, proposals, and pipeline reviews. - Build AI-powered tools and agents that make sales and marketing faster, more informed, and more personalized. - Partner directly with sales and marketing to find bottlenecks, run experiments, measure conversion, and ship improvements quickly. - Own what you build in production: integrate APIs, handle edge cases, monitor reliability, document the system, and keep it running. Make
- .
Requirements: "Who you are" bullet list:
- You're technical enough to script, call APIs, and wire tools together into reliable systems
- You have product sense for what actually moves pipeline, not just what looks cool
- You're comfortable owning systems end-to-end, from idea to running in production
- You're fast, experimental, and obsessed with leverage
- You're fluent with AI and LLM tooling and constantly finding new ways to apply it
- You care about our mission, and you want to see the American manufacturing base get stronger
- You're excited to work in person 5 days a week in our NYC office, with a founder and growth mindset
Make list.
Qualifications: "Bonus points":
- You've built GTM automations with tools like Clay, Apollo, enrichment providers, or CRM APIs
- A background that blends engineering with sales or marketing operations
- You've shipped internal AI tools that a team actually adopted
- Familiarity with our stack: TypeScript / NodeJS / PostgreSQL
Make list.
Skills: Could combine technical skills: APIs, scripts, LLMs, AI tooling, TypeScript, NodeJS, PostgreSQL, maybe also mention "outbound and enrichment pipelines, CRM and data plumbing". We'll list.
Make list.
Benefits: "great healthcare coverage, dinner provided at the office, and unlimited Celsius." Also maybe "opportunity to receive meaningful early-stage equity" is pay not benefit. So benefits: healthcare, dinner, unlimited Celsius.
Make list.
Pay: Base salary $160,000-$200,000 depending on level and experience, plus the opportunity to receive meaningful early-stage equity ($45,000-$100,000 per year). Also maybe mention "Comp & Benefits Base salary..." We'll put that.
Make
maybe. Schedule: "You'll be in our NYC office five days a week." Also "In person every day in NYC for high-bandwidth collaboration" from How We Work. So schedule: in-person 5 days a week. Make
. We should also maybe include "How We Work" and "Our Values" content somewhere? Could incorporate into About the role or Responsibilities as extra bullets? But we already have responsibilities covering many aspects. The "How We Work" includes: In person every day in NYC for high-bandwidth collaboration, Talk to users constantly: we build with manufacturers, not for them, Own outcomes end-to-end and drive solutions without waiting for permission. These are cultural aspects; could be added to About the role or maybe as a separate section not in list but we risk many thin sections. Could add a short paragraph under About the role after the initial paragraph describing work style. That would preserve info. Similarly "Our Values" list: We're Here to Win, There's Always a Way, Truth Over Comfort, Act Now, Step Up, The Team. The Team. The Team.: We put the team first, push and support each other, share wins, and own failures together. Could be added as a paragraph under About the role or maybe as a separate "Values" section but not in allowed headings. Since we prefer few sections, we can incorporate into About the role as a paragraph. Thus About the role will be longer: include role description, work style, values. Let's craft About the role paragraph(s). We'll have maybe two
elements: first paragraph role description, second paragraph work style and values. But we must not create filler. Ensure we have substantive content. Now produce HTML. We'll output:
About the role
...
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Now craft content. About the role first paragraph: as given. Second paragraph: combine How We Work and Our Values. How We Work: "In person every day in NYC for high-bandwidth collaboration Talk to users constantly: we build with manufacturers, not for them Own outcomes end-to-end and drive solutions without waiting for permission" Our Values: list: "We're Here to Win: We are building to help American manufacturers, our customers, our company, and our teammates win at the highest level. There's Always a Way: We are relentlessly resourceful, take ownership of constraints, and find a path forward when others stop. Truth Over Comfort: We choose honesty over ego, surface reality quickly, and change course when the facts demand it. Act Now: We move fast, trust our instincts, and correct course as we go. Step Up: We act like founders, fill gaps, fix problems, and follow through until the work is done. The Team. The Team. The Team.: We put the team first, push and support each other, share wins, and own failures together." We'll combine into a paragraph. Now Responsibilities list as above. Requirements list as above. Qualifications list as above. Skills list: maybe: "APIs, scripts, LLMs, AI tooling, TypeScript, NodeJS, PostgreSQL, outbound and enrichment pipelines, CRM and data plumbing". We'll list. Benefits list: "Great healthcare coverage", "Dinner provided at the office", "Unlimited Celsius". Pay paragraph: "Base salary $160