GTM Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, there is an introductory paragraph about ProviderTrust & the Role. That could be "About the role". We'll include that as prose under

About the role

. Then "Role Phasing & Success Expectations" could be part of responsibilities? Might be better to treat as part of responsibilities or separate? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. We have content about what you'll do (responsibilities). That's "What You'll Do". So we can put under

Responsibilities

. We have "What We're Looking For" which includes requirements, qualifications, skills. Could split: Requirements (must-have), Qualifications (maybe same), Skills (nice to have). But we need to avoid thin sections. We can combine Requirements and Qualifications into one? But we need to follow instruction: Use headings only when posting has real specific content. We have content for Requirements (Proof-of-Work Portfolio etc.) and Nice to Have (Prior experience...). Could treat Requirements as mandatory, Nice to Have as Skills. Qualifications maybe not distinct. We could put Requirements under

Requirements

, Skills under

Skills

. Qualifications maybe omitted if not distinct. We also have Benefits section: "What It's Like to Work Here" includes many benefits: hybrid schedule, caregiver leave, PTO, insurance, etc. Also "Things That Make Us A Great Place To Work" list. So we can put Benefits. Pay: Not mentioned explicitly. No salary numbers. So we should NOT include Pay section. Schedule: Hybrid schedule mentioned: 2 days in office. That's schedule info. Could be under Schedule section. But also hybrid schedule is part of Benefits? It says "Hybrid schedule: 2 days in office". That's schedule. We could include Schedule section with that detail. However we also have hybrid schedule mentioned under Benefits list. Might be redundant. Better to put schedule under Schedule section, and other benefits under Benefits. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. The posting includes "ProviderTrust is an equal opportunity employer." That's boilerplate; remove. Also "To be great at ProviderTrust, we find our team members have these things in common:" list of traits; that's maybe culture, could be part of Benefits? It's not a benefit but could be part of "What It's Like to Work Here". We'll keep as part of Benefits or maybe as a separate section? Not in allowed headings. Could incorporate into Benefits as prose. We also have "Things That Make Us A Great Place To Work" list with many items; those are benefits/perks. We'll include under Benefits. Now craft HTML. Structure:

About the role

ProviderTrust was founded in 2010 ... (the intro paragraph up to "To learn more, visit [providertrust.com]" maybe we keep that as part of about). We'll include the description of ProviderTrust mission and the role building AI/GTM intelligence layer. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details but can condense into prose? The instruction: Use

for prose. So we can put multiple paragraphs. We must not repeat the job title as a heading. The job title is GTM Engineer? Not given explicitly but implied. We'll not add. Now Responsibilities: take "What You'll Do" bullet points (actually they are sentences). We'll convert each line into

under

