Back to jobs

Staff Data Engineer

Pay
Pay not listed
Work setting
Hybrid — work setting source
Work setup in the employer’s posting: Hybrid
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting

Pearson Virtual Schools runs online K-12 programs, including Connections Academy and Pearson Online Academy, for students and families across the country.

We're starting a new Data Engineering group, and this is one of its first two hires.

  • You'll design and build how our data is secured and served to AI from the start.

  • Implement per-user and per-location access in BigQuery using row-access policies and column-level masking, so each person sees only the data they're entitled to.

  • Work that protects students.

From the employer’s posting
Pearson Virtual Schools runs online K-12 programs, including Connections Academy and Pearson Online Academy, for students and families across the country. Our data includes some of the most sensitive information there is: student assessment results and records protected under FERPA. As AI tools start working with that data next to our people, the access rules have to be right for both.
We're starting a new Data Engineering group, and this is one of its first two hires. You'll design and build how our data is secured and served to AI from the start. That means fine-grained access enforced in the data itself, plus a governed gateway, built on the Model Context Protocol (MCP), through which AI agents act as the user: same models, same permissions, one security model for people and AI.
Pearson Virtual Schools runs online K-12 programs, including Connections Academy and Pearson Online Academy, for students and families across the country. Our data includes some of the most sensitive information there is: student assessment results and records protected under FERPA. As AI tools start working with that data next to our people, the access rules have to be right for both. We're starting a new Data Engineering group, and this is one of its first two hires. You'll design and build how our data is secured and served to AI from the start. That means fine-grained access enforced in the data itself, plus a governed gateway, built on the Model Context Protocol (MCP), through which AI agents act as the user: same models, same permissions, one security model for people and AI. This is a greenfield, senior technical role. You'll be the go-to expert on data security and AI access, make the key architecture decisions, and mentor the engineers around you.
What you'll do Enforce access in the data. Implement per-user and per-location access in BigQuery using row-access policies and column-level masking, so each person sees only the data they're entitled to. Make purpose part of the policy. Design and build purpose-based access control (raw, anonymized, or aggregated data depending on the declared purpose), with policies authored in Collibra and enforced natively in BigQuery.
A rare greenfield problem. Secure, identity-aware AI access to governed data is still new ground, and you'll help define it. Work that protects students. You'll safeguard data that belongs to kids and families. Senior scope without managing people. You'll own the architecture as an individual contributor.
Apply at hccz

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 2026today
Recorded sightings
2
Last seen by us
Nov 19, 2026
Employer says posted
Oct 29, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 6 and day 56.

From 14,166 similar postings that came down. Coming down is not always a hire.

hccz is hiring

8 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • BigQuery
  • Collibra
  • Databricks
  • Snowflake
  • Trino
Where the posting names them
- Strong SQL, plus enough familiarity with a semantic / BI layer (LookML or similar) to expose it safely. - Python or a comparable language for service development. - Comfort working on your own in a greenfield setting and setting patterns others follow.
- Platform and integration engineering skills: you can build and run a service that handles authentication and passes user identity through to the data (OAuth or similar). - Strong SQL, plus enough familiarity with a semantic / BI layer (LookML or similar) to expose it safely. - Python or a comparable language for service development.
What you'll do - Enforce access in the data. Implement per-user and per-location access in BigQuery using row-access policies and column-level masking, so each person sees only the data they're entitled to. - Make purpose part of the policy. Design and build purpose-based access control (raw, anonymized, or aggregated data depending on the declared purpose), with policies authored in Collibra and enforced natively in BigQuery.
- Enforce access in the data. Implement per-user and per-location access in BigQuery using row-access policies and column-level masking, so each person sees only the data they're entitled to. - Make purpose part of the policy. Design and build purpose-based access control (raw, anonymized, or aggregated data depending on the declared purpose), with policies authored in Collibra and enforced natively in BigQuery. - Open a governed door for AI. Build an MCP service over our LookML semantic layer. AI agents authenticate as the user and inherit that user's access, with no separate back door.
What you'll bring - Hands-on experience with fine-grained security on a cloud data warehouse: row-level and column-level security, masking, authorized views, and IAM. BigQuery is ideal, and Snowflake or Databricks experience also counts. - A solid grounding in data security and governance: role- and attribute-based access control, PII handling, and anonymization / masking.
- MCP or other LLM tool-use / agent integrations; Looker API or embedding. - BigQuery cost governance. - Collibra policy automation.
- BigQuery cost governance. - Collibra policy automation. - Federated query engines (Trino / Starburst).
- Collibra policy automation. - Federated query engines (Trino / Starburst). - Experience with FERPA, HIPAA, or other regulated data.

