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 adjustments, risks, dependencies, or optimization opportunities before major build work begins.   

Candidates should surface any concerns, risks, or recommended adjustments during discovery before implementation begins.

What You Will Build

Workstream 1 — Multi-Object Catalog Architecture

Our catalog setup needs to be rebuilt to support efficient, accurate data retrieval across multiple connected objects within the same email send. You will:

• Design and implement multi-object catalog schemas with proper field types, key structures, and inter-catalog relationships
• Configure lookup logic that eliminates null-return errors and supports simultaneous cross-catalog queries
• Build a reusable snippet framework for calling data from multiple catalogs into a single email template using Iterable’s Handlebars templating engine
• Produce a working reference email template demonstrating the framework in action
• Deliver a Snippet Playbook — a documented guide covering all patterns, naming conventions, null handling, and edge cases for our template authors to follow going forward

Workstream 2 — Proprietary CDP Implementation & Iterable Integration

We have a proprietary Customer Data Platform (CDP) that needs to be architected, configured, and connected to Iterable. Because the tracking framework is not yet finalized, you will collaborate with our internal team to design the data strategy before executing the integration.

• Collaborate with the Carnegie team to define, design, and configure the behavioral event taxonomy, tracking plan, and user attribute data points for the proprietary CDP, ensuring they are optimized for downstream mapping into Iterable
• Configure behavioral insight rules and audience definitions as directed
• Validate that all tracked events fire correctly and populate the right fields
• Establish the CDP → Iterable integration (method TBD during discovery: native connector, webhook, or API)
• Map CDP profiles, events, and attributes to Iterable user fields and custom events
• Build in deduplication logic, field-type validation, and error handling for the data pipeline
• Conduct end-to-end testing and deliver a Data Flow Diagram and QA report

Deliverables at a Glance Catalog schemas built and validated in Iterable Reference multi-catalog email template Snippet Playbook (documented framework for template authors) CDP configured and implemented per co-developed tracking plan CDP → Iterable data pipeline live and tested Data Flow Diagram and QA Test Report One recorded handoff walkthrough per workstream

Acceptance Criteria & Definition of Done

To ensure alignment on scope, quality, and project completion, each milestone below includes minimum acceptance criteria. Candidates are encouraged to identify additional best practices or QA considerations during implementation.

Milestone 1 — Catalog Architecture & Snippet Playbook

This milestone will be considered complete when:

• All agreed-upon catalog schemas are built and functional within Iterable
• Catalog relationships and lookup structures successfully support cross-catalog data retrieval within a single email send
• Required lookup logic handles null values, missing records, and fallback conditions without rendering failures
• Reusable snippets are implemented and documented according to the agreed framework
• At least one production-ready reference email template is delivered demonstrating multi-catalog functionality
• Snippet Playbook is completed and includes:
  • naming conventions
  • lookup patterns
  • null-handling standards
  • troubleshooting guidance
  • implementation examples
• Carnegie stakeholders review and approve the delivered framework during walkthrough

Milestone 2 — CDP Configuration & Iterable Integration

This milestone will be considered complete when:

• The co-developed tracking plan and event taxonomy are finalized and approved
• All behavioral events and user attributes are successfully configured within the CDP
• CDP-to-Iterable data transmission is operational and validated
• Event ingestion, field mappings, and audience qualification behaviors are tested successfully
• Deduplication logic and field validation processes are functioning as intended
• Error handling and retry behavior are documented where applicable
• Carnegie stakeholders confirm visibility of required data within Iterable

Milestone 3 — QA, Documentation & Handoff

This milestone will be considered complete when:

• End-to-end testing is completed across all agreed workflows
• QA report is delivered with documented test cases, outcomes, known limitations, and resolutions
• Data Flow Diagram is finalized and shared in editable format
• All implementation documentation is delivered in a format accessible to internal Carnegie teams
• Documentation should be written for technically capable marketing operations users and internal administrators who may maintain these systems after project completion
• One recorded walkthrough session per workstream is completed and shared
• Carnegie confirms receipt of all deliverables and implementation artifacts

Change Management & Scope Alignment

Any material scope additions, architectural changes, or newly requested deliverables introduced after project kickoff may require timeline and pricing reassessment by mutual agreement.

Scope Assumptions & Out of Scope

Project Assumptions

The following assumptions are reflected in the project scope and pricing expectations:

• Carnegie will provide access to required systems, environments, credentials, and technical documentation in a timely manner
• Carnegie will provide raw data inputs and business requirements to collaboratively finalize the CDP tracking plan and data dictionary during the initial phase of the project.
• Iterable access and necessary permissions will already be provisioned
• Selected contractor will receive direct access to relevant Iterable and CDP environments as needed for implementation
• The proprietary CDP platform already exists and is operational; this engagement focuses on configuration, mapping, integration, and implementation rather than core platform engineering
• Carnegie will designate a primary point of contact for approvals, feedback, and implementation decisions
• Major architectural decisions, if needed, will be finalized during the discovery phase at project start

Out of Scope

Unless otherwise agreed in writing, the following are not included in this engagement:

• Net-new feature development for the proprietary CDP platform
• Core frontend engineering or native website/app code instrumentation (actual SDK deployment or script installation on the website/app)
• Creative email design or copywriting
• Ongoing campaign operations or audience management
• Long-term system maintenance, monitoring, or support after project completion
• Rebuilding or redesigning Carnegie’s broader data taxonomy or analytics strategy
• Third-party platform licensing costs or external vendor fees
• Additional integrations beyond the approved CDP → Iterable implementation scope

