Own the plugin architecture. Define the tools, resources, and UI contracts that expose Adobe capabilities to third-party hosts. Keep one design working across hosts with different capabilities and harnesses, while it connects seamlessly with the Adobe ecosystem.
Lead partner engineering. Run the technical relationship with partner companies and internal product teams. Shape integration contracts and pick the technical bets that differentiate Adobe.
Make it real, fast. Build compelling prototypes and demos that settle architecture debates with working code, speed up partner and leadership decisions, and get others inspired by what's possible.
Push for scale and quality. Optimize tools so models choose them correctly. Set a high bar for latency and result quality. Build evaluation suites and compatibility layers so reliability holds as hosts change. Make sure the plugin rests on a foundation that supports observability and the operational needs of a product at Adobe's scale.
Lead engineers. Set technical direction, run investigations, and help the team weigh trade-offs. Mentor engineers on MCP, agent harness, generative-UI patterns, and AI-assisted development. Work closely with the Firefly, Photoshop, Lightroom, Premiere, Express, and Acrobat teams, plus platform, security, identity, and trust and safety. Together, keep guardrails, data protection, and content credentials intact on every host.
Shape the standards and their adoption. Stay ahead of the latest models capabilities, frameworks, and agent protocols. Recommend when and how to adopt them. Represent creative and productivity use cases where those protocols are defined, with proposals and reference implementations.