About Matt Signorello

I started by building the whole thing.

The product. The infrastructure. The pitch. The support queue. The team came later, and eventually became the work I cared most about building.

Home base

Sparta, New Jersey.

Husband, dad, and persistent tinkerer.

I live in Sparta with my wife, daughter, and Lucy. Our basement is part arcade, part workshop, and part technology lab, which probably explains more about me than another list of professional credentials.

Outside work, I restore pinball machines, collect and repair retro games, experiment with homelab and soldering projects, write, and run. I enjoy understanding how systems fit together, fixing what does not, and leaving things more useful than I found them.

Map of New Jersey marking Sparta in the northwestern part of the state

The throughline

Each step taught me a different part of building something useful.

Building the whole solution introduced me to customers. Working with customers pulled me toward sales and delivery. Supporting products showed me how operational choices shape the user experience. Leading connected products brought teams, technology, and business priorities together. Each step made the next one feel less like a pivot and more like a natural progression.

Professional evolution

Five chapters. One operating instinct.

  1. 2005 - 2011 Builder

    ISPBX, LLCCo-Founder & Owner

    My successful failure taught me the whole system.

    I co-founded ISPBX with a school colleague and my father when VoIP was still new. Using open-source tools, we built VoIP hardware and a graphical interface, sold and supported the systems, and ran colocated infrastructure that provided calling services. It did not make us millions, but it survived, made some money, and taught me how an end-to-end technology business actually works. Borrowing from Apollo 13, I think of it as my successful failure.

    When you build, sell, host, and support the product, every decision eventually comes back to you.
    • Whole-product thinking
    • Customer proximity
    • Ownership
  2. 2010 - 2013 Customer translator

    Matthijssen, Inc.Business Development Representative

    The hunt was another kind of building.

    ISPBX taught me how much I loved the sale: finding an opportunity, understanding the problem, shaping the solution, writing the proposal, and pitching the idea. At Matthijssen, I applied what I had learned about sales, marketing, and practical solution design to a wider range of managed-services customers.

    A good sale begins with curiosity and ends with a solution people believe will work.
    • Solution selling
    • Customer discovery
    • Proposal building
  3. 2013 - 2016 Team builder

    DataMotion, Inc.Director of SaaS Implementation & Support

    I was given the keys and expected to make things better.

    DataMotion gave me my first real opportunity to build and lead a team. I scaled the function, mentored people, and worked directly with enterprise customers while remaining hands-on. We built out the data-center stack, implemented virtualization, handled late-night software upgrades, and owned the regulated SaaS implementation and support experience end to end. It was my first real taste of being trusted to create meaningful change, and the long nights were worth it when we delivered what our customers needed.

    Leadership started with ownership: give the team direction, stay close to the work, and do what it takes for the customer.
    • Team building
    • Enterprise delivery
    • Technical ownership
  4. 2016 - 2024 Product leader

    Volvo Cars USAManager / Senior Manager, Connected Car

    Everything I had learned was tested at a new scale.

    I never expected to stay at Volvo as long as I did. After years in small businesses serving small-business customers, Volvo brought me into a methodical, technology-driven international company and a whole new world, literally and figuratively. It became the first real test of bringing everything together: thinking like an owner, selling ideas, rallying people, supporting operations, earning trust, and growing a team. The organization grew into double digits as I led remote developer teams, learned new skills, and shipped connected products including EV charging and customer self-service. It was one of the longest and most rewarding chapters of my career, and I left the team and systems better than I found them.

    Scale made me dangerous in the best sense: I learned what success looks like and how people, process, and tools work together to reach it.
    • Leadership at scale
    • Global product delivery
    • People, process, and tools
  5. 2025 - Now Organization leader

    Justin Alexander GroupDirector, Digital Products & Engineering

    Building the team became part of building the product.

    Today I lead Product Owners, UX, engineering, partners, digital platforms, customer journeys, CRM and data integrations, analytics, and AI-assisted tools. The work is increasingly about creating the ownership, operating rhythms, information, and trust that let teams make better decisions without waiting for one person to solve everything.

    Good leaders do not collect every decision. They build teams capable of owning them.
    • Operating models
    • Empowered teams
    • Measured outcomes

What stayed constant

Build for the customer. Understand the system. Give people ownership. Expect accountability. Make room to learn when something fails.

Read my operator's notebook