SQL L2/L3 Production Support Engineer

SQL L2/L3 Production Support Engineer

New York City

 

Role Summary

We are looking for an experienced SQL L2/L3 Production Support Engineer to provide advanced production support for enterprise database applications. The role requires strong SQL troubleshooting, database performance analysis, incident management, root-cause analysis, and collaboration with application, infrastructure, development, and business teams.

Key Responsibilities

• Provide L2/L3 production support for database-driven applications and enterprise systems.

• Troubleshoot production incidents involving SQL queries, stored procedures, database jobs, data issues, and application/database connectivity.

• Analyze and resolve complex database-related incidents within defined SLAs.

• Perform detailed Root Cause Analysis (RCA) and implement permanent corrective actions.

• Write, analyze, and optimize complex SQL queries, joins, subqueries, CTEs, views, and stored procedures.

• Troubleshoot slow-running queries, blocking, deadlocks, locks, and database performance issues.

• Analyze execution plans and identify opportunities for query and database performance optimization.

• Monitor database health, capacity, performance, scheduled jobs, and failed processes.

• Investigate data discrepancies and perform data validation using SQL.

• Support database batch jobs, ETL processes, interfaces, and scheduled workflows.

• Troubleshoot application-to-database connectivity and integration issues.

• Work closely with application development teams to identify and resolve SQL/database-related defects.

• Coordinate with DBA, Infrastructure, DevOps, Application Support, QA, and Business teams during major incidents.

• Support production deployments, database changes, patches, scripts, and emergency fixes.

• Review and validate database scripts before production implementation.

• Participate in incident, problem, and change management processes.

• Maintain support documentation, knowledge articles, SOPs, and troubleshooting runbooks.

• Identify recurring