HubSpot Systems & Data Engineer

We need to output HTML fragment with sections: About the role? Actually we have "About Us" but we shouldn't repeat job title as heading. We need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections when posting has real specific content. We have content: About Us (company description) could be "About the role"? Not exactly about the role. Could treat as "About Us" but heading must be one of allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have Position Overview (description) -> could be "About the role". We have Core Outcomes (maybe responsibilities?). Actually Core Outcomes are expected outcomes, could be part of Responsibilities or Qualifications. We have General Expected Duties -> Responsibilities. We have Compensation & Logistics -> Pay, Schedule, Benefits? It includes Job Type, OTE, Additional Compensation, Schedule, Location. So we can have Pay section (OTE range), Schedule section (Monday-Friday 9-6), Benefits? Not mentioned besides bonus opportunities. Could include Benefits as bonus opportunities? Might be okay. We also have "You SHOULD apply..." and "You SHOULD NOT apply..." which are qualifications/requirements. Could go under Requirements or Qualifications. We'll put Requirements. We also have "Ideal background:" etc. Could be Qualifications. We need to avoid boilerplate like EEO etc. Not present. We must not repeat job title as heading. So no heading "HubSpot Systems & Data Engineer". Good. We must not include Job ID etc. We must preserve all substantive info. We'll produce sections:

About the role

with paragraph(s) from Position Overview and maybe About Us? Actually About Us is company description; could be included in About the role? Might be okay. But we can also include a separate "About Us"? Not allowed heading. So we incorporate into About the role. We'll put Position Overview paragraph(s) and maybe a brief about Curvion. We'll need to ensure we don't invent content. Let's extract text: About Us: "Curvion is a high performance RevOps & sales augmentation agency that installs and deploys enterprise-grade, AI-driven revenue engines and selling systems for our clients. Think of a lead generation based marketing agency…. But focused on sales! We design and install complete sales systems from sales processes and GTM strategy to CRM setup all the way to fully outsourced sales engagements. Then we enhance those systems with AI enabled tools and battle tested playbooks, and finally, we provide highly trained sales talent to help our clients execute so their revenue engine runs faster, scales efficiently, and performs consistently. In short, we build and power modern, AI-driven sales systems that help companies grow with clarity and control." Position Overview: "HubSpot Systems & Data Engineer The HubSpot Systems & Data Engineer is the person who makes sure the infrastructure underneath our clients' sales operations actually works. This is a deeply technical, hands-on role centered around HubSpot architecture, data integrity, automation, integrations, reporting, and system performance. You’ll work across multiple client environments, identifying problems, building solutions, cleaning up messy systems, and creating infrastructure that can scale. This is not a CRM admin role where you occasionally create a property or fix a contact record. We’re looking for a legitimate HubSpot and data nerd who enjoys getting into the weeds. Someone who can look at a complicated CRM environment, understand what is happening under the hood, find what is broken, and build a better way. This is an agency role. You’ll work across multiple clients, each with different sales processes, systems, data structures, and business requirements. Experience working in a client-services environment is critical. Ideal background: HubSpot Solutions Partner, HubSpot agency, RevOps agency, CRM consultancy, or similar technology/implementation agency." Then "You SHOULD apply to this role if:" bullet list (actually sentences). We'll convert to

