Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Company A or Company B

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,
I am new to this forum so if there is any mistake in posting please ignore it.

I have just completed my computer engg and got job offers from two companies i.e Company A and Company B. But I am unable to decide which company should i go for Company A or Company B.
Company A is a product based company so it will give me good experience about insights of product development
Company B on other hand service based IT giant which again gives me different exposure...

So I am really confused which company should i go for ..... my main objective is learning and career growth

please help me
 
Ranch Hand
Posts: 65
  • Likes 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

gaurav sh wrote:
So I am really confused which company should i go for ..... my main objective is learning and career growth



You should go for the product base company anytime

I am working in India's one of the top service based MNC for over 2.5 years and presently I am desperate to quit my job. All the service based companies are same where most of the top level technical people (not all, exceptions are always there but the numbers are very few) such as module leads, team leads, etc would hardly do some technical work and will bump everything on you along with a strict deadline. They will pretend that they have got lots of process related stuffs to do but I have seen them hardly doing anything. They are here to become manager (their ultimate goal) and then ride on developers head. Even I have seen a few leads who used to go for unplanned leaves for months whenever they see something really difficult coming their way or some client escalations are on their. I had a very poor experience with a branded MNC and willing to quit ASAP once I get an alternative job.

On the other side, it also depends on the project you are working and how are the technical senior members in your team. In a service based company, if you are stuck with a project that you don't like then you won't get release from that easily (your wish does not matters for the managers, hence they never release employees easily until you do some blunder). There are very few employees in my organization who are enjoying their work but most of the employees are frustrated and willing to quit their job anytime they get a better alternative.

Best of luck with your decision
 
gaurav paul
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What exactly the main problem is that the product based company is based on telecom domain (it is best in that domain) and i fear that my will get limited to that domain....
On the other hand, service based company can give me experience of multiple domain.... so i would get good knowledge ...

The counter point is that there are very few product oriented companies in market (specially in India) as compared to service based company... so working for product based company would give me an insights of their process , standards followed them , their software engineering model etc..

because these two points i am unable to decide between the two

any help would be highly appreciated
 
Anthony D'Souz
Ranch Hand
Posts: 65
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

gaurav paul wrote:What exactly the main problem is that the product based company is based on telecom domain (it is best in that domain) and i fear that my will get limited to that domain....
On the other hand, service based company can give me experience of multiple domain.... so i would get good knowledge ...



Yes I agree the fact that domain knowledge is important...but I will clear your misconception.

Service based companies does have multiple domain but you will be working in a single domain for most of the time. Even if you are released from the project, your domain won't be changed and they will try their best to retain you in that specific domain rather than replacing you with someone who does not have any idea on that domain.

Hence, once you complete the training and join the production unit, at that time whatever is your domain; you have to work on that throughout with very few exceptions.

Now coming into the telecom domain, what if in the service based company also you are put into telecom domain? It is not in your hands right

Still telecom domain is better since I have seen quite a few telecom based product/service based companies growing big these days and recruiting IT people; personally i feel it won't be a bad option. In a service based company, you have the danger to be put into such a domain in which other MNC or service providers hardly have some clients (I am such a victim and my domain is not at all known to other MNC /service providers).
 
Rancher
Posts: 2759
32
Eclipse IDE Spring Tomcat Server
  • Likes 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Generally speaking, if you are a consultant, you get exposed to a lot more technologies. If you are an employee at a well established product development company, you get exposed to a lot more processes. If you are an employee at a startup, you get exposed to everything. What is right for you depends on which path you want to take.

When you are a consultant, you are essentially going to a new job every 3-6 months. You get exposed to how differrent companies do things, and you get to learn a lot of technologies. Flip side, is that you have to learn a new technologies pretty quickly, and your client will expect you to hit the ground running. They are not going to train you. Your employer might train you, but don't count on it. You learn a lot, but you have to be ready to learn quickly and on the job. You can expect the client to ride you pretty hard, because they are paying for you a lot more than they pay their employees, and they will try to get their money's worth.

When you are an employee at a product company, you "belong" there. They will treat you as family. This means that if they are a good family, they take care of you, and if they are not they will abuse you, and most probably will do both. This means that they will take the time to train and mentor you. Also, since you are part of the family, you will be more exposed to the kind of decision making processes that consultants are kept away from. You will also get an opportunity to build your soft skills. If you stay there long enough, you will get to know why things are done a certain way, not just how things are done.

IMO, if you have the opportunity to pick one of the 2, and you are frsh out of college, go for the consultancy, and build up your resume. You are young. You don't have a personal life. You can work 12-14 hrs a day, right? What else you have to do? Go on a date?. Geeze!! Once you resume is built up, work for another 5 years in a product development company, and learn the in and outs of software development. Expect your technical skills to lag.. which is ok.. 5 years of going through the fire in your previous job should make you confident enough to pick any technology quickly. Now you have 10 years of experience, your technical skills are top notch, and you have a lot of soft skills built up, go work for a startup. The startup will either be succsfuly, and you will be a millionaire, and you retire; or it goes bust, and you just go work for another startup. Startup surf for 5-7 years more, and if you aren't a millionaire yet, go back to becoming a consultant again. Except that now, you are some kind of architect consultant, who goes around telling people to not burn their water, or something like that.

And that my friends is what I call the recipe for a successful software career

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Jayesh A Lalwani wrote:Generally speaking, if you are a consultant, you get exposed to a lot more technologies. If you are an employee at a well established product development company, you get exposed to a lot more processes. If you are an employee at a startup, you get exposed to everything. What is right for you depends on which path you want to take.

When you are a consultant, you are essentially going to a new job every 3-6 months. You get exposed to how differrent companies do things, and you get to learn a lot of technologies. Flip side, is that you have to learn a new technologies pretty quickly, and your client will expect you to hit the ground running. They are not going to train you. Your employer might train you, but don't count on it. You learn a lot, but you have to be ready to learn quickly and on the job. You can expect the client to ride you pretty hard, because they are paying for you a lot more than they pay their employees, and they will try to get their money's worth.

When you are an employee at a product company, you "belong" there. They will treat you as family. This means that if they are a good family, they take care of you, and if they are not they will abuse you, and most probably will do both. This means that they will take the time to train and mentor you. Also, since you are part of the family, you will be more exposed to the kind of decision making processes that consultants are kept away from. You will also get an opportunity to build your soft skills. If you stay there long enough, you will get to know why things are done a certain way, not just how things are done.

IMO, if you have the opportunity to pick one of the 2, and you are frsh out of college, go for the consultancy, and build up your resume. You are young. You don't have a personal life. You can work 12-14 hrs a day, right? What else you have to do? Go on a date?. Geeze!! Once you resume is built up, work for another 5 years in a product development company, and learn the in and outs of software development. Expect your technical skills to lag.. which is ok.. 5 years of going through the fire in your previous job should make you confident enough to pick any technology quickly. Now you have 10 years of experience, your technical skills are top notch, and you have a lot of soft skills built up, go work for a startup. The startup will either be succsfuly, and you will be a millionaire, and you retire; or it goes bust, and you just go work for another startup. Startup surf for 5-7 years more, and if you aren't a millionaire yet, go back to becoming a consultant again. Except that now, you are some kind of architect consultant, who goes around telling people to not burn their water, or something like that.

And that my friends is what I call the recipe for a successful software career



Well written ! But, I need to devote sometime to my girlfriend also
 
Without deviation from the norm, progress is not possible - Zappa. Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic