Lead Agentic Automation Engineer — AI & RPA
Nutanix
Turn this role into an interview — a resume and cover letter built around what this employer wants.
Job summary
Qualcomm Incorporated is seeking a highly skilled Senior Agentic Automations Engineer to join our AI Engineering organization in San Diego, CA. This role focuses on evolving our RPA capabilities into agentic automation for enterprise-wide processes, combining AI, automation, and secure enterprise integration.
You will lead technical delivery across a global matrixed team, design AI-driven agents and enterprise-grade assistants, and deploy solutions with Docker and Kubernetes while collaborating
Qualifications
- Bachelor’s degree in Engineering or related technical field required.
- 7+ years of experience in automation engineering, software development, or related roles.
- Proven expertise in agentic automation and AI agent development.
Responsibilities
- Define and implement automation standards for agentic workflows across the enterprise.
- Lead the technical delivery of agentic automation solutions, ensuring scalability and security.
- Serve as the technical lead for a global, matrixed team (no direct reports).
- Design and develop AI-driven agents, enterprise-grade chatbots, MCP servers, and workflow engines.
- Integrate and extend existing RPA platforms into agentic automation frameworks.
- Build and deploy solutions using Docker and Kubernetes in enterprise environments.
- Collaborate with business stakeholders to identify process optimization opportunities.
Skills
Education
Tools
Job description
Qualcomm Incorporated is seeking a highly skilled Senior Agentic Automations Engineer to join our AI Engineering organization in San Diego, CA. This role focuses on evolving our RPA capabilities into agentic automation for enterprise-wide processes, combining AI, automation, and secure enterprise integration.
You will lead technical delivery across a global matrixed team, design AI-driven agents and enterprise-grade assistants, and deploy solutions with Docker and Kubernetes while collaborating
'/%3e%3cpath%20d='M101.744%2012.4726L102.894%2016.1947L99.0021%2013.2201L101.744%2012.4726ZM105.3%208.40937H100.488L99.0026%203.59473L97.5116%208.41047L92.7%208.40385L96.5965%2011.3834L95.1055%2016.1942L99.0021%2013.2196L101.408%2011.3834L105.3%208.40992V8.40937Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_5593_1381'%20x1='90'%20y1='9.44471'%20x2='99'%20y2='9.44471'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%2300AD70'/%3e%3cstop%20offset='0.998594'%20stop-color='%2300B67A'/%3e%3cstop%20offset='1'%20stop-color='%23DCDCE6'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e){kind=small}
