St. wrote:

>    You're not that far from Northamton are you? Go for this job, they want 
> someone quickly:
> 
>     http://www.cwjobs.co.uk/JobSearch/JobDetails.aspx?JobId=42113428&Location=32
> 
>    Look at what they're willing to pay - if you're lucky in the interview, 
> you might just get the job and that money, and if you think that the 
> interviewer is trying to fob you off or it's not sounding promising, then 

> resort.
> 
>   If I was in your position right now, Northampton is where I'd be heading.

It has a flavour...

Post a reply to this message

"Invisible" <voi### [at] devnull> wrote in message 
news:49257a9e$1@news.povray.org...
> St. wrote:
>>   If I was in your position right now, Northampton is where I'd be 
>> heading.
>
> It has a flavour...

    It's something you could do. Go for it. I don't know how far from 
Northampton you are, (I assume you're fairly close though), but even if it 
meant a train journey, it would be worth it - well, that's better than 
driving that's for sure.

   Just take the plunge, and see what happens, and if you get it, lend me a 
tenner. ;)

     ~Steve~

Post a reply to this message

St. wrote:

>     It's something you could do. Go for it. I don't know how far from 
> Northampton you are, (I assume you're fairly close though), but even if it 
> meant a train journey, it would be worth it - well, that's better than 
> driving that's for sure.

It's pretty close. You have to drive down winding country roads and 
through several villages with low speed limits, but the actual distance 
isn't that far.

>    Just take the plunge, and see what happens, and if you get it, lend me a 
> tenner. ;)

Hee! Normal recruiters want you to *give* them a tenner, not "lend". ;-)

Post a reply to this message

"Invisible" <voi### [at] devnull> wrote in message 
news:49257f75$1@news.povray.org...
> St. wrote:
>
>>     It's something you could do. Go for it. I don't know how far from 
>> Northampton you are, (I assume you're fairly close though), but even if 
>> it meant a train journey, it would be worth it - well, that's better than 
>> driving that's for sure.
>
> It's pretty close. You have to drive down winding country roads and 
> through several villages with low speed limits, but the actual distance 
> isn't that far.


   Cool, even better. I know you like your driving.


>
>>    Just take the plunge, and see what happens, and if you get it, lend me 
>> a tenner. ;)
>
> Hee! Normal recruiters want you to *give* them a tenner, not "lend". ;-)

   HAHA! True, so GIVE me a tenner!  <eg>

   Are you going to go for it Andrew? Please say yes. Just think, at the end 

and you find that you 'hate it', well, it's no different to the job you hate 
now, but you'd be mega bucks better off  for it.

   Personally though, I think you'll be a far lot happier if you did get the 
job - you'd meet new people, (girls!), new workmates, and some of them might 
have the same interests as you. You just don't know if you don't try.

 Damn, I'd beat their door down for that job.

   ~Steve~

Post a reply to this message

"St." <dot### [at] dotcom> wrote:
>  Damn, I'd beat their door down for that job.
>
>    ~Steve~

Yeah! But with a salary of 30,000 - 35,000 there will be 4000 people applying
for the job.

BTW Andrew, did you look at the modified CV I tarted up for you? I thought that
we could have a game of "polish up the CV ping pong".

Stephen

Post a reply to this message

Invisible wrote:
> ....unless they say "so how much are you expecting us to pay you?" ;-)

Anyone who is the first to give a number in a negotiation loses.

The right answer to this question is "what's the range you've budgetted 
for the job?"  Followed by "I can work with that."

If they ask "What did you make at the last job?" the answer is "I've 
made between $X and $Y in previous positions."  Of course, you're just 
starting out, so that's difficult. Instead a good answer is "I'd like to 
start with $X at this position."  What you made in the job you're 
leaving is irrelevant and detrimental.

Other countries, of course, may have other customs.

I'd suggest picking up a book on negotiating tactics. It'll be well 
worth the price, and easy to understand.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

scott wrote:
> Exactly.  You never know, once you tell them you are leaving for another 
> job, they might offer you a pay rise to keep you. 

And it's always a *terrible* idea to accept that. Because then they'll 
be looking for a replacement for you, knowing you are looking to leave. 
You get booted out on their schedule, not yours.

If you want to go that way, tell you boss you need more money, not that 
you're looking for a different job.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

Invisible wrote:
>>> This is again untrue. The scripts don't "correct" anything,
>> You never wrote a script that fixed something?
> Nope.

So, the script that checks the CDs, or that does the pings... what did 
you do with the output of those?  Toss it away after looking at it, 
going "Hmmm, interesting."   Or did you (for example) give the ping 
report to the ISP to get them to diagnose the problem from their end?

>> Suggestion: don't put on your resume that there are a whole bunch of 
>> other more-experienced people available, either. They know that too. :-)
> 
> Right, so... why are they going to hire me again??

Because you're there, and the experienced people are happy where they 
are? :)

>>> Where do I stop? I mean, I could say I know HTML, CSS, XML, XSLT, 
>>> LaTeX, PostScript, AmigaGuide... where do you draw the line?
>>
>> Yep. Put all that in. Anything you think an employer might need.
> 
> Ooo, AmigaGuide, an obsolete markup language that predates HTML 1.0 by 
> several years. They *really* need to know about that! :-P

It shows your breadth of knowledge. If you have the room, put it in. If 
you don't, of course leave it out.

>>> Sure. But it's hard to disguise something that's actually true.
>> No doubt. But important nonetheless. :-)
> Oh sure, I'm not doubting it's importance, I'm just saying it's really 
> hard. :-(

Yep. So you need to work at it. :)

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

Invisible wrote:
> It's pretty close. You have to drive down winding country roads and 
> through several villages with low speed limits, but the actual distance 
> isn't that far.

I'd say go interview even if you *don't* want the job. That's the best 
kind of interview. It lets you think about your interview strategies 
without the stress of actually wanting the job and being afraid to mess 
up. :-)

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

scott wrote:
>> LOL! I suppose I could explain that it's a Turing-complete scene 
>> description language for photorealistic image and animation 
>> construction / scripting... that could sound impressive. ;-)
> 
> Actually, I only found out about POV when I was applying for a job that 
> mentioned it.  I forget the name of the company, but they did realtime 
> and pre-rendered work for car companies etc.  Of course I looked up 
> everything that was mentioned on the job advert, and well here I am :-)

Definitely mention POV. Almost everyone I've spoken to in graphics & 
programming has heard of it.

Mentioning POV on my CV was one of the things that got me my current job.

Post a reply to this message