Pericent Reviews

Thank you for this — and for the specificity. "Real-time projects, backend development, server-side management" is exactly the kind of work we want every engineer here to be able to name when describing what they do. Not theoretical. Not training exercises. Live systems, live clients, real consequences. Your cons and your advice to management are three of the most constructive pieces of feedback we have received in a public review and I want to address each one directly. On heavy workload during server maintenance and critical deployments — this is honest and accurate. Go-live periods and production deployments for enterprise clients carry genuine pressure and that pressure concentrates on the backend engineers who own server stability. We are working to make these periods more predictable through better release planning and earlier staging environment testing so that the intensity is bounded rather than open-ended. It is a real area of improvement and we are not done yet. On streamlining internal workflows and communication — agreed. As we have grown, some of our internal processes have not kept pace with the team size. We are formalising sprint documentation, communication protocols, and cross-functional handoffs this quarter specifically to address the friction you are describing. On structured technical training and transparent appraisals — both points are taken seriously. We are building a formal technical development track for engineers at every level, and we have committed to making the appraisal framework — KRAs, performance criteria, promotion thresholds — visible and documented for every team member before the next cycle. You should not have to guess what growth looks like here. That is a fair expectation and we will meet it. Less than a year in and already contributing to production systems at this level — that trajectory is exactly what Pericent's engineering function is built to produce. Keep building. — Sanjay Sharma, MD · hr@pericent.com

Thank you — At our stage of growth, the people who have been here three to four years are not just employees — they are the institutional memory, the technical foundation, and the culture carriers of everything Pericent is building. The fact that you describe the culture and environment as excellent, and your colleagues as genuinely supportive, tells me that what we have been trying to build is actually being experienced — not just described in a document. The collaborative engineering culture you have described is not accidental. It is the result of a team that has worked through sprint cycles, production deployments, client go-lives, and technical challenges together — and chosen to support each other through all of it rather than retreat into individual silos. That is something the people in the team have built as much as the leadership has, and your three to four years of contribution to that culture is part of why it exists. On workload — your framing is exactly right. Project cycles in enterprise software are inherently variable. Go-live periods and sprint closes carry more intensity than steady-state development. What matters is that across the arc it remains balanced — and we will keep working to ensure that it does. Three to four years of building real products for real enterprise clients. That is a career foundation that will serve you well wherever you go. Thank you for building it here. — Sanjay Sharma, MD · hr@pericent.com