Purpose of the Team: GGRO Azure Infra Launch Ops runs the operational launch pipeline for Azure infrastructure products: new products, pricing changes, geo expansions and lifecycle transitions for Azure consumption meters and SKUs. The team handles more than 100 launches a month, and errors in meter or pricing data can create downstream customer or financial impact, so accuracy matters at every step.
Key projects: This role will contribute to owning the end-to-end execution of Azure Infrastructure launches, partnering with Engineering, Business Planning, Operations, and Commerce teams to bring products and pricing to market on time and with high quality. They will also contribute to continuous improvement of the process. This role manages launch intake, triage, scope validation, execution tracking, risk mitigation, and stakeholder coordination across the launch lifecycle.
Key Responsibilities
- Independently own operational requests from intake and validation through launch preparation, submission, downstream monitoring, issue resolution and closure.
- Investigate and reconcile discrepancies across request data, operational systems, launch artifacts and downstream requirements.
- Use data, queries and operational systems to validate assumptions, diagnose issues and determine the right next action.
- Work a high-volume queue of concurrent requests with different priorities, deadlines, dependencies and complexity.
- Resolve incomplete, conflicting or unclear requirements directly with requestors, Business Planners and partner teams, and push back respectfully when a request cannot proceed as submitted.
- Monitor downstream execution, catch stalled activity or unexpected outcomes, and resolve or escape them.
- Manage launch deadlines and dependencies, proactively following up on required actions and surfacing risks before they become missed milestones.
- Exercise judgment within established processes: determine what can be resolved independently, what requires stakeholder clarification and what should be escalated, including requests that fall outside the team's agreed scope.
- Recognize recurring issues upstream and downstream, distinguish isolated problems from emerging patterns, document examples and operational impact, and raise systemic concerns to GGRO Ops leadership.
- Contribute operator insight to postmortems, SOP updates and process‑improvement discussions, while continuing to work within the approved process until leadership changes it.
- Keep request history, decisions, status and supporting evidence accurate, so the work can be understood without relying on anyone's memory.
- Handle sensitive product, pricing, launch and business information appropriately, sharing only what each audience needs.
Candidate Requirements
- Disqualifiers: They dont want someone that runs quearys all day long but need to know how to do it if asked,
- Best vs. Average: The focus of the role is the request as submitted: ensuring it is accurate, complete, executable and delivered. Process design, tooling and operating‑model decisions are owned by GGRO Ops leadership; the Operations Engineer identifies recurring issues and surfaces them with supporting evidence.
Hard Skills Assessments
- Expected Dates that Hard Skills Assessments will be scheduled: asap
- Hard Skills Assessment Process: The assessment process will include one round with the sponsor, one round with team
- Required Candidate Preparation: NA
Summary
The Operations Engineer is a hands‑on operations role responsible for executing Azure infrastructure launch requests end to end. The role validates each request, investigates and reconciles discrepancies across systems and launch artifacts, prepares and submits the launch package, monitors it downstream and closes it out. The Operations Engineer works a high‑volume queue of concurrent requests with fixed deadlines and shifting priorities, within an established operating model that continues to evolve as new scope and partner teams are added.
The focus of the role is the request as submitted: ensuring it is accurate, complete, executable and delivered. Process design, tooling and operating‑model decisions are owned by GGRO Ops leadership; the Operations Engineer identifies recurring issues and surfaces them with supporting evidence
Top Skills
- 1- Queary Language (Kusto, SQL)
- 2-Running tickets and crunching through ticket ques.
Job Responsibilities
- Independently own operational requests from intake and validation through launch preparation, submission, downstream monitoring, issue resolution and closure.
- Investigate and reconcile discrepancies across request data, operational systems, launch artifacts and downstream requirements.
- Use data, queries and operational systems to validate assumptions, diagnose issues and determine the right next action.
- Work a high-volume queue of concurrent requests with different priorities, deadlines, dependencies and complexity.
- Resolve incomplete, conflicting or unclear requirements directly with requestors, Business Planners and partner teams, and push back respectfully when a request cannot proceed as submitted.
- Monitor downstream execution, catch stalled activity or unexpected outcomes, and resolve or escape them.
- Manage launch deadlines and dependencies, proactively following up on required actions and surfacing risks before they become missed milestones.
- Exercise judgment within established processes: determine what can be resolved independently, what requires stakeholder clarification and what should be escalated, including requests that fall outside the team's agreed scope.
- Recognize recurring issues upstream and downstream, distinguish isolated problems from emerging patterns, document examples and operational impact, and raise systemic concerns to GGRO Ops leadership.
- Contribute operator insight to postmortems, SOP updates and process‑improvement discussions, while continuing to work within the approved process until leadership changes it.
- Keep request history, decisions, status and supporting evidence accurate, so the work can be understood without relying on anyone's memory.
- Handle sensitive product, pricing, launch and business information appropriately, sharing only what each audience needs.
Skills
- Experience with SQL, Kusto or similar query languages, including modifying queries to investigate unexpected results. Demonstrated ability to learn unfamiliar technical systems quickly is valued over experience with any specific tool.
- Experience in pricing, billing or other operations where errors carry direct financial impact.
- Experience contributing to standard operating procedures or postmortems from an operational perspective.
Education/Experience
- 3+ years of hands‑on experience in complex operational environments, personally working and resolving individual requests, records or tickets, such as product, catalog, SKU, pricing, billing, commerce, supply chain or data quality operations.
- Demonstrated ability to investigate problems end to end: isolating the cause, determining the correct fix, verifying the outcome and recognizing when an issue is recurring.
- Experience using data, queries, operational systems or other technical tools to investigate discrepancies and validate outcomes.
- Strong attention to detail and the ability to reconcile information across multiple systems and sources.
- Ability to manage many concurrent, time‑sensitive requests with competing priorities, fixed deadlines and changing conditions without losing accuracy.
- Ability to work through incomplete or conflicting requirements, data or system signals, and to determine when to proceed, when to seek clarification and when to escalation.
- Curiosity and learning agility, including the ability to work through unfamiliar systems, documentation and processes independently before escalating.
- Clear, direct written and verbal communication with technical and business stakeholders, including the ability to state plainly when a request is incomplete, inconsistent or cannot proceed.
- Composure and disciplined execution under pressure when multiple urgent issues arise at once.
- Sound judgment in handling confidential product, pricing and business information.