> Markdown version of [/jobs/ext/4748765-platform-data-architect](https://www.wearedevelopers.com/jobs/ext/4748765-platform-data-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Platform Data Architect - **Company:** Stellic Inc. - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Databases, Relational Databases, Software Debugging, Student Information Systems, SQL Databases, People Soft, Banner Advertisement, Workday - **Published:** November 16, 2026 - **Apply:** https://startup.jobs/platform-data-architect-stellic-com-10236678 ## About the Role You've spent years inside student information systems and you learned early that the hard part was never the SQL. You know that "we freeze terms in March" changes what the data looks like three systems downstream, and you'd rather find that out in the first conversation than at go-live. You're credible with a registrar and a database admin in the same room, you write your own queries, and you document what you build because you've inherited work from someone who didn't. And when the same problem shows up twice, you'd rather change the pattern than fix it again., * 5+ years working hands-on with student information systems, either inside a university or building integrations against them. * Real depth in two or more SIS platforms, with PeopleSoft as one of them. Banner, Colleague, Workday, Jenzabar, Power Campus, or a homegrown system all count for the second. * Proficiency in SQL & RDBMS. You've built the queries, understand schemas, nuances of datatypes and can do debug queries on your own. * Data modeling instincts, and feeds that had to keep running. Scheduled extracts rather than one-time pulls. You design an integration that's still correct three terms from now, and you think about the hundredth university rather than just this one. * Ability to learn new, unfamiliar SIS/ERPs quickly. Every organization has a different flavor of software even when it's the same vendor. It's critical that you understand and figure out integrations for specific implementations. * Credibility with both sides of the house. You can explain a blocker to a registrar in terms they can act on, and argue a data model with a DBA in the same afternoon. * Great at writing documentation. This role deals with a lot of communication, explaining and clarifying. We prefer writing documentation as a repeatable solution over one-off advice. Clear written documentation is key to a successful delivery. * Willingness to travel for partner onsites, a handful of times a year. ## Description * The integration for a named set of universities. You own them from the first data conversation through to a signed-off feed, and you stay with them afterwards. Product Delivery Leads own what gets built on that data. You own the data itself. * New partner deployments, end to end. Source discovery onsite or remote, writing the queries, standing up the feeds, validating the output, and getting a registrar to sign their name to it. * Upgrades and migrations for partners already live. Every feature we ship means going back through the institutions already running on the platform and bringing them forward. * The translation between policy and data. Turning how an institution actually operates into an extract that reflects it, and catching the mismatch before it reaches a student. * The visibility that keeps data problems out of your inbox. Defining what the team needs to be able to see, in inspection and in logs, so a Product Delivery Lead can tell what a feed is doing without coming to you first. * Standardization over one-offs. Documentation, patterns and decisions written down, and the integration pain we hit repeatedly turned into a standard approach, so the next university costs less than the last.