Do Freshers at Persistent Systems Have the Freedom to Choose Technologies?

When joining a tech giant like Persistent Systems, the initial enthusiasm can quickly turn into frustration when faced with the reality of project assignments. Many freshers encounter a lack of autonomy in selecting the technologies they will work on. Persistent Systems generally follows a structured onboarding process that includes training in various technologies. However, the extent to which freshers can choose their preferred technology stack varies based on the company's current projects, team needs, and available roles.

Rigidity in Technology Choice

Upon joining Persistent Systems, freshers often find themselves working in roles where technology choice is not entirely within their control. The company may assign them to specific teams based on their skills and the company's current requirements. While this approach can ensure that freshers are exposed to a wide range of technologies during their training phase, it can also limit their immediate ability to work on their preferred technologies.

Initial Training and Random Assignments

Typically, freshers are initially trained on any technology the company deems necessary based on the projects available at the time of hiring. From there, they are often assigned to projects randomly, leading to a mixed experience. Some freshers may end up on projects that align closely with their interests, while others may not.

Ancient Policies and Frustration

A recent interviewee at Persistent Systems shared a particularly frustrating experience during their initial days. They were asked to choose either JavaCPP or .Net for an MPC exam, but like many others, they quickly realized that their preference did not necessarily translate to their actual project assignments. The reality was that Java and .Net roles were more plentiful, thus delivering the majority of projects. Initial training often involved learning any technology deemed necessary by the company, followed by random project assignments.

Limited Project Changes

The inability to change projects before completing 18 months is a strict company policy. This can be particularly challenging for freshers who may find themselves struggling with a project they were not initially interested in. One freshener, despite being an enthusiast of C technologies, ended up working on Java projects. When they expressed their dissatisfaction to resource management, it was difficult to make a change.

Call for Change

After leaving the company, this freshener felt compelled to voice their concerns during an exit interview. They suggested that Persistent Systems should take more interest in the preferences of freshers regarding technology assignments. While it was acknowledged that not all freshers would work on their preferred technologies, it was recommended that efforts be made to align project assignments with their interests, at least after a few months of exposure to different technologies.

For accurate and up-to-date information, it's best to check directly with Persistent Systems or refer to their official recruitment resources.