data engineering in 2025: json schema engineer
write json schema. validate json schema. debug json schema. find out prod has been silently coercing nulls this whole time. write more json schema. that's the job
19
write json schema. validate json schema. debug json schema. find out prod has been silently coercing nulls this whole time. write more json schema. that's the job
senior schema engineer. principal schema engineer. staff schema engineer who gets paged at 2am when the vendor changes their api. the levels are real
and then upstream sends you a field that changed from int to string and your schema validation passes because someone set additionalProperties to true six months ago
schema drift is the actual job. the engineering is 20%, the other 80% is finding out why the field name changed from user_id to userId three months ago and nobody told you