Technical Recruiter
About the role
thenwith that paragraph. - What You'll Do: responsibilities. Use
Responsibilities
then- each bullet.
- Who you are: qualifications/requirements. Could be "Requirements" or "Qualifications". We'll decide: "Requirements" for must-have, "Qualifications" for nice-to-have? The posting includes "Who you are" bullet list of traits. Also "Bonus points". So we can put "Requirements" for the core traits, and "Qualifications" for bonus points? Or "Skills" for sourcing etc. Let's map:
Core traits: full-cycle recruiting experience, ideally technical; excellent sourcer; sharp on candidate experience; organized and data-driven; low-ego collaborative; care about mission; excited to work in person 5 days a week in NYC office, with founder and growth mindset.
These are requirements.
Bonus points: recruited engineers at startup/high-growth; built sourcing or hiring process from scratch; use AI tooling; experience recruiting across both technical and GTM roles. These could be "Qualifications" or "Skills". We'll put them under "Qualifications".
Skills: maybe not separate; we could omit Skills if not distinct.
Benefits: "Comp & Benefits Base salary $140,000-$180,000K depending on level and experience, plus the opportunity to receive meaningful early-stage equity ($15,000-$70,000K per year) in Forgepoint. You'll also have great healthcare coverage, dinner provided at the office, and unlimited Celsius." That's benefits and pay. We need separate Pay and Benefits sections if content exists. Pay: base salary range and equity. Benefits: healthcare, dinner, unlimited Celsius. So we need Pay section and Benefits section.
Schedule: "Location You'll be in our NYC office five days a week." That's schedule/location. Could be Schedule section: "In-person 5 days a week in NYC office."
We also have "About Forgepoint" description, founders, how we work, values, team. Those could be "About the company" but not in allowed headings. The allowed headings are limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not add other headings. So we need to decide where to put company description. Possibly we can incorporate into About the role? But that would be mixing. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should only use those headings? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings only. So we should not add other headings like "About Forgepoint". We could incorporate that info into About the role or maybe into Responsibilities? But better to put company info under About the role? However About the role should be about the role, not company. But we could still include some company context as part of role description. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company info into About the role section. Thus About the role: include the introductory paragraph plus maybe company mission description. Let's extract substantive content: Intro: "The Role This is a true 0→1 recruiting role. You'll build the team that builds Forgepoint. You'll own full-cycle recruiting across engineering and go-to-market: sourcing, pipeline, candidate experience, and close. You'll be hands-on and high-volume, and you'll set the bar for how we hire as we scale from a small founding team to many. You'll work directly with the founders and hiring managers to define what "great" looks like for each role, run a fast and thoughtful process, and give every candidate an experience that reflects how much we care about the team. This is a seat for a builder who wants to shape a company through the people they bring in." We can keep that as About the role. Responsibilities: from "What You'll Do" bullet list: - Partner with founders and hiring managers to define scorecards, ideal profiles, and a rigorous interview process for every open role. - Build targeted pipelines for engineering and GTM roles through creative sourcing, referrals, communities, and highly personalized outreach. - Own the candidate journey end-to-end, from first contact and screening through interviews, references, offer, and close. - Assess candidates against role outcomes and values, synthesize evidence clearly, and continually calibrate the hiring bar with the team. - Run a fast, thoughtful process with excellent communication, tight scheduling, and a candidate experience that reflects how Forgepoint operates. - Instrument the recruiting funnel, forecast hiring progress, find bottlenecks, and build repeatable systems that help the team scale. We'll put each as
- .
Requirements: from "Who you are" bullet list (core traits):
- You have full-cycle recruiting experience, ideally technical
- You're an excellent sourcer who can find and engage top talent others miss
- You're sharp on candidate experience and move fast without dropping the ball
- You're organized and data-driven about your pipeline
- You're low-ego and collaborative with hiring managers
- 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
Note: the last about working in person 5 days a week could also go to Schedule, but it's a requirement. We'll keep it in Requirements; but we also have Schedule section later maybe just location. To avoid duplication, we could move the schedule info to Schedule section and remove from Requirements. Let's see: The requirement list includes "You're excited to work in person 5 days a week in our NYC office, with a founder and growth mindset." That's both a requirement and schedule. We could keep it in Requirements as a cultural fit, and Schedule just says "In-person 5 days a week in NYC office." Might be duplicate but okay. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay as long as we preserve. But better to avoid duplicate content? Not prohibited. We'll keep both.
Qualifications: from "Bonus points":
- You've recruited engineers at a startup or high-growth company
- You've built a sourcing or hiring process from scratch
- You use AI tooling to accelerate sourcing, screening, and outreach
- Experience recruiting across both technical and GTM roles
We could also include "Experience recruiting across both technical and GTM roles" as a qualification.
Skills: Not explicitly listed; we could omit Skills section.
Benefits: great healthcare coverage, dinner provided at the office, unlimited Celsius.
Pay: Base salary $140,000-$180,000K depending on level and experience, plus the opportunity to receive meaningful early-stage equity ($15,000-$70,000K per year) in Forgepoint.
Note: The formatting "$140,000-$180,000K" seems odd: maybe they meant $140,000-$180,000. We'll keep as written.
Schedule: "Location You'll be in our NYC office five days a week." We'll phrase as "In-person 5 days a week in NYC office."
Now produce HTML fragment with
headings and
or
- .
We must not include or . Just the fragment.
Let's craft:
- Partner with founders and hiring managers to define scorecards, ideal profiles, and a rigorous interview process for every open role.
- Build targeted pipelines for engineering and GTM roles through creative sourcing, referrals, communities, and highly personalized outreach.
- Own the candidate journey end-to-end, from first contact and screening through interviews, references, offer, and close.
- Assess candidates against role outcomes and values, synthesize evidence clearly, and continually calibrate the hiring bar with the team.
- Run a fast, thoughtful process with excellent communication, tight scheduling, and a candidate experience that reflects how Forgepoint operates.
- Instrument the recruiting funnel, forecast hiring progress, find bottlenecks, and build repeatable systems that help the team scale.
- You have full-cycle recruiting experience, ideally technical
- You're an excellent sourcer who can find and engage top talent others miss
- You're sharp on candidate experience and move fast without dropping the ball
- You're organized and data-driven about your pipeline
- You're low-ego and collaborative with hiring managers
- 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
- You've recruited engineers at a startup or high-growth company
- You've built a sourcing or hiring process from scratch
- You use AI tooling to accelerate sourcing, screening, and outreach
- Experience recruiting across both technical and GTM roles
- Great healthcare coverage
- Dinner provided at the office
- Unlimited Celsius
About the role
The Role This is a true 0→1 recruiting role. You'll build the team that builds Forgepoint. You'll own full-cycle recruiting across engineering and go-to-market: sourcing, pipeline, candidate experience, and close. You'll be hands-on and high-volume, and you'll set the bar for how we hire as we scale from a small founding team to many. You'll work directly with the founders and hiring managers to define what "great" looks like for each role, run a fast and thoughtful process, and give every candidate an experience that reflects how much we care about the team. This is a seat for a builder who wants to shape a company through the people they bring in.
Maybe also add company mission? Could add after that paragraph: "Forgepoint revitalizes American manufacturing by building AI workers for back‑office functions like quoting, purchasing, invoicing, and sales coordination, helping US manufacturers move faster, grow, and compete globally." That's from About Forgepoint. It's substantive. We'll add as anotherunder About the role. Thus About the role will have two paragraphs. Now Responsibilities:
Responsibilities
Requirements
Qualifications
Benefits
Pay
Base salary $140,000-$180,000 depending on level and experience, plus the opportunity to receive meaningful early-stage equity ($15,000-$70,000 per year) in Forgepoint.
Schedule:Schedule
In-person 5 days a week in NYC office.
We should ensure no extra whitespace issues. Output only HTML. Check for any boilerplate removed: we removed founders details, how we work, values, team, etc. That's okay as not in allowed headings. But we might lose substantive info about founders etc. However instruction: "Prefer a few substantive sections over many thin