About the role
<div class="trix-content">
<div><strong><br>Innovate, Excel, Succeed with Our Team!</strong></div><div>
<br>The Center for Outcomes Based Contracting seeks an outstanding contractor to build the data infrastructure that powers how we track, analyze, and act on student outcomes at scale.<br><br>
</div><div>The Center for Outcomes Based Contracting (OBC) is designed to foster partnerships between school districts and service providers, with the goal of improving student outcomes. At the Center for OBC, we are not just innovating educational contracts; we're transforming the way school districts and service providers collaborate to improve student outcomes. Established with the mission to uphold excellence and opportunity for all students in K-12 education, the Center for OBC empowers districts to contract for clear student outcomes and compels mutual accountability for achieving them.</div><div><strong><br>The Opportunity</strong></div><div>We're looking for a contract Data Engineer to build the foundational data infrastructure that supports and connects the Center's core systems: the OBC Data Dashboard (powered by Lumen and built in partnership with Littera), our data warehouse (to be built out in Snowflake), and Salesforce (our CRM for relationship management). This is a greenfield opportunity to design and build data pipelines that will power the Center's analytics and relationship management for years to come. Part of that opportunity includes thinking critically about where emerging tools (including AI-native data tooling) could augment what we're building, not just connect what already exists.<br><br>
</div><div>This is not a role where you'll receive a detailed technical spec. You'll work directly with subject matter experts who understand deeply what data they need and how it should be structured — but who have varying levels of technical knowledge. Your ability to listen carefully, ask great questions, translate business needs into working infrastructure, and then verify that what you've built actually solves the problem is as important as your technical skills.<br><br>
</div><div>
<strong>What You'll Do<br></strong><br>
</div><div><em>Month 1: Build the Foundation</em></div><ul>
<li>Conduct discovery with the Center's team to map existing data flows, understand the contract and relationship data model, and identify integration points across the OBC Data Dashboard, Snowflake, and Salesforce, including gaps in what data is currently being captured that could be valuable to collect</li>
<li>Architect our data model from scratch and describe how data will flow between Snowflake and other sources, including Salesforce and eventually a backend</li>
<li>Design and build data pipelines that move contract data, provider data, and district relationship data from the Data Dashboard into Snowflake for analysis and visualization</li>
<li>Build integration pathways from Snowflake into Salesforce so the team can manage relationships with current, accurate data</li>
<li>Document everything — architecture decisions, pipeline logic, configuration, and operational runbooks — so that whoever maintains and extends this work (including potentially you) — can do so without guesswork</li>
</ul><div><em>Month 2: Extend and Roadmap</em></div><ul>
<li>Refine and harden the pipelines built in Month 1 based on team feedback and real usage</li>
<li>Develop a technical roadmap for future data infrastructure development, organized by workstream (e.g., additional integrations, reporting automation, data quality, back-end infrastructure for future product development, and emerging tooling worth evaluating)</li>
<li>Present the roadmap to the Center's leadership with clear prioritization, effort estimates, and recommendations</li>
</ul><div><strong>Who You Are</strong></div><ul>
<li>
<strong>Experience gathering requirements from non-technical stakeholders </strong>and translating business needs into working data models and pipelines. </li>
<li>
<strong>Hands-on experience building data integrations and pipelines between systems</strong>, using whatever tools make sense (Python, dbt, Fivetran, Airbyte, etc.). You've done this enough to know what breaks and how to build something reliable.</li>
<li>You’ve designed and built data architectures from scratch, and you know how to make decisions that will scale well into the future. </li>
<li>
<strong>Familiar with cloud data warehouses</strong> (Snowflake preferred; Redshift, BigQuery, or Databricks also relevant). Comfortable writing SQL for data transformation.</li>
<li>
<strong>Salesforce integration experience </strong>is a plus. If you've worked with Salesforce's APIs before, you'll have a smoother ramp-up — but if you haven't, you can learn what you need.</li>
<li>
<strong>Curious about the evolving tooling landscape.</strong> You follow how AI-native data tools are changing what's possible in pipeline development and data capture, and you can offer a grounded point of view on where they add value versus where they introduce unnecessary complexity.</li>
<li>
<strong>Strong documentation practice.</strong> When this engagement ends, your documentation is how we will evaluate the work. You can point to past examples where someone else maintained or extended your work using your docs.</li>
<li>
<strong>Experience designing and building back-end infrastructure. </strong>Even if you haven't built full production backends, you should be able to look at the Center's current setup and propose a coherent technical direction.</li>
<li>
<strong>Comfortable making technical decisions independently and explaining your reasoning clearly.</strong> The Center doesn't have an engineering team. You'll have a technical consultant providing oversight, but day-to-day you're the decision-maker, and the team will want to understand the "why" behind key choices, not just the outcome.</li>
</ul><div><strong>Engagement Details</strong></div><ul>
<li>Type: Short-term contract engagement (with potential for future project-based work under separate agreement)</li>
<li>Duration: ~2 months, based upon completion of defined deliverables</li>
<li>Commitment: Estimated level of effort of 15-20 hours/week; schedule determined by contractor to achieve outcomes, with availability for occasional meetings from 10 am - 5 pm ET</li>
<li>Desired timeline: beginning June 2026 (June-August)</li>
<li>Location: Remote</li>
</ul>
</div>
<p>This is a remote position.</p>
This page is fully interactive when JavaScript is enabled. Please enable JavaScript to apply or browse related roles.