ZipRecruiter

Log In

1

Contract Finops Jobs in Tennessee (NOW HIRING)

All JobsContract Finops JobsContract Finops Jobs in Tennessee

Contract Finops information

What is the difference between Contract Finops vs Cloud Financial Analyst?

AspectContract FinopsCloud Financial Analyst
CredentialsFinancial, cloud, or FinOps certificationsFinance, accounting, or cloud cost management certifications
Work EnvironmentContract-based, often remote, within cloud or finance teamsFull-time or contract, typically in finance or IT departments
Employer & IndustryCloud service providers, tech companies, consulting firmsLarge enterprises, cloud providers, finance departments
Search & Comparison IntentCost optimization, cloud spend management, FinOps rolesCloud cost analysis, financial planning, cloud budgeting

Contract Finops professionals focus on managing and optimizing cloud costs through financial practices, often working on short-term projects or contracts. Cloud Financial Analysts analyze cloud expenses, develop budgets, and support financial planning within cloud environments. While both roles involve cloud cost management, Contract Finops emphasizes operational cost control and vendor negotiations, whereas Cloud Financial Analysts focus on financial analysis and forecasting.

What skills and qualifications are needed to thrive as a Contract FinOps?

To thrive as a Contract FinOps professional, you need a solid understanding of financial operations, cloud cost management, and contract negotiation, often backed by a degree in finance, accounting, or a related field. Familiarity with cloud financial management tools like AWS Cost Explorer, Azure Cost Management, and FinOps frameworks, as well as certifications such as Certified FinOps Practitioner, is highly valuable. Strong analytical skills, attention to detail, and effective communication are essential soft skills for collaborating with technical and non-technical stakeholders. These skills ensure accurate financial planning, optimization of cloud spending, and alignment of business and IT goals for cost efficiency.

What is a Contract FinOps?

Contract FinOps professionals are specialists who manage the financial operations (FinOps) related to cloud contracts and services. They focus on optimizing cloud spending, overseeing budgeting, and ensuring that contractual agreements with cloud service providers are cost-effective and aligned with business needs. Their role involves analyzing usage data, negotiating contracts, and implementing financial best practices to maximize value from cloud investments. By bridging the gap between finance, operations, and IT, Contract FinOps professionals help organizations achieve transparency and efficiency in cloud financial management.

What challenges do Contract FinOps face when managing cloud costs across multiple vendors?

Contract FinOps professionals often encounter challenges such as tracking usage and expenses across various cloud providers, ensuring contract compliance, and optimizing costs while meeting business needs. Balancing cost efficiency with performance requirements and accurately forecasting cloud spend can also be complex due to fluctuating workloads and evolving contract terms. Effective collaboration with engineering, procurement, and finance teams is essential to gather accurate data and implement cost-saving measures.
What are the most commonly searched types of Finops jobs in Tennessee? The most popular types of Finops jobs in Tennessee are:
What are popular job titles related to Contract Finops jobs in Tennessee? For Contract Finops jobs in Tennessee, the most frequently searched job titles are:
What job categories do people searching Contract Finops jobs in Tennessee look for? The top searched job categories for Contract Finops jobs in Tennessee are:
Contract Finops jobs near you
Infographic showing various Contract Finops job openings in Tennessee as of June 2026, with employment types broken down into 75% Full Time, and 25% Part Time. Highlights an 82% Physical, 2% Hybrid, and 16% Remote job distribution.

Palantir Foundry Engineer

IT America Inc

Nashville, TN • On-site

Contractor

Re-posted 2 days ago

Job description

Position: Palantir Foundry Engineer

Location: Nashville, TN

Duration: 6 Months

Role Summary:

Hands-on Foundry specialist who can design ontology-first data products, engineer high-reliability pipelines, and operationalize them into secure, observable, and reusable building blocks used by multiple applications (Workshop/Slate, AIP/Actions). You’ll own the full lifecycle: from raw sources to governed, versioned, materialized datasets wired into operational apps and AIP agents.

Core Responsibilities:

  • Ontology & Data Product Design: Model Object Types, relationships, and semantics; enforce schema evolution strategies; define authoritative datasets with lineage and provenance.
  • Pipelines & Materializations: Build Code Workbook transforms (SQL, PySpark/Scala), orchestrate multi-stage DAGs, tune cluster/runtime parameters, and implement incremental + snapshot patterns with backfills and recovery.
  • Operationalization: Configure schedules, SLAs/SLOs, alerts/health checks, and data quality tests (constraints, anomaly/volume checks); implement idempotency, checkpointing, and graceful retries.
  • Governance & Security: Apply RBAC, object-level permissions, policy tags/PII handling, and least-privilege patterns; integrate with enterprise identity; document data contracts.
  • Performance Engineering: Optimize joins/partitions, caching/materialization strategies, file layout (e.g., Parquet/Delta), and shuffle minimization; instrument with runtime metrics and cost controls.
  • Dev Productivity & SDLC: Use Git-backed code repos, branching/versioning, code reviews, unit/integration tests for transforms; templatize patterns for reuse across domains.
  • Applications & Interfaces: Expose ontology-backed data to Workshop/Slate apps wire Actions and AIP agents to governed datasets; publish clean APIs/feeds for downstream systems.
  • Reliability & Incident Response: Own on-call for data products, run RCAs, create runbooks, and drive preventive engineering.
  • Documentation & Enablement: Produce playbooks, data product specs, and runbooks; mentor engineers and analysts on Foundry best practices.

Required Qualifications:

  • 7+ years in data engineering/analytics engineering with 4+ years hands-on Palantir Foundry at scale.
  • Deep expertise in Foundry Ontology, Code Workbooks, Pipelines, Materializations, Lineage/Provenance, and object permissions.
  • Strong SQL and PySpark/Scala in Foundry; comfort with UDFs, window functions, and partitioning/bucketing strategies.
  • Proven operational excellence: SLAs/SLOs, alerting, data quality frameworks, backfills, rollbacks, blue/green or canary data releases.
  • Fluency with Git, CI/CD for Foundry code repos, test automation for transforms, and environment promotion.
  • Hands-on with cloud storage & compute (AWS/Azure/GCP), file formats (Parquet/Delta), and cost/perf tuning.
  • Strong grasp of data governance (PII, masking, policy tags) and security models within Foundry.

Nice to Have:

  • Building Workshop/Slate UX tied to ontology objects; authoring Actions and integrating AIP use cases.
  • Streaming/event ingestion patterns (e.g., Kafka/Kinesis) materialized into curated datasets.
  • Observability stacks (e.g., Datadog/CloudWatch/Prometheus) for pipeline telemetry; FinOps/cost governance.
  • Experience establishing platform standards: templates, code style, testing frameworks, domain data product catalogs.

Success Metrics (90–180 Days):

  • ≥99.5% pipeline success rate, with documented SLOs and active alerting.
  • <20% runtime/cost reduction via optimization and materialization strategy.
  • Zero P1 data incidents and ≤4h MTTR with playbooks and automated remediation.
  • 3+ reusable templates (ingestion, CDC, enrichment) adopted by partner teams.
  • Ontology coverage for priority domains with versioned contracts and lineage.

Example Work You’ll Own:

  • Stand up incremental CDC pipelines with watermarking & late-arrivals handling; backfill historical data safely.
  • Define business-ready ontology for a domain and wire it to Workshop apps and AIP agents that trigger Actions.
  • Implement DQ gates (null/dup checks, distribution drift) that fail fast and auto-open incidents with context.
  • Build promotion workflows (dev → staging → prod) with automated tests on transforms and compatibility checks for ontology changes.