neofinancial · Marketing
Calgary, ABOnsite
Add to shortlist and compare later — open your saved-role workspace.
Pulled from the employer's career page. Always verify details at the source before applying.
Work locations
Role read
A quick read on what this posting appears to emphasize, based on the employer description and role fields.
Worth noticing
Lifecycle / email / CRM
“… for a different one. This is not a lifecycle role and it's not a traditional "Head …”
Retention and reactivation programs are core here.
SEO / content
“… web and app surfaces - Own the technical SEO and CRO infrastructure: landing page clusters, conversion …”
Organic traffic and editorial cadence are typical scope.
Website / CRO
“… attribution, A/B testing and experimentation, web and landing page infrastructure (CMS/headless), digital asset management (DAM), and …”
Experimentation cadence and on-site conversion live here.
Marketing ops / analytics
“… writing the scripts, connecting the APIs, building the attribution models, and setting up the experimentation frameworks …”
Systems ownership and reporting usually anchor this work.
Segment
“… MAP (Iterable, Braze, or SFMC) and CDPs like Segment - Strong SQL; you query data yourself …”
Clarify before applying
Experimentation ownership
Who owns experimentation and analytics implementation day-to-day?
Where this comes from
Every line below is grounded in the actual posting or in the title, role fields, and seniority tags. Snippets are quoted verbatim; the source tag tells you which part of the listing they came from.
Channels mentioned
… for a different one. This is not a lifecycle role and it's not a traditional "Head …
Why it matters here: Retention and reactivation programs are core here.
… web and app surfaces - Own the technical SEO and CRO infrastructure: landing page clusters, conversion …
Why it matters here: Organic traffic and editorial cadence are typical scope.
… attribution, A/B testing and experimentation, web and landing page infrastructure (CMS/headless), digital asset management (DAM), and …
Why it matters here: Experimentation cadence and on-site conversion live here.
Growth stack
Use this posting to prepare
Each subsection below is grounded in something the posting or the role fields actually say. Use them as prompts — not as finished resume copy.
Step 1
Terms in the actual posting. Use these only where they match your real experience.
neofinancial
neofinancial has 2 other live roles on this site right now across 2 different role categories. The list below shows what they’re hiring for alongside this posting.
Other live roles
Original employer description
Reproduced verbatim from the employer. Verify everything in this brief against the source text below.
Neo's customer base grew primarily through partnerships and co-branded products. The infrastructure that powered those relationships was built for that model. Now Neo is competing directly for consumer attention and retention, and the systems that personalize, automate, and measure that relationship need to be rebuilt for a different one.
This is not a lifecycle role and it's not a traditional "Head of" role where you manage vendors and sit in meetings. You're the one writing the scripts, connecting the APIs, building the attribution models, and setting up the experimentation frameworks that let the marketing team move fast. When something needs to get built, you build it.
There are two types of people who thrive here. Engineers who fell in love with the psychology of marketing and got tired of being three steps removed from the growth chart. And marketers who got frustrated waiting for dev tickets and started coding them themselves. If either describes you, keep reading.
You'll report to the CIO and work closely with marketing. No direct reports to start. The scope grows as Neo does, and so will the team.
The stack exists: Iterable, Intercom, FinAi. What isn't fully built is the connective layer: clean data pipelines, reliable triggers, attribution that actually works, A/B testing infrastructure, and the governance that keeps it from becoming a mess as the team scales.
The systems you'll own and build out span the full marketing infrastructure: marketing automation (MAP), customer data (CDP/CRM), analytics and multi-touch attribution, A/B testing and experimentation, web and landing page infrastructure (CMS/headless), digital asset management (DAM), and promotion and voucher management. Some of these exist. Some need to be built. All of them need to work together.
You'll be embedded in the core infrastructure team within the CIO org. Marketing is your internal customer. You're not downstream of marketing strategy. You're upstream of it.
Architect and own the end-to-end marketing technology stack: which tools we use, how they connect, and when to replace them
Write scripts, automations, and API integrations in Python or JavaScript to connect systems and move data between them
Own the data schema and governance for customer data across CDP and CRM platforms
Build and maintain multi-touch attribution models across devices and channels
Set up and embed A/B testing and experimentation frameworks across web and app surfaces
Own the technical SEO and CRO infrastructure: landing page clusters, conversion instrumentation, tagging governance
Implement and operate CMS/headless architecture so marketing can move without being blocked by core engineering
Build promotion and voucher management systems to support acquisition and growth programs
Deploy AI agents to automate repetitive MarTech workflows and accelerate the team's output
You can write code: scripts, automations, API integrations, glue code in Python or JavaScript
Expert-level on at least one MAP (Iterable, Braze, or SFMC) and CDPs like Segment
Strong SQL; you query data yourself and don't wait for someone to clean it first
You've built multi-touch attribution models, not just implemented analytics platforms
You've owned A/B testing infrastructure end to end, including the framework setup
You understand funnel economics: CAC, LTV, cohort retention — not as dashboards handed to you, but as the lens you use to make decisions
You're AI-native: deploying agents to automate workflows, not just prompting tools manually
You build things that last — documentation, QA, governance are part of the work, not overhead
You're comfortable operating across two functions without positional authority
This is not the right role if you want clean requirements, managed timelines, and a large team beneath you. The engineers and technical operators who thrive here find that environment frustrating.
A vendor manager. If your primary relationship with the martech stack is managing contracts and running status meetings, this role will feel wrong immediately.
A pure technologist who doesn't connect their work to business outcomes. The stack exists to move LTV, reduce churn, and make the customer relationship better. If someone else has to make that connection for you, that's a problem.
Someone who is primarily a people manager at this stage. The team will grow. Right now the job is to build something worth scaling.
No compromises on tooling: Cursor, Claude with unlimited tokens, CodeRabbit, GitHub Enterprise, Datadog, Snowflake, AWS. MacBook Pros. Standard issue, no justification required.
Competitive salaries beating the top tech companies in Canada. This role is eligible for STIP: cash bonuses tied to company milestones. All team members receive equity through stock options that are in the money from day one. Over four to five years, total comp at Neo outpaces what you'd make staying where you are.
Three consecutive years as Canada's fastest-growing company on the Deloitte Fast 50. $400M+ raised. Over one million customers.
Relocation support available for candidates moving to Calgary or Toronto.
Comprehensive health benefits, 21 days PTO, and parental top-up.
7+ years in MarTech, growth engineering, or a related technical discipline
Light programming skills in Python or JavaScript; strong SQL
Expert-level experience with marketing automation platforms (Iterable, Braze, or SFMC)
Experience with CDPs (Segment or equivalent) and multi-touch attribution modeling
API integration experience, including custom-built integrations
B2C or consumer fintech experience preferred
Based in Canada; we work in-person
Successful candidates will be required to complete a security screening including a criminal record check and credit check.
By continuing with your application, you agree to the Candidate Privacy Notice, which guides how we process your personal information for the purpose of your application.
… writing the scripts, connecting the APIs, building the attribution models, and setting up the experimentation frameworks …
Why it matters here: Systems ownership and reporting usually anchor this work.
Tools mentioned
… MAP (Iterable, Braze, or SFMC) and CDPs like Segment - Strong SQL; you query data yourself …
… - Expert-level on at least one MAP (Iterable, Braze …
… team. WHAT YOU'RE WALKING INTO The stack exists: Iterable …
… or SFMC) and CDPs like Segment - Strong SQL …
Why it matters here: Queries against the data warehouse show up in this listing's stack.
Success metrics mentioned
… the framework setup - You understand funnel economics: CAC …
… framework setup - You understand funnel economics: CAC, LTV …
Step 2
Worth raising before applying or in the first recruiter conversation.
01Who owns landing page testing, analytics implementation, and shipping decisions?
Why ask this: Triggered when CRO, experimentation, or website signals appear. Triggered by the posting’s mention of website / cro signals.
02Which systems and attribution models are considered the source of truth?
Why ask this: Triggered when marketing ops, attribution, or analytics tooling is named. Triggered by the posting’s mention of marketing ops / analytics tooling.
03How is the relationship between paid acquisition and lifecycle structured?
Why ask this: Triggered when both paid and lifecycle signals appear. Triggered by the posting’s mention of both paid and lifecycle signals.
04How are retention, activation, and reactivating-lapsed accounts measured?
Why ask this: Triggered when lifecycle or retention signals appear. Triggered by the posting’s mention of lifecycle / retention signals.
05What's the team's experimentation cadence and how are winning experiments shipped?
Why ask this: Triggered when A/B testing or experimentation language appears. Triggered by the posting’s mention of experimentation / a/b test signals.
Step 3
Each angle below starts from a real signal in the posting. The phrase “if this reflects your real experience” matters — don’t invent experience you don’t have.
Angle 01
Lifecycle / CRM angle
If this reflects your real background, emphasize: segmentation and lifecycle journeys, CRM tooling and journey orchestration, and retention, activation, and reactivation impact
Why we suggest this: posting mentions lifecycle / email / crm and retention.
Angle 02
Marketing ops angle
If this reflects your real background, emphasize: systems ownership (CRM, CDP, automation), data quality, attribution, and reporting, and stakeholder workflows and dashboards
Why we suggest this: posting mentions marketing ops / analytics.
Angle 03
Web / CRO angle
If this reflects your real background, emphasize: experimentation cadence and analytics, on-site conversion wins, and collaboration with design and product teams
Why we suggest this: posting mentions website / cro.
Keyword stuffing, fabricated bullets, or borrowed metrics tend to backfire in the first screen. Use these as a checklist, not a script.
Apply before August 22, 2026.