Snowflake
Warehouse development, SQL logic, data modelling, and analytical workflows.
Snowflake / SQL Server / C# .NET / Reporting
Eamonn Watson
Internal tools · Reporting · Data warehousing
I build the internal systems where data, reporting, and software have to work together — data warehouses, operational reporting, validation tooling, and the C#/.NET applications that real business processes depend on.
About
I’m a database programmer and developer — comfortable across the full range from warehouse logic and SQL reporting to the C#/.NET and Blazor applications that consume and act on that data.
I like work that makes complicated things feel calmer: a well-structured data model, a reporting view that answers the right question, or an internal application that removes friction from a process people rely on every week.
My public projects reflect the same practical style — C# desktop utilities, Blazor tools, validation logic, and testable application structure.
Skills
Tools I use to move data from raw operational detail into reporting, decisions, and internal systems that hold up over time.
Core Stack
Warehouse development, SQL logic, data modelling, and analytical workflows.
Relational database design, stored procedures, querying, and data reliability.
Internal tools, web applications, desktop utilities, and maintainable business software.
Clear metrics, repeatable reporting datasets, and decision-support outputs without unnecessary noise.
Structures and pipeline logic that make operational data consistent, trusted, and reusable downstream.
Supporting Tools
Practical analysis, imports, exports, validation, and business-friendly data handling.
Automation, data processing, scripting, and lightweight integration tasks.
Modern .NET web interfaces with practical component-driven layouts and workflows.
Windows desktop utilities, MVVM structure, validation logic, and user-facing internal tools.
Engineering & Delivery
Layered application design, xUnit test projects, and cleaner separation of concerns that holds up when requirements shift.
Business logic validation, audit-friendly workflows, and maintainable architecture for systems that need to stay trustworthy over time.
Projects
FS-Duenna is a public project. The enterprise examples below are intentionally generalized to respect confidentiality while still showing the kinds of systems, tools, and problem spaces I work with.
Real project / flight simulation
A C# desktop utility built for the Round The World Race community. FS-Duenna monitors simulator state in real time, validates flights against race rules, captures supporting log evidence, and produces shareable validation graphics — giving pilots and race organisers a reliable, auditable record of every flight.
Representative enterprise work
Warehouse and reporting work built on Snowflake and SQL Server — turning raw operational data into structured, reusable reporting foundations. Covers data modelling, stored procedures, scheduled pipelines, and the view layers that analytics, extracts, and business outputs depend on.
Details available in conversationRepresentative enterprise work
A Blazor-based internal workflow for weekly operational performance reporting. Configurable goals, weighted scoring, and ranking — with built-in data quality checks and a full audit history that keeps records trustworthy and reviewable over time.
Confidential client and business details omittedRepresentative enterprise work
A Blazor web application that replaces a manual spreadsheet-driven roster process. Handles Excel imports, directory validation, flagged-record review, searchable history, and audit-safe edits — reducing friction and improving confidence in every change.
Architecture and examples can be discussed safelyHow I Work
I think about software from the perspective of the people who have to depend on it — where the data comes from, how it gets validated, and what happens when something changes.
Reporting and analytics are only as reliable as the structures beneath them. I focus on getting the models, pipelines, and validation logic right so that outputs are consistent, repeatable, and explainable.
The best internal tools are built around how work actually happens. I pay attention to the real workflow — what gets imported, what needs reviewing, where the friction is, and what change history matters.
Systems that people rely on keep evolving. Clean layering, clear validation logic, and structured test coverage make that manageable — and make the next change easier to land safely.
Contact
I work best on problems where data reliability, reporting clarity, or internal workflow tooling matters. If you’re building, improving, or rethinking something in that space — Snowflake, SQL Server, reporting infrastructure, or C#/.NET internal tools — I’m happy to talk.