Practice By Numbers Senior Software Engineer salaries in India

Likes

- Nothing to like over here - Good pay as compare to other start-ups

Dislikes

- Firing on same day. They won't let you know the reason why they are firing you. They don't even let employee complete their minimum notice period of 7 days. No Job Security at all - There are 16 CCTV cameras installed in entire floor. No privacy at all. Cameras have mic too so any conversation between employees is recorded & used against them while firing - Very high attrition rate. Considering the organisation opened its office in Gurgaon, India in the month of February, they have fired half their numbers by now. Very clearly, the management is not in their right minds - Very suffocated environment. They haven't released a single Sprint successfully till now since February & blames IT team for that. Poor vision & lack of proper implementation

Likes

Near metro station

Dislikes

...n listened in on conversations! (obviously via mics installed in the workplace). Apparently, salary raises weren't a thing he liked to discuss - lots of yelling every time. The official workday ended at 6, but guess what? 10-hour days were the norm, weekends sometimes too, and forget about getting paid back for that extra time. Broken promises were the company motto. They weren't making money from India Dev Center, so the CEO decided salaries were charity and told us to forget about the performance appraisals we were promised during hiring. Even the basic stuff was lacking. The office was packed - like, 30 people in a space meant for 10! with no cafeteria to even eat comfortably. The coffee situation was questionable (powdered milk, anyone?), and the office staff wasn't exactly helpful. Getting hot water felt like a daily quest. And guess what? No dedicated toilets in the office, so we had to resort to nasty public restrooms. Not exactly a recipe for employee well-being. And, don't get me started on the Engineering Head, that guy is useless, he doesn't even know what's CSS (like really?) and he's the leader (the CEO has appointed) we should be looking to if we end up in a problematic situation like merging wrong branches. Does he even know what git is? After all this, they still forced us to write positive reviews on Glassdoor. The tech side of things was a mess too. The code was buggy as heck, and pointing fingers was the go-to move. Nobody shared knowledge, and taking risks was a big no-no. People were more worried about saving their skin than actually innovating. Asking the higher-ups for help just got you ridiculed. Code reviews were a joke, and if something went wrong in production, guess who got blamed? The Devs or QA, of course, sometimes even fired. This past year has been just miserable. PS: They recently started responding to reviews here. While it's good to see them engaging, don't get influenced by this, they're just trying to boost their rating. This is a facade, why? Just go and check the ratio of "likes" on these reviews. Negative reviews are getting significantly more traction than positive ones. You do the math, they have a really bad habit of putting forced positive reviews.

Likes

The office's proximity to the metro station made commuting convenient.

Dislikes

...se of unprofessional language with some employees, conveys a demanding attitude. This includes instances of yelling to maintain control, possibly as a strategy to discourage salary hike discussions. Despite official working hours being 9-6, employees are expected to work a minimum of 10 hours on weekdays and sometimes on weekends as well with no comp-off. Moreover, the CEO frequently emphasizes that the Indian center is not yielding profits, leading to a refusal of promised half-yearly appraisals, directly contradicting what was communicated during the hiring process. He thinks salary payments are an act of charity rather than fair compensation for our services. His attempts to manipulate ratings by encouraging management to write favorable reviews add another layer of concern. 5. Workplace conditions: Basic amenities are lacking, showcasing a focus on cost-cutting at the expense of employee comfort. The workspace is overcrowded, attempting to accommodate 50 people in a space meant for 20, creating cramped conditions. Additionally, the quality of coffee and tea provided is questionable, being made with milk powder rather than fresh ingredients. The office boys's unhelpful attitude further exacerbates the situation. as simple tasks, like obtaining hot water, become unnecessarily challenging due to reluctance and questing. The absence of dedicated toilets within the workplace forces reliance on unsanitized public facilities, posing a considerable challenge to employees' well-being and comfort. 6. Code quality and collaboration: The codebase exhibits subpar and unoptimized practices, riddled with bugs that compromise the software's functionality and user experience. Rather than focusing on constructive solutions, there is a tendency to blame others, impeding team morale and collaboration. Knowledge transfer is virtually nonexistent, with the prevailing mindset being, "You're an engineer, figure it out yourself." The fear of taking risks and implementing improvements hinders progress, as individuals here prioritize self-preservation over innovation. Additionally, obtaining information from leadership is accompanied by taunts, creating an unwelcoming atmosphere for communication. Despite the use of numerous technologies, none seem to function optimally. The workplace lacks a favorable environment for knowledge acquisition. Code reviews are not taken seriously, and in the event of production issues, developers are often targeted for blame, potentially leading to termination.