Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Job Offer Advice

Status
Not open for further replies.

imterpsfan3

Programmer
Jul 22, 2005
160
US
I was recently offered a job with a company as a mid-level C# developer. I am still in the midst of considering whether I am going to take it or not. Some of the things that went on during the interview made me very cautious of taking the job, and I wanted to hear some feedback from others who may have faced similar circumstances.

During the interview I was asked about 50 questions in rapid-fire fashion. They mentioned something about "letting people go" if they find that an application has an error after it hits production. I also found out that they let 3 people go in the department I would be in, as well as another 10 people in another location. When I asked about this high turnover rate, they replied "they were stubborn, they didn't want to do things our way".

Another instance in the interview they asked "how do you know your code's any good" but in a more attacking manner. Also when I brought up that I use a coding technique that a very well-known developer uses, they asked "so do you do that just because he's well known?" also in a tone that didn't seem professional.

There didn't seem to be much room for error here, not that anyone wants to make any mistakes in an application.

Maybe this is a no-brainer to not take this position but it would offer a chance to elevate my skills and lessen my commute.
 
I would be very wary of taking a position like that. If they follow it one step further, then everyone above the developer should be let go as well. Cause if the developers fault for the error, its the QA teams fault they did not catch it before prodution. Its the developers manager fault for not having done enough to prevent it. Its the QA managers fault for allowing his team to miss it. Pretty much you could wipe out the entire structure all the way up to ceo. Just follow the development hierarchy.

Call them back and ask them then that. im cursious about thier response. If they say it rests completly with the developer, then they dont support them. and Do not accept a company that does not support their developers. They dont take responsibitly for thier mistakes and always have to blame someone. Im guessing this is not for an internal development position. They have to tell the client who was at fault.

Errors happen. Period. Anyone who believes otherwise is fooling themselves. The goal is to minimize the amount down to a certain acceptable level by the time you get to production. I work now for a contractor that does work for a govt agency with 3 letters. Even they accept that errors happen.
 
USAF, USMC had four, but true, most have three.



Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Typo...

They still have four (I'm sure there are more, those are the only that come to mind though).

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
USAF and USMC aren't goverment agencies. The agency they fall under is the DOD.

Shoot Me! Shoot Me NOW!!!
- Daffy Duck
 
According to them the primary responsibility lies with the developer.

I don't think I'm going to take this job. Nearly everyone I've talked with about this suggests I not take and wait for something better.
 
they were stubborn, they didn't want to do things our way

I would probably have ended the interview right there. If they aren't willing to listen to someone else's experience, then they're coding with blinders on.

Go somewhere else.

Chip H.


____________________________________________________________________
Donate to Katrina relief:
If you want to get the best response to a question, please read FAQ222-2244 first
 
I would suggest that you were not being told the whole truth. Instead I think they were employing a technique to see how you perform under pressure. I had a placement agency do that one to me a couple of years ago and it really through me for a loop. I would suggest interviewing the company prior to signing on and have them address your concerns. It certainly can not hurt to turn the tables (in a nicer way).
 
Oh man... A privitised DOD.

"The Department of Defence. A Haliburton Company."

-------------------------
Just call me Captain Awesome.
 
I decided not to take the job. I was really turned off by this interviewing technique and figured the environment would be worse on the job.

On of the things the lead architect said when I was leaving after the first interview really dissuaded me from taking the job. "A lot of people come in here all confident and they leave with a different attitude", he said with a sense of pride.

In one sense I think they were trying to see how I would react under pressure. In other sense, I think they exhibited arrogance.

I feel I could learn and contribute in a better work atmosphere.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top