Senior Software Engineer, Komodo Health

• Significant experience optimizing data retrieval processes supporting API output, as above, ideally within a low query volume / high data volume environment
• Demonstrably deep experience with Python
• Experience designing APIs for use in web application development (synchronous vs asynchronous response patterns, caching strategies, etc)
• Experience with separate caching/cache invalidation strategies, particularly tiered strategies for highly variable unit volumes of data
• Experience with multiple relevant data storage platforms, and the ability to understand the benefits of drawbacks of each for specific types of read patterns (‘data lakes’ like S3/Hive-based systems, RDBMS, MPP platforms, KV/doc stores, etc)
• Strong communication with engineers, product managers, data scientists, and commercial teams

Desirable

• As a member of the team responsible for Komodo’s standardized approach to healthcare cohort generation, you are ensuring that every product in our catalog has a standard, performant approach to meeting their core data needs
• Mission: This role is primarily backend-focused, but ties into the end-to-end function of the complex cohort generation queries served through the cohort generation API, ensuring adherence to SLAs, and for the underlying caching necessary to support the variety of distinct access patterns across our entire product suite
• Promote API versioning best practices and open API standards in development
• Partner with product managers to understand the variety of internal and external cohort specification needs across a diverse set of use cases
• Ensure non-functional requirements are met, such as around developer experience and maintainability
• Manage tasks at an epic level to both raise the standard of engineering and continue to move new & existing functionality to meaningful mini/micro-services
• Set a high technical standard overall and be a mentoring resource for others on the team
• Looking back on your first 12 months at Komodo Health, you will have accomplished…
• Expanded or enhanced the UCC API’s internal data model to ensure timely performance for all types of cohort generation requests
• Designed and optimized caching strategies (including, perhaps, the inclusion of new data storage mediums/platforms) for cohort output, differentiated as needed to serve multiple distinct read patterns from consumers
• Recommended and implemented additional pre-calculation and caching strategies as needed to ensure that SLAs are met
• Transformed our internal service layer used to serve cohort generation along various dimensions - patients, payers, providers, etc. through successful retrieval of our data