GitLab - Engineering Manager, Observability, Monitoring, and Integrations (Monetization)
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT
Requirements
• Experience managing product, platform, or development teams and building values-aligned environments where team members can grow and deliver meaningful results. • Strong technical judgment across architecture, system design, and pragmatic delivery for complex integrations and business-critical workflows. • Strong technical judgment • Experience working on purchasing, billing, provisioning, subscription, commerce, or other revenue-impacting systems. • Knowledge of observability-first architectures, including tools such as Prometheus, Grafana, and modern incident management tooling. • Knowledge of • Knowledge of • Experience defining service level indicators and targets, writing runbooks, and coordinating incident management in operationally rigorous environments. • Strong collaboration and written communication skills in asynchronous, handbook-first teams that work across engineering, product, finance, customer service, and go-to-market functions. • Strong collaboration and written communication skills • Ability to translate complex technical and product issues into clear, actionable language for both technical and non-technical audiences. • Ability to translate • Sound judgment when handling confidential or financial information, customer-facing incidents, and changes that can affect revenue, with openness to transferable experience from related domains. • Sound judgment • Sound judgment • The Fulfillment team builds and operates the infrastructure behind GitLab's purchasing workflows, and we partner closely with sales, finance, information technology, and support to deliver secure, reliable buyer experiences. Within the broader Monetization section, we focus on the systems and integrations that connect billing, provisioning, subscriptions, and usage across multiple platforms. We work asynchronously across regions with a strong emphasis on planning, retrospectives, operational ownership, and safe rollouts. For more on how we work, see the Fulfillment Sub-department Handbook. • How GitLab Supports Full-Time Employees • Benefits to support your health, finances, and well-being • Flexible Paid Time Off • Team Member Resource Groups • Equity Compensation & Employee Stock Purchase Plan • Growth and Development Fund • Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application. • Country Hiring Guidelines: GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process. • Country Hiring Guidelines:
Responsibilities
• Architect end-to-end telemetry and observability across CustomersDot, Salesforce, and Zuora to enable real-time monitoring and faster issue resolution across purchasing and provisioning flows. • Architect • Architect • Implement automated billing anomaly detection to identify event drops, abuse spikes, and transactional discrepancies that affect reconciliation and financial integrity. • Implement • Implement • Define the integration strategy between customer-facing monetization services and enterprise applications, including Salesforce and Workato, with a focus on durable API contracts and reliable financial workflows. • Define • Define • Drive an AI-native engineering approach that uses machine learning and AI-enabled tooling to surface anomalies, improve infrastructure operations, and inform delivery planning. • Drive • Drive • Hire and grow a high-performing team, setting expectations for ownership, quality, and collaboration from the ground up. • Guide architecture and implementation discussions, helping the team make sound tradeoffs across reliability, availability, data model quality, and developer experience. • Guide • Guide • Partner with cross-functional stakeholders across engineering, product, finance, customer service, and go-to-market teams to coordinate changes in revenue-impacting systems with care and clarity. • Partner • Partner • Establish incident management practices, rollout safeguards, and operational standards for systems handling customer-facing and financially critical workflows. • Establish • Establish
No credit card. Takes 10 seconds.