EdTech platform serving thousands of students with adaptive learning. Cross-platform Flutter apps, Go microservices, and a Rust core.
Senior Software Engineer
● nowOct 2022 — Present · 3 yrs 7 mos
- ›Ship across the full Tutero stack — Flutter clients, Go microservices, and a Rust core. Roughly 5,700 commits over 4+ years across the monorepo.
- ›Building a new whiteboard product — Flutter front-end with a Rust core via FFI. Worked on freehand drawing, shape tools, and AI-assisted whiteboard tooling.
- ›Handled a cross-cutting error-handling migration across 14+ Go services (eris → fault → oops) — done in coordination with the team, with zero production regressions.
- ›Reworked the lesson-plan generation backend — moved from a legacy skill-plan model to a sections-first API now consumed by every client.
- ›Re-architected the snapshotter pipeline to render on the client across multiple apps — meaningful cost + performance wins.
- ›Built curriculum CSV import APIs, contributed to the schools app layout system, lesson-plan editing flows, and 2FA + admin overhaul.
- ›Reorganized notification tooling into a provider-based architecture; contributed to shared tooling for code generation, Neo4j edge ops, and Firebase migrations the rest of the team uses.
- ›Comfortable across Flutter/Dart, Go, Rust, Neo4j, and Postgres, plus NATS / Kafka / Kubernetes glue.
FlutterGoRustNeo4jNATSKafkaKubernetesGCPGraphQLgRPC
Flutter Developer
Oct 2021 — Oct 2022 · 1 yr
- ›Joined the early Flutter team and helped lay down foundations of the main student app — onboarding, design system, brand language, and a shared widget library.
- ›Worked on a clean-architecture migration of the main client app — restructured the codebase into use-case driven layers the team continues to ship on top of.
- ›Took on a Firebase dependency upgrade and module-instantiation refactor across the monorepo — unlocked safer DI patterns for new features.
- ›Started crossing from client into backend: helped introduce a code-generation pipeline, refactored Neo4j edge operations to use a provider pattern, and contributed to the first version of an internal Neo4j tooling library.
- ›Contributed Flutter and monorepo conventions still in use as the engineering team scaled.
FlutterDartFirebaseNeo4jCode Generation