• . Then "You SHOULD NOT apply to this role if:" similarly. Then "Core Outcomes": list of bullet points. Then "General Expected Duties": list. Then "Compensation & Logistics": includes Job Type: Full-time, W-2; OTE: $72,000 - $100,000 annually; Additional Compensation: Bonus opportunities; Schedule: Monday-Friday, 9:00 AM-6:00 PM; Location: Remote; Compensation Range: $72K - $100K (duplicate). We'll extract Pay: OTE range $72k-$100k; Bonus opportunities maybe as Benefits? Could put Benefits: Bonus opportunities. Schedule: Monday-Friday 9am-6pm. Location remote maybe not a section; could be included in About the role? Not required. We'll maybe include a short paragraph for location under About the role? But we shouldn't invent headings. Could add a

  inside About the role for location? Might be okay. We must not include duplicate content. We'll keep Pay section with OTE range and maybe note bonus opportunities as part of Benefits. We'll create sections:

  About the role

  Curvion is a high performance RevOps & sales augmentation agency ... (About Us)

  HubSpot Systems & Data Engineer ... (Position Overview)

  Responsibilities

  • Build, configure, and optimize HubSpot properties, objects, pipelines, workflows, automations, and system architecture
  ... etc from General Expected Duties

  Requirements

  • You have agency, consultancy, or client-services experience
  • You’ve preferably worked for a HubSpot Solutions Partner, HubSpot agency, RevOps agency, CRM consultancy, or similar organization
  • You have configured and optimized HubSpot environments for multiple clients
  • HubSpot is basically your playground
  • You understand CRM architecture, objects, properties, pipelines, workflows, automation, and data structures
  • You’ve worked with integrations, APIs, webhooks, dialers, schedulers, reporting tools, or other sales technology
  • You’re obsessive about clean, accurate, usable data
  • You enjoy troubleshooting why data isn't behaving the way it should
  • You can walk into a messy HubSpot account and quickly identify what needs to change
  • You understand how CRM data impacts reporting, attribution, forecasting, and sales execution
  • You’re comfortable managing multiple client environments simultaneously
  • You’d rather fix the root cause than keep patching the same problem every week
  • You enjoy documenting systems so other people can actually understand and maintain them
  Maybe also include "You SHOULD NOT apply..." as part of Requirements? Could be separate "Disqualifiers" but not allowed heading. Could incorporate into Requirements as negative? Might be okay to include as part of Requirements but we could also add a separate section "Requirements" and include both should and should not? Might be confusing. Better to keep Requirements as positive qualifications; we could add a separate section "Requirements" and also include a short paragraph about disqualifiers? But we must not create extra headings not in list. Could we add a

  inside Requirements that mentions disqualifiers? That would be mixing. Probably acceptable to include both should and should not as part of Requirements (they are still requirements). We'll include both sets. Thus Requirements list includes both should and should not items.

  Qualifications

  maybe not needed if we used Requirements. But we have Ideal background etc. Could be Qualifications. However we already covered many. To avoid duplication, we could treat Requirements as the should list, and Qualifications as Ideal background etc. But we have overlapping. Let's decide: Use Requirements for the should/apply list, and Qualifications for Ideal background and maybe core outcomes? Actually Core Outcomes are more like expected outcomes, could be part of Responsibilities. But we already have Responsibilities covering duties. Core Outcomes could be part of Responsibilities as well but we might add a separate section "Qualifications" for Ideal background and maybe Core Outcomes? Let's see. We have sections allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these without duplication. We have: - About the role: company description + position overview. - Responsibilities: General Expected Duties (list). Could also include Core Outcomes? But Core Outcomes are outcomes expected; could be part of Responsibilities as well but we can keep them under Responsibilities as additional bullet points. - Requirements: You SHOULD apply list (positive). Also maybe include "Experience working in a client-services environment is critical" etc from Position Overview? Already covered. - Qualifications: Ideal background: HubSpot Solutions Partner, etc. Also maybe "You have configured and optimized HubSpot environments for multiple clients" etc? That's more requirement. Might be overlapping. - Skills: Could be specific technical skills: HubSpot architecture, objects, properties, pipelines, workflows, automation, data structures, integrations, APIs, webhooks, dialers, schedulers, reporting tools, etc. Could extract from requirements. - Benefits: Bonus opportunities. - Pay: OTE range $72k-$100k. - Schedule: Monday-Friday 9am-6pm. We need to avoid thin sections. Let's try to combine. We could have: About the role (company + overview) Responsibilities (General Expected Duties + Core Outcomes) Requirements (You SHOULD apply list) Qualifications (Ideal background) Skills (Technical skills list: HubSpot architecture, objects, properties, pipelines, workflows, automation, data structures, integrations, APIs, webhooks, dialers, schedulers, reporting tools, data hygiene, troubleshooting, documentation, managing multiple client environments, root cause fixing, etc.) Benefits (Bonus opportunities) Pay (OTE range) Schedule (Monday-Friday 9am-6pm) We must ensure we don't invent content. Let's extract exact phrases. From Position Overview: "You’ll work across multiple client environments, identifying problems, building solutions, cleaning up messy systems, and creating infrastructure that can scale." That's duty. From Core Outcomes list: - HubSpot environments are clean, scalable, and intentionally structured - CRM data is accurate, reliable, and usable - Workflows, automations, and integrations operate as intended - Data issues are identified and resolved before they become operational problems - Reporting and downstream data systems receive reliable CRM data - CRM architecture and standards remain consistent across client environments - New client systems are deployed with strong technical foundations - System documentation accurately reflects the environments we operate These are outcomes; could be under Responsibilities as expected outcomes. General Expected Duties list: - Build, configure, and optimize HubSpot properties, objects, pipelines, workflows, automations, and system architecture - Audit client HubSpot environments for data quality, structural issues, and operational inefficiencies - Identify and resolve CRM data integrity issues - Build and maintain integrations between HubSpot and other sales, marketing, communication, and reporting platforms - Work with APIs, webhooks, imports, exports, and other data movement processes - Support CRM migrations, account deployments, and large-scale system changes - Partner with data and RevOps teams to ensure CRM data is structured properly for reporting and analysis - Build processes for data validation, deduplication, normalization, and ongoing data hygiene - Troubleshoot CRM and integration issues and identify root causes - Establish and maintain CRM data standards and governance - Document system architecture, workflows, integrations, and technical processes - Identify opportunities to improve the reliability, scalability, and performance of client CRM environments - Support broader RevOps initiatives where CRM architecture and data are critical components Now Requirements (You SHOULD apply): - You have agency, consultancy, or client