I think the bar is raised much higher for telecommuting, because of the need for trust - a virtue not normally associated with successful businesses.

I've had several jobs where I started off working in the office, and when negotiating contract renewal after an initial six months was able to get telecommuting considered as part of the package. I think that the initial period was important for several reasons: on the one hand to show that I was inclined to work all the hours I billed, that I tended to complete projects within time and budget, that the finished code was usually easy to deploy and rarely caused later problems due to bugs or to grey areas in the specification; and on the other hand to get an understanding of the day to day business of the company and of my colleagues - what sort of people they were, their strengths and weaknesses, and how to communicate with them.

The only job I've had in which I worked at home from the start is my current one, and there I had the advantage of word of mouth: the director of technology is someone I've worked with several times in the past (indeed I gave him some initial perl lessons, way back when) and a close personal friend. And in this job, more than in any previous one, I feel occasionally isolated from the rest of the team, and more likely to have problems with communication, because I have never worked with them cheek by jowl and learnt their peccadillos (and given them a chance to learn mine).

As far as applying for jobs is concerned, I would never send a CV in isolation: I'd always contact the company or recruiters directly first (by phone if at all possible) to ask some more details and warn them my CV was on the way, and then follow up with regular additional calls to check that they had received it and find out what else was happening. Indeed, many of the contracts I've taken were not what I originally contacted a recruiter to apply for but arose thereafter because I kept in touch with them. Don't get me wrong, most recruiters in IT are quite terrible, and will try to push you in inappropriate directions unless you are firm with them (to the extent of modifying your CV to be a complete lie without informing you), but I've found them to be a necessary (or at least useful) evil.

Hope some of that helps,

Hugo

In reply to Re: Have you got a telecommuting job? by hv
in thread Have you got a telecommuting job? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.