|
Interesting to know of a white Australian wearing lungis/sarongs - picked up the habit from your time in SE Asia?
Just you or is it common elsewhere in Aussieland?
Cheers,
Vikram.
|
|
|
|
|
Vikram A Punathambekar wrote: picked up the habit from your time in SE Asia
Yes - although I have influenced a number of people to wear them.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
- Pack some spares in a dry bag.
2.
put a sign outside.
Zoom meeting in Progress.
Knock twice firmly and give us one minute to wrap up.
Once you hear the knock start talking real loud until you are zipped up.
“Good meetin, I think we made some progress…
|
|
|
|
|
So we are born successful and it's downhill from there.
I will test your theory today by getting drive-thru lunch without pants. If I feel successful, I may try lunch as a walk-in customer tomorrow.
The sign on the door says, "No shirt, no shoes, no service." It seems they are making an allowance for the successful. I never knew! 
|
|
|
|
|
Hi All,
When writing a CV I have always stuck to Experience, Qualifications & Skills. My thinking is my Experience details what I have done for how long & where, My qualifications detail what bits of paper I got when & Skills what I can do. Now I get people telling me I need to detail spefic things (for instance a chip change I was involved in) how many suppliers and 'stake holders' ( ) How I managed various things. I was of the opinion and it has alway born out these are questions that are ask in face to face interviews rather than CV. If I took the approach they want I would rewrite my CV for every application... thoughs please...
|
|
|
|
|
glennPattonInThePub3 wrote: If I took the approach they want I would rewrite my CV for every application
Back in the day ...
When I sent out CV's, then yes - I rewrote the CV for every application, enhancing relevant experience and reducing irrelevant.
A CV is all about "catching the eye" and looking like a close to perfect fit for the job in order to get the interview where you can shine!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If you know what the company wants I can do that if it's a 'Blah, Blah, Interfacing' role It can be hard to work whats wanted and what will get it in the bin, also
Quote: • You will have the ability to bring complex systems together into an integrated platform, with a knowledge of interfaces
• You will demonstrate an understanding of technical risk analysis and risk based decision making, and the principals of engineering management
• You will have experience working with suppliers, contractors, subject matter experts and/or stakeholders
There is a big chunk of my experience that is basically that, also the example I can think of for the risk analysis section is a bit technical (change to an Elan BGA from a TI part (DIP layout) meaning the costs of a board respin and a load of unused TI chips) how can that be put with ease in a way that can be understood if you are not of a technical background...
|
|
|
|
|
I was on a "back to work" course some years ago where this subject was discussed at length. The key point the instructors made was that there must be enough information on the first page to pique the interest of the recruiter. So get the basics of skills and experience there, with a note about detailed explanations on pages 2 to the end. Most managers skim read the first page and if it does not contain the answers to their basic questions it goes straight in the bin.
|
|
|
|
|
As a hiring manager, if I see a CV that's more than two or three pages long I put it at the bottom of my pile to read.
|
|
|
|
|
As a hiring manager, do you read cover letters/emails?
I was taught to use the cover letter as the teaser to get the resume read, pointing out specific things in the resume that apply specifically to the job applied for.
|
|
|
|
|
If there are cover letters, they never make it to my desk. I only see a resume. I like to see a summary of skills, then listing of where you've worked & kinds of projects. I'm generally looking for embedded skills, because it's easier to learn Windows programming starting from that than to work with embedded constraints if all you've worked on is database projects (for example). I like to see clues that you can read a data sheet, use a soldering iron and 'scope, etc.
|
|
|
|
|
What they really want to see:
Replaced x with y, which saved the company z dollars
|
|
|
|
|
Also I was told ( by a recruitment agent ) if you are submitting a CV to one of the online guys to include your buzzwords dozens of times in a very small white font - the naked eye can't see them but their scanning software can
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
I don't know if this is odd, or not, but 'back in the day' when I recruited people, (permies), I was always interested to see what their interests and hobbies were! Yes, I was looking for a person capable of doing the job - but what someone does in their spare time can tell you quite a lot about a person. Also, discussing their interests at the beginning of an interview was a good way to help them relax.
|
|
|
|
|
I was told to take off that section by an 'expert' one job I got was because I play Bass and my boss could tell from that I was used to explaining complex things very quickly and simply...
|
|
|
|
|
I once spent the first 15 minutes of an interview chatting about favourite guitars and guitarists with a candidate. Even though we disagreed, (he was a Les Paul fan and I'm a Strat lover), he got the job - and he was a great hire.
|
|
|
|
|
glennPattonInThePub3 wrote: because I play Bass and my boss could tell from that I was used to explaining complex things very quickly and simply...
Seems like bit of a stretch, were you transcribing the likes of Niels-Henning Ørsted Pedersen or Jaco Pastorius? Seriously though, a lot of the engineers that I know play instruments, so I see see it as a plus to include on a CV.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I've been asked to go through a pile of resumes myself, and frankly interests and hobbies are just filler that work against you. Remember that you typically aren't the only person applying for a job, and if I have 20 resumes to go through, I will absolutely not be reading every single last word on an 8-page resume - so interests and hobbies will be ignored anyway. If someone's really interested, it'll come up during an actual interview.
|
|
|
|
|
|
This is probably not the answer you're looking for, but...
I never put a lot of effort into making one. I just sort of threw something together and kept adding to it. As far as skills, I'd have never gone into the detail being asked of you.
At one point I thought I should get some professional help with it, but I realized that the best jobs I've ever had were started with a handshake rather than a document exchange.
Furthermore, I've found that I prefer to work in places where you have to demonstrate your skillset during an interview. It keeps the team solid. It also gives me an opportunity to show what I can do where I can't do so on paper in terms of my education.
These days, my portfolio is what I use to sell myself. My codeproject profile, my github profile, and my client list. I've found all of my current jobs that way.
But that's me, and I've taken kind of a weird arc through software development. YMMV.
Real programmers use butterflies
|
|
|
|
|
I was involved in recruiting for a job recently and saw how much things seem to have changed. I was always taught that CVs should never exceed two pages. Some of the ones I looked at were 6, 7 or 8 pages filled with waffle and an immediate "off-putter."
I would say keep it concise. Many people would say to focus on the specifics being asked for but, in my opinion I was certainly swayed by seeing that someone had broader experience and was clearly adaptable to do something not in their normal remit.
I also asked a mate of mine who works for JobCentre Plus and his response was that the "rules" for CV writing are changing on a two weekly basis and what someone says is the way to do it this week, may not be next week.
Finally, the problem is, you don't know who'll be reading the CV. Some idiot from HR who is looking for buzzwords or someone who actually understands the job and the person required.
|
|
|
|
|
My preference is to keep it to two pages. As a some-time reader of resumes, I take an instant dislike to any longer than that. If I want to know details I will ask for them. Until then, I'll pass. For that reason, I would avoid details unless you have a CV of 1.7 pages and need to fill it out to 2.0.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I would say always highlight relevant skills first, it might mean tweaking it but so be it, put a personal statement at the top, perhaps add some key skills as bullet points below this.
For how to detail changes to component level, well just put down that you have experience in obsolescence and part changes down to component level, if they ask you how you would manage this then say where applicable you would suggest a dual footprint on the design etc.
Your CV can be generalised but tweaked and it is the cover letter that gets tailored to suit the company in my experience.
Ensure that your CV does not span more than at an absolute MAX 3 pages, keep it shorter if possible but make sure it is readable i.e. don't put it at font size 6 to cram it all in, and make sure you use a decent font (no Comic Sans or Wingdings!)
These would be my tips.
|
|
|
|
|
Test Tickle wrote: These would be my tips.
And for the love of everything that is holy, fix your typos.
If you can't be bothered with that simple task for a document that's supposed to represent you, it speaks volumes about your attention to detail. And if you don't have that as a software developer, we're getting off on the wrong foot.
|
|
|
|
|
After one underwhelming contractor, we considered adding a spelling test.
Native English speaker, not a second language! Anybody who comes close with English as a second language proves genius status.
“Templet” is one that I remember because it is still hanging around in a few spots.
There were a few others that slip my mind.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