Post-Launch Support

Candidates may optionally propose separate pricing for:

• post-launch monitoring
• ongoing optimization support
• additional template development
• future integration enhancements

Timeline & Working Expectations

Estimated Timeline

The project is expected to run approximately 8 weeks from kickoff through final handoff, assuming timely access to systems, approvals, and required documentation.

Candidates should include:

• earliest available start date
• estimated timeline for each milestone
• any known scheduling constraints or timezone limitations

Working Style

This engagement will operate in an async-first environment with scheduled working sessions as needed.

We expect:

• proactive communication on blockers or risks
• clear documentation of implementation decisions
• regular progress updates throughout the engagement
• responsiveness during agreed working hours

Meetings & Collaboration

The anticipated collaboration structure includes:

• one kickoff session
• recurring status check-ins (typically weekly)
• implementation review sessions as needed
• final walkthrough and handoff meetings

Most collaboration will occur through written updates and shared documentation.

Dependencies & Delays

Carnegie will make reasonable efforts to provide timely feedback, approvals, and system access. If project delays occur due to access restrictions, evolving requirements, or dependency issues outside the contractor’s control, milestone timelines may be adjusted collaboratively.

Who We Are Looking For

Required

• 2+ years of hands-on Iterable technical experience, specifically including catalog management and template development
• Demonstrated experience building multi-object catalog structures in Iterable — please be ready to show examples or describe past implementations
• Proficiency with Iterable’s Handlebars templating syntax: loops, conditionals, catalog lookups, and null handling
• Experience integrating a CDP with Iterable via API, webhook, or native connector
• Working knowledge of REST APIs, webhooks, and JSON data structures
• Strong written communication — you will produce documentation that non-developers will use

Preferred

• Experience with behavioral event tracking and data taxonomy design
• Familiarity with data deduplication and pipeline error-handling patterns
• Prior work with proprietary or custom-built CDPs (not just Segment or mParticle)
• Comfort working across time zones with async-first communication

What a Strong Candidate Looks Like Has built multi-catalog Iterable setups before and can describe the decisions they made Knows where catalog lookups commonly break and how to prevent it Has connected a data source to Iterable end-to-end, including testing and error handling Asks clarifying questions before building, not after Delivers documentation that someone else can actually use

Budget & Payment

This engagement is fixed-price with milestone-based payments. 

• Milestone 1: Catalogs built, validated, and Snippet Playbook delivered
• Milestone 2: CDP configured and CDP → Iterable integration live and tested
• Milestone 3: Final QA sign-off, documentation complete, and handoff sessions delivered

We are open to candidates based anywhere in the world. Invoicing terms and preferred payment method (wire, PayPal, Wise, etc.) will be confirmed at contract stage.

Milestone Approval & Payment Process

Milestones will be considered complete upon written approval from Carnegie’s designated project owner. The contractor must submit a milestone completion notice and any associated deliverables for review. Payment will be processed following approval and receipt of invoice, in accordance with agreed contract payment terms established at engagement kickoff.

How to Apply

Please send the following to Halie Lewis at hlewis@carnegiehighered.com by June 1, 2026.  

• A brief summary of your relevant Iterable experience, specifically catalog work and any CDP integrations you have built
• One or two examples of past projects that are most relevant to this scope (links, case studies, or written descriptions are all fine)

Selected candidates will be required to review and agree to Carnegie’s Terms & Conditions prior to contract award and project kickoff.

Pricing Submission Requirements

Please include:

• A fixed-price quote for the full project scope
• A proposed milestone-based payment breakdown aligned to the milestones outlined above
• Any assumptions that materially affect pricing or delivery timeline
• Estimated timeline for completion
• Earliest available start date

Because portions of the current implementation may require discovery during onboarding, candidates should identify any assumptions or dependencies that could materially impact scope, timeline, or pricing.

Optional: Pricing for post-launch support or future optimization work

Optional: Alternative implementation approaches, if applicable 

Selection Criteria

Candidates will be evaluated based on:

• Relevant hands-on Iterable implementation experience
• Demonstrated success with catalog architecture and CDP integrations
• Clarity and practicality of proposed approach
• Communication and documentation capabilities
• Ability to execute within timeline expectations
• Overall value relative to scope and expertise

While budget is a consideration, selection will not be based solely on lowest cost.

We are not looking for a lengthy proposal — a clear, specific overview of your relevant experience is more useful to us than a generic pitch. Shortlisted candidates will be invited to a 30-minute call.

Confidentiality, Security & Ownership

Because this engagement involves proprietary systems, customer data structures, and internal marketing infrastructure, selected contractors will be required to sign a confidentiality agreement prior to project kickoff.

Data Handling Expectations

Contractors are expected to:

• follow reasonable security practices when accessing Carnegie systems and data
• limit access to authorized project personnel only
• avoid storing sensitive data outside approved systems where possible
• promptly report any suspected security or data access concerns

Ownership of Work Product

All deliverables produced as part of this engagement — including documentation, schemas, snippets, templates, workflows, mappings, diagrams, and implementation materials — will become the property of Carnegie upon final payment.

Contractors may reference the engagement in general terms within private portfolios or experience discussions unless otherwise restricted by agreement, but may not share proprietary implementation details, data structures, or internal documentation publicly.

Questions? Reach us at hlewis@carnegiehighered.com. We aim to respond to all applicants within 5 business days.

This brief is confidential and intended for prospective candidates only. Please do not distribute.