Pros
none. Kansas based interns preferred.
Cons
This is a small company with very limited processes and standards, and whatever standards exist are rarely followed. There is little to no proper documentation, no effective Scrum Master, no story-pointing, and no clear technical leadership hierarchy. If you come from a company with mature engineering practices, it can be very difficult to adapt and work here.
A non-technical product manager largely drives decisions, while senior technical leadership is mostly uninvolved. Your experience heavily depends on the product leader you are assigned to—if that leadership is weak, it becomes extremely challenging to succeed.
The HR function exists mostly in name only, and reporting concerns is unlikely to lead to meaningful action. While there are a few good managers, working with them is mostly a matter of luck rather than structure.
Stories are assigned with minimal or no context, and there is no concept of backlog grooming or refinement. The architecture is outdated, the codebase is largely legacy, and documentation is almost nonexistent. Genuine technical input is rarely appreciated or acted upon.
This environment may suit very junior employees or interns who are comfortable simply following instructions, but it can be frustrating for experienced professionals who value structure, collaboration, and modern engineering practices.