11 - 25 employees
< 10 engineers
$5m - $10m funding
Series a

InformedK12 transforms how district departments and school sites work together through our workflow and reporting platform. Problems we tackle include helping principals hire the best teachers faster, managing bus routes for students without permanent housing and ensuring teachers get reimbursed and paid on time. Most excitingly, we are helping district decision-makers unlock critical operational insights from data that has been historically trapped on paper.

We are powering the future of school district operations by enabling administrators to gain operational insights that drive productivity, accountability and equity.

InformedK12 photo 1 InformedK12 photo 2 InformedK12 photo 3

Why join us?

  • We've increased revenue by over 50% every year since we started selling in 2015. We have great customer retention and have net negative churn as our customers expand to larger and larger contract sizes (ie: a deal that grows from 15K to 150K.)

  • User research drives our business and product by enabling us to drive deep value for our customers. Along with other team members across the company, our engineers go onsite to see our users in their environment and also participate actively in remote user testing and research.

  • We have 100% test coverage :)

Engineering at InformedK12

Engineering team and processes

We work in small, nimble teams of 2-3 engineers. We have a bi-weekly standup meeting and use Clubhouse to manage our projects and tasks. Projects that each team takes on range from real-time search and export tools, database and server optimization, or building our front end system. We do planning on a quarterly basis and some projects take a few months, while some 6 months to a year. When you join you will probably end up getting to work with everyone on the team at some point.

We take code quality seriously and are constantly improving our codebase. Every project we work on has dedicated time to address tech debt and we prioritize code quality initiatives on our product road map. Oh, and we never ship code without writing a full suite of tests (don’t worry, we’ll help in case this is newer to you)!

Technical Challenges

We are building a workflow and reporting platform that has to be powerful enough for support hundreds of unique approval processes in a school district but easy enough for anyone, from the Chief Business Officer to a school site office manager, to use.

Our users work at all levels of the district in district office departments ranging from finance, payroll, HR, custodial services, transportation, food services and more. They also work at individual school sites as principals, teachers, substitutes, counselors, and even parents. To meet the needs of this wide variety of users, there are thousands of unique forms and processes on our system that span from new hire packets to student injury reports to bus services requests to permission slips. Our backend models need to be flexible enough to support a wide variety of use cases but structured enough to allow for scale and data retrieval across the entire system.

Other technical challenges may relate to:

  • Data security and privacy, as our forms may collect sensitive information

  • Customized bulk data exports in a variety of formats (csv, pdf, zip)

  • Seasonality and spikes of system usage - 1/3 of our total traffic for the year occurs in the rush up to the start of the school year, in August and September

Finally, because our districts rely on us for their critical processes we must ensure our system is reliable and stable. The team understands that working code is not enough and a primary component of an engineer's job is to improve the maintainability of the long-term structure of the system.

Projects you might work on
  • Form/user permissions system - We recently wanted to add a new user type with restricted access to features and data, but realized our access logic was not totally consistent throughout the application. In order to ensure the same behavior wherever a feature was exposed via a front-end page or backend authorization we refactored our permissions model using a set of rules tied to feature names. Now we have a centralized place to configure access for each feature, and can easily understand where each feature is used and modify the application experience for each user type.

  • Whiteboard - Our front-end component system that was built from scratch.

  • Auto-detect - We created a separate gem from our main codebase to use image detection/OCR to recognize lines on a document so we can automatically place fields for user input on the documents our users upload.

Tech stack
Ruby on Rails

Working at InformedK12

Everything we do at Informed K12 starts with an unwavering commitment to the people who run our nation’s school systems. We also deeply believe in building a different kind of tech company.

Our core values:

Build, don’t disrupt: We seek to deeply understand and build long-term value for our districts; we don’t strive to “disrupt” or break things in the traditional Silicon Valley sense.

Unreasonable quality, uncommon results: We place a high premium on quality because we understand the important impact our work has on districts.

People first: We care deeply about our district partners and each other as people . We seek to build a truly diverse and inclusive environment so our employees can thrive as their authentic selves.

Know when to go rogue: We’re not afraid to think for ourselves and break from traditional wisdom in order to find what works in our context.

Perks & benefits
  • Maternal/Paternal Leave
  • Flexible Hours
  • Work from Home
  • Beautiful Office
  • Company Retreats
  • Health Insurance
  • Team Activities
  • Other

    Company-wide volunteer/community activities

Our Team by the Numbers

Interested in this company?
Skip straight to final-round interviews by applying through Triplebyte.