Working with an Outsourced Developer

Ever wondered why most companies fail in their road towards web or software development? I understand the bold statement I made there but hear me out. There is something I would like to share what I have experience working with an Outsourced Developer.
Today marks the fifth-month working with an outsourced developer from India. I was assigned to project manage a dynamic web application using Javascript framework, React.js.
A little background about the client, they are well versed and detail oriented people. They are super meticulous on the project requirements and specifications. In the very beginning, I thought, it would be excellent for me because it will reduce the trouble to deliver the message to the outsourced developer.

“Let’s just call the outsourced developer by Miss A.”

The project started out in good fashion. All the requirements are given, and most of the items are well briefed. I assumed we move off to a great start. Unfortunately, I was wrong…
I run the project in an agile method. Meaning, whenever there’s need for change, we will concurrently update client and get further feedback on what needs to change. Along the way, Miss A seems to miss out many important key factors of the task required to do. It appears to look like I need to spoonfeed every information for her to do a simple task.
For example, there one task that requires her to do up a simple landing page with a simple email sign up form. I told her to follow exactly the same as the mockup that I have prepared for her. All she needs to do is to strictly follow the mockup and refer to the UI Style guide (given to her prior to the project). But she didn’t!
At this day and age, responsiveness is a norm to all websites. It may be something new few years ago but all business websites should be responsive at the very least. I just don’t know what Miss A was thinking back then.

“In the end, I have to tell her again and again until she gets it.”

And that is time-consuming for sure. Sigh.

Another thing that we should take note is their national holidays. India has plenty of public holidays! Meaning, if you need to get things done urgently and it’s their public holiday, all the best to you. You can only hear them back on the next working day. Sigh.

At this point in time, the project is still ongoing. Our actual deadline is March. Unsurprisingly, its April now. It’s the matter of waiting for the client to turn into a devil.
So in conclusion to my experience working with them – I do not quite like it. Language is indeed a barrier. It took them awhile to understand the certain task. Style of work is not comprehensive. They do not look into the project in a holistic manner. If I were to list out the brunt of their work, there are plenty.

“In the end, I have to tell her again and again until she gets it.”

But I’m going to stop here. I am not going take everything from them. They can still do the job. It’s just the manner of them doing it. I am not referring to all Indian developers, but I have quite a number of feedbacks from other companies that hired them said the same thing too. So what does that tells us?
They might be charging us cheap but I guess the price speaks for itself. Low quality work. Perhaps there are those who are skilled and easy to communicate ones – you are looking at 1 out of 20? The rate that they set is ‘spoil market’. It appears to look like they’re degrading their development work.

Enough of my rant, I would like to know what is your experience like working with outsourced developers. Comment down below and let me know. I’m out.


Working with an Outsourced Developer

time to read: 10 min