Don't stay there for long - Dev Team
Pros
• Salary is always on time or even earlier. • Good place to start your career and learn from your peers and get exposed to different projects and use 1 year old coding and architectural standards. • Colleagues in some team love collaborating and helping one another.
Cons
All the following is from my experience in Victorylink, and dealing with the Dev team, it's not a review of Victorylink it's just my opinion about the Dev department and other related departments: • Low yearly appraisal and no adjustment after price changes. • Preference to hiring someone with higher salary, compared to increasing some of the current employee. - A newcomer with less responsibilities that another might be earning higher in terms of salary. It's all kept a secret. • Some Leaders and managers started to care less about working-environment, and are just focused on getting the employees to under control and micro-managed. • You are always either overloaded with work; not because there is too much work. They prefer to overload you so you can't just take a breather and think about the current situation or about developing yourself and your team. They want you to be so dependent on them. Otherwise you might find yourself doing almost nothing for 1-2 months in a row. - You'd be overworked in the beginning and the end of the year, then suddenly, you're just maintaining some projects and releasing, and even then you're asked to stay on prem. • No clear job description, you might find yourself doing stuff that you shouldn't be doing. (Translating app localization, Working with non-working deliverables) • You might be asked for daily reports or even hourly reports for both you and your fellow team members. • You can wait for devices for over 3-6 months and might last more. If it takes a while their solution is just to give you an old device. (No Mice and Keyboards) • If you get an upgrade for your device, you are expected to an increase inn delivery by X%. Even though your old device might be a 2015-2019 model, some even have no SSD hard drives. • Onboarding process is a mess, as a senior I was asked to have the new-comers work with no devices. And if the person works on their own device, then you'll find yourself doing it forever. • They don't want to address their problems, they think their way it's the right way of doing things and there is no need to change. • They work using a model which is worse that is neither agile nor kanban nor waterfall. It's a Frankenstein model that just wastes a whole lot of time. To make up for the wasted time you're then pushed to overwork. • As a senior you might find yourself in a position to either over-work your developers to catch up with the mis-aligned goals and deadlines. If you don't you will be blamed a bit even if you're on par with deadlines, any other late delivery because of another team will be your team's fault. • Some Managers and leaders hide deadlines even if you are trustworthy and deliver on time. Some might even tell you the delivery dates, however, they are non-realistic designed to stress you and over-work you and then if you finish; you'd find the real delivery in weeks/months. • Your appraisal criteria is gauged by how much of extra hours you do (unpaid), and how fast you deliver. • Some managers micromanages you even in tasks, as well as asking for project status on an hourly basis. • Some people get treated different than others: allowed to come later, get more benefits (overtime, late attendance gets covered for with HR, deduction removal and even remote options for a few months, even early appraisals). • Some employees in the Business and Innovations team, aren't flexible and don't accept opinions easily. You are provided you with a SRS document which can be as long as hundreds of pages and might not be updated regularly. Sometimes you aren't given enough time to even read it before starting development. Moreover, the experienced team members are constantly leaving. • If you do what some of the managers wants, even if it's harmful to your fellow team-mates you get treated in a great way. Although, there were some which had the tables turned upon them even as they were just doing as they were asked to do. • As you have the responsibility of developing the solutions as well as releasing them, you are early in the Software development Life cycle process, and you are at the end of it as well. You are affected by any late deliveries from the other teams in other departments as well as your department. You might find yourself being scolded for late delivery even though it's another teams fault. That case happens a lot in the some members of theQA team as well as the some of the back-end team. • Some Back-end teams do not test or add data (empty responses) for the delivered APIs, so it falls upon your shoulders to test their administration tool as well as enter data, and in the end the endpoints might be failing. So you're delivery rates will be affected as well and you will blamed for it. • You might get communications through mail (official and documented) and zoom, your personal phone, Whatsapp (non official and not documented). Moreover, it's a norm for some to call you after working hours. - You might agree on some deliverable but if it wasn't send on mail then it didn't happen. • Some of the QA team is inexperienced as the team-members tend to learn the ropes then leave, to seek out better opportunities. So you are constantly working with new-comers. • I think they have no reason to keep all employees on-site especially when currently their main goal is to cut costs. (Eliminated coffee, tea, breakfast, allowance, even toilet papers). In my honest opinion it's just to micromanage you and overwork you but I might be wrong. Note: All these points might differ from team to team.