Practice 02 · Techology, Inc.
A dashboard is only as good as the system underneath it.
The position002
I build and repair the entire path: authenticated extraction, durable raw data, orchestration, transformations, semantic contracts, serving layers, and the visual surface where someone finally makes a decision.
Representative systemsBuilt + designed
Connector patterns that use browser sessions only where login and MFA require them, then move to direct authenticated HTTP, hardened parsing, original-response preservation, immutable publication, and fail-closed drift detection.
DLT · Browserbase · HTTP · S3 · Schema validation · IdempotencyDagster and dbt systems that coordinate incremental syncs, partitions, backfills, tests, source-scoped schedules, and safe production canaries across warehouses and serving layers. Exceptions stay visible and recoverable instead of becoming manual cleanup.
Dagster · dbt · ECS · Redshift · BigQuery · Snowflake · AuroraSemantic and reporting layers that preserve grain, confidence, and financial boundaries; reconcile conflicting systems; and publish through Cerebro, Tableau, Looker, embedded dashboards, and purpose-built analytical tools.
Semantic layers · Reconciliation · Metrics · Tableau · Looker · CerebroOperating standardsNon-negotiable
Original inputs and immutable artifacts remain available when the model or parser changes.
Orders, receipts, consumers, accounts, and events are never blended into a convenient but misleading total.
Release, orchestration, serving, and the final rendered surface are checked as one delivery path.
Continue exploringPractice 03
Operational software↗