Topic: Software Development Team RFP

Camp: Agreement

Camp Statement
Go live Time :

Chief Software Architect


Software as a service Firm

We need someone who can lead the canonizer software team continuing the development of the open source Canonizer.2.0 system, currently using LAMPS with the Laravel framework. Including help with the following priorities:

  1. Currently the system is running on a single AWS EC2 instance. This can only handle a small number of users at a time, without significant performance degradation. A system needs to be designed, enabling the system to expand to new instances, as needed, to handle any load. We also need to develop a way to test it to prove it is working.
  2. Re Architect and help implement and convert to a new text editing and management system module. The current wiki markup is cumbersome with inconsistent formatting. “Ease of use” being of utmost importance, so UI design abilities are important.
  3. Where possible support the open source community. If there is open source code we can use, let’s leverage that, or else architect modules others can use.
  4. Help finish the design of and conversion to a fully test driven development system, with 100% automated tests and deployment to enable continuous release process.
  5. Help prioritize tasks and perform team code reviews of all new development.
  6. Convert the system to a service oriented architecture, starting with the creation of a new “canonizer” service. This service may be built on something other than LAMPs, with cpu efficiency being of primary importance. Design an API which can provide a topic num, an asof value, and a canonizer id. Given that, it will return a JSON tree structure of camps and supporters of that topic, decorated with canonized scores of the selected canonizer ids, which can then be rendered on topic pages, or called by third parties. We eventually want to provide users the ability to program their own canonizer algorithms, so a design towards making this easy for users is important.
The goal of Canonizer is to be a leaderless organization where everyone knows everything. Anyone interested in applying for this job is invited to create a sub camp, with a camp statement describing how they are the best person for the job. Then the canonizer canonizer algorithm will be used to select the top candidate. Candidates are also encouraged to support the camps of themselves, and all competing candidates, in the order they think is the best candidate to achieve the Canonizer goal of bringing the world together.

The target salary for this job is $12000 USD / month or $144,000 USD / year, (paid in Ether if desired) depending on experience. However, if you are able to be a top performer, and willing to work for less money, indicating such in your camp statement would increase your chances of getting more people to support your camp.

You could answer at least the following questions in your camp statement:

  • How would you enable canonizer to be massively scalable? It needs to be able to automatically grow, when needed, to handle millions of simultaneous users, then scale back to save costs when load is absent?
    • You will get extra credit if you collaborate with others competing for this position to build consensus around and collaboratively develop a design, possibly creating a supper camp multiple competing camps can support, showing your support for that scalable software design as it is being collaboratively developed. If you are late to the game, and others competing for this position have already developed and are supporting a good design, you may just choose to move your camp into a supporting sub camp position of that design, indicating you think it is the best design. Of course, any additional contribution to improve any existing design camp will be to your credit.
  • What type of team management or prioritization tools do you like to use, if any?
  • What is your philosophy on code reviews by team members, or strategies such as team or pair coding?
  • What experience do you have setting up and maintaining systems that are 100% continuous delivery enabled, including automated tests that prove 100% of functionality still works with each modification made to the code, along with automatic deployment of such fully tested changes
    • What were the most difficult parts of setting up and maintaining such a continuous delivery system, and how were these issues addressed?
  • Provide any other ideas of how you could contribute or help improve Canonizer and it’s goals.
  • Do you have any examples of times when you went beyond what was being asked of you by your immediate supervisor to further the goals of the company or humanity as a whole?
This recruiting process is expected to take multiple months to find the best person. We are a global team so it doesn’t matter where in the world you are located, we only ask that you be flexible with meeting times.

Support Tree for "Agreement" Camp

Total Support for This Camp (including sub-camps):

Current Topic Record

Topic Name : Software Development Team RFP
Namespace : /organizations/canonizer/

Current Camp Record

Camp Name : Agreement
Keywords : canonizer, network, db, design
Camp About URL :
Camp About Nick Name : No nickname associated