Community Software Lab summer 2008 VISTA application & info

We are located in Lowell Massachusetts

There are other less hard-core jobs at the CTCVISTA project.

[top] Prerequisites and disclaimers

You should not apply unless you have:

  1. Excellent good writing and speaking skills (for grant writing)
  2. Solid entry level sys admin and coding skills (for tech work)
  3. US citizenship or green card. (sorry)

Your specific responsibilities will vary with the skills and interests you demonstrate. Your work will not fall (far) outside the job descriptions below.

You should:

  1. Read the material at the national VISTA website.
  2. Read the VISTA FAQ provided by UMass Boston

[top] Hiring contact

**Please** email or call with questions, comments or suggestions. We want this to be a happy experience for everyone.

Job Descriptions

  1. Software Engineer
  2. System Administrator
  3. Lead Tech Support
  4. Grant Writer / MVHub Evangelist

There will be overlap, Everyone will do at least a little bit of everything. How much of each job you wind up doing will depend on your interests and accomplishments. For example, If you do well with sys admin, you'll get to write more code. If you are struggling with grants, you'll get to do more presentations.

General Qualifications and duties:

Everyone we work with needs an:

Note: We do not require people to be "team players", cooperation is good, groupthink is bad.

Everyone in our group must:

Note: We have somebody who likes to make the coffee, this will not be part of your duties.

Note: New ideas are worse than useless without the commitment to implement them.

Software Engineer

Goal: Useful web server based software for non profit organizations

Duties:

Qualifications:

Network Manager

Goal: Keep 12 servers, 3 switches and 1 router running smoothly

Duties:

Qualifications:

Tech Support Manager

Goal: Make our users feel informed and supported (perhaps by informing and supporting them)

Note: It is a difficult to find a person with skill to solve technical problems, skill to communicate the solutions and empathy enough to help the user enjoy the expierence. It is very difficult to find a person who enjoyes this particular work. This postion is most likely to be funded at higher than VISTA wages.

Duties:

Qualifications:

Grant Writer / MVHub Evangelist

The mix of duties for this job depends on the skills, interests and accomplishments of the person doing the job. If you are introverted and successful writing grants, you will spend most of your time writing grants. If you enjoy meeting strangers, you'll probably spend more time making presenations.

Goal: Write grants that bring in $50,000 in funding.

Goal: Increase the number of agencies and programs listed in http:/mvub.com

Grant writing Duties

Evangelist duties

Skills and Qualifications

Qualifications:

[top] Positive bullet points about the job

  1. Meaningful service
  2. Real work experience
  3. Medical benefits
  4. $4,700 Education award
  5. All expenses paid trip to national conference

[top] Negative bullet points about the job

  1. $10,000 per year for 40 hours per week
  2. No other paid work allowed
  3. School limited to 1 class per semester (work schedule permitting)

[top] Details on why you might want to work with us

We run the best web based community resource guide and provide a level of service to 35 organizations that they otherwise could not afford. We don't feed the hungry, shelter the homeless, or teach the young. We provide reliable services to the people that do.

Twelve out of fourteen of our former VISTA and long term volunteers now work at market rate tech jobs.

Our projects are often quite substantial. It is one thing to apt-get install apache2 and drop a few files in /var/www/default. It is another thing to configure an apache server with 500 different sites.

[top] Details on why you might not want to work with us

Failure is the norm for the IT industry. We have a small budget. Sometimes we favor ideology over results. We are very informal . Honesty and criticism are essential to our work. There are only a few people in our group. If you see only bugs and no features in these facts, you probably shouldn't spend the next year with us.

Ten of our twelve past full time volunteers are happy with their experience with us. Three people are still in touch, contributing via our listservs. At least 4 volunteer alumni have contributed cash to our efforts.

However, two people bitterly regret their time with us. Your milage may vary

We have a budget of about $50,000 per year. Most of that goes to labor. (Management is volunteer) Sometimes we have to substitute labor for equipment. For example we run smartmontools and monitor hardware health instead of buying new servers every two years.

This lack of money is (mostly) not a bug. We have enough money to do what we need to do. Empirical, scientific research indicates salary is not strongly connected to competence and that projects more often fail because of a surplus of resources than a shortage. In my own experience, I've not done better work when getting paid $45 an hour than I've done working for free.

There is often a conflict in our legally incorporated non profit purposes . We exist to support non profit organizations and to promote free software. Sometimes, the best solution for a non profit organization is not free. It is not good for morale when we choose less than the best.

For example, We didn't install exchange server to serve the youth center than needs Outlook integrated calendaring and task lists that can be synced to street worker's smart phones. Instead we are spending months experimenting with free software replacements for Exchange Server.

We are very informal. We do not have a personnel manual. You should not need a rule book to know what is right and wrong. For example, Our holiday and working hours policy is:

	Take off whatever time you want. Set whatever schedule you want. 
	Be sure everyone knows what your schedule is and stick to it. You 
	are responsible for results and that is how you are judged.

 

If you lack have real world information technology experience, you should be open to the fact that norm in IT projects is failure Arguably, 4 of 5 projects fail. We don't keep statistics of success and failure. (This lack of statistics is of course a failure). However, on major projects we're batting about 500. mvhub.com is an unqualified success. On all of the smaller 1-2 day projects we've done, our success rate is probably very close to the IT industry norm. Our full time volunteers probably do a good bit better on small projects. The later success is probably because we don't set arbitrary deadlines and therefore don't fail to meet them.

