Iterable Developer

**Location**: Remote **Engagement Type:** Freelance / Independent Contractor — Project\-Based **Estimated Duration:** Approximately 8 weeks **Start Date:** ASAP upon approval and contract execution We are seeking an experienced Iterable developer to lead two interconnected workstreams: building a scalable multi\-object catalog architecture within Iterable and integrating Carnegie’s proprietary Customer Data Platform (CDP) to power behavioral targeting and personalization. This engagement focuses on creating a maintainable, extensible personalization framework that Carnegie’s internal marketing team can confidently operate and evolve over time. **The Opportunity** We are looking for an experienced Iterable developer to lead two workstreams: building a connected multi\-object catalog architecture inside Iterable, and integrating our proprietary Customer Data Platform (CDP) with Iterable to power behavioral targeting and personalization. This is a project\-based engagement with a defined scope and deliverables. You will work directly with our marketing technology team with a designated point of contact and an emphasis on clear communication, documentation, and implementation transparency. The ultimate goal of this engagement is to create a scalable, maintainable personalization and behavioral targeting foundation that Carnegie’s internal marketing team can confidently operate and extend over time. ##### **Current Environment \& Project Context** Carnegie currently uses Iterable as part of its marketing technology ecosystem and is seeking to improve both catalog architecture and behavioral data activation capabilities. ##### **Current State** Candidates should assume the following at the start of the engagement: * Iterable is already implemented and in active use * Existing catalog structures may require refactoring or complete rebuilds within the current Iterable instance to achieve the multi\-object catalog architecture specified in the workstream. * A proprietary CDP platform exists and contains behavioral and profile\-level data; existing event tracking and instrumentation may require configuration, completion, or refinement during implementation based on the co\-developed tracking plan. * Initial business requirements and tracking use cases will be provided during onboarding to serve as the baseline for co\-developing the tracking plan. * Existing implementation patterns may include technical debt or inconsistencies. ##### **Discovery \& Validation** The first phase of the engagement will include a brief discovery and validation process to: * confirm technical assumptions * review existing catalog structures * validate available event data and mappings finalize the recommended CDP* Iterable integration approach * identify implementation risks or dependencies early Following discovery, the contractor should provide a brief implementation recommendation summary outlining any proposed architectural adjust