Developer -API/Backend/Email System

Background

We’re launching a new recruitment solution and are building a website which will have two components:

- a brochure site
- an online application which will be integrated into a recruitment system backend.

The company is a brand new start up, offering an innovative recruitment solution for blue chip clients. The company combines our proprietary filtering system with an online application to reduce cost and increase value.


Requirement

A Developer to build an API between the website and our recruitment system backend, building and integrating a transaction based, scheduled email system, plus management console.

We are looking for a developer to recommend the best technology to fit with our requirements. Particular focus will be on simplicity, user management and opportunity to evolve.


Deliverables Overview:

All deliverables need full integration with our backend recruitment through API’s. Our preference is not to store any data outside of our recruitment system, though we recognise that this may not be possible in specific cases.


1. Search For Jobs

Candidates should be able to search for jobs based upon industry standard search criteria. See jobserve, CWJobs, Jobsite for examples.


2. Post a Job

Clients should be able to easily and simply upload a job spec, leaving their contact details, name and company name.

During this process we will need to capture further detail to allow us to begin the recruitment search. This further information includes - acceptance of terms, credit card details, further job detail including location, duration, rates, tick boxes confirmations of budget approved/7 day exclusivity/agreement to feedback in 7 days.

Posting a job is a 3-4 stage process, the system will need to capture lead information from users that drop off at any stage of this process. Ideally this will include an email to our sales team, and populated fields in our recruitment system.



3. Apply for a Job

Contractors can apply for a job once they have searched on our site, or been driven to our site by email blasts or via one of our advertising partners.

When entering this process they will be asked to upload a CV, which (through an API to our recruitment system) may be used to populate most forms needed for their application. Whether the CV parsing functionality is low latency enough for enjoyable customer experience will determine whether this functionality should be used, or a manual form filling process should be followed.

Aspects of the candidate’s personal details can be parsed from the CV –details in wireframe.

Screening Candidates

In addition to an industry standard job application process the applicant will need to complete a bespoke screening process to help our algorithms rank the applicant against all other applicants for the specific job role. In order to provide the relevant information for the algorithm calculation the site needs to capture a breakdown of experience in a job title and for 5-10 skills for each applicant. For the job title and each skill the candidate will be asked how long they have in the job title/worked with the skill and when they last worked in the job title/with the skill.

The system will need to access the algorithm built in excel and rank applicants based on their score in the algorithm, then capture their score in our in house recruitment system. Advice is needed as to whether this is possible using the excel based algorithm (currently available), or can only be delivered once the algorithm is hard-coded.


4. Transaction Based Emails (including Scheduled Emails)

A system is required that can send emails which are triggered by database transactions, and in addition scheduled emails up to 1 week after the database transaction has occurred. This system should be rules based and should include a user console to build new transaction based emails and amend emails that are sent (including revision of timelines for schedules).

Use case example: If an applicant’s CV is sent to a customer, a further email should be sent to the customer on the 2nd, 4th and 7th following days asking the customer to feedback on the desire to progress or reject the CV’s. This is one of the most complex of use cases as it includes multiple emails over a protracted period of time, in addition the system needs to query the database to ensure that feedback has not been received before issuing each email request for feedback.

There are a number of use cases in which transaction based emails will need to be created, and we expect new use cases to be defined as the business develops.

All emails need to populate the recruitment technology via API.

Initial research into email systems have included Postageapp, Sendgrid, Mailjet, and Jango (being the most widely recognised), however we have no working experience of these systems and require guidance in selection of a technology solution.


5. Feedback System

Each CV that is sent to a customer requires feedback from that customer. As such, the customer must be able to formally progress [to interview] or reject an applicant's CV. Our strong preference is an email solution that allows the person reviewing the CV to reply to the CV send email noting whether to Progress or Reject that candidate. Ideally our system would recognise the content of the mail and change the status of the application in the third party system to Rejected or Interview request.

Could this be achieved through a table in an email? i.e.

Candidate Name Interview Reject
John Smith Yes
Dave Jones Yes


If the proposed solution above is not achievable another method to manage feedback must be proposed in its place.


Required Output of this Brief

- Suggest technology solution for the building of the backend of the site. Please provide supporting explanatory note for why the technology architecture has been suggested.
- Suggest technology for transaction-based email. Please provide supporting information for proposed transaction based email technology
- Examples of API projects completed recently
- Proposed costs for the engagement


Next Steps

A decision will be made following the initial proposal. The successful supplier will then be provided with a more detailed technical brief (including data map) and full wireframes.


Deadline

Initial proposal and costing required: Tuesday 10th April 2012
All requirements delivered by: Tuesday 24th April 2012


Your Costing and Proposal
1. Costing and proposal submission deadline is 10th April 2012
2. Please highlight any assumptions that you make within your costing and proposal.
3. Please breakdown your costs against the deliverables outlined above using the same numbered format.
4. Please provide us with the process you would follow in order to fulfil the project brief, any input or assets needed from Project Brighter and a timeline for these items.
5. Please sign and return the NDA document.