The failure causes we seem most prone to is poor requirements gathering or poor requirements communication. Often people will work for days or longer on a project, before we (I?) realize that this is not what we needed and work has to start almost from scratch. This is an area in need of improvement, but possible improvements may be limited. Arguably, many small failures are more demoralizing than one lengthy complete plan that sits idle. However, in many circumstances, trying and failing in a small way is more effective and less costly than an lengthy planning process.

Right now there are the equivalent of 4 full time people in our group. Given our scheduling policy, you might spend many hours alone in an empty basement room. If you do not have local friends or an online life, our work can be very, very lonely. We've made some progress on this problem, but haven't solved it and it may not be solvable. If you are lonely and isolated where you are now, you will only grow more lonely and isolated when you join us.

Criticism is essential. It is our firm policy not to scream, belittle or make personal attacks. However, we often do not have the skill to nuance criticism to preserve feelings. To succeed with us you must like criticism. It is probably not enough for you to tolerate criticism, if you don't see it as good, you probably won't be happy. We will attempt to be as honest and clear with you as we are with ourselves in this document. If we notice even a potential problem, we will mention it. We expect the same from you, if there is a problem, you are obliged to mention it. Criticism is futile sometimes but we are all obliged to make and accept the effort to criticize. Criticism is required for success.

Work with us is both rewarding and frustrating. If you are prepared for the frustration it will not overcome the reward.

[top] Interview Process

Interviews and interview questions are probably a good way to hire sales people. We're not hiring sales people. Our past experience has been pretty mixed. A couple people who interviewed badly did very well for us or other organizations. A couple people who interviewed well, did bad work.

You'll probably have a 1-2 phone interviews with past VISTAs.

If the phone interview(s) don't go horribly, you'll come to our space, answer 10-20 questions, do some actual work for 2-4 hours and talk with us about the work you did. While there will be some questions that come up in discussion, you'll get most questions in advance.

For sys admin people, The actual work will probably be to run our All Servers First checklist

For coders, The actual work will probably be to take a short production perl script, and add more tests using Test::More

For writers, We'll probably ask you to write small section of a grant.

If money, time and geography don't work out, the final interview will be virtual as well. We'll give you a xen instance to work with.

For phone interviews, we don't care what you wear. For the physical interview, as long as you remember to bathe and aren't wearing anything extrodinarily distracting (no flashing leds please), we don't care what you wear. You should wear what you are most comfortable in. If you are comfortable in a tux wear that. If you are comfortable in jeans and a tee-shirt, wear that. We'll probably be wearing jeans.

[top] Timeline and Deadlines (subject to change)

Dates and Deadlines are approximate. If things change, they will probably change for the worse. On the other hand, asking if a deadline has really past, works better than giving up.

Community Software Lab online application due ASAP

Second round screening test (if needed) ASAP

interview/evaluation days Monday May 05 to Monday May 12

Offer(s) made / regrets extended 5:00pm Tuesday May 13 2007

Paperwork in to Corporation for National Service Friday May 16 2008

Approval by corporation for national Service (usually a formality) (probably) Monday June 9, 2008

hotel stay in Boston (orientation) Tues-Fri July 8-11 2008

Start work Monday July 14 2008

[top] Application Form (tech)

If you submit things before they are due, we will try to point out any errors and give you a chance to correct them.

You may submit the online form as often as you wish. Only your last submission will count. (Assuming it is before the final deadline)

For many people it will take a few hours to fill out this form. To avoid frustrating data loss, it would be a good idea to create and save the information for this form outside the form.

Before starting, you should understand what the VISTA program is about.

Before you can complete this form, you must complete the long online form at the Corporation for National Service . Specifically, you will need an application ID.

Name
email
CNS application ID (for example: MA87031255 or FP88212866)
motivational statement from cns application
First reference name
Relationship to you
Best times to reach
First reference phone number
Second reference name
Relationship to you
Best times to reach
Second reference phone number
Resume text (just paste it in formatting doesn't matter):

Write a Javascript (not Java) program that can run when a web page is opened. The script should:

  1. Prompt the user for a positive integer.
  2. Print the numbers from zero to that number in the web page, each number on a separate line.

You do not have to do data validation. You can assume the user will actually give you a positive integer. You do not have to worry about over writing the page with your results.

Javascript works well for the purposes of this test, since anyone with access to a web browser and Notepad can create and test Javascript. The task is simple enough to be completed by somebody who has mastered a 101 level programming course but has no Javascript experience. It is actually better if you don't have Javascript experience. as we are most interested in your ability to figure things out.

As strange as this sounds, Don't try to impress us with extra work on this test. This is a check box, yes/no pass/fail test. We'd rather give you real work than have you spend any needless time on this. There is also the possibility that something complicated won't work in our browser... (right now our browser is Etch Ice Weasel)

paste your javascript here.
comments/notes/questions (optional)

[top] Application Form (writer)

If you submit things before they are due, we will try to point out any errors and give you a chance to correct them.

You may submit the online form as often as you wish. Only your last submission will count. (Assuming it is before the final deadline)

Before starting, you should understand what the VISTA program is about.

Name
email
Resume text (just paste it in formatting doesn't matter):

Clear, simple writing is absolutely essential. Careful reading and research is a related useful skill. This sentence:

  While freely conceding that the Soviet regime exhibits certain features 
  which the humanitarian may be inclined to deplore, we must, I think, 
  agree that a certain curtailment of the right to political opposition 
  is an unavoidable concomitant of transitional periods, and that the 
  rigors which the Russian people have been called upon to undergo have 
  been amply justified in the sphere of concrete achievement."

...is from George Orwell's essay, Politics and the English Language. Translate the sentence into clear, simple english. Get as close to George Orwell's style and meaning as you possibly can. Reading the essay will provide valuable clues.

paste your clearer sentence here.
If you wish, comment on your translation here: