hirly

Apply with hirly

Senior Solution Architect – Agentic Sales Technology

Salesforce · Indiana - Indianapolis · Texas - Dallas

Upload your resume to see how well you match this job — free, in seconds, no account needed.

Your resume is used only to score it against this job. If you don't create an account, it is deleted within 24 hours.

To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts. Job Category Software Engineering Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. The Experience We're looking for a Senior Solution Architect who operates at the intersection of deep business process intuition and hands-on agentic engineering. This is a senior individual contributor role operating at director level — you will be a hands-on technical leader who builds, ships, and influences at scale without relying on organizational authority. You will not have direct reports, but your impact will be felt across an architecture organization. You think strategically and execute rapidly, often in the same week. The core mandate of this role is incremental transformation of prospect management — from lead generation and qualification through lead management and opportunity progression. This pipeline was architected for human-scale workflows, and the business expectation is clear: rapidly layer in new agentic tooling (Salesforce on Salesforce), measure impact, innovate, and iterate. You won't be rebuilding from scratch — you'll be threading intelligent agents into a live, complex system while keeping it moving. That requires as much judgment as it does technical skill. Wherever there is an opportunity to apply agentic AI to transform a business process, your first question on every engagement is always: does this process make sense before we agentify it? You'll bring coherence to a multi-technology landscape where multiple agentic tools are being implemented simultaneously — ensuring that buyer engagement agents, conversational sales agents, and the underlying CRM and routing infrastructure form a coherent, observable, and scalable whole. This role sits at the intersection of three organizational pillars — Sales Technology, Digital Marketing, and Data Solutions — and operates as a key architectural partner across all three. You will be accountable for E2E outcomes while holding direct responsibility for the architectural and technology components that live in CRM. Strong cross-pillar collaboration is not optional; it's how this role delivers. This role oscillates between two modes. In fast-twitch mode, you're supporting small, focused squads — simplifying the process, and getting a working prototype in the hands of users within days, making key architectural decisions that set the squad up for delivering a successful business outcome. You're not waiting for alignment; you're generating it through working software. In slow-burn mode, you're providing early architectural points of view on complex enterprise systems that don't fit the fast-twitch pace model — influencing the direction of large, integrated programs where the cost of getting the architecture wrong compounds over time. Strategic thinking and rapid execution are both required; this role demands you bring both, calibrated to the situation. You'll work across initiatives of varying scale and complexity — from focused two-week sprints to multi-quarter enterprise programs — and your job is to bring the right architectural posture to each one. Speed of learning and speed of shipping are equally important here — rapid learning is what makes rapid delivery sustainable. Equally important: this role advances how we build. You'll practice and model an AI-native development lifecycle (AIDLC) — using Cursor, Claude Code, and Codex not as productivity shortcuts but as a fundamentally different way of working. Architecture patterns, best practices, and compliance checks should be baked into the tooling, not left to individual teams to figure out. What You’ll Actually Be Doing... Agentic Architecture & Incremental Transformation

  • Own the architectural foundation for agentic selling across the full marketing-to-sales pipeline — lead generation, lead qualification, lead management, and opportunity progression
  • Drive an incremental transformation approach: layer agentic tooling into live systems deliberately, instrument for impact, and create tight feedback loops for innovation and iteration
  • Define and track meaningful architectural success metrics — including agent-driven pipeline conversion lift, lead qualification rates, routing accuracy, and agent deflection/escalation patterns
  • Assess and rationalize the current multi-technology landscape, identifying conflicts, dependencies, and integration gaps
  • Design multi-agent orchestration patterns that are coherent, observable, and production-grade — not prototypes layered on existing systems
  • Ensure lead routing, territory assignment, and CRM workflows are refactored — incrementally — to support agent-scale throughput and decision-making
  • Lead context engineering practices — designing the information architecture, retrieval strategies, and grounding mechanisms that give agents the right context to act reliably and accurately
  • Define agent lifecycle management practices: design, testing, iteration, observability, and governance from prototype through production Agentic Builder — Design & Build
  • Assess and simplify business processes before applying technology; show the business a working prototype within days on fast-twitch engagements
  • Develop and Apply agentic architecture patterns that apply across the the full Prospect-to-Cash domain
  • Design context engineering strategies — information architecture, grounding, memory patterns, and retrieval design — that give agents the right context to act reliably
  • Define agent lifecycle practices: design, testing, iteration, observability, and governance from prototype through production
  • Codify architecture patterns and best practices directly into tooling so they travel with the work, not sit in a document Forward-Looking Architecture
  • Serve as an early architectural point of view across multiple initiatives, technology, product innovations. Serve as a trusted advisor to the Product, Engineering organization as well as Senior Leadership to navigate through ambiguity.
  • Engage across initiatives of all scales, bringing the right level of architectural rigor to each — from rapid prototyping engagements to complex, multi-system programs
  • For complex enterprise programs, break down intake requests to achieve incremental outcomes, minimize dependencies, and reduce downstream cost and risk — this is where judgment about what not to build matters as much as what to build
  • Identify and escalate process or data blockers that will slow agentic transformation; make them visible rather than working around them
  • Act as connective tissue between fast-moving squads and the domain teams that own core business technology — ensuring fast-moving work lands on solid architectural ground Strategic Influence, Rapid Validation
  • Approach every engagement with a strategic lens — understand the business outcome before proposing a technical direction
  • Validate with the business first, use AI to generate evidence of value quickly, then scale
  • Accelerate business analysis and decision-making by applying AI — reducing the time between a question and a validated answer from weeks to days
  • Work with one empowered business decision-maker per engagement, not a committee
  • Influence enterprise architecture direction on complex programs where the fast-twitch model isn't appropriate, wit