AI Central - Measurement and Reporting Engineer

Zensar · Remote

Source and collection record

Last observed by our collector: 9 October 2026 at 12:32 am IST. This is not a manual review or a confirmation from the employer.

Employer requisition: 151507

Job type and experience labels are automated discovery categories. The employer determines eligibility. Original experience wording was not retained separately; check the current employer page.

How sourcing and classification work · Report a discrepancy

Your application evidence checklist

Mark the statements you can support after reading the employer source. This checklist stays on this page; it does not score your eligibility or submit an application.

Attendance and availability: I checked the employer page for work location, office attendance, start date and duration.Current requisition: I checked the current employer requisition and its application requirements.

0 of 2 checks marked. Keep unresolved requirements as questions for the employer.

Collected role description

SQL, Python for data pipelines, and a reporting layer — Power BI preferred • GitHub data extraction via REST and GraphQL APIs: pull-request lifecycle, review events, Actions run telemetry. Must be able to derive merge rate, review cycle time and reviewer effort per pull request. • ServiceNow reporting and data extraction, specifically the Vulnerability Response module and Application Vulnerable Item records; ServiceNow Table and REST APIs. • Jira extraction and defect metrics at product grain. • Engineering-metrics literacy (DORA or equivalent) and the judgment to distinguish an activity count from an outcome. • Able to build an attribution model that records how a finding was closed — by agent, by tooling, or manually. Nice To Have Planview or comparable resource/time systems. • GitHub Copilot usage and telemetry APIs. • Dimensional data modeling. • Experience instrumenting a program that was under scrutiny, where the numbers were contested. SQL, Python for data pipelines, and a reporting layer — Power BI preferred • GitHub data extraction via REST and GraphQL APIs: pull-request lifecycle, review events, Actions run telemetry. Must be able to derive merge rate, review cycle time and reviewer effort per pull request. • ServiceNow reporting and data extraction, specifically the Vulnerability Response module and Application Vulnerable Item records; ServiceNow Table and REST APIs. SQL, Python for data pipelines, and a reporting layer — Power BI preferred • GitHub data extraction via REST and GraphQL APIs: pull-request lifecycle, review events, Actions run telemetry. Must be able to derive merge rate, review cycle time and reviewer effort per pull request. • ServiceNow reporting and data extraction, specifically the Vulnerability Response module and Application Vulnerable Item records; ServiceNow Table and REST APIs. • Jira extraction and defect metrics at product grain. • Engineering-metrics literacy (DORA or equivalent) and the judgment to distinguish an activity count from an outcome. • Able to build an attribution model that records how a finding was closed — by agent, by tooling, or manually. Nice To Have Planview or comparable resource/time systems. • GitHub Copilot usage and telemetry APIs. • Dimensional data modeling. • Experience instrumenting a program that was under scrutiny, where the numbers were contested.

Collected experience requirement

4-7 years