As we kick off 2014 we wanted to introduce the BrightGauge Team to our community of customers, partners, friends and family. Over the next few months we’ll share more info about each of them but in the mean time, here's a little summary of each of us.
Steve works with our customers focusing his efforts mainly on support with a secondary responsibility of consulting engagements. His main goal is to make sure that all of the support requests we receive get addressed as quickly and thoroughly as possible. If you submit a question to our team you will most likely meet Steve!
David is responsible for the front end of our software application, which means all the screens you interact with are his responsibility. So when you click a button and it takes you to another page, or runs a job, that’s all David’s work.
Larry works with all of our prospective customers as they are evaluating our software. Larry isn’t your typical “sales guy” that you only work with before signing up. Since his background is in the education space he likes to work with our customers after they sign up to make sure they are getting the most out of the product.
Eric is one of our two co-founders (along with his brother Brian) and he is responsible for all of our sales, marketing, educating our customers, communicating with our customers as well as some boring finance stuff like following up on expiring credit cards. Eric was the lead of our former MSP and we tap his experience to help our customers with the data and metrics they should be monitoring.
Brian is our other co-founder and the one responsible for originally coming up with the idea of BrightGauge. He plays a variety of roles but primarily he’s the Product Manager helping manage the development team along with helping customers with any custom work required. His passion for BrightGauge is evident when you speak with him and he loves hearing feedback so feel free to share.
Orlando is one of our lead developers and knows the backend of the application better than anyone. He handles our bi-weekly releases and doubles as 2nd and 3rd level support if there is a major issue. When he’s not supporting the code base, he helps architect new projects and features as well as implements them.
Christian is our lead architect which means he’s working with Orlando on any high level issues that might pop up but he spends most of his time working on new projects that we have on the roadmap. Christian has experience with Big Data projects and products and is helping us prepare our infrastructure to scale as we grow.
We are a tight group of 7 that work very hard on making sure our customers have the best possible experience.
