Qualia

Qualia (formerly LocalResponse) empower brands with the ability to conquest consumers through intent targeting.

Marketing to consumers with ordinary tools is so five minutes ago.

The best way to reach today’s consumers is to move beyond devices and platforms to understand consumer actions, including posts, shares, check-ins, likes, hashtags, wishlists, couponing, e-commerce purchases, and more. Qualia is a pioneer and leader in discovering and delivering on consumers’ ever-evolving cross-channel expressions of intent. We effectively influence behavior across all devices, delivering true omni-channel campaigns.

Even as consumers act differently in reaction to new technologies, Qualia will be here to provide the latest and best in intent targeting, driving KPIs for brands as the evolution of targeting progresses.

In market since 2011, Qualia is led by Kathy Leake, CEO (co-founder Media6Degrees) and Niels Meersschaert, CTO (Founding Principal Architect of Magnetic) who are committed to defining the next generation of Intent targeting. Industry accolades include: Red Herring's "Top 100 North America," Inc. Magazine's "Top 100 Marketing Companies - Ranked #63," Inc. Magazine's "5000 Fastest Growing privately held companies" - Ranked #204 in U.S. and #19 in NYC Metro Area, and Forbes' "America's Most Promising Companies."

Qualia is headquartered in NYC and has offices in Chicago, Los Angeles and San Francisco.

Engineering & Product

We believe there is a difference between computer science and software engineering. Unfortunately, typical software interview processes ensure you have a computer science degree and ask algorithm questions on a white board, but never see if you actually know software engineering and how to go about building extensible code. In the real world, it's rare to write code on a white board. As an agile shop, we have weekly code reviews with the team. Since that's how we actually work, our interview process involves a code review as well. We want to see how you handle real-world software engineering. Why did you choose a certain design? How did you organize code? Why did you name that variable "a" instead of account_balance? How would you tweak the system if you needed to support this new feature? Is that less readable for performance reasons?

We're both idealists and realists. We know that software engineering is often about tradeoffs. There are many ways to solve a problem, but some are better than others based on other factors. We ensure that we've considered the options when we build our systems and thought about the future changes we may require.

Company trajectory

Qualia is only 3 years old, but growing very quickly. Our revenue grew 1600% from year 1-2 and 250% year 2-3. We're still on a great growth curve this year and looking for people to join the team and help us continue to grow.