Jobs · Management · New York

Director of Implementation & Onboarding

Rebar · New York, NY · 1 mo ago
On-siteManagement$14/hrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Rebar" then "The Role" then "What You’ll Do", "What Success Looks Like", "Who You Are", "Compensation & Benefits". Also maybe "About Rebar" is not a required heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? Probably we should map content to those headings: "About the role" corresponds to description of role. "Responsibilities" corresponds to "What You’ll Do". "Requirements" corresponds to "Who You Are". "Qualifications" maybe not separate. "Skills" maybe not. "Benefits" corresponds to Compensation & Benefits. "Pay" maybe not given (salary based on experience). "Schedule" maybe not given (full-time, onsite). We should include sections only if posting has real specific content. So we can include About the role, Responsibilities, Requirements, Benefits, Pay?, Schedule? Pay: they have "Salary: Based on experience" and "Equity: Meaningful equity grant depending on experience". That's specific enough? It says based on experience, not a number. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . "Based on experience" is similar to "commensurate with experience"? Might be considered placeholder. Safer to omit Pay section if not specific numeric. Schedule: they say "This is a full-time, onsite role based in NYC’s Flatiron District". That's schedule info (full-time, onsite). Could be considered schedule. It's specific enough: full-time, onsite. So we can include Schedule section with that. Benefits: they list Medical, dental, vision coverage, Free lunches and dinners. Also equity? Equity is compensation but could be in Benefits? We'll put equity in Compensation & Benefits maybe. But they said Benefits heading for benefits. We'll include Benefits with medical/dental/vision and free meals. Equity maybe under Compensation? But we omitted Pay. Could include Compensation section with salary and equity? But they said avoid filler like "Based on experience". Might be okay to include Compensation with salary based on experience and equity grant depending on experience. That's still vague but it's actual content. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . "Based on experience" is similar to commensurate with experience. Might be considered filler. Safer to omit Compensation/Pay sections. But we could still include Benefits and Schedule. The role description etc. We need to preserve all substantive information. If we omit compensation details, we lose info about salary and equity. But maybe we can include them under a "Compensation" heading but note it's based on experience; is that allowed? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . That suggests we should not create a heading if the content is just placeholder like "Based on experience". So we should omit Compensation heading. Similarly, we could omit Pay heading. So we lose that info. But maybe we can incorporate salary/equity into Benefits? Not ideal but maybe we can include a short paragraph under Benefits that mentions equity grant depending on experience? But equity is not a benefit per se but could be considered compensation. The instruction says "Prefer a few substantive sections over many thin ones." So we could combine Compensation and Benefits into one Benefits section? But they gave examples of headings; we can use Benefits heading for benefits and maybe also include compensation details there? Might be okay. Let's think: The posting includes "Compensation & Benefits" with Salary, Equity, Benefits, Perks. We could make a Benefits section that includes medical/dental/vision, free lunches/dinners, and note that salary is based on experience and equity grant depending on experience. That's still some info. Schedule: full-time, onsite role based in NYC’s Flatiron District. That's substantive. Thus sections: About the role (maybe from "About Rebar" and "The Role"? Actually "About Rebar" is company description; but we could put that under About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (company + role overview). Responsibilities (What You’ll Do). Requirements (Who You Are). Benefits (Compensation & Benefits + perks). Schedule (full-time, onsite location). We'll not include Qualifications, Skills, Pay separately. Now we need to output HTML fragment only, no /. Use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information. Let's extract. Company description: "About Rebar Rebar is building the next-generation operating system for commercial HVAC, electrical, and plumbing suppliers and subcontractors. Over the past year, our V1 quoting product has scaled to thousands of quotes completed weekly, doubled revenue six weeks into 2026, and gained adoption across many of the top suppliers in North America. Fresh off a $14M Series A backed by leading construction tech investors, we're entering our next phase of growth, and we are looking for a Client Experience Leader to support our Client Success motion. You’ll work directly with the Client Success (CS), Product, and Sales teams to support new and existing clients and build the systems that will define Rebar’s client onboarding experience. We’re transforming the $250B HVAC industry with AI-native software—an industry still largely untouched by modern tools. This is your chance to get in early." Then "The Role" heading: "We’ve hit strong product market fit and are now scaling how we onboard clients across more complex implementations as our software and client-base expands. We’re hiring a Director of Implementation & Onboarding to help redefine this critical function. You’ll run implementation end to end, ensuring clients get up and running quickly in a way that fits their unique operational needs. This role is a balance of building repeatable processes and playbooks, while leading a team to deliver thoughtful, consultative, and technical implementations that adapt to how each client operates and drive real outcomes. You’ll lead a team of Implementation Managers who come from both the mechanical engineering and tech backgrounds, layering in the right level of SaaS rigor and structure without losing flexibility. You’ll work closely with Client Success, Product, Sales, and Engineering to remove friction and scale onboarding as we grow." We can combine About Rebar and The Role into About the role section. Responsibilities: "What You’ll Do" bullet list: Own and scale the end to end implementation and onboarding function; Build repeatable workflows, playbooks, trainings, and systems while supporting highly custom client implementations: White glove enterprise + SMB onboardings at scale; Define and operationalize onboarding across areas like organizational setup, workflow design, product configuration, and user training; Lead and grow a rapidly expanding team of onsite and remote Implementation Managers across various construction verticals; Coach domain experts and translate their knowledge into scalable processes; Partner with Sales and CS on handoffs and implementation scoping; Work closely with Product and Engineering to identify friction points and influence the roadmap; Drive time to value, product adoption / usage, implementation efficiency, and consistency across all accounts; Establish key metrics, forecasting, and operational visibility across implementations; Deliver scalable training and enablement across virtual and onsite environments; Act as an escalation point for complex or high priority client implementations; Travel onsite once per month to support and elevate client onboarding and implementation; plus "A typical week might include:" list: Designing and rolling out a new onboarding playbook for enterprise clients; Reviewing implementation pipelines and identifying bottlenecks; Partnering with Product on recurring implementation blockers; Coaching team members on managing complex client rollouts with new API and custom workflow requirements; Jumping into a high stakes client onboarding to ensure a successful kickoff. We'll put all as

    • . Requirements: "Who You Are" bullet list: You’ve scaled or led an implementation or onboarding team in a complex vertical SaaS environment; You have experience managing complex, multi stakeholder deployments, ideally involving configurable products and / or custom workflows; You’ve implemented products that require deep configuration and adaptation to existing client processes, not just plug and play onboarding including technical API integrations; You’ve built repeatable scalable processes for SMB and self-serve segments; You’re highly operational and know how to build systems, not just manage projects; You have experience leading specialized or domain expert teams, and know how to balance structure with autonomy with a player/coach attitude; You’re comfortable working cross functionally with Product, Engineering, Sales, and Client Success; You can translate between technical product teams and industry practitioners; You balance speed and quality in a fast paced, high growth environment; You’re hands on and willing to dive into the details when needed; You’re structured, metrics driven, and focused on continuous improvement; Bonus points if you have: Experience in construction tech, industrial, or legacy industries; Experience building implementation functions from startup / early stage through scale. We'll put as
      • . Bonus points maybe separate but still list. Benefits: "Compensation & Benefits" includes Salary: Based on experience; Equity: Meaningful equity grant depending on experience; Benefits: Medical, dental, and vision coverage; Perks: Free lunches and dinners. We'll create a Benefits section with
        • for medical, dental, vision coverage; free lunches and dinners; plus note salary based on experience and equity grant depending on experience maybe as

          or list items. Schedule: "This is a full-time, onsite role based in NYC’s Flatiron District, steps from Madison Square Park and Union Square." We'll put as

          . Now produce HTML. We need to ensure no extra text outside HTML. Provide only fragment. Let's craft:

          About the role

          ... company description and role overview ...

          Responsibilities

          • ...
          • ...

          Requirements

          • ...
          • ...

          Benefits

          • Medical, dental, and vision coverage
          • Free lunches and dinners

          Salary is based on experience; equity grant is meaningful and depends on experience.

          Schedule

          This is a full-time, onsite role based in NYC’s Flatiron District, steps from Madison Square Park and Union Square.

          Check that we didn't repeat job title as heading. Good. Now ensure we preserved all substantive information: company description, role overview, responsibilities list, requirements list, benefits, schedule. We omitted mention of "Client Experience Leader" earlier? Actually the About Rebar paragraph mentions they are looking for a Client Experience Leader to support Client Success motion. That's part of company description; we included that in About the role paragraph. Good. We also omitted mention of "Director of Implementation & Onboarding" as the role title; we included in role overview. Good. We omitted mention of "You’ll work directly with the Client Success (CS), Product, and Sales teams to support new and existing clients and build the systems that will define Rebar’s client onboarding experience." included. We omitted mention of "We’re transforming the $250B HVAC industry with AI-native software—an industry still largely untouched by modern tools. This is your chance to get in early." included. We omitted mention of "Fresh off a $14M Series

Similar jobs