Software Engineer Technical Lead

Software Engineer Technical Lead – Digital Asset Management (DAM) / Content Supply Chain

Location: Flexible -candidates may be sourced from any location or time zone

Work Arrangement: Onsite preferred; exact site and attendance requirements to be confirmed

Platform Preference: Aprimo DAM preferred; Adobe DAM experience acceptable for consideration

Current Project Phase: Technical discovery, feasibility analysis, proof-of-concepts, detailed technical definition, and implementation planning

Purpose: Establish an engineering foundation for DAM and Content Supply Chain by translating architecture and upstream integrations into maintainable solutions.

Overview

Our client is seeking a hands-on Software Engineer Technical Lead to support technical discovery and engineering definition for a major Digital Asset Management (DAM) and Content Supply Chain initiative. The immediate focus is discovery rather than production implementation: evaluating architecture, technical feasibility, constraints, proof-of-concepts, and the approach for a future minimum viable product (MVP). Under the Solution Architect, the Tech Lead translates architectural concepts into engineering approaches and assesses upstream integrations, dependencies, and risks. The Architect owns end-to-end solution decisions; the Tech Lead owns feasibility, technical design support, and delivery readiness. The DAM platform has not been selected. Aprimo is preferred, while Adobe DAM experience is acceptable. Candidates should have strong enterprise engineering fundamentals and the ability to adapt to the selected platform and technology stack.

During implementation, responsibilities are expected to expand to detailed design, development leadership, integrations, code reviews, releases, CI/CD, automated testing, and production readiness.

Objectives

1. Complete Engineering Discovery and Validate the DAM Implementation Approach.

Lead discovery under the Solution Architect to assess DAM options, upstream integrations, and MVP feasibility. Translate requirements into technical questions, dependencies, constraints, and approaches. Work with Product, BTA, Architecture, QA, DevOps, and engineering to identify gaps requiring validation.

Success measures: Accepted discovery findings; documented priority questions and resolutions; agreed MVP investigations.

1. Validate DAM Platform Capabilities Through Technical Spikes and Proof-of-Concepts.

Lead hands-on evaluations of DAM capabilities, extensions, integration approaches, and platform constraints. Develop or guide focused proof-of-concepts involving metadata handling, asset processing, workflow behavior, API connectivity, and integration feasibility. Assess Aprimo and Adobe implications, including potential .NET or Java requirements, without assuming either stack is final.

Success measures: Completed spikes, documented recommendations, and accepted feasibility conclusions.

1. Translate Approved Architecture into MVP Engineering Designs and Delivery Plans.

Partner with the Solution Architect to define technical approaches for planned MVP capabilities and upstream integrations. Identify engineering components, interface considerations, dependencies, preliminary development stories, testing requirements, and relevant non-functional requirements. Evaluate reusable components, DAM extensions, cloud services, and custom integration options. Full production implementation is outside the current discovery phase.

Success measures: Accepted design artifacts, agreed dependencies and sequencing, and readiness for further planning.

1. Establish Engineering Readiness for Future Integration and Release Execution.

Define technical standards and implementation-readiness recommendations for the planned MVP. Assess future requirements for CI/CD, automated testing, environment management, observability, troubleshooting, code reviews, release coordination, and integration quality with Architecture, QA, DevOps, and engineering teams. Focus on current upstream integrations, treating downstream integrations as future work.

Success measures: Accepted readiness assessment, documented standards and release dependencies, and agreed implementation prerequisites.

Critical Subtasks

1. Review Target Architecture and Conduct Engineering Discovery.

Review the proposed solution architecture, MVP assumptions, upstream integration requirements, and engineering constraints. Identify technical risks, unresolved questions, and candidate proof-of-concepts.

Deliverables: Accepted engineering discovery summary, prioritized technical risk register, and initial proof-of-concept backlog.

1. Assess DAM Platform Engineering Capabilities and Technology Dependencies.

Evaluate Aprimo and Adobe implementation implications, including extensions, APIs, metadata, workflows, integration patterns, and potential .NET or Java requirements. Identify where product-specific knowledge is needed and where reusable enterprise engineering patterns may apply.

Deliverables: Technical evaluation findings, documented platform constraints, and Solution Architect acceptance.

1. Execute Targeted Technical Spikes and Proof-of-Concepts.

Lead or personally perform technical experiments to validate high-priority assumptions involving metadata mapping, asset processing, upstream API connectivity, workflow behavior, and DAM extension feasibility.

Deliverables: Completed proof-of-concepts, reproducible evidence, and disposition of critical uncertainties.

1. Define the Engineering Approach for Upstream Integrations.

Translate the approved upstream architecture into implementable engineering approaches. Evaluate interface requirements, authentication, data mapping, integration service patterns, error handling, and dependencies between DAM and relevant source systems.

Deliverables: Accepted upstream integration engineering approach, validation of high-risk assumptions, and documentation of outstanding implementation dependencies.

Requirements

• Software Engineering: 8+ years of experience, including demonstrated technical leadership.
• Enterprise Platforms: Hands-on experience implementing or technically evaluating DAM, CMS, MarTech, enterprise content, or comparable platforms.
• Discovery and Feasibility: Experience identifying engineering constraints and technical risks and leading proof-of-concepts.
• Architecture-to-Engineering Translation: Ability to turn solution architecture into practical technical designs, specifications, and delivery plans.
• REST APIs and Integrations: Strong experience with REST APIs, enterprise integration patterns, and connecting enterprise platforms.
• Cloud Engineering: Experience with cloud systems, integration services, and enterprise platform engineering.
• DAM Capabilities: Understanding of asset ingestion, metadata and data mapping, workflows, and enterprise content processing.
• Engineering Quality: Experience with CI/CD, automated testing, monitoring, troubleshooting, and software engineering quality practices.
• Technical Leadership: Ability to guide investigations, participate in design reviews, solve complex problems, and prepare for future team and release leadership.
• Collaboration: Ability to work effectively with Solution Architects, Product, BTA, QA, DevOps, and engineering teams.

Preferred Qualifications

• Aprimo DAM: Hands-on implementation, integration, extension, or technical evaluation experience.
• Adobe DAM: Experience with Adobe Experience Manager Assets or comparable Adobe content platforms.
• Programming Stacks: .NET and/or Java enterprise development; final preference depends on platform selection.
• DAM Connectors: Experience designing or developing custom connectors, APIs, extensions, or enterprise integration components.
• AWS and S3: Experience with AWS integration services and Amazon S3.
• Enterprise Implementation: Experience with large enterprise or global platform implementations.
• Onsite Availability: Willingness to collaborate onsite as required; candidates from any location or time zone may be considered initially.

Ideal Candidate Profile

The ideal candidate is a hands-on Technical Lead, Engineering Lead, or senior enterprise software engineer experienced with complex DAM, CMS, MarTech, or Content Supply Chain initiatives. They have translated solution architecture into engineering plans, led technical discovery, built proof-of-concepts, and identified implementation risks before full development.

Aprimo experience is preferred, particularly with integrations, platform extensions, metadata, or content workflows. Strong Adobe DAM engineers with transferable integration and technical leadership experience should also be considered.

The candidate must work effectively under a senior Solution Architect while independently driving technical investigation, detailed design, and feasibility validation. Strong candidates can explain technical problems they solved personally, proof-of-concepts or integration components they built, and how they converted architecture decisions into engineering deliverables.

This is not primarily a project management or pure architecture role . It requires hands-on engineering during discovery and the ability to transition into integration, development, and release execution as implementation proceeds.