Braze Solutions Engineer (CRM)

About the Role

This is a build role, not a campaign calendar role. You will own the Braze layer of enterprise loyalty programmes: multi-step Canvases that call live APIs mid-flow, Liquid that assembles JSON payloads, catalog-driven mission and reward logic, and monthly reset cycles running across millions of member profiles.

Our programmes sit in front of real transactions. A malformed payload is not a reporting error; it is a member who did not get their reward. You will be the person who makes sure that does not happen, and the person who debugs it when it does.

"Your mission: ship Braze implementations that run in production without manual intervention, and document them well enough that the client's engineers can build against them."

Key Responsibilities

• Build multi-step Canvases combining webhooks, delays, messaging, entry filters, and re-entry logic.
• Write Liquid that constructs JSON request bodies for the Braze REST API, including capture blocks, conditional event arrays, and string handling.
• Model programme data in Braze catalogs and read it with composite lookup keys that resolve by segment, tier, and month.
• Manage nested custom attributes and object arrays, including incremental updates and scheduled reset logic.
• Integrate Braze with client and partner APIs through webhooks: auth, correlation IDs, error paths, and silent aborts when a step should not fire.
• Design throttling for downstream endpoints (per-member jitter, sequenced waits) so bulk canvas runs do not overwhelm a client's API
• Take builds from QA through UAT to production across workspaces, with documented canvas IDs, key permissions, and catalog sync.
• Build Content Cards and in-app messages that render directly off profile attributes.
• Own the data contract with the upstream CDP (mParticle, Segment, or similar) and the client app: user attributes, custom events, and event properties, and the distinction between them.
• Write and run test harnesses (curl, shell, or Postman) that trigger events and verify resulting profile state.
• Debug live issues: why an event did not fire, an attribute did not write, or a catalog lookup returned empty.
• Document what you build. Produce specs a client engineering team can implement against without a call.

What You'll Achieve

• Production canvases that complete their monthly cycle with no manual intervention.
• A documented data contract per client that survives handover and staff turnover.
• Secrets and API keys managed properly, never inline in webhook bodies.
• Fewer client escalations, because state is observable and every path is tested before release.

What You Bring

• 4 to 6 years in marketing automation, CRM engineering, or CDP implementation, with at least 2 years hands-on in Braze.
• Real Liquid fluency. You can build a conditional JSON payload in a webhook template and explain every filter in it.
• Braze depth across Canvas, webhooks, Catalogs, Connected Content, Content Cards, in-app messages, the REST API, and Currents.
• Comfortable with JSON, REST, auth headers, and HTTP status codes. You read API documentation unaided.
• Scripting for test and verification work: shell, Python, or JavaScript. SQL for checking data.
• CDP experience (mParticle, Segment, or similar), including identity resolution and event forwarding.
• Experience shipping through multi-environment deployment, not just building in one workspace.
• Ability to write technical documentation aimed at a client engineering audience.
• Bonus: Braze certification, loyalty or rewards programme experience, enterprise clients in QSR, retail, or telco

How We Assess

Expect a hands-on exercise. You will be given a catalog schema and an event payload, and asked to build the Liquid and the webhook body that turns one into the other. We are testing whether you can do the work, not whether you can describe it.