Pros
- Real, complex problems to solve in philanthropy. - A few engineers were thoughtful and collaborative. - If managed right, can actually support good social impact
Cons
My experience: Culture needs intention: Day-to-day felt tense rather than supportive. Calls often ran hot, and time wasn’t always respected. Everyone seemed a bit afraid of making the wrong move, which slowed progress. Nice people, light experience: Many teammates are good humans but relatively inexperienced for modern product/UX execution. The org hasn’t really invested in culture, coaching, or repeatable practices. Product roles without product backgrounds: Several product managers/owners came from non-product, non-tech areas (e.g., accounting) and were still learning product thinking. Decisions were slow, debates long, and it was hard to get crisp product direction. Not design/research-driven: This isn’t a UX- or data-driven company. You’ll need to provide heavy guidance and frameworks yourself. Research tools, structured discovery, and evidence-based decisions were limited. Old-school delivery: Legacy products and “how we’ve always done it” often overruled good UX rationale. Getting consistency across multiple systems without resources felt unrealistic. Interview/onboarding signals: My long technical interview was entirely verbal (no portfolio/case review), and one interviewer was notably disengaged. Later, a simple one-week start-date shift request was declined with little discussion—felt needlessly rigid.
