Principal Software Engineer

Full Job Description

You will lead through influence, remain hands-on in critical technical areas, raise engineering standards, and partner across disciplines and organizations to deliver durable customer and business outcomes. Define and drive the multi-year technical strategy and architecture for services that manage and optimize Dataverse's globally distributed database fleet. Translate that strategy into executable roadmaps, milestones, and measurable outcomes. Demonstrate strong end-to-end ownership of critical technical areas—from problem definition and architecture through implementation, deployment, operational health, and long-term evolution. Proactively identify gaps, drive issues to closure, and remain accountable for customer and business outcomes. Create clarity in complex and ambiguous engineering spaces by framing problems, gathering and analyzing data, identifying root causes, evaluating tradeoffs, and converting insights into coherent technical strategies and concrete deliverables. Lead complex initiatives spanning multiple teams and organizations. Align stakeholders, resolve architectural disagreements, establish clear system boundaries and invariants, and manage dependencies across database, service, infrastructure, security, and compliance domains. Effectively manage competing priorities, balancing strategic engineering investments, customer commitments, live-site issues, technical debt, and operational responsibilities while maintaining high standards for quality and execution. Own quality, security, compliance, reliability, and operability by design. Establish automation and engineering practices for validation, safe deployment and rollback, observability, capacity management, incident response, and continuous improvement of mission-critical services. Multiply the effectiveness of the engineering organization by mentoring engineers, reviewing architecture and code, establishing reusable patterns, simplifying systems, and raising the bar for engineering excellence. Define and validate security, reliability, and correctness invariants for both new and existing systems. Bachelor's Degree in Computer Science or related technical field AND 6+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python These requirements include but are not limited to the following specialized security screenings: Master's Degree in Computer Science or related technical field AND 8+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python OR Bachelor's Degree in Computer Science or related technical field AND 12+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python OR equivalent experience. Experience architecting and delivering large-scale production cloud services, including providing technical leadership across multiple teams and managing complex cross-organizational dependencies. Experience with SQL and enterprise-grade relational database systems, including database administration, query and workload optimization, capacity and resource management, reliability engineering, and automation at fleet scale. Experience designing, building, and troubleshooting scalable, resilient, event-driven systems, including asynchronous processing, failure recovery, observability, controlled flighting, and resource optimization. Demonstrated ability to create clarity in ambiguous problem spaces, set technical direction, build alignment, and influence architecture and execution across organizational boundaries without direct authority. Demonstrated end-to-end ownership from requirements through production deployment, including diagnosing complex cross-service failures using logs, telemetry, correlation IDs, and distributed traces, supported by comprehensive unit, integration, functional, and end-to-end testing strategies.

Verified from public schema.org JobPosting structured data on the official source page. The complete published description, responsibilities, requirements and benefits were normalized when present; unstated facts were not inferred.