CRM Platform Engineer (Customer.io)

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have "Job Summary" which is a brief description; we could put that under About the role? Or we could create a section "About the role" with that summary. The instruction says do NOT repeat the job title as a heading. So we can have About the role heading with the job summary paragraph. Then Responsibilities: the "What you’ll be doing primarily" bullet list (actually paragraphs with bold headings). We need to extract duties as list items. The content includes many paragraphs each starting with a bold heading like "Own the CRM data foundation", then description. We can turn each bold heading into a list item? Or we could keep prose? The instruction: Use

• for any list of duties/requirements/benefits, and

  for prose. So we need to decide if duties are presented as a list. The original has headings and paragraphs; we can convert each heading+description into a list item (

• ) containing the description (maybe with

  inside?). Simpler: make each duty as

• with the text (including the heading). We'll preserve all substantive information. Requirements: The "Required Qualifications And Skills" section includes bullet list of qualifications. We'll make a
  • list. Benefits: There's "What We Offer" bullet list and "Our Benefits" bullet list. We'll combine into Benefits section. Pay: Salary line: "Salary: $150K + Bonus". Also there is "Bonus if you have Experience..." but that's part of qualifications? Actually after Salary line: "Salary: $150K + Bonus, Benefits Bonus if you have Experience in fintech..." Wait reading: "Salary: $150K + Bonus, Benefits Bonus if you have Experience in fintech, financial services or another regulated industry." Actually the text: "Salary: $150K + Bonus, Benefits Bonus if you have Experience in fintech, financial services or another regulated industry." That seems misplaced; maybe it's part of "Bonus if you have Experience..." under "Bonus if you have Experience..." Actually after Salary line there is a sentence: "Bonus if you have Experience in fintech, financial services or another regulated industry." That seems like a qualification bonus. But we already have qualifications list includes "Bonus if you have Experience in fintech, financial services or another regulated industry." Actually that line appears under "Bonus if you have Experience..." after Salary line. Let's scroll: In the text: "Salary: $150K + Bonus, Benefits Bonus if you have Experience in fintech, financial services or another regulated industry.Familiarity with cryptocurrencies or other digital assets, as they are core to our business.Experience running CRM across multiple products or brands from a single platform.Experience with Customer Data Platforms and reverse ETL tooling.Experience with Snowflake, dbt or similar modern data stack tooling.Practical experience applying AI tooling to marketing or CRM operations.Deep email deliverability experience, including reputation management and remediation.Experience integrating mobile SDKs for push and in-app messaging.Community talks, certifications, and/or blog posts on your interests and research.Open source project contributions of any kind. Importantly, if you are looking for a senior role with us, you will have achieved many of the things above while also providing mentorship to others, and have engaged in public speaking opportunities." So after Salary line, there is a run-on sentence: "Bonus if you have Experience in fintech, financial services or another regulated industry." Actually it's likely part of qualifications: "Bonus if you have Experience in fintech..." So we should treat that as a qualification item (maybe under Required Qualifications And Skills). The "Benefits" mention after Salary is confusing; but we have separate Benefits sections. Thus Pay section: just salary: $150K + Bonus. We should not include Schedule (not mentioned). No need. We must remove boilerplate: EEOC, legal, etc. Also remove navigation, cookie, etc. Not present. We must not include duplicated lines. Now produce HTML fragment:

    About the role

    Uphold is looking for a CRM Platform Engineer (Customer.io)/CRM MarTech Manager to take full ownership of Customer.io, the platform we use to communicate with millions of customers across email, push, in-app and SMS. This is a technical role, not a campaign execution role. You will own the data model, the integrations, the workflow architecture and the operating standards that make customer communication possible at scale. You will sit between Engineering, Data, Marketing and Commercial, and you will be the person who decides how the platform is built and how it is used. The scope is wide. Uphold runs multiple products and regions on shared infrastructure, in a highly regulated industry, with a large volume of personal data. Getting this right means designing for reuse, for auditability and for safety, not just for the next campaign.

    Then Responsibilities:

    Responsibilities

    • Own the CRM data foundation: Own the data layer inside Customer.io: Define and maintain the objects, attributes, events and identifiers that power the platform. Segmentation quality is a direct function of data quality, so this is the core of the role. Work hand in hand with Engineering and Data: Design and maintain the pipelines that feed Customer.io. Agree on schemas, event contracts and data freshness requirements, and hold the line when they drift. Guarantee freshness and correctness: Put monitoring and alerting in place so that stale, missing or malformed data is caught before it reaches a customer, not after.
    • Architect workflows that last: Apply systems thinking to campaign design: Build journeys, triggers and segments that are modular, reusable and understandable by someone who did not build them. Prevent workflow sprawl: Establish naming conventions, versioning, documentation and deprecation routines. Retire what is no longer used. Treat the CRM workspace as a codebase, not a folder of one off campaigns. Design for scale: Anticipate volume, message throughput, rate limits and platform constraints before they become production issues.
    • Operate with a multi product and multi brand mindset: Serve several products and brands from one platform: Design workspace structure, data models and templates so that Wallet, Topper, Enterprise and future brands share what should be shared and separate what must be separated. Balance consistency with autonomy: Give each product team room to move without letting the overall architecture fragment. Manage cross brand message pressure: Own global frequency capping, priority rules and suppression logic so customers receive a coherent experience across products.
    • Translate business objectives into CRM capability: Partner with Marketing and Commercial: Understand what the business is trying to achieve, then decide what the platform needs to look like to support it. Push back when a request is better solved a different way. Turn requirements into architecture: Convert commercial goals into concrete data, segmentation and workflow design, with clear trade offs and sequencing. Own the roadmap for the platform: Maintain a prioritised view of platform work and communicate it to stakeholders.
    • Enable marketing autonomy: Build for self sufficiency: Create templates, reusable components, documented segments and clear guardrails so marketing teams can launch routine work without engineering support. Train and document: Run enablement sessions and maintain practical documentation. Success is measured by how much the teams can do without you, not by how much depends on you. Set the guardrails: Define what marketers can change freely, what needs review, and what is locked. Make the safe path the easy path.
    • Drive automation and AI adoption: Identify automation opportunities: Look for manual, repetitive or error prone steps across the CRM operation and remove them. Apply AI where it earns its place: Evaluate and implement AI for content generation, send time and channel optimisation, segmentation, anomaly detection and QA. Be pragmatic about where it adds value and where it does not. Keep improving the operation: Measure the cycle time from business request to live campaign, and work it down.
    • Security and data protection first: Treat personal data with care: This is a PII heavy environment. Apply data minimisation, least privilege access, retention rules and clear handling standards by default. Own consent and preferences: Maintain the consent, opt out and preference model, and make sure it is respected consistently across every channel and every brand. Support compliance and audit: Work with Security, Privacy, Compliance and Legal on GDPR, access reviews, vendor risk and audit evidence. Be able to explain who received what, when, and on what basis. Respect jurisdictional rules: Uphold operates under multiple regulatory regimes. Build the targeting and suppression logic that keeps communications compliant by market, including mandatory risk warnings and geographic restrictions on financial promotions.
    • Protect quality at the customer touchpoint: Be detail and quality obsessed: Every message is a direct customer touchpoint and a reflection of the brand. Own the QA process, including test sends, seed lists, rendering checks, link validation and pre send review. Own deliverability: Manage domain and IP reputation, authentication (SPF, DKIM, DMARC), warm up, list hygiene, bounce and complaint rates. Deliverability is an engineering problem, and it belongs to this role. Run change management: Define approval gates, no send windows, rollback procedures and incident response for communication failures. Measure and improve: Own experimentation design, holdout groups and performance reporting, in partnership with the Data team.
    Then Requirements (or Qualifications and Skills). We'll use

    Requirements

    maybe.

    Requirements

    • BS or advanced degree in Computer Science, Software Engineering or equivalent practical experience.
    • 4+ years of experience in the field, with meaningful time spent owning a marketing automation, CRM or customer engagement platform in a technical capacity.
    • Hands-on experience with Customer.io, or a comparable platform such as Braze, Iterable, Klaviyo or Salesforce Marketing Cloud, at an architecture and administration level rather than campaign execution only.
    • Strong SQL and comfort working with data warehouses and modern data pipelines.
    • Solid understanding of REST APIs, webhooks, event driven data models and identity resolution.
    • Working knowledge of templating languages such as Liquid, plus HTML, CSS and JavaScript for email and in-app content.
    • Demonstrated systems thinking: the ability to design maintainable, scalable structures rather than solve each request in isolation.
    • Experience working with personal data under a security and privacy first approach, including consent management and GDPR.
    • Ability to explain complex technical concepts clearly to both technical and non technical audiences.
    • Comfortable working across functions with Marketing, Commercial, Product,