Jim Catts is a Co-Founder & CTO at Rhythm Software at Rhythm Software. He possess expertise in saas, software development, microsoft sql server, .net, soa and 46 more skills. Colleagues describe him as "Jim is one of the most capable and thoughtful people I’ve worked with. He is not only a great system architect who has built highly scalable, data-intensive, always-on SaaS solutions but he can jump in at any level and diagnose performance problems, find the trickiest bugs, and code solutions. Jim brings a breadth and depth of knowledge across the AWS spectrum. He is able to match the application needs to the right AWS services to reduce spend and increase reliability. Our solution was sophisticated, making use of relational and noSQL data, queueing, workflow, and analytics. Jim designed it so we could scale out to add capacity and we never had downtime. For all of Jim’s capabilities, he is remarkably humble and a pleasure to work with. He is a great teacher, and I learned a ton about AWS working with him. Any team would be fortunate to have Jim on their side.", "If you need a short answer, I will recommend Jim Catts as a welcome addition to any team. I would like to put emphasis on the fact there are no specifics around what that team would be for, what type of team it would be, or even what sector the team would be working in. It would not matter, Jim would still receive my recommendation. I don’t intend to go into the skill set Jim has, which is extensive, or his level of expertise within that skill set, which is high, you can look at any of his other recommendations if you need to see that. My intent here is to focus on what makes it so easy for me to vouch for Jim in any situation and that is who he is as a person. First, Jim is extremely likable, I say this from the perspective of both a subordinate and a peer. This makes it easy for him to hop into any team and become an integral part of it. Second, Jim is empathetic. He understands what drives people and why they feel the way they do. In a position of leadership this allowed him to manage people effectively without dealing with misunderstandings. Third, Jim is adaptable. Jim is quick to learn, and faster to understand. This allows him to come into a new field and become an expert on the matter. Last, Jim has common sense, or put another way, he is self-aware both in a business setting as well as socially. This might seem like something trivial but, in my opinion, can make or break a team. This common sense allows him to make properly informed decisions without creating unrealistic goals for his team. It fosters a team that can achieve what they set forth to do and where everyone understands the “why” of what they are doing. The above traits are not confined to any specific business, technology related or otherwise, and define why I would be willing to recommend Jim for any team and believe the team would be better for it.", and "Working with Jim was fantastic. The best I've worked with. He set great technical vision for our product and lead the engineering team to incorporate new technologies and constantly push the boundaries of what we could do. As Director of Product I worked closely with Jim to redesign the front end of our application. It was during this project I developed an appreciation for how talented Jim is. In particular, 3 things stood out: 1. Jim is very in tune with what customers are trying to accomplish. He understands their business, the nature of the challenges the face and what will be the drivers of their future success. He was my go to person when I would start to validate ideas and stories. 2. Jim is always looking forward and scouting new technologies that can move the needle for us and our customers. He is always looking to increase performance, experience, or wow factor of the product. Jim constantly learns about technology and does small experiments with new tools and then brings them to the team for ideation. 3. Jim is a great teacher. It is important for non-technical staff, such as me, to understand what a piece of technology does, the difference it makes, or could make, and the benefits/consequences of implementing it. Jim is the best I've ever worked with at this. He explains tech clearly and simply and in a way that focuses on why you we should or shouldn't consider it, vs. rattling off features and technical nuances."