. List them: - Work as an embedded partner with Product and Engineering to build that infrastructure, aligning RevOps' data needs with the core platform's architecture and roadmap - API & Data Architecture: design and build automations across our GTM stack (e.g., n8n, Slack, Gmail, Zoom, CRM) that eliminate manual handoffs in the revenue lifecycle - Build and maintain applied-AI tooling that supports internal GTM use cases — lead/account intelligence, forecasting inputs, rep-facing copilots, and workflow agents - Partner with Commercial and Ops leadership to translate operational pain points into engineered solutions, not just dashboards - Prototype quickly, ship iteratively, and instrument what you build so impact is measurable - Work alongside Data & Forecasting to ensure automations and AI tooling are grounded in clean, trustworthy data - Stay current on applied-AI and GTM-engineering practices and bring outside frameworks in where they sharpen our approach - Build and manage multi-channel sequences often representing more than 1 system at the time. (Example: such as LinkedIn → email → cold call → SMS) - Where possible, integrate into one workflow multiple existing digital processes - Report on automation ROI: such as time saved, revenue impact, headcount savings, accelerated sales cycle, bypass manual process, etc. (this list can be defined periodically with your leader) We'll keep as list. Now Requirements: from "What We're Looking For" bullet points (the mandatory ones). Let's extract: - Proof-of-Work Portfolio: a practical track record of shipping automation and insight - Experience designing or building AI automation coming from desperate sources (data warehouse, CRM Salesforce, BI tools, ETL data sources…). This role starts at the foundation layer, not just the automation layer on top of it - Experience building automations/integrations across SaaS tools (Slack, Gmail/Google Workspace, Zoom, CRM systems) using platforms like n8n, Zapier, or custom scripting - Hands-on experience building with LLMs/AI agents in a production or internal-tooling context, not just prompting, but architecting - Strong scripting/programming ability (Python and/or JavaScript) and comfort working directly with APIs - A GTM or RevOps background, or enough exposure to sales/CS/marketing motions to know what "useful" looks like to a rep or CSM - Bias toward shipping: comfortable owning a build end-to-end with limited scaffolding, in a function still being stood up - Team player mentality and a ‘Can Do’ attitude We'll list as
• . Now Skills (Nice to Have): - Prior experience in a healthcare, compliance, or data-integrity-adjacent SaaS business - Project management experience with scoping, documenting, and implementation steps We'll list under Skills. Now Benefits: from "What It's Like to Work Here" and "Things That Make Us A Great Place To Work". Need to capture all substantive benefits. Let's extract: Hybrid schedule: 2 days in office 16-week paid primary caregiver with a 2-week phase-back leave policy 4-week paid secondary caregiver leave policy We're genuinely curious about AI. Team members are encouraged to experiment and share what they learn Competitive base salary and incentive package with 401k matching, HSA employer contribution, and company-paid life and disability insurance Medical, dental, and vision benefits: PT pays 80% of your premiums. We also offer access to a range of free mental health and well-being resources. Unlimited PTO, 11 paid holidays, and a flexible work schedule Internal professional growth, development, and mobility Daily all-company morning huddles to sync up across the business In-office experience: fully stocked kitchen, ergonomic desk setup, and many celebrations! Remote experience: home office set-up with technology provided, remote-friendly meetings and celebrations, and interest-specific Slack channels for connecting across teams Fitness stipend and cell phone reimbursement Modern Healthcare Best Places to Work (2021-2026) The Tennessean Top Work Places (2022-2026) Also list of traits: Gain energy from working in a fast-paced, creative environment; Decision-making that employs a blend of data-driven insights and intuition; Ability to multitask and handle multiple projects concurrently; Resilience and positivity, able to address setbacks and bounce back quickly; Resourcefulness, discovering creative ways to get things done; Joy in making an immediate and positive impact; Diverse interests that are welcomed and extend beyond our organization. These are cultural traits, could be part of Benefits? Might be considered part of "What It's Like to Work Here". We'll include as prose under Benefits maybe as a paragraph. We should not include boilerplate like equal opportunity employer. Now Schedule: we have hybrid schedule: 2 days in office. That's schedule. Could also mention flexible work schedule. We'll put schedule details. We must not create Pay section because no specific salary. Now produce HTML. We need to ensure we don't include any markdown fences. Let's craft. We'll start with

  About the role

  then paragraphs. We need to preserve all substantive information; we can split into multiple paragraphs for readability. Let's write:

  About the role

  ProviderTrust was founded in 2010 with a mission to create safer healthcare for everyone through OIG and state Medicaid exclusion monitoring. Today, the organization has developed the industry’s most accurate dataset for ongoing exclusion monitoring and primary source verification, serving the nation’s top health systems, payers, and healthcare organizations. Our solutions monitor employees, vendors, provider networks, licenses, credentials, and more for OIG and state Medicaid exclusions, sanctions or disciplinary actions, license expirations, or suspensions. With a team of 100+ employees, our Nashville-based company has consistently been recognized as one of the Best Places to Work by Modern Healthcare, Inc. Magazine, and the Nashville Business Journal.

  ProviderTrust is building an internal AI/GTM intelligence layer as the strategic backbone of our Revenue Operations function — the connective tissue between Commercial, Ops, and Marketing that turns fragmented systems and manual workflows into a signal-driven revenue engine. The GTM Engineer owns the build: designing, shipping, and maintaining the automations, integrations, and applied-AI tooling that let RevOps operate at scale, not by hand. This is a builder's role, not an analyst's. You'll sit inside the AI & GTM Innovation pillar of RevOps and work in close partnership with Client Intelligence, Commercial Operations, Systems & Tooling, and Data & Forecasting to identify where AI and automation create leverage, then build it. Building the initial AI infrastructure will require working closely with Product and Engineering; this is not a role that builds in isolation from the core platform team.

  Now Responsibilities.

  Responsibilities

  • Work as an embedded partner with Product and Engineering to build that infrastructure, aligning RevOps' data needs with the core platform's architecture and roadmap
  • API & Data Architecture: design and build automations across our GTM stack (e.g., n8n, Slack, Gmail, Zoom, CRM) that eliminate manual handoffs in the revenue lifecycle
  • Build and maintain applied-AI tooling that supports internal GTM use cases — lead/account intelligence, forecasting inputs, rep-facing copilots, and workflow agents
  • Partner with Commercial and Ops leadership to translate operational pain points into engineered solutions, not just dashboards
  • Prototype quickly, ship iteratively, and instrument what you build so impact is measurable
  • Work alongside Data & Forecasting to ensure automations and AI tooling are grounded in clean, trustworthy data
  • Stay current on applied-AI and GTM-engineering practices and bring outside frameworks in where they sharpen our approach
  • Build and manage multi-channel sequences often representing more than 1 system at the time.