Software Developer - Anaplan

Part time 10-15 hrs
SKILLS AND REQUIREMENTS
Technical
6+ years of professional software development, including 2+ years running production workloads on Google Cloud Platform (equivalent AWS or Azure depth considered where Google Cloud Platform fundamentals can be demonstrated)
Strong Python (FastAPI, Flask, or Django) and working TypeScript/React, sufficient to own a data-dense internal application front to back
Strong SQL and hands-on BigQuery: analytic functions, query optimization, partitioning and clustering, cost control, authorized views, layered data modeling
Cloud Run or equivalent container platforms, CI/CD, secret management, and structured logging; Terraform, including reading state, recognizing drift, and spotting a plan that would destroy something that matters
Solid IAM and cloud security grounding: service accounts, least privilege, impersonation, workload identity, and network-level versus application-level authorization
Experience integrating enterprise systems over REST/OData (OAuth client-credentials, pagination, inconsistent APIs) and building pipelines with sound judgment on idempotency, full versus incremental loads, explicit schemas, and late-arriving or restated data
Finance Systems & FP&A
Strong understanding of FP&A and management reporting — budgets, forecasts, actuals, variance analysis, headcount, departmental reporting, KPIs, and common finance dashboard structures
Ability to translate finance requirements into technical changes (“change this variance logic,” “add a forecast scenario,” “restructure this P&L view”) and understand the business logic well enough to implement them without everything being translated by IT
Finance data validation and QA skills: reconcile dashboard outputs to source systems and reports, identify mapping or aggregation issues, and ensure totals, dimensions, periods, and calculations are accurate before go-live
Working familiarity with financial and operational data concepts (e.g., purchase commitment versus accrued liability; why two similar-looking figures must never be added together)
Professional
Comfortable working directly with non-technical stakeholders; able to surface unstated assumptions and explain technical constraints in terms of business consequence
Excellent written communication, a verification instinct (prove it, and state plainly what was not verified), and a self-directed, pragmatic approach in a fast-moving environment where requirements may arrive as a screenshot and a question