Introduction

https://images.unsplash.com/photo-1506749841726-3df2e72b9564?ixlib=rb-1.2.1&q=85&fm=jpg&crop=entropy&cs=srgb

☀️ Highlights ☀️

💖  Take me to the application!

This might be the start of something great...


Hi, I'm Brian, co-founder & CTO of Chameleon. I lead all things technical and am looking to expand our distributed engineering team 👋🏻 🗺 💻

This is me, last summer, working in the garden of my backyard in Encinitas CA. I often find myself moving around the house through the day and enjoy taking meetings in a hammock.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/18f34122-f5c5-4208-9dde-7cab1583f737/IMG_7903.jpg

[https://s3-us-west-2.amazonaws.com/secure.notion-static.com/a2a93598-2187-42d9-b72d-55a399c185e1/Photo_on_11-3-20_at_15.24_2_(12420](https://s3-us-west-2.amazonaws.com/secure.notion-static.com/a2a93598-2187-42d9-b72d-55a399c185e1/Photo_on_11-3-20_at_15.24_2_(12420)

This is Ruby, named after Ruby on Rails and Chameleon's third co-founder (unofficial)

We started Chameleon after being frustrated at poor user onboarding, and feeling required to speak with sales before we could start using new products.

As engineers, we want to solve the hardest problems, and apply our creativity to design beautiful software. It's tedious to build and maintain tooltips, or banners, so we built Chameleon to let the product people handle that independently, while letting engineers focus on the core value proposition a product provides.

This approach has resonated and we now have a great product, happy customers, and traction.