Implementations Jobs in Washington (NOW HIRING)

You’ve configured the SSO. You’ve debugged the Clever sync at 7 a.m. You’ve sat in the room when an integration didn’t go the way the kickoff deck promised and you’ve figured out what the deck didn’t say. Whether you did that work inside a school district or alongside one as a vendor, you know what it actually takes to land a K-12 technical implementation that doesn’t fall apart in month three.

That’s the kind of Implementation Engineer we’re looking for.

Every school district in America runs on service — parents need answers, teachers need support, IT teams need systems that work. Most districts cobble that together with disconnected tools, overwhelmed staff, and no real visibility into what’s working.

Onflo built the platform that fixes that. Our unified service platform brings together customer service, help desk ticketing, call center operations, AI chat, and IT asset management — purpose‑built for K‑12 public education. When a district runs on K12 Insight, their staff spends less time firefighting and more time serving students.

That’s the product you’ll be deploying, integrating, and standing up. It’s a good one. And the people who run it — district IT teams, operations leaders, superintendents — are trying to do something that matters.

You’ll own implementations. Not coordinate them — own them. From the kickoff call through validated go‑live and clean handoff to Account Management. You’ll know which districts are on track, which are quietly stalling, and which are heading toward a missed go‑live — before anyone asks. When the integration breaks, you’re already in the logs. When a district IT director throws a technical question you didn’t expect, you don’t punt to engineering — you work the problem.

• End‑to‑end implementation lifecycle — kickoff, configuration, integration, training, go‑live, and validated handoff
• Hands‑on technical work across SSO, SIS/ERP, MDM, and ticketing — partnering directly with district IT departments
• Diagnostic troubleshooting across the platform, integration layer, and client environment — independent, not engineering‑dependent
• Training delivery across stakeholder types, from end users to executive sponsors
• A clean, documented handoff that sets up Account Management for renewal and expansion from day one

We’ll be direct with you, because we think you’ll appreciate it.

The strongest candidates for this role come from one of two places. Some have spent their careers inside K‑12 district IT departments — configuring the systems, holding the line on integrations, and learning what good (and bad) vendor implementations actually look like. Others have spent their careers on the vendor side, delivering technical implementations into K‑12 districts and getting calibrated to vendor pace and accountability. Both backgrounds work here. What we can’t train into a candidate is the peer credibility you bring on day one with a district IT director — and that credibility is built either way.

K12 Insight is a small, entrepreneurial team. We don’t have a perfect playbook for everything. Priorities shift. Conversations can be intense. Communication isn’t always tidy. We know that — and we’re actively working on it. What we do have is a product that genuinely helps schools, clients who trust us, and a team that cares about doing the work well.

The people who do their best work here own their outcomes completely — no waiting, no excuses, no “that’s not my job.” They stay calm when priorities shift, surface problems before being asked, and hold themselves to a higher standard than anyone else would set for them. They’re technically curious — they get hands on a new platform and figure it out without waiting for training. They’re direct without being harsh, coachable without being passive, and motivated by the work landing well more than by recognition. They go the extra mile for a district not because it’s in their job description, but because letting someone down isn’t something they’re comfortable with.

If you’ve spent your career waiting for clear direction before you move — this probably isn’t your role. If you’ve spent it figuring things out and moving anyway — keep reading.

• 3+ years in either: (a) a K‑12 district IT role — systems administrator, identity/SSO administrator, SIS administrator, network administrator, IT manager, or IT director — with hands‑on accountability for vendor integrations and platform deployments; or (b) client‑facing K‑12 SaaS implementation, system integration, or solutions delivery, with hands‑on technical work — not project coordination.
• Hands‑on depth in at least one of: SSO/rostering (Clever, ClassLink, OneRoster); K‑12 SIS/ERP (PowerSchool, Infinite Campus, Skyward); K‑12 MDM (Jamf, Filewave, Mosyle, Intune); or ticketing and asset management.
• 1+ year working in K‑12 technology systems, including hands‑on data integrity and quality checking.
• Comfortable holding a peer‑level technical conversation with a district IT director.
• Technically curious — you learn new platforms by getting in and clicking around.
• Active Salesforce user and AI tool adopter.

The right person reading this already knows if they’re right for it. If that’s you — apply.

Expected Base Salary: $90,000–$110,000 / year + annual discretionary corporate bonus plan.

Onflo is an equal opportunity employer committed to building a team that reflects the diverse communities our clients serve. All are encouraged to apply. K12 Insight uses E‑Verify to confirm employment eligibility. Learn more at www.DHS.gov/E-Verify

The pay range for this role is:

90,000 - 110,000 USD per year (Onflo HQ)