My company is looking for a PHP developer to build an OS Commerce module so merchants can integrate with our billing system. This is a paid position. Location is not important.
I will be personally reviewing the code, so I know what to look for. Code quality is important. Code should take full advantage of OS commerce and MVC integration. If our API doesn't do something OS commerce has an option for, it would be nice if you let me know so I can build the functionality into the API.
Price is negotiable. I am looking for project rates rather than an hourly rate. I don't require that you know how to build OS commerce modules, though it would help. The end project will be distributed under an open source license. So that means I am going to pay you to write open source code. Most likely the code will be GPL'ed.
Doing this job could also lead to other jobs in the future.
If you are interested, please PM me via these boards with any questions, as well as CV or a site where I can see your accomplishments/experience, etc.
Paid Job: OS Commerce Module
Moderator: General Moderators
I got a couple of offers; however, in the end, it was just faster, and cheaper for me to do it myself. We will be releasing the module under the GPL within the next few days. Thanks for the offers.
As a side note: Suggestion to people responding to job offers, make sure you read the job offer completely, and if the job offer asks for something send it, or at least explain why you can't send it in the initial email. I got several people messaging me that didn't include a project rate, or wouldn't provide one. I wasn't asking for anything firm, just a general idea of what it would take to get a module written. I understand that these quotes can change as the developer get's more information, however, a simple "Usually a payment module runs $XXX.XX, however, this is obviously subject to the API" would have been fine. I didn't get that.
Now, this may seem like a small thing, but if you can't be bothered to read my original post, and address my needs, how will that reflect on you?
Remember, when you reply to a job post, you have to make a good first impression. This means providing as much information as possible. If I feel like I am having to jump through hoops to get you to give me an general estimate, then I am not going to deal with you.
To be more precise: I didn't know how long a payment module would take, on the norm. If you come back and tell me it usually costs $5000 for a module, than I am going to have something to work with. Granted, my project may only cost $2000, or it may cost $10000, but I have a budget, and knowing up front the general price range we are talking about is important.
When I say "I am looking for something", don't give me the opposite of what I am looking for.
Now, this is not to target any one person. I got several offers, and they all had the same problems. I don't do much contracting, mostly because of bad experiences in the past, and because a lot of what we do needs to be a part of a much larger system, so it's not easy to just bring someone on board for a small project. Small projects are always apart of bigger one's.
However, I think the real issue here is that those people who responded to this post had one thing in common: their was very little substance. Basically, if you want the job, you have to work for it. I put out the general information that is needed for the project. I got very little back beyond hourly rates, and that the person was interested.
I didn't get CV's, I didn't get really anything I had asked for, and the net result was that I felt like I had to do more work just to get the stuff I would expect initially. I shouldn't have to ask you for things that I had already asked for. This is not a good sign.
So, for those of you interested in getting jobs on the web, let me offer some advice:
1. Read the job offer completely.
2. Answer all the questions in the job offer to the best of your ability. Heck, if you don't know the answer because you don't have certain information, say so. But still, you can "assume" certain things. Saying something like this "While I don't know this about your project, most projects like yours involve this. However, I would need to get more details before I can give you an accurate answer" is, at least in my eyes, much better than saying "I don't know, send me this information", or not addressing the issue at all.
3. A CV/Resume is important. Frankly, I don't care if it's just a website, but something so I can get a feeling of who I am talking to. Please note, telling me the link is in your profile is not really that good. After all, if I print out your response, I won't see any link.
4. Finally, make me feel like you are interested in the job. A response of "Yes I am interested, here is my email if you want more information" does not suffice. Of course I want more information! I asked for it in the original job offer. That's along the lines of me posting something like "I have a job, email me if you want to know more." It just doesn't work.
Just some things to keep in mind. After all, these suggestions are only coming from someone who does and will hire people. =)
As a side note: Suggestion to people responding to job offers, make sure you read the job offer completely, and if the job offer asks for something send it, or at least explain why you can't send it in the initial email. I got several people messaging me that didn't include a project rate, or wouldn't provide one. I wasn't asking for anything firm, just a general idea of what it would take to get a module written. I understand that these quotes can change as the developer get's more information, however, a simple "Usually a payment module runs $XXX.XX, however, this is obviously subject to the API" would have been fine. I didn't get that.
Now, this may seem like a small thing, but if you can't be bothered to read my original post, and address my needs, how will that reflect on you?
Remember, when you reply to a job post, you have to make a good first impression. This means providing as much information as possible. If I feel like I am having to jump through hoops to get you to give me an general estimate, then I am not going to deal with you.
To be more precise: I didn't know how long a payment module would take, on the norm. If you come back and tell me it usually costs $5000 for a module, than I am going to have something to work with. Granted, my project may only cost $2000, or it may cost $10000, but I have a budget, and knowing up front the general price range we are talking about is important.
When I say "I am looking for something", don't give me the opposite of what I am looking for.
Now, this is not to target any one person. I got several offers, and they all had the same problems. I don't do much contracting, mostly because of bad experiences in the past, and because a lot of what we do needs to be a part of a much larger system, so it's not easy to just bring someone on board for a small project. Small projects are always apart of bigger one's.
However, I think the real issue here is that those people who responded to this post had one thing in common: their was very little substance. Basically, if you want the job, you have to work for it. I put out the general information that is needed for the project. I got very little back beyond hourly rates, and that the person was interested.
I didn't get CV's, I didn't get really anything I had asked for, and the net result was that I felt like I had to do more work just to get the stuff I would expect initially. I shouldn't have to ask you for things that I had already asked for. This is not a good sign.
So, for those of you interested in getting jobs on the web, let me offer some advice:
1. Read the job offer completely.
2. Answer all the questions in the job offer to the best of your ability. Heck, if you don't know the answer because you don't have certain information, say so. But still, you can "assume" certain things. Saying something like this "While I don't know this about your project, most projects like yours involve this. However, I would need to get more details before I can give you an accurate answer" is, at least in my eyes, much better than saying "I don't know, send me this information", or not addressing the issue at all.
3. A CV/Resume is important. Frankly, I don't care if it's just a website, but something so I can get a feeling of who I am talking to. Please note, telling me the link is in your profile is not really that good. After all, if I print out your response, I won't see any link.
4. Finally, make me feel like you are interested in the job. A response of "Yes I am interested, here is my email if you want more information" does not suffice. Of course I want more information! I asked for it in the original job offer. That's along the lines of me posting something like "I have a job, email me if you want to know more." It just doesn't work.
Just some things to keep in mind. After all, these suggestions are only coming from someone who does and will hire people. =)
That has to be the best, and most informative post this section of the forum has ever seen. Great stuff, Jason.
Not to take anything away from that advice but, if you're a programmer who desires some further reading on the subject of freelancing and client relations, check out the tutorial links in the sticky.
Not to take anything away from that advice but, if you're a programmer who desires some further reading on the subject of freelancing and client relations, check out the tutorial links in the sticky.
Last edited by m3mn0n on Tue Oct 05, 2004 9:36 pm, edited 1 time in total.
- John Cartwright
- Site Admin
- Posts: 11470
- Joined: Tue Dec 23, 2003 2:10 am
- Location: Toronto
- Contact: