Development Manager, Data & Reporting

About the Role

We are looking for a Development Manager to lead the team that builds data, reporting, and dashboard products for clients across our healthcare application ecosystem an environment where billing and payer data sits alongside patient data from our electronic health record (EHR) platform.

This is a technical leadership role.

You will own how the reporting stack is built: the data model beneath it, the standards the team works to, and the judgment calls about whether an approach is sound, reusable, and worth the effort it will take. You will not be writing every report, but you will know a valuable one from a bad one, and you will be able to explain why to a developer, a product partner, or an operations leader asking what effort is involved and how long it should take.

You will work closely with Product/Sprint Owners who run the ceremonies and the backlog.

Your contribution is the technical spine: mentoring a team of developers, guiding how complexity gets broken down and sized, and representing the team credibly to stakeholders who need answers fast and do not always agree with the answer.

Responsibilities

Lead and mentor a team of developers: set the technical bar, review work, develop skills deliberately, and build a team that raises questions early rather than discovering them late.

Own the technical understanding of the reporting ecosystem how billing and payer data relates to clinical and EHR data, how it moves, and how it should be modeled for reporting deeply enough to judge whether a proposed solution is the right one.

¢ Guide the team in breaking down complexity and sizing work: challenge estimates in both directions, separate genuine technical difficulty from padding or guesswork, and insist on reusable solutions where repeated one-offs are being requested.

¢ Communicate delivery timelines, tradeoffs, and status to internal stakeholders and, where appropriate, clients with enough technical credibility to explain the "why" and enough judgment to know when the answer needs to change.

¢ Handle escalations from revenue cycle, MSO, and support partners: distinguish real urgency from routine pressure, resolve what can be resolved, and hold the line on commitments without damaging the working relationship.

¢ Drive consistency, quality, and version control across reporting assets, including stored procedures, views, and report definitions.





¢ Oversee the SQL Server and database layer that powers reporting, including stored procedure design, view structure, and query performance.

¢ Own the team responsible for building and maintaining the ETL pipelines that generate billing, payer, and clinical data into reporting-ready structures.

¢ Ramp quickly on existing databases, SQL codebases, and reporting code with minimal onboarding support, and document what you learn along the way.

¢ Partner with the Product/Sprint Owner on the intake, triage, and prioritization of reporting requests arriving through Tier 1 (Product) and Tier 2 (Support) channels, ensuring technical input shapes what is committed and when.

Required Qualifications

¢ Proven experience managing or leading a development team, ideally in a reporting, BI, or data delivery context.

¢ Deep, hands-on SQL expertise query optimization, stored procedures, and views on SQL Server or a comparable relational platform.

¢ Solid understanding of ETL pipelines and data integration patterns, independent of any specific tool.

¢ Strong hands-on experience with an enterprise analytics or BI platform, with the judgment to distinguish a well-built report from a poorly built one. Power BI experience is a plus.

¢ Experience working in a cloud data environment; Microsoft Azure is a plus.

¢ Experience guiding a team through scoping and estimation, and the confidence to push back on unrealistic timelines or unsound requests with a clear technical rationale.

¢ Demonstrated ability to self-start: learning unfamiliar databases, codebases, and reporting tools quickly without extensive oversight.

¢ Comfort working with healthcare data, including sensitivity to compliance and data-handling requirements.

Preferred Qualifications

¢ Prior experience in healthcare technology, particularly with billing and payer data alongside EHR or clinical data.

¢ Experience with Power BI, SSRS, or other enterprise reporting tools.

¢ Experience with Azure Data Factory or comparable orchestration tooling.





¢ Experience building ETL pipelines with dbt.

¢ Familiarity with medallion (bronze/silver/gold) data architecture patterns.

¢ Experience leading distributed teams and working in an Agile delivery model alongside a live support queue.

¢ Experience in AI-Driven Product Development Lifecycle (AIPDLC)

What Success Looks Like In the First 30 Days

¢ You can trace a report end to end source system, ETL, database layer, published dashboard and explain the path to both a developer and a non-technical stakeholder.

¢ You know the most frequently requested reports, which clients drive them, and which recurring one-off requests should be consolidated into configurable, multi-client solutions.

¢ You are active in grooming alongside the Product/Sprint Owner: every ticket the team picks up has a clear technical understanding behind it, and team members can restate the work in their own words before it is sized.

¢ You have met the operations and support leaders who send work to the team, and you understand how requests arrive, how urgency is communicated, and where work is bypassing the intake process.

¢ You have made at least one technical call that changed an approach a simpler design, a reusable solution, or a rejected estimate that did not hold up.

In the First 90 Days

¢ Estimates are defensible and improving: sizing is a team exercise grounded in technical reasoning, and the gap between estimated and actual effort is measurably narrowing.

¢ The reporting data model and source-to-target logic for the reports is documented, so the team is no longer dependent on any one person to answer how something works.

¢ Version control and delivery standards are in place and followed for reporting assets stored procedures, views, and report definitions with changes moving to production through a controlled path rather than direct edits.

¢ Escalations from operations partners are trending down, because timelines, tradeoffs, and delivery dates are communicated before a deadline becomes a problem rather than after.

¢ You can name each developers strengths and gaps, have a development plan for each, and have begun cross-training to remove single points of failure on the team.

¢ You have independently identified at least one structural problem in the reporting architecture and proposed a plan to address it.

📌 Data Development Manager (Pune)
🏢 Saisystems Health
📍 Pune