Leave the current job and accept the new offer?

[mary jacobson]

Hi,

Currently I am working for a small company where I started as a java programmer and moved on to different areas (like javascript, actionscript and macromedia related tools), I do use java for flash remoting classes but not as much as I want to. (only 10% of coding is done in Java). I do have fun, because they are very flexible with my timings. so I work 10 to 12 hrs one day then I can take off next day and I have fun at work. Problem here is : Not much as coding in java as I want, since small company not following good practices, (requirements change until delivery)which I hate, only 2 people team (me and my coworker).

There is a big firm in our city and yesterday they asked me if I would like to come for an interview, I applied to this company 2 years ago and they did not even know that i am working now, they need someone for jdbc (sql server) applications and all the other projects will be with JAVA. and also I have opportunity to go for training, presentations etc. What should I do? I am very confused.

Salary comparison, right now I am getting 40K with no benefits but the big firm has offered 50K with benefits (401K) I have not gone for the interview yet, but I told them I will let them know if I want to consider by tomorrow.

Currently this company is depending on me for almost everything, if I leave this company I would feel guilty because they may loose few projects. I have UML, comments for the work I did.

please give me your suggestions.. I am going crazy.
[ April 29, 2005: Message edited by: mary jacobson ]

[ali haider]

I say go for it. You are lucky to get a higher offer in salary in the new firm. Mostly on changing from a small firm you get a pay cut. Plus, if you dont move now, later this experience will work against you. Work with small firms is not as recognized as good names in the industry. Can I ask how much experience you have .... ?

[Jayesh Lalwani]

How much experience do you have? From your post I gathered that you are just starting out. I think if you are just starting out, you should try to get exposure in technologies that you are most interested in. There is a chance that the new job won't be as much fun, or it might be more fun. The important thing is to keep your goals in mind. At this point, you can afford to change jobs every year or so. 5 years down the line, prospective employers will look at whether the candidate changes jobs often. But, if you have just 1 or 2 years experience then it's ok to change till you find a job you like.

And don't worry about leaving your current company. It's their responsibility to discuss your career goals with you and work something out that will help you acheive your career goals and get their work done. There is a differrence between a person and a work-horse. People have goals. You should not be stuck doing a job that you don't like. If you are really feeling guilty, you can talk to the manager and tell them that you are not getting what you expected from this job, and you are looking for a change. If they don't want to work something out, then you are clear, right? If they do work something out then you get best of both worlds, right?

[Anselm Paulinus]

The small firm will not wink to fire you when it is time to lay off, so do not think you are indispensable; they just have not found a better person who is ready to do your job for less than the 40K you are currently making.

The more risks you take the more returns you get;
Going to the big firm with the associated uncertainties is a risk worth taking; guess what, the name and goodwill of the big firm will sell you at the end of the day.

[Henry Wong]

Well, it can't hurt (or at least, it shouldn't) to go on an interview (call it an informational interview). Find out all you options so that you can weight them.

Henry

[mary jacobson]

Thank you very much for replying.

I asked the new company to send the job description, it starts with requriement collection to automated testing. and in desire skills, they look for java web development. They have scheduled my interview later next week. (I am a graduate student too, so i have finals and the next day this interview)

here are my questions:
1) Interview is 5 hrs long, this is the first time I will be having interview this long, what happens? will they ask me to write a test. (The new company is in USA, I live in USA)

2) Interview starts with breakfast, here I am vegetarian, should I let them know before hand

3) How do I prepare for this interview?

4) What kind of questions should I ask them?

Thanks again,

[Mark Herschberg]

You should definately strongly consider the new job. Unless the company culture isn't a fit, everything about it sounds better. Not only are the pay and beenfits better, but the long term opportunities are better. You generally have more opportunities at a larger company (or maybe smaller but growing company). It sounds like you skills and learning will stagnate. Early in your career it is especially important to have good mentoring. Also, from a technology standpoint, while I recommend learning many different technologies, it sounds like you're doing more web forms than hard core programming. That may limit career choices later.

To answer you specific questions...

