GTM Systems Developer

We need to output HTML fragment with sections: About the role? The posting includes intro about CompanyCam, then "The Role", "What You'll Do", "The Impact You'll Have", "What You'll Bring", "Benefits & Compensation". Also location line. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: About the role: could be the intro paragraph about CompanyCam and the role description? The "The Role" paragraph: "We’re looking for a GTM Systems Developer to design, build, and scale the systems and automations that power our go-to-market (GTM) organization..." That's about the role. So we can put that under

About the role

. Responsibilities: corresponds to "What You'll Do" list. Use

• . Requirements: could be "What You'll Bring Required" list. Use
  • . Qualifications: maybe "Preferred" list? Or we could combine Requirements and Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have Required and Preferred. Could treat Required as Requirements, Preferred as Qualifications or Skills. Also we have Benefits & Compensation: includes salary range and equity etc. So Benefits heading with content. Pay heading maybe separate? But we have salary range in Benefits & Compensation. Could put Pay under Benefits? But instruction: include Pay section only if posting actually states them. It does state salary range. So we could have

    Pay

    with the salary range. Benefits could include equity and other benefits. However they said "We also offer meaningful equity and other benefits." Not detailed. Could still include Benefits section with that statement. Schedule: location remote, must live in US. That's schedule? Could be Schedule heading with location and remote. But they said include Schedule only if posting actually states them. It does state location: remote, must live in US. So we can put Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, etc. Also remove "Note: Resumes sent to this email will not be reviewed..." etc. Also remove "For any accommodations..." etc. Also remove "CompanyCam is an equal-opportunity employer..." etc. Also remove "Great ideas come from all backgrounds..." etc. Also remove "Even if your work experience..." etc. Also remove "What really matters to us..." etc. Also remove "Please do not include any medical..." etc. Also remove "To be considered for a position, you must apply directly through our careers page." Also remove "Hi, We’re CompanyCam" maybe keep intro? The intro about CompanyCam is substantive? It's describing company. Could be part of About the role? Might be considered boilerplate? It's not navigation/legal/EEO. It's describing company. Could keep as part of About the role? But we already have About the role heading with role description. Could include a short paragraph about company before that? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description. Where to put? Could be part of About the role section as a paragraph before the role description. Or we could have a separate section like "About CompanyCam" but not in allowed headings. Since only allowed headings are those listed, we should fit it into one of them. Probably About the role can include both company description and role overview. Thus About the role

    About the role

    then

    CompanyCam description...

    then

    The Role ...

    . Or combine. Responsibilities: list from "What You'll Do". Use
    • . Requirements: list from "What You'll Bring Required". Use
      • . Qualifications: list from "What You'll Bring Preferred". Use
        • . Skills: maybe we could extract skills from required? But we already have Requirements and Qualifications. Skills maybe not needed. Could omit if no specific skills list beyond those. But we could put technical skills under Skills? However we already have required and preferred. Might be redundant. Better to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But headings are predefined; we can choose to include only those with content. Could include Requirements (required) and Qualifications (preferred). Skills maybe not needed. Benefits: include equity and other benefits. Pay: salary range. Schedule: location remote, must live in US. We must not include filler like "commensurate with experience". Not present. Now craft HTML. We need to output only HTML fragment, no /, no markdown fences. Let's draft:

          About the role

          We’re CompanyCam, a simple-to-use photo documentation and productivity app for contractors of every industry. Packed with intuitive functionality, CompanyCam facilitates unparalleled communication and accountability across a contractor’s entire business. By providing a consumer-grade, game-changing experience, we help contractors build trust within their company and with their users. CompanyCam is a fun, energetic team united by our core values of Show Up, Grow Up, and Do Good. As soon as you join our team, you'll notice that we trust our employees to do what's best for our product, customers, and team members and empower them to make the right calls.

          We’re looking for a GTM Systems Developer to design, build, and scale the systems and automations that power our go-to-market (GTM) organization. This highly hands-on technical role is ideal for someone who has deep experience in Salesforce administration and development and has evolved into broader systems architecture, automation engineering, and cross-functional GTM problem solving. You'll be deep in the work — designing, building, and shipping — with full ownership from start to finish. You’ll partner closely with stakeholders across the business to understand operational pain points, translate business requirements into technical solutions, and build scalable systems that drive measurable business outcomes. You’ll be focused on building intelligent and scalable workflows, enhancing Salesforce and the broader GTM ecosystem, and driving operational efficiency across Sales, Marketing, Customer Success, and Revenue Operations.

          Responsibilities

          • Design, build, and maintain automations and workflows across Salesforce and the broader GTM tech stack
          • Develop custom Salesforce solutions using Apex, flows, and advanced platform functionality
          • Build and maintain integrations across CRM, marketing automation, sales engagement, enrichment, and revenue platforms
          • Create AI-powered workflows, prompt frameworks, and automation solutions leveraging modern AI tools and APIs
          • Support end-to-end GTM processes across lead management, opportunity management, onboarding, customer success, and renewals
          • Partner with stakeholders to gather requirements, troubleshoot issues, and deliver scalable technical solutions
          • Work within Jira ticketing and project workflows to execute enhancements, resolve bugs, and support larger initiatives
          • Optimize workflows and system architecture to improve operational efficiency, data integrity, and reporting accuracy
          • Build and support automation using tools such as Clay, Zapier, n8n, and similar orchestration platforms
          • Maintain documentation, governance standards, and scalable processes across systems and integrations
          • Support reporting, dashboards, and data visibility initiatives across GTM and Revenue Operations
          • Continuously evaluate new AI capabilities, automation tools, and process improvements that enhance business performance

          Requirements

          • 4+ years of experience in GTM Systems, Revenue Operations, Sales Operations, Marketing Operations, or related technical roles
          • Strong hands-on Salesforce administration and development experience, including Apex development and workflow automation
          • Experience building and maintaining integrations across multiple GTM platforms and systems
          • Strong understanding of Salesforce architecture, automation frameworks, and CRM best practices
          • Experience designing and implementing scalable automation workflows in production environments
          • Technical fluency with APIs, system integrations, and data movement across platforms
          • Experience working within Jira or similar ticketing/project management systems
          • Strong communication skills with the ability to work cross-functionally across technical and non-technical stakeholders
          • Strong process orientation with the ability to document workflows, systems, and operational standards clearly
          • Experience leveraging AI tools and automation technologies to improve workflows and productivity

          Qualifications

          • Experience with GTM tools such as Marketo, Gong, Outreach, ZoomInfo, Clay, or similar platforms
          • Experience with automation/orchestration tools such as Zapier or n8n
          • Java or Python experience
          • SQL and data querying experience
          • Experience supporting SaaS go-to-market organizations
          • Experience with CPQ, CLM, or contract management platforms such as PandaDoc or DocuSign

          Benefits

          Meaningful equity and other benefits.

          Pay

          Starting salary range is $115,000‑$125,000 per year, based on experience.

          Schedule

          Remote position; must live and work permanently in the U.S.

          Check for any boilerplate left: We removed EEO, equal-opportunity, accommodations note, etc. Also removed "CompanyCam is an equal-opportunity employer..." etc. Also removed "Great ideas come from all backgrounds..." etc. Also removed. Also removed "Even if your work experience..." etc. Also removed "What really matters to us..." etc. Also removed "Please do not include any medical..." etc. Also removed "To be considered for a position, you must apply directly through our careers page." Also removed "Hi, We’re CompanyCam" we kept as part of About the role? Actually we started with "We’re CompanyCam". That's fine. We kept "Location: This is a remote position. You must live and work permanently in the U.S. to be considered." turned into Schedule. We kept "What You'll Have At CompanyCam, your work makes a real impact..." That's the Impact section. We omitted Impact section because not in allowed headings? The allowed headings include Impact? Not listed. The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive but those are examples. However they say "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; maybe we can also use other headings if they exist? But they gave examples; likely they expect only those headings. The Impact section is not in the list, so we should omit it or fold its content into another section. The impact statements could be folded into About the role or Responsibilities? Probably better to incorporate into About the role as a paragraph about impact. But we already have About the role with company description and role overview. Could add a paragraph about impact there. However we must preserve ALL substantive information; we cannot omit impact statements. So we need to include them somewhere. Could add a separate section "Impact" but not in allowed headings; risk of being considered not following instruction. However instruction says "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills,