You have chosen to sponsor your bid up to a maximum amount of .
To apply for this job...
*Please Submit Your Sample Source Code*
Provide us with some sample source code you have created in the past in Lisp or Ruby or Python or Perl or C++ or Java or some other language. However, please do not submit source code have created in PHP.
*Please Submit Your Monthly Rate*
Bid the monthly salary you require in US dollars for working 200 hundred (two hundred) hours per month.
*Repeat: Please Submit Your Sample Source Code*
Yes. We mentioned above that we want you to submit your sample source code but many candidates don't bother submitting their sample source code to us initially. Therefore, we'd like to persuade you to submit your sample source code to us along with your bid.
If you bid your monthly rate but fail to submit sample source code to us then we will send you a personal message via GetAFreelancer in which we request you to submit sample source code to us. We will also be mildly annoyed with you because we will feel you have needlessly wasted our time.
Please understand that if we merely know how much money you want to earn we will not have enough information to decide whether or not you seem like a good candidate. We need to get an idea of how well you write code.
If the source code you submit to us is good enough and if your salary requirement for working 200 hours per month is low enough, then we will create a small $30 test project just for you on GetAFreelancer. Therefore, please save us time and yourself time by submitting source code to us along with your bid for working 200 hours/month.
We will permit you to work any hours of the day you prefer. In other words, we do not care what hours of the day you work. If you are part of a team of 2 or 3 developers, and wish to apply as a team, please list the rate for each developer in the PM (personal message).
Regarding your sample source code, perhaps you created the code 2 weeks ago, 2 months ago, or even 2 years. If you are worried that by submitting the sample source code to us that you may be violating something like a client confidentiality agreement or non-disclosure agreement for source code you created as a "Work for Hire" then you may submit merely a snippet of the source code, not the entire source code. We are not looking to steal anyone else's software. Not at all. We merely want to review a sample of code you have created in the past so we can properly judge the quality of your code.
Please do not package your files in Visual Studio or any other framework. Your files must be available individually and not packaged (except as, say, a .zip or .rar file). We have had trouble in the past with tests that candidates have submitted C++ which they created with Visual Studio.
The software architect normally uses Linux and Macintosh but not Windows. Please make it easy for the software architect to review your code.
We are currently looking for 1 or 2 or 3 very clever, full-time software application developers (not mere coders) to work with us for at least a year but hopefully longer. We have many challenging new development projects that we need help with (no maintenance).
You must develop software for us using Steel Bank Common Lisp http://www.sbcl.org/. Our development server runs Apache and mod_lisp.
Of course, we assume you have practically no experience developing with Lisp. We know that very, very few developers use Lisp. Therefore, we recommend you review "Practical Common Lisp" http://www.gigamonkeys.com/book/ and "Common Lisp HyperSpec" http://www.lisp.org/HyperSpec/FrontMatter/index.html
Why did we choose Lisp? Isn't Lisp almost, well, almost a dead language? Sort of. We realize that Lisp is hardly used in software development except by a very small group of elite software developers. We chose Lisp for one simple reason: we believe it is the best tool available for building most of the software we need. In other words, we think Lisp is a great language. If you study Lisp we suspect you'll think it's a great language too.
If you prefer to use Java or .NET then you definitely should not apply for this job. We do not like those languages at all. We feel strongly that those languages are like diseases. However, we do not mind if you currently develop in one of those languages and, like a refugee from a war zone, are seeking to escape.
Furthermore, even though we like and respect Perl, Python, and Ruby on Rails, if you prefer to use one of these languages then you should not apply for this job either. We know Perl is for the old-timers, Python is what they use at Google, and that all the cool kids these days use Ruby on Rails.
We are not trying to be "old school" http://www.urbandictionary.com/define.php?term=old+school or to be like Google or to be cool. No. We are attempting to develop great software.
We did not inadvertently or naively choose Lisp. Not at all. We very carefully weighed the pros and cons of various languages and chose to use Lisp.
You must be willing to teach yourself Steel Bank Common Lisp. We will *not* pay for you to learn Steel Bank Common Lisp. You must currently have a *reliable* high speed Internet connection (DSL, Cable, T-1, etc).
We will provide you with no benefits whatsoever. No medical benefits. No holidays. Nothing. But we will pay all fees you will be assessed to receive your money, such as fees charged by GetAFreelancer and ATM machine fees.
We will not withhold any taxes from your salary whatsoever nor will we report your earnings to you local tax authorities. That will be your responsibility alone.
Except for the initial 10 day probationary period (during which we will only permit you to work 2 hours each day), we will pay you daily for the work you completed. Therefore, you will not need to, essentially, extend much credit to us. In other words, normally you will only need to trust us to pay you for one day of work.
During the 50 days following the 10 day probationary period, we will allow you to work as few as 2 hours each day but may allow you to work up to 10 hours per day. In other words, after the 10 day probationary period we may allow you to begin working full-time with us.
However, we will not require you to begin working full-time during this 50 day period. Why? Because we realize you may currently, for example, have a full-time job which you probably don't like, but at least "pays the bills."
However, after this 50 day period, we will require you to work 200 hours each month with us. Therefore, if you currently have a full-time job or other commitments which would interfere with you working 200 hours each month with us, then within 60 days after you begin working with us you will almost certainly need to quit your current job and/or abandon your other commitments.
In other words, after the initial 60 day period we are not interested in working with you on a part-time basis. We are only willing to work with you on a part-time basis for the initial 60 day period so that both you and we may become confident that we should work together on a full-time basis. Please do not apply for this job unless you are willing to work 200 hours each month with us after you complete the initial 60 day period.
In other words, we realize that many software developers reviewing the opportunities on GetAFreelancer are looking for part-time work. After all, this website is called GetAFreelancer not GetAnEmployee. However, if you are looking for a "side job" or some part-time work to supplement your current income and are therefore hoping to work, say, 50 to 100 hours per month, then please do not apply for this job. We are only interested in working with candidates who will be willing to work 200 hours each month with us after they complete the initial 60 day period.