Mômô Goudarzi: technology and community operations

Selected projects

Things I build
and use myself.

01

Niki

A multi-tenant platform for the administration of Italian nonprofits. It manages members, volunteers, board terms, assemblies and Third Sector compliance.

Live demo
React · Hono · Workers · D1
02

Dossier My fork

My fork of an open-source, self-hosted resume builder. I added a refine chat that tailors one application, a flow that sends new facts back to the profile, visual theme settings and server backups. I built it with AI coding tools.

Original project
Next.js · PostgreSQL · MCP · Ollama
03

emo

A native planner for Mac, iPhone and iPad. It puts your tasks around your fixed commitments. Each day, you record your energy level, and the planner sets the tasks to match it.

SwiftUI · SwiftData · Foundation Models
04

lexicon

A tool to learn languages. Paste a text, and a local LLM adds information to the words that you do not know. Then review these words with spaced repetition.

React · Dexie · Ollama
05

Social media blocklist

A list of social media and messaging domains in hosts format, for Pi-hole and other DNS filters. Use it to block social media on a network.

Shell · Pi-hole
More projects on GitHub

Experience

Backend work
and nonprofit work.

01 / Software & teaching

  1. Software Engineer, Backend & Cloud

    Glue Labs · 2023 – 2025

    I owned the backend and cloud of two in-house products: Pupau, an AI agent platform, and Baghera, an HR platform. I was also the only backend engineer on 5+ client projects, and on call.

    • Made a critical query ~90% faster by tracing it to a data bug upstream.
    • Led the split of a monolith into microservices on Kubernetes.
    • Added Keycloak SSO to Apache Superset without forking it.
    • Client integrations: PDND for PNRR projects, payments, chatbots, e-commerce and warehouse APIs. One public example is Easy Plan.
    • Taught a backend course to 20+ developers and mentored an intern.

    TypeScript · NestJS · Java · Python · GCP · Kubernetes · PostgreSQL · Kafka

  2. Software Engineer

    Orbyta Technologies · 2022 – 2023

    I built REST APIs and microservices on Microsoft Azure for public transport clients. I led dependency security audits with Snyk on 4+ production codebases (Java dependency trees and Docker base images). The client teams adopted my prioritized remediation reports.

    Java · Spring Boot · Angular · Azure · PostgreSQL

02 / People & operations

  1. Vice President & Secretary

    Dialogue Explore Bond · 2024 – 2025

    I was the contact person for ~50 volunteers, members and board members. I helped create the volunteer HR area, which did not exist before: intake interviews, training, recognition and growth paths with one-to-one follow-up. Volunteers moving into board roles went from ~2 to ~6 a year. I built a referral network with 7 Turin Third Sector organizations, including Arci and ACMOS, and it is still active.

  2. IT & Systems Coordinator

    Dialogue Explore Bond · 2023 – 2024

    I set up the workspace, knowledge base and documentation, and managed accounts for ~50 users with documented onboarding and offboarding. I met the non-technical volunteers one by one, and active use of the tools went from ~5 to ~30 volunteers in 12 months. I also ran a full GDPR and Third Sector compliance review and handed it to my successor.

  3. Treasurer

    Dialogue Explore Bond · 2022 – 2023

    I managed the ~€7,500 annual budget and built a treasury team, which did not exist before, then trained the volunteers who took it over. With the board, I co-wrote the yearly funding applications to Politecnico di Torino (up to ~€10,000) and kept audit-ready records for the funds.

MSc Cybersecurity Engineering
Politecnico di Torino · 2026 – now
BSc Computer Engineering
Politecnico di Torino · 2019 – 2023 · 97/110
Languages
Persian (native) · English (C2) · Italian (C2) · French (A2)

Why I build



I grew up inside systems that had already failed the people in them. So I don't get excited about new tools. I ask who they're for, who gets left out, and who pays.

New things land on a world that's already there. Where work burns people out, it burns them out faster. Where a few already hold the opportunities, they keep more of them. Where care is left to unpaid people, they carry more of it.

I studied chemistry before computer engineering, and Le Châtelier's principle still shapes how I think. Disturb a system and it pushes back to the same balance. Speed it up and it just gets there faster. The only way to a different balance is to change the conditions it lives in. That's the work: not absorbing whatever happens to us, but changing what happens next, together. See it in practice ↓

Software engineer · Nonprofit operations · Mental health advocate
Turin, Italy

Mômô Goudarzi
Mômô Goudarzi

Le Châtelier in practice

Every system
pushes back.

