Senior Product Engineer

Senior Product Engineer, Marketing Analytics Dashboard

Location: Remote (US). Hybrid from Detroit or Nashville preferred.

About the Role

A growing martech company is hiring its first product engineer to own its cross-channel marketing analytics Dashboard. You are the head of this product's engineering.

You will be the first dedicated engineer on the Dashboard, writing code every week and owning the architecture, the data pipeline, the code review bar and the quality of what ships. Day to day, that means adding channel integrations, building new features, working through bug and data-integrity reports from clients, and hardening the platform. You also own production infrastructure until that seat is filled.

You start as a team of one by design. As milestones are hit, you earn the budget to hire, define the roles, run the hiring and lead the people you bring in.

The Dashboard exists and clients use it. It was built quickly with heavy use of AI coding tools, and there is bloat to cut and real refactoring ahead. Deciding what to keep, what to rewrite and in what order, while clients keep using it, is a large part of the first year.

This is a data engineering and marketing analytics role as much as a product engineering one. The person who succeeds here knows what a media buyer needs on Monday morning, why numbers from three platforms never add up on their own, and how to build a system where they do.

What You'll Build

• Channel integrations: OAuth connection for Meta, Google and Amazon DSP advertiser accounts with daily updates and no manual exports. You own the connection flow, token lifecycle and recovery when a platform changes its API or restates numbers. You also own the platform approvals (Meta App Review, Google Ads API developer token, Amazon Advertising API onboarding) and keep each in good standing. New channels slot into the same framework.
• Syncs and rate limits: scheduling, batching, backoff and retries so hundreds of accounts refresh daily without tripping each platform's limits, and new accounts backfill history without starving everyone else.
• Data pipeline: daily ETL that normalizes field names, currencies, attribution windows and conversion definitions into one model, stored for fast reads. Every number traces back to its source.
• Taxonomy and cross-channel merge: a naming convention the media team follows, automatic matching where it holds, a manual mapping layer where it does not, and clear surfacing of what did not match.
• Dashboard and charts: charts by time, channel, initiative and campaign, filters that work together across every chart, metric and dimension controls, rate metrics computed correctly at every grouping, and export of any view. A chart style guide and component library make a new chart a configuration change, not a design project.
• Per-client customization: custom conversions and KPIs, chosen charts and dashboard templates by business type, held as configuration without forking the code.
• Speed and security: dashboards that open in under two seconds on a year of data through pre-aggregation, caching and deliberate storage choices. Encrypted, tenant-isolated client data, least-privilege token handling and audit logging, with a clear path to SOC 2.
• AI features: the foundation for users to ask for a chart in plain language and get one built on the same data model and style guide.

What You'll Do

• Work out what the product needs, decide what to build and in what order, then build it
• Design the sync strategy and daily ETL, including backfills, restatement handling and alerting
• Define the unified data model and campaign taxonomy, and work with the media team on the naming convention that feeds it
• Guarantee data integrity through reconciliation against the platforms, lineage from every chart to its source, and tests that catch a wrong number first
• Own the database on MySQL and the infrastructure on AWS and Railway, or make the case for something better
• Lead the cleanup: remove bloat, consolidate duplicated logic and refactor area by area without disrupting clients
• Review all Dashboard code and set the standard for how the team builds, tests and deploys
• Build the team as milestones are met: define roles, run hiring and onboarding, and lead them

Tech Stack

• Node.js, TypeScript, React
• MySQL
• AWS and Railway
• Meta Marketing API, Google Ads API, Amazon DSP reporting

What You'll Bring

• 5+ years shipping production data and analytics software, with experience mentoring or leading other engineers
• Production experience with Node.js and React, ideally in TypeScript
• Daily, hands-on use of AI coding tools such as Cursor and Claude, and the judgment to review and correct what they produce
• A good working understanding of the Meta Marketing API, Google Ads API and Amazon DSP reporting, including how each meters access, and experience taking an integration through platform approval
• ETL experience across sources with different schemas and attribution windows, and sync systems that respect rate limits across many accounts
• Strong SQL and relational modeling, and experience designing taxonomies or working with media teams on data hygiene
• Strong frontend charting experience (Recharts, ECharts, D3, Highcharts or similar) and a clear sense of what marketers look at, ignore and trust
• Performance engineering on data-heavy UIs, and clear opinions on when a warehouse or columnar store is the right call
• AWS in production, OAuth and token management, and experience with SOC 2 or similar
• A habit of distrusting numbers until they reconcile
• A track record of taking over fast-built codebases and making them clean and maintainable while customers keep using them
• A desire to keep writing code as a lead, not move into pure management

Nice to Have

• Time at a marketing analytics or dashboarding company, or on the reporting team at an agency or ad platform
• Experience with additional channels: TikTok, LinkedIn, Pinterest, other programmatic DSPs, Search Console, GA4
• dbt, Airflow, Dagster or similar orchestration tools
• Natural language to chart or natural language to SQL systems

Why Join

• Join early, before the architecture is set, with real ownership of what you build
• Clear priorities: the Dashboard is the product, and this role owns it
• Technical cleanup is a funded, scheduled part of the work, not something squeezed in

Details

• Full-time
• Remote (US). Hybrid from Detroit or Nashville preferred.
• $155,000 to $185,000 base