(402) 555-0115 ◇ Omaha, NE
gaurav.nimbalkar@example.com ◇ linkedin.com/in/gaurav-nimbalkar ◇ gauravnimbalkar.com
SQL developer with 5 years building database code and reporting for logistics operations, currently developing for a freight company that moves 1.2 million shipments a year. Cut average query run time on the main shipment reports from 4 minutes to 12 seconds, built 90 stored procedures and views used by 6 applications, and automated 25 manual reports. Writes clean, well-tested SQL that the next developer can read.
Coursework in Database Design, SQL Programming, Data Warehousing, and Systems Analysis.
Core data concepts, relational data in Azure, and analytics workloads.
- Develop database code for a freight company moving 1.2 million shipments a year across 6 applications.
- Cut query run time on the main shipment reports from 4 minutes to 12 seconds through indexing and rewrites.
- Built 90 stored procedures and views and automated 25 manual reports used by operations daily.
- Wrote about 40 stored procedures and 15 SSIS packages for a policy administration system.
- Fixed about 120 data defects found in testing across 3 releases.
- Moved 200 database objects into Git source control, ending untracked production changes.
- Wrote 20 SQL queries for claims reporting and documented 60 tables in a data dictionary.
- Built 3 Power BI reports on claims volume used by 2 claims managers each week.
- Received a full-time junior developer offer for 2021 at the end of the internship.
Shipment Report Performance Tuning. Reviewed execution plans for the 15 slowest reports, added 8 covering indexes, rewrote cursor logic into set-based SQL, and moved heavy queries to a reporting replica, which cut the main report run time from 4 minutes to 12 seconds.
Report Automation. Replaced 25 manual spreadsheet reports with scheduled stored procedures feeding Power BI, which saved operations staff about 40 hours a week and removed copy-and-paste errors.
Database Source Control. Set up Git and Azure DevOps pipelines for database code with review and deployment steps, which cut failed database releases from about 1 a month to 0 in the following year.
- Member of a regional data community, speaking at 1 local SQL user group meeting in 2025.
- Volunteer data helper for a food bank, building 2 dashboards on donations and deliveries.
- Play cricket in a local league with about 12 matches each summer.
- Review SQL changes from 4 application developers before each monthly release.
- Wrote the team SQL style guide with 30 rules on naming, formatting, and error handling.
- Mentor 1 data intern each summer on SQL basics and database documentation.

.webp)



.webp)


%20Which%20Should%20You%20Use.webp)