In chemistry, a system at equilibrium pushes back against anything you do to it. Add more, take some away, squeeze it: under the same conditions it returns to the same balance, the equilibrium constant. A catalyst only gets it there faster. Only a change in the conditions, like the temperature of a reaction, moves the balance itself. Pick a disturbance and watch both happen.

1×
Conditions

At equilibrium

Atoms turn into each other at the same rate both ways, so the amounts stay level. That balance is set by the conditions. Pick a disturbance.

01 Disturbance

A product team ships an AI assistant that answers customers’ questions from the company’s own documents.

02 How the system pushes back

  • Stale docs, served fast
  • Confident wrong answers
  • Nobody owns the sources
  • Side tools nobody approved

03 What I change

  • Clean and date the sources before they are indexed.
  • Give every source an owner who keeps it current.
  • Test it on the questions people really ask, not on demos.
  • Keep a person on every decision that matters.

AI is a catalyst: it gets a team to the balance it already had, only faster. Change the balance first.

01 Disturbance

A critical vulnerability lands in a dependency, or a credential leaks.

02 How the system pushes back

  • Panic patching
  • Blame
  • Everyone locked out
  • Alerts nobody reads

03 What I change

  • Keep secrets out of the code, so a leak takes minutes to rotate.
  • Patch by real exposure, not by the severity score alone.
  • Write a blameless post-mortem, so people report early next time.
  • Make the safe path the easy one: SSO and least privilege.

Locking everything down after a leak is push-back. Making the safe path the easy one is a new condition.

01 Disturbance

A foundation opens a grant call with a short deadline.

02 How the system pushes back

  • Project bent to fit the money
  • Partners on paper only
  • Budget doesn’t match the work
  • Indicators nobody measures

03 What I change

  • Start from the needs analysis, then check whether the call fits.
  • Tie each goal to a real task and a person who owns it.
  • Bring in partners with a real role and a line in the budget.
  • Ask the people it was for whether it helped.

Bending the project to fit the call is push-back. Starting from the need changes the conditions.

01 Disturbance

Two people in a group clash over how something should be done, and the work stalls.

02 How the system pushes back

  • Sides form
  • People go quiet
  • Gossip instead of feedback
  • Someone leaves

03 What I change

  • Find out who owns the problem before anyone tries to fix it.
  • Listen actively, and say back what I heard before I answer.
  • Speak in I-messages: what I see, how it affects me, what I need.
  • Look for a solution both people accept (Gordon’s no-lose method), then agree on a check-in.

Taking sides is push-back. A shared way to resolve conflict, that everyone knows, is a new condition.

01 Disturbance

A volunteer group moves its chats, files and sign-ups into one shared platform.

02 How the system pushes back

  • WhatsApp is still the real channel
  • “I’m not technical”
  • Two places for everything
  • Only ~5 people use it

03 What I changed

  • Document every flow, including onboarding and offboarding.
  • Keep one place for each kind of information.
  • A year later, the platform is still the one place people look.

A new tool on old habits settles back into the old habits. Change where the work lives, not just the tool.

Don’t fight the push-back. Change the conditions.

06 Ideas · this page

A new idea arrives.

  1. 01 Disturbance

    Someone says it could be different

    Who care is for, who work serves, who gets a say. This page is one of those voices.

  2. 02 Push-back

    The system pushes back

    • “That’s just how it is”
    • “Nice, but not realistic”
    • It becomes a slogan
    • The people pushing it get tired

    Left alone, things settle back where they were.

  3. 03 What I change

    So I change the conditions

    • Make it a habit. Something people do every week, not just agree with once.
    • Build it in. Into the rules, the budget, who’s at the table.
    • Don’t carry it alone. A group survives one person leaving.
    • Pass it on. So it outlives whoever started it.
  4. 04 A new balance

    And this time it holds

    An idea on its own gets pushed back like anything else. It lasts when it changes the conditions: who decides, who gets paid, who’s in the room.

In 1978, Italy closed its psychiatric hospitals with the Basaglia law. It held in Trieste, where Franco Basaglia’s team had spent years building community mental health centres to replace them. Where nobody built those services, the reform stalled. The law was the disturbance. The centres changed the conditions.

If this resonates, let’s talk. No project needed, just a conversation :) Say hello ↓

Technology, people, or neither

Say hello :3
No agenda needed.

A project, a question, or just a chat with someone new. Some of my favourite people started as a random message, or a random encounter.

Don’t know how to start? Let’s break the ice.

How do you squeeze the toothpaste: from the end, or from the middle?

m.gdrzi77@gmail.com