001
Data Pipelines
Pipelines and warehousing with Python, Dagster and AWS — reliable data for product teams.
Building systems that turn energy, data, and automation into reliable power
001
Pipelines and warehousing with Python, Dagster and AWS — reliable data for product teams.
002
Utility-scale software for inspections, construction monitoring, and O&M reporting. Construction deadlines and compliance.
003
Architecture for messy domains - one deploy lane, feature flags, systems teams can ship.
004
Hands-on with modern models - cloud, rental and local LLMs, agentic workflows for software operations.
005
Ownership and accountability for the technology stack, from architecture to deployment.
006
Cut spending on cloud and eliminated thousands of hours of manual effort with smarter tooling.
Know-How
20
Products and operational software for energy and data teams.
Cloud Impact
3500
Annual cloud cost cut through smarter platform choices.
Ops Efficiency
1500
Manual effort removed from reporting and coordination.
Notes on product engineering, AI workflows, data platforms, and the changing shape of software in energy — practical takes, not hype.
Read the whitepaper regarding the impact of human attention on AI systems.
Small Language Models are revolutionizing the way we interact with AI.
An article I wrote for a uk publication.
I'm a product engineer - I work where software, data, and operations meet, turning messy solar and grid workflows into systems that run reliably. Less ops drag, more automation, clearer decisions for the people keeping power on.
Building something in energy, data, or automation? Reach out directly! I'm happy to explore where better systems could save your team real time.
Python, Dagster and AWS — reliable data for product teams.
I design and ship pipelines and warehousing that keep product teams moving — scheduled jobs, clear ownership, and data you can trust without babysitting the stack. From ingestion through transformation to delivery, the goal is boring reliability: fewer fire drills, faster answers, and systems ops can actually run.
Utility-scale software for inspections, construction monitoring, and O&M.
Software for the people keeping sites on schedule — drone and field inspections, construction progress, and O&M reporting that fits how asset teams actually work. Less spreadsheet chase, clearer compliance trails, and fewer surprises when deadlines land.
The architecture for efficient domains — one deploy lane, systems teams can ship.
I shape platforms where the domain is messy and the release path has to stay simple — one deploy lane, feature flags, and boundaries teams can reason about. Less tribal knowledge, more systems that survive handoffs and keep shipping under pressure.
Cloud, rental and local LLMs — agentic workflows for ops software.
Hands-on with modern models where they earn their keep — cloud APIs, rented capacity, and local LLMs wired into real operational workflows, not slide-deck demos. Agentic loops, review gates, and tooling that cut grunt work without inventing new risk.
Accountability for the stack — from architecture to deployment.
Ownership means someone is answerable for the stack and architecture choices, the delivery path, and the operational reality after launch. I take that end-to-end accountability so product and ops are not left guessing who owns the next decision. All of this while at the same time keeping the tech department with a single and simple roadmap and multiple responsible heads
Cut cloud spend and remove hours of manual effort with smarter tooling.
Automation that pays for itself — platform choices that cut cloud spend and tooling that erased 1000+ hours of manual grind. Fewer handoffs, fewer copy-paste rituals, more time on work that actually moves the needle.