January 20th, 2009

Job Hunting in 140 Characters

Chelsea Winkel needed a job. A recent Chicago transplant, the interaction designer wasn’t having much success. Advice from others mostly fell along the lines of, in her words: “I got my first job in Chicago through a recommendation of someone already working in Chicago.” After applying to yet another job and barely receiving a response, she decided to take her search public- and direct. Although she originally created a Twitter account (under the name hirechelsea) for social purposes, the transition from pleasure to business was an easy one. Within hours of Tweeting “Who do I have to schmooze to get a job in this joint?” she received three direct messages, a much better (and as it would turn out, more substantial) turnout than anything else she’d tried so far.

One of those messages was from Jeff Kenny, a veteran interaction designer for Duo. After attending the IDEA 2008 conference, Jeff noticed Jason Fried, founder of 37signals, thank another Twitter user for a write-up of the conference: Chelsea had also attended, but she and Jeff had not crossed paths. After reading her updates, jeffkenny and hirechelsea began chatting back and forth, and eventually “I started following her and ended up replying to one of her questions and then she started following me.” From her Twitter account Jeff found her website, and noticed she had worked for Pearson, for whom he’d done freelance work for in the past. After following each other for about a month and exchanging numerous Tweets, he saw she was looking for work. After a few direct Twitter messages, Jeff sent Chelsea’s resume to the head of Duo’s design department, and the rest is history. Interestingly enough, word may have spread: after Chelsea was hired, Jeff experienced a brief surge of followers.

Was Chelsea’s success a fluke, or does Twitter have applications beyond what its name would suggest? “Apparently, being less formal and little more public worked,” said Chelsea of her job-finding strategy. She credits the application’s almost innately informal style with helping land her current position: “People can see your personality.” Jeff’s reasoning supported these sentiments: “I clicked her name to see what kind of stuff she tweeted about,” he said, “and it seemed mostly in line with my thinking.” Twitter heightens the chance of serendipitous meetings, allowing those with a few degrees of separation to find each other and connect in ways they might not have otherwise. It allows users to customize their level of involvement, and as Jeff put it “just throw something out there and it goes to the public timeline, not just followers- which allows you to reach a potentially wider audience.”

Both seemed to agree that despite the fortunate accident that brought them together, the key to making Twitter work for you is being proactive. Chelsea put her skills and desire out to a network of thousands, and was rewarded with Jeff’s interest and eventually, a job. “Along with a hefty campaign to brand myself and the name ‘hirechelsea’,” she said, “what it comes down to is I asked.”

Jeff and Chelsea’s conversation is archived here.

Add a Comment (5)

Intermittant outtages on .org sites (i.e. ncsasports.org)

We’re tracking a problem that’s manifesting itself as intermittent outages to .org domains.  what appears to be happening is that sometimes the .org DNS servers will return a null response instead of the authoritative servers.  This results in our local DNS servers caching a “null value” on the response and the site appears down until the cache expires and the full recursive lookup happens again.

Here’s an example of a failed recursive lookup:

sfrazer-mbp:~ sfrazer$ dig +trace www.prairie.org

; <<>> DiG 9.4.2-P2 <<>> +trace www.prairie.org
;; global options:  printcmd
.            79601    IN    NS    l.root-servers.net.
.            79601    IN    NS    j.root-servers.net.
.            79601    IN    NS    c.root-servers.net.
.            79601    IN    NS    k.root-servers.net.
.            79601    IN    NS    i.root-servers.net.
.            79601    IN    NS    d.root-servers.net.
.            79601    IN    NS    b.root-servers.net.
.            79601    IN    NS    f.root-servers.net.
.            79601    IN    NS    a.root-servers.net.
.            79601    IN    NS    m.root-servers.net.
.            79601    IN    NS    e.root-servers.net.
.            79601    IN    NS    h.root-servers.net.
.            79601    IN    NS    g.root-servers.net.
;; Received 449 bytes from 192.168.0.21#53(192.168.0.21) in 11 ms

org.            172800    IN    NS    C0.ORG.AFILIAS-NST.INFO.
org.            172800    IN    NS    D0.ORG.AFILIAS-NST.org.
org.            172800    IN    NS    A0.ORG.AFILIAS-NST.INFO.
org.            172800    IN    NS    A2.ORG.AFILIAS-NST.INFO.
org.            172800    IN    NS    B0.ORG.AFILIAS-NST.org.
org.            172800    IN    NS    B2.ORG.AFILIAS-NST.org.
;; Received 435 bytes from 192.58.128.30#53(j.root-servers.net) in 31 ms

org.            0    IN    SOA    a0.org.afilias-nst.info. noc.afilias-nst.info. 2008502420 1800 900 604800 86400
;; Received 96 bytes from 199.19.56.1#53(A0.ORG.AFILIAS-NST.INFO) in 49 ms

sfrazer-mbp:~ sfrazer$

A0.ORG.AFILIAS-NST.INFO should have returned a list of our DNS servers, which would then be queried.

In short, the issue is out of our control, as our DNS servers remain healthy and serving the correct content, and the websites themselves are still up, even though some people will be unable to get to them.

Because we set our Time To Live on DNS zones to 5 mintues, the outtages generally don’t last long (the cache expires quickly, and is refilled) but the request rate is higher, so people are more likely to see the problem.  The alternative would be longer TTL settings which would reduce the number of times people saw the problem, but would lengthen the time until the problem resolved itself.

Update: The problem has apparently been resolved.  More information here.

Add a Comment (1)