There were a lot of pros once upon a time when Morningstar was not PitchBook.
All the admin folks get the Panther award.
Following the transition of the technology organization to PitchBook, the company has experienced noticeable attrition among senior technology leaders, including several experienced leaders from the India GIH team. This has created uncertainty among employees regarding the long-term vision for the legacy Morningstar technology organization and whether its people, processes, and expertise are valued equally alongside the incoming PitchBook teams.
There has also been a perception among employees that comparisons made by some PitchBook leaders have undervalued the capabilities of the legacy Morningstar technology organization, negatively impacting morale, collaboration, and employee confidence.
An AI proof-of-concept was completed for the Equity dataset collection nearly two years ago, with ambitious expectations to dramatically accelerate software delivery. However, the first meaningful production outcome reportedly took nearly two years to materialize, and many employees felt the results did not align with the expectations initially communicated. Concerns also remain around delivery timelines, solution quality, and the overall value being delivered to customers.
The return-to-office policy has also been a source of employee dissatisfaction. Many employees perceive an inconsistency in leadership expectations, where a senior leader continues to work remotely while requiring their direct reports to be in the office four days a week. This perceived double standard has raised concerns about fairness and leadership credibility.
From a technology perspective, modernization efforts appear uneven. Many private data collection processes continue to rely on legacy manual workflows, while significant effort has been invested in reworking areas that were already relatively automated. Employees question whether modernization priorities are aligned with the areas that would deliver the greatest operational value. Similarly, initiatives such as UDCP were presented as transformational, but many employees believe they did not sufficiently leverage the 10–12 years of institutional knowledge and domain expertise possessed by long-tenured Morningstar employees.
There is also a perception of inconsistent delivery expectations across global teams. Some teams appear to receive greater flexibility with delivery timelines, while the India GIH team is consistently expected to deliver at a much faster pace despite handling equally complex work. This has contributed to concerns about fairness, recognition, and workload distribution.
Another concern is the perceived lack of confidence in the Global Capability Center's (GIH/GCC) capabilities. Despite the global industry trend of expanding strategic leadership and engineering roles within GCCs, many senior leadership and critical technology positions remain based in the U.S. Employees question whether the organization is fully leveraging the depth of talent and institutional knowledge available within the India GIH. There is also a perception that the executive leadership team has not sufficiently challenged or revisited this approach.
As a result, many employees feel the organization is moving away from the mature, high-performing engineering model that Morningstar India had built over more than a decade, limiting opportunities for local talent to influence strategy and own key business outcomes.
Finally, employees have expressed concerns about leadership accountability. There is a perception that successful outcomes are readily attributed to senior leadership, while delivery challenges and failures are often pushed downstream to execution teams.
It would be helpful to evaluate concretely what revenue-impacting outcomes the Data Collection technology leadership has delivered since the transition to PitchBook.
There's also broader confusion among employees about the current organizational identity — many are unclear on which entity has effectively taken over, and whether the Morningstar brand/culture still meaningfully applies.
The interviewer was very much helpful. They provided me tips and motivated me. 1) Executor service and how it works 2) What is thread pool 3) Spring Boot 4) DispatcherServlet 5) Difference between deadlock and starvation 6) Create a singleton class
First initial introductory interview with HR followed by 2 levels of tech interview rounds. One with peer within the team and another with the global reporting manager. Overall good experience.
Total across 3 rounds (2 technical, 1 "get to know you") was surprisingly less than an hour. Response time after each one was quite fast (they have dedicated hiring managers).
The interviewer was very much helpful. They provided me tips and motivated me. 1) Executor service and how it works 2) What is thread pool 3) Spring Boot 4) DispatcherServlet 5) Difference between deadlock and starvation 6) Create a singleton class
First initial introductory interview with HR followed by 2 levels of tech interview rounds. One with peer within the team and another with the global reporting manager. Overall good experience.
Total across 3 rounds (2 technical, 1 "get to know you") was surprisingly less than an hour. Response time after each one was quite fast (they have dedicated hiring managers).