Job description

A leading organization is seeking a Workfront Fusion Integration Developer to build, support, and optimize integrations across its marketing technology environment. This full-time contract position may extend for an initial assignment of up to 12 months. The Workfront Fusion Integration Developer will create advanced automation scenarios, connect content and campaign platforms, and translate complex marketing workflows into reliable technical solutions. The position requires deep Workfront Fusion expertise, strong API integration skills, and experience consulting with business and technical stakeholders.

Responsibilities

• Design, build, test, and deploy complex Workfront Fusion scenarios supporting marketing and campaign workflows.
• Create automated data and asset flows across intake, planning, content creation, review, activation, and reporting processes.
• Integrate Workfront with Adobe Express, Firefly, GenStudio, Adobe Journey Optimizer, and related Adobe Experience Cloud technologies.
• Build Workfront integrations with digital asset management platforms and Jira.
• Develop custom REST and SOAP API integrations using JSON, XML, OAuth 2.0, API keys, and other authentication methods.
• Configure advanced Workfront automation using custom rules, API calls, and webhooks.
• Support automated content review and brand compliance workflows.
• Troubleshoot, debug, and optimize existing Fusion scenarios and API connections.
• Monitor system performance, API limits, webhook responses, workflow stability, and integration bottlenecks.
• Design reusable error-handling, logging, and recovery processes to reduce data loss and service disruption.
• Partner with marketing, creative, and system administration teams to translate operational requirements into scalable technical solutions.
• Document integration scenarios, data mappings, credentials, workflow diagrams, and support procedures.
• Collaborate with external technology vendors and implementation partners to maintain architectural consistency.

Required experience and skills

• At least three years of intensive, hands-on Workfront Fusion or Integromat development experience.
• Experience building complex, multibranch, and iterative automation scenarios.
• Deep knowledge of the Adobe Workfront object model, custom forms, project templates, queues, sharing settings, and advanced reporting.
• Strong experience developing integrations using REST and SOAP APIs.
• Proficiency with JSON, XML, data parsing, mapping, and transformation.
• Experience with OAuth 2.0, API keys, basic authentication, and credential management.
• Strong debugging, logical reasoning, and integration troubleshooting skills.
• Professional consulting experience in an agency, professional services firm, or independent consulting environment.
• Ability to gather requirements, manage stakeholder expectations, balance competing priorities, and drive technical alignment.
• Experience supporting and optimizing production integrations.
• Experience creating technical documentation, data mappings, and workflow diagrams.
• Adobe Workfront or Workfront Fusion Developer certification is preferred.
• Experience with Adobe Experience Manager Assets, GenStudio, Adobe Express, Firefly, or Adobe Journey Optimizer is preferred.
• Experience integrating Workfront with Jira or digital asset management platforms is preferred.
• Experience within a regulated industry such as healthcare, insurance, or financial services is preferred.

FAQs

1. What does a Workfront Fusion Integration Developer do?

A Workfront Fusion Integration Developer designs, builds, and maintains automated workflows that connect Adobe Workfront with other business applications. The role focuses on integration architecture, data movement, workflow automation, API connectivity, error handling, and maintaining reliable business processes.

2. How is Workfront Fusion used for integration automation?

Workfront Fusion connects Workfront with external applications through configurable scenarios, triggers, actions, routers, and data transformations. Developers use these capabilities to automate processes such as project updates, task synchronization, notifications, approvals, and data exchange between systems.

3. What types of systems can be integrated with Workfront Fusion?

Workfront Fusion can connect Workfront with applications such as CRM platforms, collaboration tools, ERP systems, cloud services, databases, and custom applications. Developers may use prebuilt connectors or HTTP/API modules when a specific application does not have a native connector.

4. How does a Workfront Fusion developer work with APIs?

Developers use REST APIs and HTTP-based integrations to retrieve, create, update, or synchronize information between systems. They work with authentication, request and response structures, pagination, rate limits, error handling, and API-specific data formats.

5. How does data mapping work in Workfront Fusion integrations?

Data mapping determines how information from one system corresponds to fields and structures in another system. Developers transform, validate, and route data so that values such as project details, users, tasks, statuses, and custom fields are transferred accurately.

6. How does a Workfront Fusion developer troubleshoot failed scenarios?

Troubleshooting involves reviewing scenario execution history, module outputs, API responses, error messages, authentication settings, and data conditions. Developers isolate the failed step, determine the root cause, implement appropriate handling or corrections, and retest the complete workflow.

7. How does a Workfront Fusion developer design reliable integrations?

Reliable integrations account for authentication failures, missing data, duplicate records, API limits, service interruptions, and unexpected responses. Developers may use error handlers, retries, conditional logic, logging, validation, and monitoring to prevent individual failures from disrupting larger workflows.

8. How does a Workfront Fusion developer manage complex workflow logic?

Complex scenarios can use routers, filters, conditional paths, iterators, aggregators, and data transformations to support different business rules. Developers structure workflows carefully so that logic remains understandable, maintainable, and easy to troubleshoot as requirements evolve.