GTM Engineer
Luminate · Los Angeles, CA · 3 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Key content:
- About the role: description of Luminate, role purpose, etc. Could be a paragraph.
- Responsibilities: list of "What You'll Do" bullet points.
- Requirements/Qualifications/Skills: "What You'll Bring" includes technical hands-on experience, practical engineering ability, experience with LLMs, fluency integrating across GTM stack, domain and mindset items, plus nice-to-have items.
We need to separate Requirements vs Qualifications vs Skills? The instruction says use headings for those categories if content exists. We can combine maybe "Requirements" for mandatory, "Nice to have" as separate? But headings list includes Requirements, Qualifications, Skills. We can decide to put mandatory under "Requirements" and nice-to-have under "Qualifications" or "Skills". However we need to preserve all substantive info.
Better: Use "Requirements" for mandatory items, "Preferred Qualifications" maybe not in list but we can use "Qualifications" for nice-to-have. Or we could have "Skills" for technical skills.
But we must not create sections with filler. So we need actual content.
Let's extract:
About the role: first paragraph(s) describing Luminate and role.
Responsibilities: bullet list under "What You'll Do". Each bullet is a responsibility.
Requirements: mandatory items under "What You'll Bring" before "Nice to have". That includes:
- Technical Hands-on experience building and deploying AI-powered workflows and agentic systems in production — writing business logic, designing solution architecture, and shipping reliably at pace.
- Practical engineering ability: comfort with scripting and data work (e.g., Python and SQL), API integration and webhooks, and workflow/automation tooling — enough to build, troubleshoot, and iterate on complex systems independently.
- Experience with LLMs, prompt engineering, and agent design applied to real revenue-workflow problems.
- Strong fluency integrating across the GTM stack: CRM, sales engagement, marketing automation, data enrichment, and intent tooling — e.g., Salesforce, Pardot, Clay, and Salesloft.
- Domain and mindset:
- A working understanding of inbound and outbound sales development — you know what an SDR and AE actually do, what slows them down, and what a pipeline conversion metric means.
- Fluency in how campaign data, intent signals, and lead flow connect to pipeline outcomes.
- An experimental, detective's mindset — you form hypotheses, test them, and let the data decide.
- The ability to communicate technical topics clearly to non-technical stakeholders and translate business requirements into technical designs.
That's the mandatory.
Nice to have: list after "Nice to have":
- Experience building agentic or LLM-powered workflows in a B2B enterprise environment.
- A track record inside or alongside a revenue org with direct accountability to pipeline or conversion outcomes.
- Several years spanning GTM engineering, marketing/revenue operations, growth, or a technical role embedded in a sales or marketing team.
- We care more about what you've built than years on a résumé — a strong portfolio of shipped systems matters most.
Also mention: As Luminate values in-person collaboration and team cohesion, employees work onsite 4 days a week and 1 day remotely with a focus on maintaining a vibrant and inclusive culture. Additionally, applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time.
Also Pay: For candidates based in California: A good faith estimate of the salary range is $130k-$150k +bonus upon hire. We consider your skills and experience, what similar jobs pay at companies of our size, and ensure fair pay among colleagues. Final base salary offer amounts are determined by factors including your experience and expertise.
Also Benefits: In addition we are proud to offer additional perks and benefits that contribute and complete our total compensation package. Luminate reserves the right to change our compensation bands at any time. It’s All About You… As a part of PMC’s family of companies, Luminate’s comprehensive benefits package is thoughtfully designed to support every aspect of your life, empowering you to thrive both personally and professionally. We offer Company-Paid Healthcare Premiums with no employee paycheck contributions on medical, dental, and vision premiums for you and your family. Luminate also offers Flexible Spending Accounts (Healthcare, Dependent Care & Commuter), an Employee Assistance Program, Life Insurance, Short & Long Term Disability, Paid Parental Leave, and a 401(k) Retirement Plan with an Employer match. Employees are also eligible to take advantage of company discounts and perks including Pet Insurance, Home & Auto Insurance, Mortgage discounts, and a variety of other savings on wellness, lifestyle, and financial essentials. As part of Luminate dedication to consistently meet employee’s needs, we maintain a Flexible Vacation Policy. At Luminate, we believe working in a highly collaborative, office-first environment that fosters real-time communication, spontaneous idea sharing, and stronger interpersonal relationships that drive innovation and team cohesion.
Also More About Us: Luminate has incredible 30 year history... We power the Billboard Charts, but we also inform the entire music industry with exclusive research, data and insights. We serve the television and film industry, providing deep meta-data on every major production and title. Luminate is an equal opportunity employer... (EEO boilerplate) - we should remove EEO/equal-opportunity boilerplate. Also remove cookie/navigation/legal/EEO etc. So we should drop the EEO paragraph.
Also "More About Us" maybe could be part of About the role? But we already have About the role describing Luminate. The "More About Us" repeats some info; we could incorporate but not duplicate. However we must preserve ALL substantive information; we cannot invent or summarize away detail. But we can combine similar info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? It says do NOT invent or summarize away detail. Summarizing away detail might be considered removing detail. Safer to keep the details as is, maybe separate sections.
We could have an "About Luminate" section (though not in allowed headings list). Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. "About the role" can include description of company and role. So we can put Luminate description there.
"More About Us" could be considered part of About the role as well, but we must not duplicate. We could incorporate the extra details into About the role paragraph.
Similarly, the schedule info: employees work onsite 4 days a week and 1 day remotely. That's schedule. So we need a Schedule section.
Pay section: we have salary range.
Benefits section: we have benefits details.
Now we need to avoid boilerplate like "We are unable to sponsor or take over sponsorship of an employment Visa at this time." That's not boilerplate? It's a requirement about work authorization. Could be part of Requirements? It's a eligibility requirement. Could be included under Requirements as a bullet: "Must be authorized to work for any employer in the U.S.; unable to sponsor visa." That's substantive.
Also "As Luminate values in-person collaboration..." is schedule/culture; we already have schedule.
Now we need to output only HTML fragment, no markdown fences.
We'll structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Key content:
- About the role: description of Luminate, role purpose, etc. Could be a paragraph.
- Responsibilities: list of "What You'll Do" bullet points.
- Requirements/Qualifications/Skills: "What You'll Bring" includes technical hands-on experience, practical engineering ability, experience with LLMs, fluency integrating across GTM stack, domain and mindset items, plus nice-to-have items.
We need to separate Requirements vs Qualifications vs Skills? The instruction says use headings for those categories if content exists. We can combine maybe "Requirements" for mandatory, "Nice to have" as separate? But headings list includes Requirements, Qualifications, Skills. We can decide to put mandatory under "Requirements" and nice-to-have under "Qualifications" or "Skills". However we need to preserve all substantive info.
Better: Use "Requirements" for mandatory items, "Preferred Qualifications" maybe not in list but we can use "Qualifications" for nice-to-have. Or we could have "Skills" for technical skills.
But we must not create sections with filler. So we need actual content.
Let's extract:
About the role: first paragraph(s) describing Luminate and role.
Responsibilities: bullet list under "What You'll Do". Each bullet is a responsibility.
Requirements: mandatory items under "What You'll Bring" before "Nice to have". That includes:
- Technical Hands-on experience building and deploying AI-powered workflows and agentic systems in production — writing business logic, designing solution architecture, and shipping reliably at pace.
- Practical engineering ability: comfort with scripting and data work (e.g., Python and SQL), API integration and webhooks, and workflow/automation tooling — enough to build, troubleshoot, and iterate on complex systems independently.
- Experience with LLMs, prompt engineering, and agent design applied to real revenue-workflow problems.
- Strong fluency integrating across the GTM stack: CRM, sales engagement, marketing automation, data enrichment, and intent tooling — e.g., Salesforce, Pardot, Clay, and Salesloft.
- Domain and mindset:
- A working understanding of inbound and outbound sales development — you know what an SDR and AE actually do, what slows them down, and what a pipeline conversion metric means.
- Fluency in how campaign data, intent signals, and lead flow connect to pipeline outcomes.
- An experimental, detective's mindset — you form hypotheses, test them, and let the data decide.
- The ability to communicate technical topics clearly to non-technical stakeholders and translate business requirements into technical designs.
That's the mandatory.
Nice to have: list after "Nice to have":
- Experience building agentic or LLM-powered workflows in a B2B enterprise environment.
- A track record inside or alongside a revenue org with direct accountability to pipeline or conversion outcomes.
- Several years spanning GTM engineering, marketing/revenue operations, growth, or a technical role embedded in a sales or marketing team.
- We care more about what you've built than years on a résumé — a strong portfolio of shipped systems matters most.
Also mention: As Luminate values in-person collaboration and team cohesion, employees work onsite 4 days a week and 1 day remotely with a focus on maintaining a vibrant and inclusive culture. Additionally, applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time.
Also Pay: For candidates based in California: A good faith estimate of the salary range is $130k-$150k +bonus upon hire. We consider your skills and experience, what similar jobs pay at companies of our size, and ensure fair pay among colleagues. Final base salary offer amounts are determined by factors including your experience and expertise.
Also Benefits: In addition we are proud to offer additional perks and benefits that contribute and complete our total compensation package. Luminate reserves the right to change our compensation bands at any time. It’s All About You… As a part of PMC’s family of companies, Luminate’s comprehensive benefits package is thoughtfully designed to support every aspect of your life, empowering you to thrive both personally and professionally. We offer Company-Paid Healthcare Premiums with no employee paycheck contributions on medical, dental, and vision premiums for you and your family. Luminate also offers Flexible Spending Accounts (Healthcare, Dependent Care & Commuter), an Employee Assistance Program, Life Insurance, Short & Long Term Disability, Paid Parental Leave, and a 401(k) Retirement Plan with an Employer match. Employees are also eligible to take advantage of company discounts and perks including Pet Insurance, Home & Auto Insurance, Mortgage discounts, and a variety of other savings on wellness, lifestyle, and financial essentials. As part of Luminate dedication to consistently meet employee’s needs, we maintain a Flexible Vacation Policy. At Luminate, we believe working in a highly collaborative, office-first environment that fosters real-time communication, spontaneous idea sharing, and stronger interpersonal relationships that drive innovation and team cohesion.
Also More About Us: Luminate has incredible 30 year history... We power the Billboard Charts, but we also inform the entire music industry with exclusive research, data and insights. We serve the television and film industry, providing deep meta-data on every major production and title. Luminate is an equal opportunity employer... (EEO boilerplate) - we should remove EEO/equal-opportunity boilerplate. Also remove cookie/navigation/legal/EEO etc. So we should drop the EEO paragraph.
Also "More About Us" maybe could be part of About the role? But we already have About the role describing Luminate. The "More About Us" repeats some info; we could incorporate but not duplicate. However we must preserve ALL substantive information; we cannot invent or summarize away detail. But we can combine similar info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? It says do NOT invent or summarize away detail. Summarizing away detail might be considered removing detail. Safer to keep the details as is, maybe separate sections.
We could have an "About Luminate" section (though not in allowed headings list). Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. "About the role" can include description of company and role. So we can put Luminate description there.
"More About Us" could be considered part of About the role as well, but we must not duplicate. We could incorporate the extra details into About the role paragraph.
Similarly, the schedule info: employees work onsite 4 days a week and 1 day remotely. That's schedule. So we need a Schedule section.
Pay section: we have salary range.
Benefits section: we have benefits details.
Now we need to avoid boilerplate like "We are unable to sponsor or take over sponsorship of an employment Visa at this time." That's not boilerplate? It's a requirement about work authorization. Could be part of Requirements? It's a eligibility requirement. Could be included under Requirements as a bullet: "Must be authorized to work for any employer in the U.S.; unable to sponsor visa." That's substantive.
Also "As Luminate values in-person collaboration..." is schedule/culture; we already have schedule.
Now we need to output only HTML fragment, no markdown fences.
We'll structure:
About the role
... paragraph(s) ...
Responsibilities
- ... each bullet ...
Requirements
- ... mandatory items ...