Chief Engineer of Operations

Key Role in Financial Platform Reliability:

The Principal Engineer, Site Reliability (SRE) plays a pivotal role in ensuring the stability, scalability, and operational excellence of Accounting and Finance platforms. This position focuses on leading the operational health of our platforms, guaranteeing highly reliable financial applications and data services that meet the demanding requirements of accuracy, compliance, and availability supporting business operations.

As a key SRE, you will build automation, implement monitoring, improve incident response, and champion DevOps practices that enable Finance and Accounting systems to operate with consistency and trustworthiness. You will also coach and mentor junior SREs to ensure overall Operational Excellence.

Operational Responsibilities:

• Platform Oversight: Own day-to-day operations for Accounting and Finance applications and data platforms, ensuring they run smoothly and meet business expectations.
• Reliability & Availability: Ensure Accounting and Finance platforms meet defined SLAs, SLOs, and SLIs for performance, reliability, and uptime.
• Automation & Efficiency: Build automation for deployments, monitoring, scaling, and self-healing capabilities to reduce manual effort and operational risk.
• Observability & Monitoring: Implement and maintain comprehensive monitoring, alerting, and logging for accounting applications and data pipelines (e.g., Snowflake, dbt workflows, ERP integrations).
• Incident Response: Lead and participate in on-call rotations, perform root cause analysis, and drive improvements to prevent recurrence of production issues.
• Operational Excellence: Establish and enforce best practices for capacity planning, performance tuning, disaster recovery, and compliance controls in financial systems.
• Collaboration with Engineering & Finance: Partner with software engineers, data engineers, and Finance/Accounting teams to ensure operational needs are met from development through production.
• Team Coordination: Manage workload, priorities, and escalations for operations staff and partner teams, ensuring alignment with SLAs and compliance requirements.
• Security & Compliance: Ensure financial applications and data pipelines meet audit, compliance, and security requirements.
• Continuous Improvement: Drive post-incident reviews, implement lessons learned, and proactively identify opportunities to improve system resilience.
• Audit & Compliance Support: Ensure operational practices meet internal controls, audit requirements, and financial compliance standards.

Qualifications:

• Bachelor's in computer science, Engineering, Information Technology, or related field (or equivalent experience).
• 12-15 years of experience in Site Reliability Engineering, DevOps, or Production Engineering, ideally supporting financial or mission-critical applications.
• Strong experience with monitoring/observability tools (Datadog, Prometheus, Grafana, Splunk, or equivalent).
• Hands-on expertise with CI/CD pipelines, automation frameworks, and IaC tools (Terraform, Ansible, GitHub Actions, Azure DevOps, etc.).
• Familiarity with Snowflake, dbt, and financial system integrations from an operational support perspective.
• Strong scripting/programming experience (Python, Bash, Go, or similar) for automation and tooling.
• Proven ability to manage incident response and conduct blameless postmortems.
• Experience ensuring compliance, security, and audit-readiness in enterprise applications.

Required Skills:

• Automation
• Operational Excellence
• Snowflake
• SQL
• Data Engineering
• Financial Systems

Nice to Have:

• Experience supporting financial applications (ERP, revenue recognition systems, accounting platforms)
• Exposure to FinOps practices for optimizing cloud spend in finance-related platforms
• Familiarity with containers and orchestration (Docker, Kubernetes)
• Experience building resilience into data pipelines and ensuring auditability for accounting data
• Strong communication skills to articulate operational issues and risks to both technical and non-technical stakeholders