Primary platform
AWS
Serverless data lakes, query-in-place analytics and event-driven processing.
- S3
- Glue
- Athena
- Lambda
- RDS
- QuickSight
- CloudWatch
Cloud Engineer · Derivatives Trader · Quant Systems
I build cloud data platforms on AWS, Snowflake, Databricks and Azure, and I trade derivatives with quant systems I design myself across futures and forex. The same engineering discipline runs both: automated, tested and monitored.
AWS
Snowflake
Databricks
Azure
CME Futures
Forex
About
I'm a cloud engineer with more than six years in cloud data architecture, ETL development and database administration. At Imperium I architect Snowflake environments on AWS and build the pipelines that feed the business.
I'm also a funded derivatives trader with over 15 years in the markets. I design and run quant systems across futures and forex derivatives, from Nasdaq 100 futures on CME Globex to USD currency pairs: research, backtesting, execution and live monitoring.
Both disciplines reward the same thing: fast, reliable, well-monitored systems. I love optimizing them.
Cloud expertise
Security, cost control and monitoring are designed in from the start, not added later.
Primary platform
Serverless data lakes, query-in-place analytics and event-driven processing.
4+ years
Administration, RBAC design, continuous ingestion and automated tasks.
3+ years
Spark development and tuning, lakehouse patterns at scale.
Multi-cloud
Orchestrated pipelines on Azure and analytics on BigQuery.
Apache Airflow, Spark, Python and Linux scripting, multi-source integration.
Parquet, SQL and NoSQL databases, lakehouse and serverless architectures.
On-call rotations, incident response, performance analysis and SDLC documentation.
Quant systems & derivatives
15+ years trading derivatives with funded and institutional capital. I build the full quant stack myself, from data pipelines and backtests to execution and live monitoring.
Futures
Systematic futures strategies on CME Globex, including a low-drawdown system with a 2.5 Sharpe ratio and a custom block trading system on Quantower.
Forex
Algorithmic systems for USD forex pairs, researched and backtested on clean historical data before going live.
Infrastructure
Where the cloud work meets the trading: market data pipelines, backtesting databases, signal delivery and real-time performance monitoring.
Projects & portfolio
Open-source repositories and production case studies. Filter by platform and open any card for details.
A scalable data lake that catalogs files with Glue, stores them in S3 and serves analytics with Athena.
Analysis and performance work on transaction data stored in Snowflake.
SQL and Python for analysis, visualization and dashboards across banking, real estate and salary data.
High-performance data pipelines, backtests and quantitative analysis tools for market data.
Architected and maintain Imperium's Snowflake analytics environment with role-based access and automated ingestion.
Pipelines that integrate several source systems at Imperium, built with an automation-first approach.
Low-drawdown systematic strategy for Nasdaq 100 futures, traded with institutional capital on CME Globex.
Algorithmic strategies for USD currency pairs, built on the same research and backtesting pipeline as the futures work.
AG Wolf Capital's infrastructure for generating, validating and delivering algorithmic signals to institutional and retail clients.
Experience
Feb 2023 – PresentRemote
Imperium · Tampa, FL
Aug 2012 – PresentRemote
AG Wolf Capital · San Francisco, CA
Apr 2019 – Apr 2023Remote
FC Stone-League Trading · Chicago, IL
Blog
Practical writing on cloud data engineering, warehouse tuning and where markets meet data.
Contact
Open to cloud engineering roles, consulting, and quant and trading-technology projects across futures and forex. Send a note and I'll reply within a day or two.
A data lake doesn't need a cluster running around the clock. With S3 for storage, Glue for cataloging and transformation, and Athena for SQL, you pay for what you use and scale without managing servers.
I keep a landing/ prefix for raw files exactly as they arrive and a curated/ prefix for cleaned, typed Parquet. Raw data stays replayable, and analysts only touch curated.
s3://lake/curated/orders/year=2026/month=10/day=18/part-0001.parquet
Athena bills by data scanned. Partitioning by date and storing columnar Parquet routinely cuts scanned bytes by an order of magnitude.
Crawlers keep table definitions in sync with S3, and PySpark Glue jobs handle the raw-to-curated transform.
CloudWatch alarms on job failures and duration route to on-call, so a broken pipeline is caught before anyone opens a dashboard.
Granting privileges straight to users works for five people and becomes unmanageable at fifty. The fix is a two-layer role hierarchy.
GRANT ROLE sales_read TO ROLE analyst; GRANT ROLE analyst TO USER jdoe;
New schema? Create its access roles once and grant them to the right functional roles. Onboarding becomes a single grant.
After more than fifteen years trading derivatives, I've found the habits that keep a trading system alive are the same ones that keep a data platform alive.
Both disciplines reward the same thing: systems that are boring to operate.