Senior AI solutions Engineer at Verity
—
Jul 20, 2026
—
Jul 22, 2026
What this job asks for AI summary
This role sits at the intersection of AI engineering and customer-facing data work, focused on building LLM-powered automations and agentic workflows that connect tools like Salesforce, HubSpot, Jira, and Confluence. The engineer will also analyze product usage data to surface churn risks and expansion signals for customer success teams, build analytics dashboards, and occasionally consult directly with clients. It suits a technically deep candidate with production LLM experience and strong SQL skills who is comfortable bridging data engineering and commercial teams.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 290 people nationally plausibly meet what this posting asks for (data scientists). range 170–520
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $122,874 (middle half $87,544–$162,374).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
No work location or CBSA is specified in the posting; the role appears to be remote-friendly given the absence of any office requirement, but this is inferred rather than explicitly stated.
The SOC classification is a genuine judgment call: the role blends LLM/agentic software development (15-1252) with data science and analytics (15-2051). The primary day-to-day deliverables — building MCP servers, deploying LLM agents, and backend automation — lean toward software development, so 15-1252 is the primary code, with 15-2051 as the runner-up.
Salesintel is mentioned in the narrative as a tool the automations connect to, but it appears only in the 'What You'll Do' context section rather than a requirements block; it is omitted from the skills list accordingly.
Claude Cowork, Claude Code, and Claude Skills are listed under the Preferred section as part of the broader tech stack familiarity; they are captured under the LLMs preferred skill rather than as separate entries because they are Anthropic product variants rather than independently named tools with distinct skill gates.
The 2-year minimum for LLMs is drawn from the explicit '2+ years deploying LLMs in production' requirement; the overall 5-year minimum is from '5+ years in a highly technical, data-driven role'.
Webhooks are mentioned alongside REST/GraphQL/OAuth in the required section but represent a protocol feature rather than a distinct named tool; they are not emitted as a separate skill.
PyCharm and VS Code appear only in the Preferred stack list and are development environment preferences rather than skill gates; they are omitted as they name no distinct technology capability.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.