View job listing
Apply to Tech Lead / Engineering Lead – Digital Asset Management (DAM) / Content Supply Chain
Position: Tech Lead / Engineering 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
Experience: 8+ years of software engineering experience with demonstrated technical leadership
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
Reporting / Technical Direction: Works under or closely with the DAM Solution Architect
Hiring Priority: High
Overview
Client is seeking a hands-on Tech Lead / Engineering Lead to support technical discovery and engineering definition for its Digital Asset Management (DAM) and Content Supply Chain initiative.
The immediate focus is not full-scale production implementation. The current phase involves understanding the proposed architecture, investigating technical feasibility, identifying implementation constraints, conducting proof-of-concepts, and preparing the engineering approach for a future MVP.
Working under the technical direction of the Solution Architect, the Tech Lead will translate the architecture into practical technical approaches, evaluate integration requirements, support upstream capability definition, and help identify engineering dependencies and risks.
The Tech Lead will operate one level below the Solution Architect. The architect will own end-to-end solution definition and architectural decisions, while the Tech Lead will own engineering-level feasibility, technical design support, and preparation for future release and integration execution.
The DAM platform remains under evaluation, with Aprimo currently preferred and Adobe DAM experience also considered. The Tech Lead should possess strong enterprise engineering fundamentals and be capable of adapting to the selected platform and technology stack.
As the initiative progresses into implementation, responsibilities are expected to expand into detailed engineering design, development leadership, integration execution, code reviews, release coordination, CI/CD, automated testing, and production readiness.
Success in the immediate phase will be measured by the quality of technical discovery, resolution of feasibility questions, proof-of-concept results, implementation planning, and readiness to support the subsequent engineering phase.
Purpose: Help establish the engineering foundation for a major enterprise DAM and Content Supply Chain initiative at ****. Work alongside the Solution Architect to determine how the proposed platform and upstream integrations can be translated into practical, maintainable engineering solutions.
Objectives
1. Complete Engineering Discovery and Validate the DAM Implementation Approach. lead technical discovery activities under the direction of the Solution Architect to assess the proposed DAM platform, upstream integration needs, and engineering feasibility of the planned MVP. Translate architectural concepts and functional requirements into engineering questions, technical dependencies, implementation constraints, and candidate technical approaches. Collaborate with Product, BTA, Architecture, QA, DevOps, and engineering stakeholders to identify requirements gaps and areas requiring proof-of-concept validation. Success will be measured by acceptance of the engineering discovery findings, documented resolution or escalation of priority technical questions, and agreement on the technical investigations needed to support MVP planning.
2. Validate DAM Platform Capabilities Through Technical Spikes and Proof-of-Concepts. lead hands-on technical evaluations of selected DAM capabilities, extensions, upstream integration approaches, and relevant platform constraints. Develop or guide focused proof-of-concepts to test technical assumptions involving metadata handling, asset processing, workflow behavior, API connectivity, and integration feasibility where these are material to the discovery scope. Evaluate implications of Aprimo or Adobe platform selection, including relevant .NET or Java technology considerations, without treating either stack as finalized. Success will be measured by completion of agreed technical spikes, documented findings and recommendations, and stakeholder acceptance of the engineering feasibility conclusions.
3. Translate Approved Architecture into MVP Engineering Designs and Delivery Plans. work with the Solution Architect to develop detailed technical approaches for the capabilities and upstream integrations expected in the initial MVP. Define engineering components, interface considerations, implementation dependencies, preliminary development stories, testing needs, and relevant non-functional requirements while keeping full production implementation outside the current discovery assignment. Identify where reusable components, DAM extensions, cloud services, or custom integration approaches may be needed and assess their implementation implications. Success will be measured by acceptance of priority technical design artifacts, agreement on engineering dependencies and implementation sequencing, and readiness of the proposed engineering approach for subsequent project planning.
4. Establish Engineering Readiness for Future Integration and Release Execution. develop the technical standards and implementation-readiness recommendations required to support the planned DAM MVP delivery phase. Assess the future needs for CI/CD, automated testing, environment management, observability, troubleshooting, code review, release coordination, and integration quality in collaboration with Architecture, QA, DevOps, and engineering stakeholders. Document the engineering approach for current upstream integration priorities while identifying downstream integration work as a future consideration rather than an immediate deliverable. Success will be measured by acceptance of the engineering readiness assessment, documented technical standards and release dependencies, and agreement on the key engineering prerequisites for implementation.
Critical Subtasks
1. Review the Target Architecture and Conduct Engineering Discovery. Success will be measured by an accepted engineering discovery summary, a prioritized technical risk register, and agreement on the initial proof-of-concept backlog.
2. Assess DAM Platform Engineering Capabilities and Technology Dependencies. evaluate the implementation implications of the DAM platforms under consideration, with particular attention to Aprimo and Adobe. Review relevant extension mechanisms, API capabilities, integration approaches, metadata handling, workflow support, and potential .NET or Java development requirements. Document where product-specific knowledge is essential and where existing enterprise engineering patterns can be reused or adapted. Success will be measured by completion of the agreed technical evaluation, documentation of platform-specific constraints, and acceptance of the findings by the Solution Architect.
3. Execute Targeted Technical Spikes and Proof-of-Concepts. lead or personally perform focused technical experiments to validate high-priority implementation assumptions. Investigate selected capabilities such as metadata mapping, asset processing, upstream API connectivity, workflow behavior, and platform extension feasibility as defined by the discovery backlog. Success will be measured by completion of the agreed proof-of-concepts, reproducible evidence of technical feasibility, and documented resolution or escalation of critical uncertainties.
4. Define the Engineering Approach for Upstream Integrations. work with the Solution Architect to translate the approved upstream integration architecture into practical engineering approaches. Evaluate interface requirements, authentication considerations, data mapping, integration service patterns, error handling, and major dependencies between DAM and relevant source systems. Success will be measured by acceptance of the upstream engineering approach, validation of agreed high-risk integration assumptions, and documentation of remaining implementation dependencies.
Requirements
Preferred Qualifications
Profile
Location: Flexible -candidates may be sourced from any location or time zone
Work Arrangement: Onsite preferred; exact site and attendance requirements to be confirmed
Experience: 8+ years of software engineering experience with demonstrated technical leadership
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
Reporting / Technical Direction: Works under or closely with the DAM Solution Architect
Hiring Priority: High
Overview
Client is seeking a hands-on Tech Lead / Engineering Lead to support technical discovery and engineering definition for its Digital Asset Management (DAM) and Content Supply Chain initiative.
The immediate focus is not full-scale production implementation. The current phase involves understanding the proposed architecture, investigating technical feasibility, identifying implementation constraints, conducting proof-of-concepts, and preparing the engineering approach for a future MVP.
Working under the technical direction of the Solution Architect, the Tech Lead will translate the architecture into practical technical approaches, evaluate integration requirements, support upstream capability definition, and help identify engineering dependencies and risks.
The Tech Lead will operate one level below the Solution Architect. The architect will own end-to-end solution definition and architectural decisions, while the Tech Lead will own engineering-level feasibility, technical design support, and preparation for future release and integration execution.
The DAM platform remains under evaluation, with Aprimo currently preferred and Adobe DAM experience also considered. The Tech Lead should possess strong enterprise engineering fundamentals and be capable of adapting to the selected platform and technology stack.
As the initiative progresses into implementation, responsibilities are expected to expand into detailed engineering design, development leadership, integration execution, code reviews, release coordination, CI/CD, automated testing, and production readiness.
Success in the immediate phase will be measured by the quality of technical discovery, resolution of feasibility questions, proof-of-concept results, implementation planning, and readiness to support the subsequent engineering phase.
Purpose: Help establish the engineering foundation for a major enterprise DAM and Content Supply Chain initiative at ****. Work alongside the Solution Architect to determine how the proposed platform and upstream integrations can be translated into practical, maintainable engineering solutions.
Objectives
1. Complete Engineering Discovery and Validate the DAM Implementation Approach. lead technical discovery activities under the direction of the Solution Architect to assess the proposed DAM platform, upstream integration needs, and engineering feasibility of the planned MVP. Translate architectural concepts and functional requirements into engineering questions, technical dependencies, implementation constraints, and candidate technical approaches. Collaborate with Product, BTA, Architecture, QA, DevOps, and engineering stakeholders to identify requirements gaps and areas requiring proof-of-concept validation. Success will be measured by acceptance of the engineering discovery findings, documented resolution or escalation of priority technical questions, and agreement on the technical investigations needed to support MVP planning.
2. Validate DAM Platform Capabilities Through Technical Spikes and Proof-of-Concepts. lead hands-on technical evaluations of selected DAM capabilities, extensions, upstream integration approaches, and relevant platform constraints. Develop or guide focused proof-of-concepts to test technical assumptions involving metadata handling, asset processing, workflow behavior, API connectivity, and integration feasibility where these are material to the discovery scope. Evaluate implications of Aprimo or Adobe platform selection, including relevant .NET or Java technology considerations, without treating either stack as finalized. Success will be measured by completion of agreed technical spikes, documented findings and recommendations, and stakeholder acceptance of the engineering feasibility conclusions.
3. Translate Approved Architecture into MVP Engineering Designs and Delivery Plans. work with the Solution Architect to develop detailed technical approaches for the capabilities and upstream integrations expected in the initial MVP. Define engineering components, interface considerations, implementation dependencies, preliminary development stories, testing needs, and relevant non-functional requirements while keeping full production implementation outside the current discovery assignment. Identify where reusable components, DAM extensions, cloud services, or custom integration approaches may be needed and assess their implementation implications. Success will be measured by acceptance of priority technical design artifacts, agreement on engineering dependencies and implementation sequencing, and readiness of the proposed engineering approach for subsequent project planning.
4. Establish Engineering Readiness for Future Integration and Release Execution. develop the technical standards and implementation-readiness recommendations required to support the planned DAM MVP delivery phase. Assess the future needs for CI/CD, automated testing, environment management, observability, troubleshooting, code review, release coordination, and integration quality in collaboration with Architecture, QA, DevOps, and engineering stakeholders. Document the engineering approach for current upstream integration priorities while identifying downstream integration work as a future consideration rather than an immediate deliverable. Success will be measured by acceptance of the engineering readiness assessment, documented technical standards and release dependencies, and agreement on the key engineering prerequisites for implementation.
Critical Subtasks
1. Review the Target Architecture and Conduct Engineering Discovery. Success will be measured by an accepted engineering discovery summary, a prioritized technical risk register, and agreement on the initial proof-of-concept backlog.
2. Assess DAM Platform Engineering Capabilities and Technology Dependencies. evaluate the implementation implications of the DAM platforms under consideration, with particular attention to Aprimo and Adobe. Review relevant extension mechanisms, API capabilities, integration approaches, metadata handling, workflow support, and potential .NET or Java development requirements. Document where product-specific knowledge is essential and where existing enterprise engineering patterns can be reused or adapted. Success will be measured by completion of the agreed technical evaluation, documentation of platform-specific constraints, and acceptance of the findings by the Solution Architect.
3. Execute Targeted Technical Spikes and Proof-of-Concepts. lead or personally perform focused technical experiments to validate high-priority implementation assumptions. Investigate selected capabilities such as metadata mapping, asset processing, upstream API connectivity, workflow behavior, and platform extension feasibility as defined by the discovery backlog. Success will be measured by completion of the agreed proof-of-concepts, reproducible evidence of technical feasibility, and documented resolution or escalation of critical uncertainties.
4. Define the Engineering Approach for Upstream Integrations. work with the Solution Architect to translate the approved upstream integration architecture into practical engineering approaches. Evaluate interface requirements, authentication considerations, data mapping, integration service patterns, error handling, and major dependencies between DAM and relevant source systems. Success will be measured by acceptance of the upstream engineering approach, validation of agreed high-risk integration assumptions, and documentation of remaining implementation dependencies.
Requirements
- Software Engineering Experience: 8+ years of software engineering experience, including demonstrated technical leadership responsibilities.
- Hands-On Enterprise Platform Experience: Experience implementing or technically evaluating DAM, CMS, MarTech, enterprise content, or comparable platforms.
- Technical Discovery and Feasibility: Ability to conduct engineering discovery, identify implementation constraints, assess technical risks, and lead proof-of-concepts.
- Architecture-to-Engineering Translation: Demonstrated ability to work under solution architecture direction and convert high-level designs into practical technical approaches, implementation specifications, and engineering plans.
- REST APIs and Integration Engineering: Strong experience with REST APIs, enterprise integration patterns, and the technical considerations involved in connecting enterprise platforms.
- Cloud Engineering: Experience with cloud-based 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 technical investigations, participate in design reviews, solve complex engineering problems, and prepare for future team and release leadership.
- Cross-Functional Collaboration: Ability to work effectively with Solution Architects, Product, BTA, QA, DevOps, and engineering teams.
Preferred Qualifications
- Aprimo DAM: Direct hands-on experience with Aprimo DAM implementations, integrations, extensions, or technical evaluation.
- Adobe DAM: Hands-on experience with Adobe Experience Manager Assets or comparable Adobe content platforms.
- Relevant Programming Stacks: Experience with .NET and/or Java enterprise development environments, with the final preference dependent on platform selection.
- DAM Connectors and Extensions: Experience designing or developing custom DAM connectors, APIs, extensions, or enterprise integration components.
- AWS and S3: Experience with AWS-based integration services and Amazon S3.
- Enterprise Implementation: Experience supporting large enterprise or global platform implementations.
- Onsite Availability: Willingness to collaborate onsite where required, while candidates from any location or time zone remain eligible for initial review.
Profile
- The ideal candidate is a hands-on Technical Lead, Engineering Lead, or senior enterprise software engineer who has supported complex DAM, CMS, MarTech, or Content Supply Chain initiatives.
- They have experience translating solution architecture into engineering approaches, leading technical discovery, building proof-of-concepts, and identifying implementation risks before full development begins.
- Aprimo experience is preferred, particularly where the candidate has worked on integrations, platform extensions, metadata handling, or content workflows. Strong Adobe DAM engineers with transferable integration and technical leadership experience should also be considered.
- The candidate must be comfortable working under the technical direction of a senior Solution Architect while independently driving engineering investigations, technical design, and feasibility validation.
- The strongest candidates will be able to describe specific technical problems they personally solved, the proof-of-concepts or integration components they built, and how they translated architectural decisions into engineering deliverables.
- This is not primarily a project management or pure architecture role. It requires a technical leader who can perform hands-on engineering work during discovery and transition into release and integration execution as the implementation phase develops.