Team Architect Β· Senior Software Engineer Β· Connector
I build the conditions where teams can build anything β through technical excellence, clear collaboration, and systems thinking.
15+ years working across every layer of software organizations β engineering, design, QA, product, operations, eCommerce, and people management. I've held roles from Software Engineer to COO, moving between them intentionally to understand how organizations function as systems.
I am a Connector: I absorb ambiguity, bridge people and systems, and translate unclear business needs into actionable technical paths. Even when my title is Senior Software Engineer, I naturally operate beyond role boundaries β because that is how I work, not what the role requires.
I left a COO role when the organization asked me to stop prioritizing people and start treating them as cost lines. I chose integrity over advancement and returned to engineering β not a step back, but a realignment with my principles.
Most recently full-stack across Ruby/Rails (API), React (web), and Flutter (mobile) β focused on data infrastructure, cross-team coordination, and building reliable systems that enable downstream teams to move faster. Currently open to what comes next.
Most of my career story doesn't fit a standard job title. Here's what's been invisible:
Career paths that didn't exist β I've proposed and negotiated my own roles 4β5 times across my career. When there were no more steps, I defined the next one, took responsibility for it, and built the scope from scratch.
Organizational systems β At Crowd Interactive / MagmaLabs I grew from Apprentice to Principal Consultant (β Director-level IC) across 6 levels. Along the way I:
- Founded MagmaHackers (later BrightCoders) β a technical excellence community that outlived my tenure
- Designed Engineering Career Paths from scratch for the whole organization
- Built 1-on-1 processes, performance metrics, and coaching structures
- Introduced Radical Candor as a cultural framework
- Trained the organization across Agile, Lean, Design Thinking, UX/CX, QA, and product methodologies
Measurable outcomes as COO β NPS: negative β 99. eNPS: 10 β 95 in 6 months. Not by optimizing metrics β by actually caring about people while also understanding every technical and operational layer beneath them.
Two proprietary people systems:
- Custom Top Grading β a 6-step hiring methodology adapted from the 12-step original. Key insight: score candidates against your team's current average (5 = team average, not world average). Hire to always improve the standard.
- Performance & Potential Matrix β a 9-box talent review tool that converts subjective performance impressions into objective, values-aligned assessments across Mastery, Impact, Growth & Recognition, and Performance.
Most organizations try to deliver first and care later. I reverse that.
Care β Trust β Teamwork β Delivery
When teams care about each other and share openly, trust grows and collaboration becomes natural. This means:
- Observing human signals β engagement, silence, defensiveness
- Clarifying agreements β expectations, responsibilities, goals
- Introducing movement β breaking stagnation through structural change
- Encouraging sharing β creating safety for ideas, questions, doubts
- Building trust β the foundation that unlocks teamwork
Once those conditions exist, delivery tends to improve naturally.
This isn't soft management. It directly produced NPS of 99 and eNPS of 95. The numbers move when the human conditions are right.
/mumocβ My master knowledge repoCLAUDE.mdβ Master context file for AI sessionsmethod/care_to_deliver.mdβ The framework in detailprofile/career_raw.mdβ Deep career interview notesprofile/build-cv.jsβ CV generator script
Published on Medium at @mumoc β AI, teams, leadership, and the gap between activity and real outcomes.
- AI Doesn't Join Individuals. It Joins Teams.
- AI Can Run Your Workflow, But It Can't Own the Outcome
- If AI Makes Us Faster, What Should We Do With the Time?
- Accountability
- Empathy and Compassion: People Management
- Success
- Coherence and Communication
- On Processes, Agile, and Professionalism
- Working Remotely
- Ruby/Rails APIs β Backend systems design, data infrastructure, performance optimization
- React + Flutter β Full-stack development across web and mobile
- AWS/Docker β Infrastructure, CI/CD, containerization
- TDD & Testing β Discipline-first development approach
- AI Integration β Building Claude-assisted workflows into development processes
I'm actively building AI-assisted workflows and tools. My approach: define business logic first, structure work with clear acceptance criteria, then use AI as a peer β not a task runner. Rules, skills, and best practices are versioned alongside code.
Projects:
-
claude_bootstrap β Portable Claude Code configuration you can clone and bootstrap on any machine in one command. Includes a full agentic ticket pipeline: orchestrator β extractor β analyzer β challenger + risk assessment (parallel) β planner β validator. Features strict/soft/human gates, append-only shared state, loop-back recovery, and a complete skill suite for engineering workflow, Jira planning, and verification.
-
bmo β A voice-activated AI companion styled as BMO from Adventure Time. Listens via microphone, transcribes locally with Whisper, generates responses via Ollama, speaks via macOS
say, and animates a browser-based face in real time. Includes conversation context, long-term memory persistence tomemory.json, and interrupt detection. Built for joy β but technically grounded. -
CLAUDE.md system β Master context file that primes any AI session with my frameworks, voice, and working principles. Paired with MCP filesystem integration so Claude reads my local repo directly.
- Publishing on Medium β exploring human-AI collaboration, team trust, and the gap between activity and real outcomes
- Deepening AI integration into full-stack development workflows using Claude Code, MCP, and agentic workflows
- Refining my methods through hands-on technical work and team leadership
- Looking for the next fertile field β open to conversations about what comes next
A fertile field for sowing β a company early enough in its growth that I can help build the right cultural and technical foundations before wrong habits take root.
I've seen what becomes possible when organizations are built with care from the start. I've also seen what it costs to try to change a culture that has already calcified around its problems. I'd rather be there earlier.
Open to conversations about:
- Technical leadership β architecture, systems design, AI integration
- Team systems β culture design, career paths, organizational structure
- Consulting β team dynamics, hiring methodology, performance frameworks
- Mentoring β engineers navigating technical growth and leadership transitions
- Speaking β AI integration, team trust, and technical leadership
Trust before authority. I've earned trust before I had a title, every time. The title confirmed what everyone already knew. The real value is always the journey.
Care is strategic. Empathy and compassion are not soft skills β they're foundational strengths that drive engagement, retention, and business outcomes.
Mistakes are data, not identity. I extend the same compassion to my own failures that I extend to others. Growth is collective.
On hiring: in a 1β10 rubric, 5 means your team's current average β not the world's. Hire above that number and you raise the standard. Hire below it and you lower it. The goal is always to improve.
AI joins teams, not individuals. The most valuable thing AI is doing inside organizations right now isn't productivity. It's giving people a reason to ask for help. And that's bringing teams back together.
Accountability can't be automated. Execution can. Judgment can't. Direction can't. As automation expands, accountability becomes rarer β and far more valuable.
Systems matter more than heroes. Most teams don't fail because people are incapable. They fail because the system stopped moving. Build the conditions. Let people excel.
- Email: mumo.crls@gmail.com
- Medium: @mumoc
- LinkedIn: linkedin.com/in/mumoc
- Based in: Colima, Mexico π΄
Let's build something together. If you're thinking about team dynamics, technical excellence, or how to integrate AI thoughtfully into your workflow, let's talk.




