Checking access…
Checking access…
One accountable delivery organization of ~12 FTE led by the Engagement Director: a small US presence (5 FTE) for client leadership, combined architecture & engineering leadership, on-prem edge work and privacy compliance, and an offshore delivery centre (7 FTE) for engineering, operations and quality — deliberately time-zoned so overnight US hours are the offshore team's working day.
Hedge-fund deliveries land before US market open; the offshore day (IST) covers exactly the overnight window when daily pipelines run, giving natural 24×5 coverage without night shifts. Offshoring the engineering backend saves ≈ versus an all-US team while keeping every client-facing, on-prem and compliance-sensitive role in the US.
Every service has a named L1→L2→L3 path and a single accountable owner (escalation matrix); external SLAs to hedge funds are owned by the US Delivery Manager, not by individual engineers. Privacy & Security reports to the Engagement Director on a dotted line, keeping compliance independent of delivery pressure.
Blue roles sit in the US (client-facing / onsite-capable); teal roles run from the offshore delivery centre. The Cloud Data Architect & Engineering Lead is one combined role reporting to the Engagement Director, and Privacy & Security holds an independent dotted line to the Director. The Delivery Manager / TPM and Client Solutions Analyst (violet, dashed) are a addition, onboarded once daily delivery is live rather than at kickoff.
Nine role profiles. "Owns" is the accountability; "Talent profile" is what to hire for. The Delivery Manager and Client Solutions Analyst (violet) are hires, onboarded once daily delivery is live.
executive relationship with the client, commercial governance, escalation terminus for client-impacting incidents, quarterly roadmap. Direct reports: Delivery Manager, Architect & Engineering Lead, and (dotted line) Privacy & Security.
every external SLA, release calendar, hedge-fund onboarding, incident communications, weekly client operating cadence. The single accountable owner for on-time daily delivery.
one combined role reporting to the Engagement Director — design authority over the GCP stack, schema contracts with on-prem, capacity & cost engineering, and ownership of the Beam codebase, code review, DAG design and promotion of ad-hoc work into production. L2/L3 escalation point for all platform and pipeline issues.
the nightly edge job in the NWK lake — eligibility filtering, tokenization, extract contract — plus the STS agents and Interconnect handoff. First responder for "no file arrived" incidents.
VPC-SC perimeter, KMS key ceremonies and rotation, DLP policies, k-anonymity thresholds, privacy reviews for any extract widening, audit readiness. Reports on a dotted line directly to the Engagement Director so compliance judgements stay independent of delivery deadlines.
day-to-day hedge-fund relationships — data questions, methodology docs, feed-change notices, onboarding walkthroughs — during ET market hours.
pipeline features, POI/demographic enrichment logic, backfills, performance tuning, unit/pipeline tests, dead-letter triage. The senior-most engineer leads the IST standup and daily handoff to the US morning.
Terraform, CI/CD, monitoring/alerting, cost dashboards, L1 on-call for all services, incident bridge operation, DR drills.
daily QA gate before client delivery (the Telco QA report), Dataplex DQ rules, anomaly investigation (URL/visitor baselines), sign-off evidence for SLAs.
The rule: The time-zone gap is an asset — IST working hours cover the US overnight window when daily pipelines actually run.
| Role | Shore | Why it sits there | Flex option |
|---|---|---|---|
| US | Client exec relationship; contract accountability. | None | |
| US | Owns client SLAs and incident comms in ET hours; hedge funds expect a US voice. | None | |
| US · onsite | Physical/badged access to client NWK environment; touches pre-tokenized data — hard residency constraint. | None — this is the one truly immovable role | |
| US | CPNI/consumer-data regulatory posture; client audit interface. | Fractional (0.5 FTE) to control cost | |
| US | Live hedge-fund support during ET market hours. | Offshore second analyst can cover EMEA/APAC clients later | |
| US → flex | Onsite presence accelerates client workshops during build. | Move offshore in steady state — saves ≈ $13k/mo | |
| Offshore | Pure build/run work on GCP; no client contact, no raw-identifier access (tokens only). | Fully offshore from day one | |
| Offshore | IST day = US night → overnight pipeline runs get daytime attention, not a night shift. | Fully offshore; weekend rota | |
| Offshore | QA gate completes before US market open thanks to time-zone lead. | Fully offshore |
The team runs two clocks: an (24×5 follow-the-sun, weekend on-call) and a (everything client-facing keyed to US market open).
| Service / deliverable | SLA target | Measured by | Support window |
|---|---|---|---|
| (per hedge fund) | Delivered by , 99.5% on-time monthly | Delivery timestamp vs calendar; QA sign-off attached | 24×5 + weekend on-call |
| Zero known-bad deliveries; restatement notice < 4 business hrs | QA gate pass rate; restatement log | QA gate every run | |
| (missed/late/corrupt feed) | Ack , mitigation path 2 hrs, client comms 30 min | PagerDuty-equivalent + incident log | 24×7 |
| (pipeline retry, DQ warning) | Ack 1 hr, resolve/downgrade same day | Monitoring alerts | 24×5 |
| First response 4 business hrs (ET) | Ticket queue | ET business hours | |
| (internal/client) | Triage 1 business day; delivery per agreed scope | Request backlog | IST + ET business hours |
| Standard onboarding ≤ 10 business days | Onboarding checklist | Scheduled |
L1 acknowledges and triages, L2 fixes, L3 redesigns, and the Accountable owner communicates and answers for the SLA. Escalate on time-in-state, not on judgement calls.
| Service | L1 (ack / triage) | L2 (resolve) | L3 (engineering) | Accountable |
|---|---|---|---|---|
| P1 path | SRE on-call (15 min) | Senior Data Engineer | Architect & Eng Lead | |
| (edge job, STS, Interconnect) | SRE on-call | On-Prem Edge Engineer | Architect & Eng Lead + operator network team | |
| SRE on-call | Data Engineers | Architect & Eng Lead | ||
| SRE on-call | SRE / DevOps | Architect & Eng Lead | ||
| QA / DQ Analysts | Data Engineers | Architect & Eng Lead | ||
| always P1 | SRE on-call → immediate page | Privacy & Security Eng | Architect & Eng Lead + operator security team | |
| P3 | Client Solutions Analyst | Delivery Manager | Architect & Eng Lead (methodology) | |
| Delivery Manager | Engagement Director | — |
Fully-loaded monthly costs (salary + benefits + overhead + vendor margin). Adjust headcount and shore strategy; US and offshore rates shown per expertise. The Engagement Director is billed separately from the delivery team and isn't part of this estimate (see the org chart and location strategy for the full team). Rows follow the same order as the Location strategy table.
| Expertise | US rate /mo | Offshore rate /mo | Recommended shore |
|---|---|---|---|
| Delivery Manager / TPM | $18,000 | $7,500 | US |
| On-Prem Edge Engineer | $19,000 | — | US onsite |
| Privacy & Security Engineer | $20,000 (0.5 FTE billed) | — | US |
| Client Solutions Analyst | $14,000 | $5,000 | US |
| Cloud Data Architect & Engineering Lead | $24,000 | $11,000 | US → flex |
| Data Engineer | $15,000 | $5,500 | Offshore |
| SRE / DevOps Engineer | $16,000 | $6,000 | Offshore |
| Data QA / DQ Analyst | $11,000 | $4,000 | Offshore |