Own the feature end-to-end
Requirements and relational schema design through ASP.NET Core Web API, Angular UI, and CI/CD-driven deployment — not a slice of the stack handed off at each boundary.
Open to new opportunities
Gaurav Wagh
Full Stack .NET Developer with 2.5+ years building production enterprise web applications on ASP.NET Core, Angular, Entity Framework Core and SQL Server/PostgreSQL — owning features end-to-end from relational schema design through Web API and Angular UI to CI/CD deployment.
01About
I'm a Full Stack .NET Developer at Tark Technologies LLP, where I build client-facing enterprise applications across manufacturing, fintech, agriculture and retail. The work is mostly the unglamorous kind that businesses actually run on: production traceability, order lifecycles, financial document processing, point of sale.
What I enjoy about it is the breadth. A feature typically starts as a conversation about how an operation really works, becomes a relational schema, then an ASP.NET Core Web API, then an Angular interface, and finally something deployed through CI/CD. Owning that whole path means the data model and the interface get designed against each other rather than negotiated across a handover.
Most of my systems are multi-module and expected to grow, so I lean on Clean Architecture, Domain-Driven Design and the Repository pattern — not as ceremony, but because the alternative gets expensive by the second year.
Education
BE, Computer Engineering
Government Engineering College · Gujarat Technological University
2020 – 2024 · CGPA 7.8 / 10.0
Requirements and relational schema design through ASP.NET Core Web API, Angular UI, and CI/CD-driven deployment — not a slice of the stack handed off at each boundary.
Clean Architecture, Domain-Driven Design, the Repository pattern and SOLID, applied so multi-module codebases stay maintainable as they grow rather than as decoration.
JWT authentication and role-based access control applied consistently across endpoints, so authorisation is a property of the system rather than a per-controller afterthought.
Query and schema optimisation for high-volume transactional systems, because in business applications the database is usually where performance is decided.
02Experience
Client-facing enterprise software delivered in a product engineering team.
Tark Technologies LLP
Deliver client-facing enterprise applications end-to-end — requirements, relational schema design, ASP.NET Core Web API development, Angular UI, and CI/CD-driven deployment — across manufacturing, fintech, agriculture and retail domains.
03Projects
Four production systems delivered at Tark Technologies, across four business domains. Each is described by the problem it solves and the architecture behind it.
These are client projects. Source code and interfaces are covered by NDA, so there are no repositories or screenshots to link — what follows is the business problem, the system design, and my own contribution to each.
Manufacturing / Food Production
Shipped
A centralised MES for a US-based cheese manufacturer, modelling the full production lifecycle as one traceable workflow.
Production tracking ran on manual, paper-based records. With no single system of record spanning intake to shipment, tracing a finished product back to the raw milk it came from meant reconstructing the trail by hand across disconnected paperwork.
A centralised Manufacturing Execution System modelling milk receiving, quality testing, silo management, cheese production, packaging and shipment as one continuous, traceable workflow rather than a set of isolated stages.
Fintech / Document Automation
Shipped
Automated bank statement ingestion with a rule-based categorisation engine replacing manual financial data entry.
Financial record-keeping depended on manually transcribing bank statements and classifying every transaction by hand — slow, repetitive, and a steady source of entry errors.
An automated processing pipeline that ingests bank statements, derives structured transactions from them, and drives downstream expense records and notifications from the result — turning a manual transcription task into a document-processing workflow.
Agriculture / Manufacturing
Shipped
Order lifecycle management for an agricultural equipment manufacturer, centralising tracking across dealers and internal teams.
Orders moved between dealers, retailers, production and dispatch with tracking fragmented across the parties involved, leaving no shared view of where any given order actually stood.
An order management platform covering the full lifecycle from dealer and retailer placement through production, dispatch and delivery, with a single source of truth shared by dealers and internal teams.
Retail / Food & Beverage
In development
A multi-outlet POS platform covering order processing, billing, payments and inventory under per-outlet access control.
Multi-outlet food and beverage operations need consistent order, billing and inventory handling across locations, while keeping each outlet’s data and operations scoped to the staff who work there.
A multi-outlet POS platform covering order processing, billing, payment management and inventory tracking, with menu management, sales reporting and cashier-operation modules governed by per-outlet role-based access control.
04Stack
Grouped by the role each plays in the systems above, rather than as a flat list of logos.
05Algo Lab
Outside of client work I build trading automation for MetaTrader 5 — Expert Advisors in MQL5 paired with an ASP.NET Core middleware layer. It is a personal engineering sandbox: an excuse to work on event-driven systems, real-time integration between processes that were never designed to talk to each other, and software that has to run unattended and fail safely.
A TradingView alert fires a webhook into an ASP.NET Core endpoint. The API is where the interesting work happens: it authenticates the request, validates the payload against the configured risk rules, and only then issues a command the Expert Advisor acts on. Nothing reaches the terminal without passing that gate.
Components I wrote
A second architecture I've been working through: trade events raised on a master terminal are normalised by the communication layer and replayed against one or more slave terminals. The problem it makes concrete is ordering and idempotency — a replicated close that arrives twice, or out of order, has to be harmless.
Components I wrote
TradingView alerts arrive as webhooks at an ASP.NET Core endpoint, which validates and translates them into commands for the terminal.
An ASP.NET Core layer sits between cloud services and MetaTrader 5, providing secure, real-time communication between the two.
Position sizing, stop placement and exposure limits are configuration rather than hard-coded constants, so behaviour is tunable per strategy.
Deployed to VPS infrastructure for 24/7 unattended operation — which makes failure handling and safe restarts a design requirement, not a nicety.
An Expert Advisor that tracks the Asian session range, identifies sweeps of that range, and takes entries on Break of Structure confirmation during the London session.
A multi-timeframe Expert Advisor that detects price swings programmatically, waits for a retracement into a configured Fibonacci level, and enters on confirmation.
A grid-based Expert Advisor with parameterised position sizing, used to explore state management across a series of related open positions.
A personal side interest, not professional experience or a financial service. Nothing here is investment advice, and no performance or profitability claims are made or implied.
06Contact
Open to full-stack .NET roles and interesting engineering problems. The fastest route is email — I read everything.