SQL Deployment Safety
Frozen 12-case synthetic corpus; 9 cases corroborated by SQL Server execution.
Pankaj Kumar · Enterprise Engineering
I modernize high-risk .NET systems without losing reliability, security, or operational control.
15+ years building and modernizing enterprise applications, SQL Server platforms, APIs, cloud infrastructure, and delivery automation.
Selected Engineering Proof
Public builds and established professional outcomes, with scope kept explicit.
Enterprise .NET Modernization
Applications, integrations, reporting, and delivery for enterprise environments.
Agentic Development Workflows
Resumable prompt routing, verification, checkpoints, and structured run reports.
SQL Performance Engineering
Report execution time reduction through query tuning and caching.
Cloud Migration / DevOps
Fewer deployment failures and lower infrastructure cost, respectively.
Engineering Case Studies
Concrete systems with public source, documentation, or a recorded demonstration.
ProdGuard SQL
Static review can miss the production risk revealed only by executing a database change and observing what it actually did.
- What I built
- A pre-deployment T-SQL review pipeline that combines deterministic parsing and rules, disposable SQL Server execution, state diffs, contract verification, and bounded agent review.
- Engineering result
- F1 1.0 on a frozen 12-case synthetic corpus versus a 0.6833 baseline. Nine cases use real SQL Server execution; the repository documents the limits and does not generalize the result.
AgentBatchRunner
Long coding-agent batches need repeatable routing, state, verification, and recovery rather than a chain of opaque one-off prompts.
- What I built
- A local .NET 8 CLI and WPF application that runs YAML-defined work through Codex, Claude Code, or dry-run adapters while recording Git checkpoints, attempts, verification, and reports.
- Engineering result
- Persistent run evidence and explicit provider routing, with folder pipelines that separate execution, review, dependency checks, and operator-controlled next-file decisions.
Enterprise Modernization
Modernizing enterprise applications requires dependable integrations, secure access, measurable performance, and repeatable delivery.
- Engineering focus
- Enterprise application delivery, REST API integrations, SQL reporting and tuning, cloud migration, and CI/CD standardization.
- Evidence scope
- Professional experience summarized below. Public implementation evidence is presented separately in the named open-source case studies.
HeavyTransfer
Very large transfers must resume safely after interruption without allowing memory use to grow with the file or treating a partial result as complete.
- What I built
- A Rust-first resumable transfer foundation with an Axum/SQLx server, durable client state, bounded-buffer I/O, range support, integrity checks, CLI, and Tauri desktop shell.
- Engineering result
- Checked 64-bit size and offset handling, restart-safe transfer state, explicit integrity modes, and unit, property, integration, boundary, traversal, and conflict tests.
Engineering Capabilities
Capabilities lead; tools and platforms support the engineering decision.
Enterprise Application Modernization
Move legacy systems forward in controlled increments while protecting critical behavior.
C#.NETASP.NET CoreMVC
SQL Performance & Deployment Safety
Measure query behavior, tune bottlenecks, and make database change risk visible before release.
SQL ServerT-SQLDapperExecution evidence
Cloud Migration & Delivery
Plan migration boundaries, standardize delivery, and operate with measurable feedback.
AzureAWSCI/CDMonitoring
API & Integration Architecture
Design explicit contracts, secure trust boundaries, and maintainable system integrations.
REST APIsOAuth / OIDCValidationObservability
Secure Application Engineering
Treat authorization, auditability, secrets, and failure behavior as architecture concerns.
RBACOWASPAudit loggingLeast privilege
AI-Assisted Engineering
Use agents within testable workflows where deterministic checks and human approval remain authoritative.
CodexClaude CodeAutomationHuman review
How I Engineer Systems
Practical rules for making complex change safer and easier to operate.
- Measure before optimizing.
- Prefer safe, incremental modernization.
- Automate repeatable verification.
- Design for observability and recovery.
- Treat security as architecture.
- Keep humans in control of high-risk automation.
Experience Highlights
Enterprise delivery outcomes and the responsibilities behind them.
Application Development Analyst
Enterprise applications · Public-sector systems
- Deliver enterprise features end to end, from requirements and design through deployment.
- Reduced report execution time by ~65% through SQL query tuning and caching.
- Cut deployment failures by ~40% by standardizing CI/CD pipelines.
- Migrated legacy applications to cloud infrastructure, reducing cost by ~30%.
- Partner with stakeholders to clarify scope and reduce production issues.
Senior .NET Developer / Lead (Highlights)
Modernization · Integrations · Reporting
- Built REST APIs and integrations with secure authentication and authorization patterns.
- Implemented CI/CD pipelines and improved deployment consistency.
- Created SSRS and Crystal Reports solutions with parameter safety and operational stability.
Contact
Email or LinkedIn is the fastest way to start a conversation.
Let’s discuss the system behind the requirement.
I’m interested in senior or lead engineering work involving modernization, reliability, platform delivery, data, or high-risk technical change.
Direct email: [email protected]
Your email draft
If an email app is configured, the link below opens it. Otherwise copy the draft into webmail and send it to [email protected].