My first thought was a project-based contract, too. But there are few
programmer projects that would require zero maintenance once finished. As
someone who has had to pick up projects "completed" by others, there are
always bugs, gaps in documentation, and difficult upgrade paths.
So I have no solutions to offer. Enticing people with telework is a good
idea. It's disappointing to see libraries (and higher ed more generally)
continuing to not invest in software development. We need developers. If we
cannot find the money for them, perhaps we should re-evaluate our
On Fri, Aug 15, 2014 at 10:12 AM, Sean Hannan <[log in to unmask]> wrote:
> Would it be possible to re-write this position as a project-based contract?
> Such a position is more appealing for short-term (part-time) gig-type work
> and telework types. Also, it helps you out in that if the telework thing
> doesnıt work for various reasons, youıre done with it at the end of the
> contract. You could always offer an opportunity to renew the contract for
> a new projects if it does seem to work for the both of you.
> On 8/15/14, 12:44 PM, "Kim, Bohyun" <[log in to unmask]> wrote:
> >I am in a situation in which a university has a set salary guideline for
> >programmer position classifications and if I want to hire an entry-lever
> >dev, the salary is too low to be competitive and if I want to hire a more
> >experienced dev in a higher classification, the competitive salary amount
> >exceeds what my library cannot afford. So as a compromise I am thinking
> >about going the route of posting a half-time position in a higher
> >classification so that the salary would be at least competitive. It will
> >get full-time benefits on a pro-rated basis. But I am wondering if this
> >strategy would be viable or not.
> >Also anyone has a experience in hiring a developer to telework completely
> >from another state when you do not have previous experience working with
> >her/him? This seems a bit risky strategy to me but I am wondering if it
> >may attract more candidates particularly when the position is half time.
> >As a current/past/future library programmer or hiring manager in IT or
> >both, if you have any thoughts, experience, or ideas, I would really
> >appreciate it.