Started a new job and i am a bit demoralised

[mavrick]

Hi out there

I just started a new job and I an a bit demoralised. I am on three month probation. I thought I new Code (asp, vb.net), but when I got here things changed. Not sure weather I should be worried or not. I have talked to people, they say that "it’s a new place, things are just done differently", isn’t that the truth! I am pretty confident about my skills, at my previous job I ran all of the development.

I was just wondering how does stuff change so much, not a lot but enough to make me get up and HEY...

Not sure weather I am going to get the job, then again I am not sure weather I am (50/50). But the fact that I can’t control this leaves me wondering...

If some of u guys out there are going or have been through what I am going through, PLEASE some advice...

Thanks

[superpower]

The absolute worst thing you can do is worry too much and talk about it. Getting fired becomes a self-fulfilling prophecy in that case. People who previously may of thought you were doing ok will start wondering...hmmm...this guy doesn't seem so sure about his skills...

The best thing you can do is to succeed at the tasks they give you. Know their expectations for your performance and simply meet or exceed them.

How do you meet expectations? Organization is key. The first thing is you have to have in writing/email what the expectations are. If they are too vague you need to fill them in yourself by asking questions about the project. Ask what it is not how to do it. Don't get overwhelmed, break everything down. Set your own internal timeline goals and identify where you think you may have a problem well in advance.

I always did well with checklists or an outline. This simply forces me to get organized. If necessary I talk to everybody to add what needs to get done to the checklist and also sequence it. Often you find discrepancies. For example, the UI guy wanted the shopping cart to have a certain flow but your engineering manager misunderstood and gave you different instructions. Once you have a list of everything you need for the project/code, then often you will know more than the managers. That makes you more important before you even get to coding.

Asking questions is good but don't be a nuisance on code issues. Make sure you have really thought out a problem, googled it etc. before asking for advice from a another engineer/boss.

[mavrick]

So i should not ask, "How i did in my First month"?

[grandpa]

Hi mavrick.

I've been there. I used to write code for a few large retailers. Each new job brought a new environment, new faces, and new methods for doing the same job. Invariably, it seemed that everyone knew more than I did. And they did. Not in the sense they were more skilled, but they knew the ropes for *that* job.

I would hope there was interview process involved in getting your job. Be assured those folks talked about your skillset, and if there are any weaknesses (as determined by their needs) they took that into consideration.

You got the seat, you're the man for the job. In my opinion, the probationary period is probably more to see how you fit into the 'team' than for your skills. If you like the job, and the people, then put on a happy face and show up when you're supposed to and do what needs to be done. It never hurt, either, to let my new co-workers show me just how talented they were. The more you can 'learn' during this probationary period, (without seeming to know nothing), the better your evaluation may be in 90 days.

<edited cause I can't spell>

[mona]

Hey, mavrick, there's some great advice in this thread. My philosophy is fake your way through it until you don't have to anymore. Half the time people can't tell the difference anyways.

The hardest part is getting the job - and you've already done that! When I got hired here for SEO, I was basically computer illiterate. I sorta "faked my way" through the interview to get hired. And for the first month, I cried almost every day on my way home because I was so clueless I thought I'd get fired. It's been 3 and half years now and my boss has paid for my last two US PubCon trips and he's thinking about taking me to London this fall:)

[mcavic]

Hey Mavrick,

I agree with everyone here. What you have to do is suprise your superiors and coworkers at how well you do the job. Be confident, and your work will speak for itself.

So i should not ask, "How i did in my First month"?

Correct. If you're doing well, people might not always congratulate you. But if you're messing up, you'll probably know about it.

[Shane]

I was in consulting for six years. One of the hardest things is moving to a new client with each new assignment. A consultant may have the knowledge but they have to "fit-in" at each new client site. What you are doing is similar and it is not easy.

Now I work for a large organization, 2,400 people. We too have probabtion timeframes. Realize I have been here 11 years and have only once seen a probabtion period terminated. It is very rarely used.

You are doing fine until everyone notices you aren't. Don't bring it up, work to succeed.

I'd wish you luck but you really don't need it. You are already in the door. Relax, do the work. :) Enjoy!

..... Shane