Internal operations
Administrative tools, dealer portals, and screens that help teams work with business records and operational tasks.
Technology in practiceEnterprise
Enterprise
Software Engineering.
C#, .NET, ASP.NET MVC, Razor & SQL Server
C#, .NET, and the tools behind business-critical web applications. A closer look at how interfaces, application logic, and structured data work together—and how I approach the engineering across them.
Web experiencesBusiness systems
Application architectureLogic · APIs · Integrations
DataCloudSecurity
.NET
C#- ASP.NET MVC
SQL Server
Built around business operations
Software that supports the way a business works.
Enterprise applications bring people, business rules, and data together. Their complexity often comes from the relationships between systems and the consequences of a change, as much as from the individual screens.
Transactional workflows
Marketplace listings, invoicing interfaces, and payment-related workflows where validation and consistent state matter.
Connected systems
Applications that exchange information through APIs and database workflows, with clear responsibilities at each boundary.
The layers of the stack
The tools and how I use them.
.NETApplication foundation.NET
.NET provides the runtime, libraries, and tools used to build and run applications. It supports the backend services and business logic that sit behind a user interface. In an existing system, the particular .NET implementation and its dependencies shape how changes should be planned.
C#Business logicC#
C# is a programming language used with .NET. It gives structure to application rules, validation, and communication between components. Clear models and well-defined responsibilities make it easier to understand what a change will affect and where a problem originates.
ASP.NET MVCWeb application structureASP.NET MVC
MVC separates models, views, and controllers: the application’s data and behavior, the interface people see, and the handling of web requests. This separation helps organize operational applications with many screens and workflows. Framework versions matter when maintaining an established application.
RazorServer-rendered interfaces
Razor
Razor combines HTML markup with C# expressions to produce web pages on the server. Layouts and reusable view elements help keep related screens consistent. I work with Razor interfaces alongside the controllers, models, and data flows that supply their content.
Telerik / Kendo UIInteractive application controls
Telerik / Kendo UI
Telerik UI for ASP.NET MVC provides server-side wrappers for Kendo UI components. Grids, forms, and other controls can support data-heavy interfaces. The engineering work includes connecting those controls to the right data, handling user actions, and preserving the application’s business rules.
SQL ServerStructured business dataSQL Server
SQL Server stores related business records in a relational database. Queries and stored procedures connect that data to application workflows. Understanding relationships, update behavior, and query results is essential when investigating a problem that crosses the interface, backend, and database.
My approach
Follow the workflow through the whole system.
I trace the interface, request, business rules, and stored data before changing a workflow. Maintenance and upgrade decisions account for the application’s actual .NET framework, dependencies, and business constraints.
Experience in context
Related project work.
Stack’s Bowers Galleries
My contributions include ASP.NET MVC/Razor and Kendo UI interfaces for marketplace listings, invoicing, and payment-related workflows, alongside APIs and other web platforms.
Read the case study
American Honda
My career experience includes dealer intranet work using ASP.NET and SQL Server.
View career creditsLet’s talk about your project.
Tell me what you’re building or what needs fixing.
Start a conversation