1) You'll meet iwth many people. They may give you a test, they may not. I've done all day interview where I just meet someone new every 30 minutes. Other times with a 3 hour interview I've had a test. You'll just have to take it as it comes.

2. Yes--although they'll probably have bagels and juice. They're unlikely to have meat products, so you're probably safe if you don't want to tell them. It sounds like you may have lunch, too.

3. Relax. The worst that can happen is you don't get it and you're no worse off than before. Do you best. Worrying about it will only work against you.

4. Try this thread.

Good luck.


--Mark

[David Harkness]

One thing that really helps me relax in interviews is focusing on your goal: you are attending the interview to find out if this company interests you or not. Sure, you'll answer their questions about your skills and background, and you'll be polite and respectful and present a good personality. But don't let that distract you entirely from asking plenty of your own questions.

Do the people interviewing you like the company? Are they excited about it? Would they join again if they weren't working there already? Does the company have a culture that encourages professional development? Do the people in positions of power have ethics compatible with your own?

Asking questions like these tells them that you're interested. It's like being on a date and showing interest by asking them about themselves instead of blabbing on for four hours about yourself.

Oh, and I would definitely ask about breakfast and/or lunch. Let them know that you do not eat meat and want to know if you should bring a snack for yourself. If they weren't planning on having non-meat choices, you better believe they'll make sure to have something. Most considerate people wouldn't tell you, "Yes, bring some crackers because we're going to be eating steak and eggs."

Good luck!

[mary jacobson]

Thanks for your reply Mark and David,

I have interview with 3 different people each an hour and an hour with HR person and an hour for breakfast.

Is it ok to ask them about what kind of professional opportunities they have to improve my self in the company?

The big firm has been doing really good because they have gained profit (it was on the news)

thanks,

[Mark Herschberg]

Originally posted by mary jacobson:
[QB]
Is it ok to ask them about what kind of professional opportunities they have to improve my self in the company?
[QB]

Most definately. Think about being there for 5 years (or maybe longer), and where you want to be in 5-10 years. Tell them where you want to be and ask them if the jobs they can give you (this first one and then other positions you'll advance into, or other skills you'll learn) will get you there. This a) makes it look like you have a direction for your career, and b) that you're looking at them for the long haul, and not just the next paycheck.

(David, good analogy. :-)

--Mark

[mary jacobson]

Hi,

I just wanted to update on what happened..

I went for an interview, they gave me different scenarios and asked me how would I solve those problems. At the end of the interview, I got a very positive response and 2 days ago I got an offer and I accepted. They have offered 54K + $2500 as signing up bonus and 7% increase after 6 months depending on my performance, they will pay for my education (4 more courses to go, graduting in Dec 2005). Not sure if this is a good deal, but I like, what I am going to be doing. This company also provides salary increase based on performance review, so I am taking a chance just by believing in myself.

Thanks so much for guiding me through this process,

[Peter Madden]

Originally posted by mary jacobson:
Hi,

I just wanted to update on what happened..

I went for an interview, they gave me different scenarios and asked me how would I solve those problems. At the end of the interview, I got a very positive response and 2 days ago I got an offer and I accepted. They have offered 54K + $2500 as signing up bonus and 7% increase after 6 months depending on my performance, they will pay for my education (4 more courses to go, graduting in Dec 2005). Not sure if this is a good deal, but I like, what I am going to be doing. This company also provides salary increase based on performance review, so I am taking a chance just by believing in myself.

Thanks so much for guiding me through this process,

Congratulations! and Best of Luck.

[Marc Peabody]

Originally posted by mary jacobson:
Problem here is : Not much as coding in java as I want, since small company not following good practices, (requirements change until delivery)which I hate, only 2 people team (me and my coworker).

Funny. I always thought the Unified Process [requirements changing] and Paired Programming [team of two] were good practices.

[peter wooster]

Originally posted by Marc Peabody:

Funny. I always thought the Unified Process [requirements changing] and Paired Programming [team of two] were good practices.

Those are good practices, but they are in response to bad situations. All iterative processes such as UP and RUP are a response to the fact that customers can never get the requirements right. One aspect that they don't address is that most customers won't notice until a final product is delivered, at which point it too late.