{"schemaVersion":"jobsearcher.job.v1","id":"2ec6f7f04dbf71235f18e8e6","url":"https://jobsearcher.com/jobs/2ec6f7f04dbf71235f18e8e6","canonicalUrl":"https://jobsearcher.com/jobs/2ec6f7f04dbf71235f18e8e6","title":"Iterable Developer","description":"Location:\n\nRemote\n\nEngagement Type: Freelance / Independent Contractor — Project-Based\nEstimated Duration: Approximately 8 weeks\nStart Date: ASAP upon approval and contract execution\n\nWe 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.\n\nThe Opportunity\n\nWe 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.\n\nThis 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.\n\nThe 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.\n\nCurrent Environment & Project Context\n\nCarnegie currently uses Iterable as part of its marketing technology ecosystem and is seeking to improve both catalog architecture and behavioral data activation capabilities.\n\nCurrent State\n\nCandidates should assume the following at the start of the engagement:\n\nIterable is already implemented and in active use\nExisting catalog structures may require refactoring or complete rebuilds within the current Iterable instance to achieve the multi-object catalog architecture specified in the workstream.\nA 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.\nInitial business requirements and tracking use cases will be provided during onboarding to serve as the baseline for co-developing the tracking plan.\nExisting implementation patterns may include technical debt or inconsistencies.\nDiscovery & Validation\n\nThe first phase of the engagement will include a brief discovery and validation process to:\n\nconfirm technical assumptions\nreview existing catalog structures\nvalidate available event data and mappings\nfinalize the recommended CDP Iterable integration approach\nidentify implementation risks or dependencies early\n\nFollowing 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.\n\nCandidates should surface any concerns, risks, or recommended adjustments during discovery before implementation begins.\n\nWhat You Will Build\n\nWorkstream 1 — Multi-Object Catalog Architecture\n\nOur catalog setup needs to be rebuilt to support efficient, accurate data retrieval across multiple connected objects within the same email send. You will:\n\nDesign and implement multi-object catalog schemas with proper field types, key structures, and inter-catalog relationships\nConfigure lookup logic that eliminates null-return errors and supports simultaneous cross-catalog queries\nBuild a reusable snippet framework for calling data from multiple catalogs into a single email template using Iterable’s Handlebars templating engine\nProduce a working reference email template demonstrating the framework in action\nDeliver a Snippet Playbook — a documented guide covering all patterns, naming conventions, null handling, and edge cases for our template authors to follow going forward\n\nWorkstream 2 — Proprietary CDP Implementation & Iterable Integration\n\nWe 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.\n\nCollaborate 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\nConfigure behavioral insight rules and audience definitions as directed\nValidate that all tracked events fire correctly and populate the right fields\nEstablish the CDP Iterable integration (method TBD during discovery: native connector, webhook, or API)\nMap CDP profiles, events, and attributes to Iterable user fields and custom events\nBuild in deduplication logic, field-type validation, and error handling for the data pipeline\nConduct end-to-end testing and deliver a Data Flow Diagram and QA report\nDeliverables at a Glance\nCatalog schemas built and validated in Iterable\nReference multi-catalog email template\nSnippet Playbook (documented framework for template authors)\nCDP configured and implemented per co-developed tracking plan\nCDP Iterable data pipeline live and tested\nData Flow Diagram and QA Test Report\nOne recorded handoff walkthrough per workstream\n\nAcceptance Criteria & Definition of Done\n\nTo 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.\n\nMilestone 1 — Catalog Architecture & Snippet Playbook\n\nThis milestone will be considered complete when:\n\nAll agreed-upon catalog schemas are built and functional within Iterable\nCatalog relationships and lookup structures successfully support cross-catalog data retrieval within a single email send\nRequired lookup logic handles null values, missing records, and fallback conditions without rendering failures\nReusable snippets are implemented and documented according to the agreed framework\nAt least one production-ready reference email template is delivered demonstrating multi-catalog functionality\nSnippet Playbook is completed and includes:\nnaming conventions\nlookup patterns\nnull-handling standards\ntroubleshooting guidance\nimplementation examples\nCarnegie stakeholders review and approve the delivered framework during walkthrough\nMilestone 2 — CDP Configuration & Iterable Integration\n\nThis milestone will be considered complete when:\n\nThe co-developed tracking plan and event taxonomy are finalized and approved\nAll behavioral events and user attributes are successfully configured within the CDP\nCDP-to-Iterable data transmission is operational and validated\nEvent ingestion, field mappings, and audience qualification behaviors are tested successfully\nDeduplication logic and field validation processes are functioning as intended\nError handling and retry behavior are documented where applicable\nCarnegie stakeholders confirm visibility of required data within Iterable\nMilestone 3 — QA, Documentation & Handoff\n\nThis milestone will be considered complete when:\n\nEnd-to-end testing is completed across all agreed workflows\nQA report is delivered with documented test cases, outcomes, known limitations, and resolutions\nData Flow Diagram is finalized and shared in editable format\nAll implementation documentation is delivered in a format accessible to internal Carnegie teams\nDocumentation should be written for technically capable marketing operations users and internal administrators who may maintain these systems after project completion\nOne recorded walkthrough session per workstream is completed and shared\nCarnegie confirms receipt of all deliverables and implementation artifacts\nChange Management & Scope Alignment\n\nAny material scope additions, architectural changes, or newly requested deliverables introduced after project kickoff may require timeline and pricing reassessment by mutual agreement.\n\nScope Assumptions & Out of Scope\n\nProject Assumptions\n\nThe following assumptions are reflected in the project scope and pricing expectations:\n\nCarnegie will provide access to required systems, environments, credentials, and technical documentation in a timely manner\nCarnegie 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.\nIterable access and necessary permissions will already be provisioned\nSelected contractor will receive direct access to relevant Iterable and CDP environments as needed for implementation\nThe proprietary CDP platform already exists and is operational; this engagement focuses on configuration, mapping, integration, and implementation rather than core platform engineering\nCarnegie will designate a primary point of contact for approvals, feedback, and implementation decisions\nMajor architectural decisions, if needed, will be finalized during the discovery phase at project start\n\nOut of Scope\n\nUnless otherwise agreed in writing, the following are not included in this engagement:\n\nNet-new feature development for the proprietary CDP platform\nCore frontend engineering or native website/app code instrumentation (actual SDK deployment or script installation on the website/app)\nCreative email design or copywriting\nOngoing campaign operations or audience management\nLong-term system maintenance, monitoring, or support after project completion\nRebuilding or redesigning Carnegie’s broader data taxonomy or analytics strategy\nThird-party platform licensing costs or external vendor fees\nAdditional integrations beyond the approved CDP Iterable implementation scope\n\nPost-Launch Support\n\nCandidates may optionally propose separate pricing for:\n\npost-launch monitoring\nongoing optimization support\nadditional template development\nfuture integration enhancements\nTimeline & Working Expectations\nEstimated Timeline\n\nThe project is expected to run approximately 8 weeks from kickoff through final handoff, assuming timely access to systems, approvals, and required documentation.\n\nCandidates should include:\n\nearliest available start date\nestimated timeline for each milestone\nany known scheduling constraints or timezone limitations\nWorking Style\n\nThis engagement will operate in an async-first environment with scheduled working sessions as needed.\n\nWe expect:\n\nproactive communication on blockers or risks\nclear documentation of implementation decisions\nregular progress updates throughout the engagement\nresponsiveness during agreed working hours\nMeetings & Collaboration\n\nThe anticipated collaboration structure includes:\n\none kickoff session\nrecurring status check-ins (typically weekly)\nimplementation review sessions as needed\nfinal walkthrough and handoff meetings\n\nMost collaboration will occur through written updates and shared documentation.\n\nDependencies & Delays\n\nCarnegie 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.\n\nWho We Are Looking For\n\nRequired\n\n2+ years of hands-on Iterable technical experience, specifically including catalog management and template development\nDemonstrated experience building multi-object catalog structures in Iterable — please be ready to show examples or describe past implementations\nProficiency with Iterable’s Handlebars templating syntax: loops, conditionals, catalog lookups, and null handling\nExperience integrating a CDP with Iterable via API, webhook, or native connector\nWorking knowledge of REST APIs, webhooks, and JSON data structures\nStrong written communication — you will produce documentation that non-developers will use\n\nPreferred\n\nExperience with behavioral event tracking and data taxonomy design\nFamiliarity with data deduplication and pipeline error-handling patterns\nPrior work with proprietary or custom-built CDPs (not just Segment or mParticle)\nComfort working across time zones with async-first communication\nWhat a Strong Candidate Looks Like\nHas built multi-catalog Iterable setups before and can describe the decisions they made\nKnows where catalog lookups commonly break and how to prevent it\nHas connected a data source to Iterable end-to-end, including testing and error handling\nAsks clarifying questions before building, not after\nDelivers documentation that someone else can actually use\n\nBudget & Payment\n\nThis engagement is fixed-price with milestone-based payments.\n\nMilestone 1: Catalogs built, validated, and Snippet Playbook delivered\nMilestone 2: CDP configured and CDP Iterable integration live and tested\nMilestone 3: Final QA sign-off, documentation complete, and handoff sessions delivered\n\nWe 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.","company":"Carnegie Dartlet","rawCompany":"carnegie dartlet","city":"Myrtle Point","state":"OR","isRemote":false,"isActive":false,"createdAt":"2026-09-28T11:07:13.640Z","occupations":[{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1254.00","title":"Web Developers","slug":"web-developers"},{"code":"15-1243.01","title":"Data Warehousing Specialists","slug":"data-warehousing-specialists"}],"industries":[{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Iterable Developer","description":"Location:\n\nRemote\n\nEngagement Type: Freelance / Independent Contractor — Project-Based\nEstimated Duration: Approximately 8 weeks\nStart Date: ASAP upon approval and contract execution\n\nWe 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.\n\nThe Opportunity\n\nWe 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.\n\nThis 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.\n\nThe 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.\n\nCurrent Environment & Project Context\n\nCarnegie currently uses Iterable as part of its marketing technology ecosystem and is seeking to improve both catalog architecture and behavioral data activation capabilities.\n\nCurrent State\n\nCandidates should assume the following at the start of the engagement:\n\nIterable is already implemented and in active use\nExisting catalog structures may require refactoring or complete rebuilds within the current Iterable instance to achieve the multi-object catalog architecture specified in the workstream.\nA 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.\nInitial business requirements and tracking use cases will be provided during onboarding to serve as the baseline for co-developing the tracking plan.\nExisting implementation patterns may include technical debt or inconsistencies.\nDiscovery & Validation\n\nThe first phase of the engagement will include a brief discovery and validation process to:\n\nconfirm technical assumptions\nreview existing catalog structures\nvalidate available event data and mappings\nfinalize the recommended CDP Iterable integration approach\nidentify implementation risks or dependencies early\n\nFollowing 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.\n\nCandidates should surface any concerns, risks, or recommended adjustments during discovery before implementation begins.\n\nWhat You Will Build\n\nWorkstream 1 — Multi-Object Catalog Architecture\n\nOur catalog setup needs to be rebuilt to support efficient, accurate data retrieval across multiple connected objects within the same email send. You will:\n\nDesign and implement multi-object catalog schemas with proper field types, key structures, and inter-catalog relationships\nConfigure lookup logic that eliminates null-return errors and supports simultaneous cross-catalog queries\nBuild a reusable snippet framework for calling data from multiple catalogs into a single email template using Iterable’s Handlebars templating engine\nProduce a working reference email template demonstrating the framework in action\nDeliver a Snippet Playbook — a documented guide covering all patterns, naming conventions, null handling, and edge cases for our template authors to follow going forward\n\nWorkstream 2 — Proprietary CDP Implementation & Iterable Integration\n\nWe 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.\n\nCollaborate 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\nConfigure behavioral insight rules and audience definitions as directed\nValidate that all tracked events fire correctly and populate the right fields\nEstablish the CDP Iterable integration (method TBD during discovery: native connector, webhook, or API)\nMap CDP profiles, events, and attributes to Iterable user fields and custom events\nBuild in deduplication logic, field-type validation, and error handling for the data pipeline\nConduct end-to-end testing and deliver a Data Flow Diagram and QA report\nDeliverables at a Glance\nCatalog schemas built and validated in Iterable\nReference multi-catalog email template\nSnippet Playbook (documented framework for template authors)\nCDP configured and implemented per co-developed tracking plan\nCDP Iterable data pipeline live and tested\nData Flow Diagram and QA Test Report\nOne recorded handoff walkthrough per workstream\n\nAcceptance Criteria & Definition of Done\n\nTo 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.\n\nMilestone 1 — Catalog Architecture & Snippet Playbook\n\nThis milestone will be considered complete when:\n\nAll agreed-upon catalog schemas are built and functional within Iterable\nCatalog relationships and lookup structures successfully support cross-catalog data retrieval within a single email send\nRequired lookup logic handles null values, missing records, and fallback conditions without rendering failures\nReusable snippets are implemented and documented according to the agreed framework\nAt least one production-ready reference email template is delivered demonstrating multi-catalog functionality\nSnippet Playbook is completed and includes:\nnaming conventions\nlookup patterns\nnull-handling standards\ntroubleshooting guidance\nimplementation examples\nCarnegie stakeholders review and approve the delivered framework during walkthrough\nMilestone 2 — CDP Configuration & Iterable Integration\n\nThis milestone will be considered complete when:\n\nThe co-developed tracking plan and event taxonomy are finalized and approved\nAll behavioral events and user attributes are successfully configured within the CDP\nCDP-to-Iterable data transmission is operational and validated\nEvent ingestion, field mappings, and audience qualification behaviors are tested successfully\nDeduplication logic and field validation processes are functioning as intended\nError handling and retry behavior are documented where applicable\nCarnegie stakeholders confirm visibility of required data within Iterable\nMilestone 3 — QA, Documentation & Handoff\n\nThis milestone will be considered complete when:\n\nEnd-to-end testing is completed across all agreed workflows\nQA report is delivered with documented test cases, outcomes, known limitations, and resolutions\nData Flow Diagram is finalized and shared in editable format\nAll implementation documentation is delivered in a format accessible to internal Carnegie teams\nDocumentation should be written for technically capable marketing operations users and internal administrators who may maintain these systems after project completion\nOne recorded walkthrough session per workstream is completed and shared\nCarnegie confirms receipt of all deliverables and implementation artifacts\nChange Management & Scope Alignment\n\nAny material scope additions, architectural changes, or newly requested deliverables introduced after project kickoff may require timeline and pricing reassessment by mutual agreement.\n\nScope Assumptions & Out of Scope\n\nProject Assumptions\n\nThe following assumptions are reflected in the project scope and pricing expectations:\n\nCarnegie will provide access to required systems, environments, credentials, and technical documentation in a timely manner\nCarnegie 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.\nIterable access and necessary permissions will already be provisioned\nSelected contractor will receive direct access to relevant Iterable and CDP environments as needed for implementation\nThe proprietary CDP platform already exists and is operational; this engagement focuses on configuration, mapping, integration, and implementation rather than core platform engineering\nCarnegie will designate a primary point of contact for approvals, feedback, and implementation decisions\nMajor architectural decisions, if needed, will be finalized during the discovery phase at project start\n\nOut of Scope\n\nUnless otherwise agreed in writing, the following are not included in this engagement:\n\nNet-new feature development for the proprietary CDP platform\nCore frontend engineering or native website/app code instrumentation (actual SDK deployment or script installation on the website/app)\nCreative email design or copywriting\nOngoing campaign operations or audience management\nLong-term system maintenance, monitoring, or support after project completion\nRebuilding or redesigning Carnegie’s broader data taxonomy or analytics strategy\nThird-party platform licensing costs or external vendor fees\nAdditional integrations beyond the approved CDP Iterable implementation scope\n\nPost-Launch Support\n\nCandidates may optionally propose separate pricing for:\n\npost-launch monitoring\nongoing optimization support\nadditional template development\nfuture integration enhancements\nTimeline & Working Expectations\nEstimated Timeline\n\nThe project is expected to run approximately 8 weeks from kickoff through final handoff, assuming timely access to systems, approvals, and required documentation.\n\nCandidates should include:\n\nearliest available start date\nestimated timeline for each milestone\nany known scheduling constraints or timezone limitations\nWorking Style\n\nThis engagement will operate in an async-first environment with scheduled working sessions as needed.\n\nWe expect:\n\nproactive communication on blockers or risks\nclear documentation of implementation decisions\nregular progress updates throughout the engagement\nresponsiveness during agreed working hours\nMeetings & Collaboration\n\nThe anticipated collaboration structure includes:\n\none kickoff session\nrecurring status check-ins (typically weekly)\nimplementation review sessions as needed\nfinal walkthrough and handoff meetings\n\nMost collaboration will occur through written updates and shared documentation.\n\nDependencies & Delays\n\nCarnegie 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.\n\nWho We Are Looking For\n\nRequired\n\n2+ years of hands-on Iterable technical experience, specifically including catalog management and template development\nDemonstrated experience building multi-object catalog structures in Iterable — please be ready to show examples or describe past implementations\nProficiency with Iterable’s Handlebars templating syntax: loops, conditionals, catalog lookups, and null handling\nExperience integrating a CDP with Iterable via API, webhook, or native connector\nWorking knowledge of REST APIs, webhooks, and JSON data structures\nStrong written communication — you will produce documentation that non-developers will use\n\nPreferred\n\nExperience with behavioral event tracking and data taxonomy design\nFamiliarity with data deduplication and pipeline error-handling patterns\nPrior work with proprietary or custom-built CDPs (not just Segment or mParticle)\nComfort working across time zones with async-first communication\nWhat a Strong Candidate Looks Like\nHas built multi-catalog Iterable setups before and can describe the decisions they made\nKnows where catalog lookups commonly break and how to prevent it\nHas connected a data source to Iterable end-to-end, including testing and error handling\nAsks clarifying questions before building, not after\nDelivers documentation that someone else can actually use\n\nBudget & Payment\n\nThis engagement is fixed-price with milestone-based payments.\n\nMilestone 1: Catalogs built, validated, and Snippet Playbook delivered\nMilestone 2: CDP configured and CDP Iterable integration live and tested\nMilestone 3: Final QA sign-off, documentation complete, and handoff sessions delivered\n\nWe 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.","datePosted":"2026-09-28T11:07:13.640Z","dateModified":"2026-09-28T11:07:13.640Z","hiringOrganization":{"@type":"Organization","name":"Carnegie Dartlet","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Myrtle Point","addressRegion":"OR","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"2ec6f7f04dbf71235f18e8e6"},"url":"https://jobsearcher.com/jobs/2ec6f7f04dbf71235f18e8e6"}}