Your next step

Complete your application on hccz.fa.em3.oraclecloud.com. The employer’s form will show what is required.

Applying through Oracle Recruiting

  • Applying starts by asking for your email address.
  • Each employer sets which files it accepts, so read the note beside the upload field.

Already applied? Track this application

Job description

View original posting ↗

Job Title: Staff Data Engineer

About the role

Pearson Virtual Schools runs online K-12 programs, including Connections Academy and Pearson Online Academy, for students and families across the country. Our data includes some of the most sensitive information there is: student assessment results and records protected under FERPA. As AI tools start working with that data next to our people, the access rules have to be right for both.

We're starting a new Data Engineering group, and this is one of its first two hires. You'll design and build how our data is secured and served to AI from the start. That means fine-grained access enforced in the data itself, plus a governed gateway, built on the Model Context Protocol (MCP), through which AI agents act as the user: same models, same permissions, one security model for people and AI.

This is a greenfield, senior technical role. You'll be the go-to expert on data security and AI access, make the key architecture decisions, and mentor the engineers around you.

What you'll do

  • Enforce access in the data. Implement per-user and per-location access in BigQuery using row-access policies and column-level masking, so each person sees only the data they're entitled to.
  • Make purpose part of the policy. Design and build purpose-based access control (raw, anonymized, or aggregated data depending on the declared purpose), with policies authored in Collibra and enforced natively in BigQuery.
  • Open a governed door for AI. Build an MCP service over our LookML semantic layer. AI agents authenticate as the user and inherit that user's access, with no separate back door.
  • Keep costs bounded. Put guardrails on AI and ad-hoc query spend using custom quotas, maximum-bytes-billed limits, slot reservations, and caching.
  • Design end to end. Work closely with our Senior Analytics Engineer (Semantic Layer) so security and the semantic layer fit together cleanly.
  • Make it auditable. Document security patterns and access procedures so the platform is easy to operate, review, and extend.

What you'll bring

  • Hands-on experience with fine-grained security on a cloud data warehouse: row-level and column-level security, masking, authorized views, and IAM. BigQuery is ideal, and Snowflake or Databricks experience also counts.
  • A solid grounding in data security and governance: role- and attribute-based access control, PII handling, and anonymization / masking.
  • Platform and integration engineering skills: you can build and run a service that handles authentication and passes user identity through to the data (OAuth or similar).
  • Strong SQL, plus enough familiarity with a semantic / BI layer (LookML or similar) to expose it safely.
  • Python or a comparable language for service development.
  • Comfort working on your own in a greenfield setting and setting patterns others follow.
  • Usually 8+ years in data engineering, data platform, or data security engineering, including leading at least one critical technical initiative.

Nice to have

  • MCP or other LLM tool-use / agent integrations; Looker API or embedding.
  • BigQuery cost governance.
  • Collibra policy automation.
  • Federated query engines (Trino / Starburst).
  • Experience with FERPA, HIPAA, or other regulated data.

Don't tick every box? Apply anyway. If you've secured sensitive data at scale and want to work out how AI should access it safely, we'd like to hear from you.

Why you'll love it

  • A rare greenfield problem. Secure, identity-aware AI access to governed data is still new ground, and you'll help define it.
  • Work that protects students. You'll safeguard data that belongs to kids and families.
  • Senior scope without managing people. You'll own the architecture as an individual contributor.
  • Shape a new team. As an early hire, your patterns become the group's patterns.

 

#LI-Hybrid

 

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 860, the most 1,353, and the latest week had 1,020.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Sri Lanka

- Shape a new team. As an early hire, your patterns become the group's patterns. #LI-Hybrid
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.