Principal Software Developer

PowerPlan•Atlanta, GA

10d•Hybrid

About The Position

This is a principal-level opportunity to shape the reliability and reach of PowerPlan's cloud-based Data Hub — the platform that turns raw data into the reporting customers depend on. You would own the data pipelines end to end, from Databricks and ADF ingestion through transformation to secure OData delivery, and set the engineering standard across a complex multi-repository codebase. Because the role spans both application and data engineering, there is room to move fluidly across tracks and drive improvements that reach every customer of the platform. It is a high-autonomy role for an engineer who raises the bar without being asked and wants their work measured by whether customers can trust their data. PowerPlan builds cloud-based software that helps asset-intensive and regulated organizations manage the financial and accounting complexity of their operations — spanning project accounting, asset accounting, depreciation, income tax, tax provision, and lease accounting. The platform models sophisticated accounting concepts accurately and delivers reliable reporting that customers rely on for high-stakes financial decisions. The Data Hub sits at the center of that mission, carrying data from ingestion through transformation to customer-facing reporting. Engineers here work in a regulated financial environment where accuracy, reliability, and security are core to the product.

Requirements

Hands-on Databricks and Azure Data Factory experience building medallion-style ingestion and transformation pipelines with Delta Live Tables, Asset Bundles, and Python ETL (Objective 1).
A track record of building reliability and observability into distributed systems — preventive health checks, data-quality gates, logging, monitoring, and graceful failure handling (Objective 2).
The ability to reason through cross-repository dependencies in a Git-based, multi-repo environment with shared libraries, and to move fluidly between application and data engineering (Objective 3).
A high personal bar for code review, test strategy, and production readiness, and the credibility to hold peers to it (Objective 4).
Strong C# and ASP.NET Core skills, including OData service design, middleware, and dependency injection (Objective 5).
Working knowledge of Microsoft Azure (App Service, Azure SQL, Key Vault, managed identities) and identity and token flows (Entra ID, OAuth2 / OIDC, SSO), plus strong production SQL skills.
A willingness to learn regulated financial and accounting concepts and model them accurately across pipelines, services, and reporting.
Bachelor’s degree in Computer Science, Information Systems, Engineering, Accounting Information Systems, or equivalent professional experience.
Typically 10+ years of professional software engineering experience, with senior-level ownership of services, data platforms, enterprise applications, or cloud-hosted systems.
Experience in Agile/Scrum delivery environments, including backlog refinement, estimation, sprint execution, code review, testing, release planning, and production support.

Responsibilities

Build and operate Databricks and Azure Data Factory pipelines that ingest raw source data and move it through the medallion pattern (bronze to silver to gold) into reliable, report-ready datasets for the Data Hub platform.
Design and maintain Delta Live Tables, Databricks Asset Bundles, Python transformation logic, and ADF orchestration (linked services, triggers, JSON-defined pipeline assets); troubleshoot failures end to end from ingestion through catalog modeling to the OData reporting layer.
Strengthen reliability and observability across the full Data Hub chain — ingestion through ETL through OData services to reporting — so failures are detected, diagnosed, and prevented before they reach customers.
Lead with preventive measures — health checks and data-quality gates — ahead of reactive alerting.
Attack the current weakest link first: the customer data-delivery path, and being able to scale to large customers.
Understand the architecture of the two methods the platform uses to deliver data to customers, and improve how those long-running requests are managed so large customers stop timing out.
Extend logging, monitoring, and run and data-health visibility across repository boundaries.
Get oriented across the multi-repository architecture — shared libraries, ingestion repos, ETL layers, OData services, UI components — and become a credible reviewer and contributor on either the application (ASP.NET Core / OData) or data (Databricks / ADF) track, with working familiarity in the other.
Map the repositories and how they depend on each other (shared libraries into ingestion into ETL into OData into UI).
Take on real review and contribution on a primary track while building working familiarity in the other, and reason confidently about how a shared-library change ripples into downstream services.
Set and hold the standard for code review, test strategy, and performance and production readiness across the multi-repository Data Hub codebase — regardless of whether the person's primary track is application or data engineering.
Establish and model review standards, test strategy, and production-readiness expectations; give rigorous, constructive reviews across repositories; drive improvements to test coverage and performance; hold peers to the same bar and coach toward it.
Design and maintain the ASP.NET Core OData reporting services that deliver Data Hub reporting data to customers, with the supporting authentication and authorization flows (Entra ID, OAuth2 / OIDC, JWT, SSO) handled as a secondary concern rather than the core of the role.
Build and maintain OData reporting APIs, shared libraries, middleware, and DI configuration, with identity and token flows (Entra ID, OAuth2 / OIDC, SSO, Okta) as supporting work.
Build robustness into the components that gather and deliver data — anticipate failure modes and handle them gracefully so reporting degrades safely instead of breaking.