Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Marketing Engineer
Review the role, location requirements, compensation details, and application process before deciding whether this opportunity fits your next career move.
- Salary
- USD 142,400–197,800 / yr
- Department
- Software Engineering
- Employment
- Full Time
- Experience
- Open level
- Published
- Apply before
- 3 Dec 2026
- Listing views
- 31
- Application actions
- 1
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
The role, at a glance.
Mercury is seeking a hands-on Marketing Engineer to build, operate, and improve the integrations, tracking infrastructure, and measurement systems used by Growth Marketing. The role combines software engineering with marketing operations, including APIs, webhooks, SQL validation, browser- and server-side conversion tracking, GA4, and audience activation. The engineer will independently own reliability, monitoring, incident recovery, documentation, and a roadmap for marketing-platform improvements. Close collaboration with Performance Marketing, Lifecycle, SEO, Data, Web, Product Engineering, and Growth Engineering is central to translating business goals into durable technical solutions.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
4/5Autonomy Level
5/5Communication Load
5/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would first define the expected conversion event, attribution window, identity rules, and reporting time zone for both platforms. Then I would trace representative events from the website or server payload through tagging, consent handling, event collection, transformation, and destination delivery, checking for duplicate identifiers, blocked requests, delayed processing, and mismatched event definitions. I would document the root cause, implement a monitored fix, and validate the result against an agreed reconciliation threshold.
I would clarify the audience definition, permitted attributes, consent requirements, destination schema, refresh frequency, and failure behavior with stakeholders. I would implement authenticated API or webhook delivery with idempotency controls, retries, rate-limit handling, logging, and alerting, then validate record counts and sample payloads with SQL. After deployment, I would provide ownership documentation and monitoring so changes in source data or destination requirements are detected quickly.
The two implementations need a shared event taxonomy and stable event identifiers so duplicate conversions can be deduplicated. I would account for consent signals, user identity, cookie limitations, payload completeness, hashing requirements, and attribution-platform specifications. I would also monitor match quality, event delivery rates, duplicate rates, and discrepancies against first-party source data.
I would evaluate each request by business impact, urgency, dependency risk, data-quality implications, effort, and whether it addresses a recurring reliability issue. I would make tradeoffs visible through a shared roadmap, identify work requiring Data or Engineering support, and reserve capacity for production incidents and preventive maintenance. This approach keeps high-value launches moving without allowing fragile systems or technical debt to accumulate.
I would query the approved source tables to confirm the audience criteria, expected population, freshness, consent status, and required identifiers. I would compare those results with destination delivery logs or export counts, investigate dropped or duplicated records, and segment discrepancies by source, timestamp, and failure reason. I would then create a repeatable validation query or dashboard so the team can detect regressions after future changes.
About this role.
Good marketing depends on systems that work: conversion signals that arrive accurately, audiences that stay current, and tools that make new ideas easier to try.
We’re hiring a Marketing Engineer to build and maintain those systems at Mercury. You’ll work directly with marketers to understand what they need, turn those needs into working integrations and tools, and keep what you build reliable after launch.
You’ll report to our Head of Growth Marketing as a hands-on individual contributor, partnering closely with Performance Marketing, Lifecycle, SEO, Data, and Engineering.
You’ll own the connections between our marketing platforms, including implementation, testing, deployment, monitoring, and maintenance. Data owns the shared customer-data foundation, warehouse pipelines and transformations, attribution methodology, and analytical models. Growth Engineering builds and maintains our GTM orchestration layer. You’ll work with both teams to make those systems useful in marketing.
Here are some of the things you’ll do:
- Build and operate marketing integrations. Connect customer engagement, advertising, analytics, and other marketing platforms using APIs, webhooks, integration tools, and custom code. Test and deploy changes using Mercury’s shared development tools and review practices, and own monitoring and recovery when something breaks.
- Own marketing tracking and conversion delivery. Maintain campaign tagging, cross-domain measurement, and browser- and server-side tracking. Investigate missing events, duplicate conversions, and discrepancies between platforms. Partner with Web and Product Engineering when fixes require changes to shared website or application code.
- Make customer data usable in marketing. Connect approved attributes, audiences, and conversion signals to marketing platforms using tools such as Segment and Polytomic. Use SQL to validate results and trace problems across systems. Work with Data on source-data requirements and the return of marketing activity to shared datasets.
- Maintain measurement and experimentation tools. Own GA4 configuration, including events, custom dimensions, platform connections, and reporting setup. Implement measurement definitions agreed with Data across tools such as GA4 and Rockerbox. Support website forms, experimentation tools, and the technical setup for SEO and AI-search experiments.
- Set priorities and improve reliability. Own the roadmap for marketing integrations, tracking, and platform improvements with Growth Marketing leaders. Address recurring failures, manage platform configuration and access, document how systems work, and build reusable tools that help marketers launch and learn faster.
We’re looking for someone with:
- A track record of independently building and maintaining software or integrations for marketing teams. You can write, test, debug, deploy, and maintain code — and explain the choices you made.
- Hands-on experience with GA4, website event tracking, and advertising conversion integrations, including browser- and server-side implementations. You understand how identity, consent, and data quality affect measurement.
- Practical SQL skills. You can inspect source data, validate an audience or conversion feed, and trace a discrepancy from the original event to its destination.
- Experience connecting customer engagement, advertising, or marketing automation platforms through APIs and webhooks. You know how to handle authentication, failed requests, duplicate events, and changing platform requirements.
- Clear communication and sound judgment. You can turn a marketer’s goal into technical requirements, prioritize competing requests, and work with Data and Engineering to resolve dependencies and ownership questions.
Our current stack includes Snowflake, Segment, Polytomic, Customer.io, Salesforce, Dato, GA4, Rockerbox, and major search and social advertising platforms. Experience with comparable systems is valuable; we don’t expect you to have used every tool.
*Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC.
Mercury values diversity & belonging and is proud to be an Equal Employment Opportunity employer. All individuals seeking employment at Mercury are considered without regard to race, color, religion, national origin, age, sex, marital status, ancestry, physical or mental disability, veteran status, gender identity, sexual orientation, or any other legally protected characteristic. We are committed to providing reasonable accommodations throughout the recruitment process for applicants with disabilities or special needs. If you need assistance, or an accommodation, please let your recruiter know once you are contacted about a role.
#LI-RQ1
Total Rewards
The total rewards package at Mercury includes base salary, equity (stock options/RSUs), and benefits.
Our salary and equity ranges are highly competitive within the SaaS and fintech industry and are updated regularly using the most reliable compensation survey data for our industry. New hire offers are made based on a candidate’s experience, expertise, geographic location, and internal pay equity relative to peers.
Our target new hire base salary ranges for this role are the following:
US employees in New York City, Los Angeles, Seattle, or the San Francisco Bay Area:
$158,200—$197,800 USD
US employees outside of New York City, Los Angeles, Seattle, or the San Francisco Bay Area:
$142,400—$178,000 USD
Canadian employees (any location):
$149,500—$186,900 CAD
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
