Senior Computer Scientist - I (frontend)

Adobe Adobe · Enterprise · Noida, India

Senior Computer Scientist role focused on leading the architecture and development of a plugin platform for creative organizations, enabling in-tool content generation and iteration. The role emphasizes frontend expertise, API design, and managing complex initiatives within an enterprise context, with a secondary focus on GenAI/LLM integration.

What you'd actually do

  1. Lead the architecture of GeoStudio plugin experiences and shared frontend infrastructure (patterns, abstractions, extensibility strategy).
  2. Drive complex, high-impact initiatives end-to-end: from ambiguous problem definition to delivery, rollout strategy, and iteration based on feedback.
  3. Set engineering direction on quality, performance, reliability, accessibility, and maintainability for plugin UI and integration layers.
  4. Define and influence API contracts with backend/platform teams to ensure developer-friendly, scalable integrations.
  5. Establish durable patterns for async workflows (job polling, progress UX, cancellation, retries, partial failures, and user trust).

Skills

Required

  • 8–12+ years of industry experience with deep frontend expertise and strong architectural ownership.
  • Expert knowledge of JavaScript/TypeScript and modern frontend architecture (component systems, state, performance, testing, build tooling).
  • Demonstrated success designing and shipping reusable, extensible frontend systems used across teams/products.
  • Strong experience integrating with REST/GraphQL APIs, handling auth and async workflows, and designing resilient client systems.
  • Ability to provide technical leadership, navigate ambiguity, and communicate clearly with engineering and product leadership.

Nice to have

  • Experience building products involving GenAI/LLMs (prompting patterns, model capabilities/limits, evaluation thinking, safety/guardrails).
  • Experience with enterprise requirements: entitlements, custom models, metering/usage considerations, compliance, and governance handoffs.
  • Practical full-stack skills (Node.js/microservices) and comfort owning small backend components when it unblocks the team.
  • Experience building developer-facing SDKs, shared libraries, or platform surfaces.

What the JD emphasized

  • brand-safe content
  • inside existing creative workflows
  • in-tool creation
  • field-role mapping
  • API-driven generation/editing flows
  • frontend-first