Senior Full-Stack / Data Engineer Needed to Build Internal “Mission Control” Dashboard
Orçamento: -
HOURLY / PART_TIME
⭐ 4.65 (39)
United States
web-programming
Qualificações preferidas
- Experiência: Intermédio
Title
Senior Full-Stack / Data Engineer Needed to Build Internal “Mission Control” Dashboard
About Us
We operate a portfolio of direct-response e-commerce and telehealth brands.
Each brand has its own operator, creative strategists, media buying infrastructure, financials, and testing systems.
We are building an internal Mission Control platform that allows leadership to understand the entire portfolio quickly and drill into individual brands when something needs attention.
This is not a basic analytics dashboard project.
We need someone who is strong in:
data architecture
API integrations
data normalization
attribution / analytics data
internal dashboard development
relational data modeling
modern frontend development
The goal is to combine information currently spread across systems such as:
Triple Whale
Meta Ads
Google Ads
Notion
Slack
Google Sheets
financial/accounting data
into one clean internal operating system.
What We Want to Build
The core goal is simple:
Leadership should be able to understand the state of the entire company in approximately 20 minutes and diagnose any major issue within 60 minutes.
There are two major components.
1. Mission Control Dashboard
A leadership-facing dashboard showing:
Financial Performance
Ad spend
New customer revenue
Recurring revenue
CAC
acquisition profit/loss
net cash
refunds and chargebacks
processing costs
prorated OPEX
MRR / recurring revenue acquired
projected cohort value
projected future profit from newly acquired customers
We operate multiple brands with different cohort economics, so cohort calculations must be modeled at the brand level and then aggregated.
Creative Intelligence
For each brand:
creative output
concepts launched
batches launched
formats tested
angles tested
winners
creative hit rate
spend generated by winning creatives
Creative Strategist leaderboard
what worked
what failed
major learnings
what the team plans to iterate on next
Media Buying
Ability to drill into:
Portfolio
→ Brand
→ Channel
→ Ad Account
→ Campaign
→ Ad / Creative
We want visibility into:
ad account spend
CAC
account health
backup accounts
creative concentration
winning ads
creative fatigue
channel performance
Operator Weekly Activity
A structured weekly changelog showing meaningful operational work such as:
new channel launched
agency onboarded
retention improvement
funnel improvement
pricing test
new product launch
infrastructure changes
major blockers
priorities for the following week
We are less interested in measuring superficial activity such as number of Slack messages and more interested in understanding what materially changed inside the business.
2. Brand Data Rooms
Our teams operate heavily inside Notion.
Each brand will have a structured Notion data room containing:
current strategy
creative database
concepts
batches
formats
angles
Creative Strategist ownership
winners
failed tests
weekly learnings
competitor intelligence
swipe/reference library
hypotheses
upcoming tests
historical weekly snapshots
Mission Control should pull structured qualitative information from these data rooms and combine it with quantitative performance data.
We do NOT want teams manually entering the same information into two systems.
Core Technical Challenge
The most important part of this project is not the frontend dashboard.
It is correctly linking information across different systems.
Example:
Notion may tell us:
Creative Concept #381
Brand: Hero
Creative Strategist: Person A
Format: Wife POV
Angle: X
Hypothesis: Y
That concept may produce:
8 variants
20 rendered assets
Those assets may then become:
50 Meta ads
across 3 ad accounts
Performance systems then contain:
spend
CAC
revenue
conversions
The system must correctly connect:
Concept → Variant → Asset → Platform Ad → Ad Account → Performance
so we can roll performance back up to:
concept
angle
format
Creative Strategist
operator
brand
This requires thoughtful data modeling and identity resolution.
Core Data Objects
We expect the system to eventually maintain canonical objects such as:
Brand
Person
Role Assignment
Creative Concept
Creative Variant
Asset
Platform Ad
Campaign
Ad Account
Channel
Performance Fact
Experiment
Initiative
Financial Day
Weekly Brand Snapshot
Activity Event
Metric Definition
Source Mapping / Alias
You should be comfortable designing this architecture rather than simply displaying API responses.
Weekly Brand Snapshot
One important system object will likely be a Weekly Brand Snapshot.
Example:
Hero — Week 36
Containing:
Financial
spend
revenue
net cash
acquisition economics
cohort value created
Creative
output
winners
formats
angles
CS performance
learnings
Media
account performance
channel movement
major changes
Operations
initiatives
changes
blockers
Forward Plan
priorities for the next week
These snapshots should power the Monday executive report and also create a historical memory of how each business evolved.
Desired Architecture
We are open to recommendations, but conceptually expect something similar to:
Source Systems
↓
Data ingestion / APIs / webhooks
↓
Central database / warehouse
↓
Canonical Avant data model
↓
Metric / business logic layer
↓
Internal API
↓
Mission Control frontend
The frontend should consume standardized objects and metrics.
We do NOT want critical business logic calculated independently inside random frontend components.
Frontend / UX
The product should feel like high-end internal operating software.
Visual inspiration:
Linear
Vercel
Datadog
Palantir-style operational tooling
We want:
dark-first interface
clean typography
high information density
excellent tables
fast filtering
drill-down navigation
minimal unnecessary animation
strong mobile experience
This dashboard will frequently be viewed from a phone.
It should not look like:
a generic admin template
crypto dashboard
Web3 UI
colorful SaaS landing page
overly large cards with excessive whitespace
Ideal Candidate
You are a strong fit if you have experience with several of the following:
TypeScript
React / Next.js
Node.js / Python backend systems
PostgreSQL
Supabase
Snowflake / BigQuery / similar warehouse systems
REST APIs
GraphQL
webhooks
ETL / ELT
data normalization
identity resolution / mapping
analytics systems
Meta Marketing API
Google Ads API
Notion API
Slack API
internal analytics dashboards
complex relational data products
Experience with e-commerce analytics or marketing attribution is a major plus.
Experience with Triple Whale is an even bigger plus.
What We Do NOT Want
Please do not apply if your primary experience is:
basic WordPress development
simple Shopify theme work
building template dashboards
no-code dashboards only
connecting APIs without designing the underlying data model
We need someone who can think about the architecture of the system.
Initial Engagement
We want to begin with a short discovery / architecture phase before building the full system.
The initial deliverables should include:
Review of our existing systems and available APIs
Source-of-truth matrix
Proposed data architecture
Canonical data model
ID / mapping strategy
Metric definition architecture
Integration feasibility assessment
V1 technical architecture
Recommended technology stack
V1 implementation roadmap
Clickable or functional prototype structure
Proof that one brand can be mapped end-to-end
For the proof of concept, we want to be able to take one real creative and trace:
Notion strategy / concept
→ Creative Strategist
→ creative asset
→ Meta ad
→ ad account
→ spend
→ performance
→ winner classification
→ weekly learning
If that data lineage works correctly, we can expand the system across the portfolio.
When Applying
Please answer the following questions:
1. Tell us about the most technically similar internal analytics/data platform you have built.
Do not only send your general portfolio.
2. How would you architect a system that needs to match creative records in Notion with ads running across multiple Meta ad accounts?
3. How would you handle situations where names or IDs are inconsistent between different source systems?
4. What database / warehouse architecture would you recommend for this project and why?
5. Have you worked directly with any of the following?
Meta Marketing API
Triple Whale
Notion API
Slack API
Google Ads API
Tell us specifically what you built.
6. What would you want to understand before writing production code?
7. Please include the phrase “Avant Mission Control” at the beginning of your application so we know you read the entire posting.
Important
We already have a detailed product brief, visual references, screen concepts, technical architecture notes, and engineering specification that will be shared with shortlisted candidates.
We are looking for someone who can challenge the architecture where necessary and help us build the underlying system correctly — not someone who simply follows screenshots.
There is significant ongoing work available if the initial build goes well.
Abrir na Upwork
AI proposal draft
Generate a short cover letter for this job. Edit before sending.
Sign in to generate an AI proposal draft.
Entrar