Partner Technical Architect

Responsibilities

• Prototype quickly to validate ideas, expose platform gaps, and unblock first‑of‑kind implementation risks.
• Build reference implementations, starter kits, demos, field kits, and evaluation harnesses that partners can fork, extend, and deploy.
• Convert field lessons into durable reusable assets: code, diagrams, checklists, decision trees, implementation notes, and architecture guidance.
• Review partner Agentforce architectures for agent design, retrieval strategy, tooling, guardrails, observability, cost, security, and production readiness.
• Coach Partner FDEs and architects through design clinics, office hours, portfolio reviews, and targeted technical walkthroughs.
• Translate recurring field blockers into clear product and engineering feedback.
• Help partners connect technical architecture choices to delivery quality, customer outcomes, and consumption economics.

• Experience building with LLMs, agents, RAG, tool use, workflow orchestration, or automation systems.
• Comfort debugging agent behavior: traces, logs, failure modes, tool calls, bad context, bad data, latency, and user experience gaps.
• Practical understanding of prompt design, retrieval quality, evaluation, hallucination risk, guardrails, and cost/performance trade‑offs.
• Strong systems thinking across APIs, data flows, identity, security, integration, observability, and operational handoff.
• Hands‑on Salesforce, Agentforce, Data Cloud, Apex, Flow, LWC, Mule Soft, or multi‑cloud architecture experience is preferred.
• Salesforce certifications are helpful, but not required if you can demonstrate strong builder evidence and rapid platform learning.

• LLMs
• agents
• RAG
• workflow orchestration
• automation systems
• prompt design
• retrieval quality
• evaluation
• debugging
• systems thinking

• coaching
• communication
• problem‑solving
• technical walkthroughs
• design clinics

• Salesforce certifications