About the Engineering Team
Our engineering team is a carefully selected group of brilliant minds, many active in the open source community. They include musicians, artists, hockey players, fathers, wives, outdoorsmen, and electronics makers, and each are so passionate about technology that it's a focus inside and outside of their work — and it shows! Technical or not, there's a strong chance that you've used a product one of our team members created. Hiring locally and nationwide, half of our team lives in the ever-growing Nashville, and the other half is distributed coast-to-coast. Through tools like Slack, Google Hangouts, and Screenhero, our team stays in close contact every day.
There are also countless opportunities for the team to expand their professional careers. We partner with Nashville Software School and the Nashville Technology Council on various events (both organizations are located in the same building as our Nashville office). We've attended conferences like Nodevember and React Rally, and we've had speakers at local meetups such as Girl Geek Dinner and NashReact.
What is the team building?
Our business involves moving huge amounts of data through real-time processing to match our customers with the technical products that will make them successful. We build tools to help make this process faster, more efficient, and more accurate. We open source everything we can on our Github and occasionally we blog about it.
What tools does our team use?
Everything we do is version-controlled on Git and deployed to AWS. Our backend is service-oriented, written mostly in Node.js and deployed into Docker containers and AWS Lambda functions. Our frontends are almost entirely static, with all applications being single-page apps deployed to Amazon S3 and Cloudfront. We use React, Redux, and have recently launched Stardust, which has become the official Semantic UI component library for React. We follow Git Flow, believe strongly in TDD, and rely heavily on CI/CD practices. Our engineers use a mix of Mac and Linux with the editors or IDEs of their choice, working mostly out of a local Docker-based development environment supported by DevLab.