---
title: Psst, buddy, want a job?
date: 2006-02-24 00:11:00.000000000 -08:00
type: post
parent_id: '0'
published: true
password: ''
status: publish
categories: []
tags: []
meta:
  _publicize_pending: '1'
  lj_itemid: '292'
  lj_permalink: http://obra.livejournal.com/74881.html
author:
permalink: "/2006/02/24/psst-buddy-want-a-job/"
---
<p>We'll be posting this publicly within the next couple days. But you, my friends, get first crack ;)</p>
<p><!--more--><br />
ABOUT US</p>
<p>We're Best Practical Solutions, a small software company located<br />
in Somerville, Mass. We build software and sell support, training,<br />
consulting and custom development. Our main product, RT (Request Tracker)<br />
is the premiere opensource issue tracking system, downloaded by about<br />
3000 new organizations every month. We've been around since the fall of<br />
2001 and are entirely self-funded. O'Reilly Media published our first book,<br />
/RT Essentials/, last fall. This winter, we unveiled Jifty,<br />
our next-generation web application toolkit. We're currently hard at<br />
work on our next new product. Things just keep getting busier.</p>
<p>ABOUT YOU</p>
<p>You should be a self-starter who has some experience with Perl, as well<br />
as at least a few of the following:</p>
<p>    * Test driven development<br />
    * User interface design<br />
    * HTML::Mason templating<br />
    * Documentation<br />
    * Web Services<br />
    * Cascading Style Sheets<br />
    * Javascript / AJAX<br />
    * SQL databases<br />
    * MVC frameworks<br />
    * Optimization and Profiling<br />
    * Subversion and SVK</p>
<p>It's ok if you don't know everything out of the gate, but you should be<br />
able to learn on the fly and be comfortable asking questions when you<br />
get in over your head.  RT is a large codebase to dive into (47000 lines<br />
of libraries, 27000 of templates) so you should be prepared to work with<br />
a project that's too big to hold in your head at once.  If you want to<br />
see what sort of trouble you're getting yourself into, download a copy<br />
of RT's source code from:</p>
<p>   http://download.bestpractical.com/pub/rt/release/rt.tar.gz</p>
<p>ABOUT THE JOB</p>
<p>We're looking for a mid-level Perl Hacker to help us enhance and refine RT,<br />
Jifty, and our Next Big Thing. You'll be responsible for everything from<br />
implementing new features across all our products to testing and applying<br />
user-contributed patches to our released software. In a typical week, you'll<br />
probably spend about half your time working on customer projects and half<br />
working on internal and opensource projects. </p>
<p>The hours are flexible and we all telecommute some of the time...though we're<br />
just about to move into new office space in the heart of Davis Sq, Somerville.<br />
We do just about EVERYTHING online and on the phone. You should be comfortable<br />
using email and instant messaging systems to collaborate and get work done.<br />
This job doesn't formally require your full-time presence in Boston, though it<br />
would certainly be an advantage.</p>
<p>We're a small company and the boss is typically overextended. You should be<br />
comfortable working independently or in small teams, prioritizing tasks on<br />
your own, and juggling tasks and projects. You need to be able to tell when<br />
you're out of your depth and ask for help.</p>
<p>COMPENSATION:</p>
<p>DOE - This is a full-time salaried position, but the details are negotiable.<br />
We're a small, self funded company. The standard benefits apply, of course:<br />
health insurance, dental insurance and junk food to make that dental insurance<br />
worthwhile.</p>
<p>HOW TO APPLY:</p>
<p>Send a something approximating a cover letter, a resume in<br />
plain text, HTML or PDF form and a sample of your Perl code to<br />
resumes@bestpractical.com. If you're involved in opensource development of<br />
one kind or another, please tell us about it. If you have a CPAN ID, tell<br />
us what it is. We won't consider applications without a code sample. We'll<br />
be paying particular attention to the readability, comments and tests.</p>
