How to politely reject job offer applicants


Hi %username%,

Thanks for taking the time to apply with %companyname%!

We’ve been fortunate to have many talented and qualified candidates express their interest in joining the %companyname% team. Ultimately, we’ve decided to continue the process with other candidates whose backgrounds are a stronger fit for our team at this point in time.

It’s never an easy decision or one we take lightly. Please know that we appreciate your interest, and wish you the best of luck in your future endeavors.

Kind regards,


Hi %username%,

Thank you for your application to %companyname%. After reviewing your work and experience, we’ve made the decision to not move forward at this time. I hope you don’t mind if we reach out to you in the future when a position opens up that may be a good fit.

We appreciate your interest in Enlitic and wish you success in your job search.

The %companyname% Recruiting Team

How to Answer: Do you have any questions about the job description?

If you don’t know how to answer this question, I will give you some examples below. So let’s get started.

Do you have any questions about the job description?

1. No, i don’t, but I understand your request.

2. I need to know more information about the project before asking any further questions.

3. Not yet.

4. May I know how many hours are needed each week? I am also interested in knowing what is your most preferred working time.

5. When I get the job.

6. I don’t have any questions yet, but I let you know upon hire.

7. I understand and can do the work successfully. It is very easy job for me and I have no questions about the job description.

And how would you answer this particular question? Share your thoughts in comments.

How to Answer: Do you have suggestions to make this project run successfully?

You don’t know what to answer this question when applying some job? I will give you some ideas below.

1. In order to make this project successful, the contractor should ensure speed, accuracy and quality of work.

2. Yes. Accuracy and Dedication makes this job 100% successfully.

3. No suggestion.

4. No, i just follow my client.

5. Honest freelancer and who have great feedback could be made this project successful.

6. Patience, accuracy and determination would make it successful.

7. It will be successful if the right work is done by the right employee.

And how would you answer the “Do you have suggestions to make this project run successfully” question? Let me know in comments.

Why Protect My Files?

A lot of people assume that just because their computer has an anti-virus suite installed, it’s going to be fine and no one can steal your data. Realistically, if you work in an office or you take your laptop to Starbucks, this just isn’t the case, and the ability of individuals to dip in and out of your hardrive is defined only by where you take it.

Encryption is the key to good data protection, and of course you’re able to encrypt everything you like, from single files to folders containing important documents and information. It’s not a complicated series of methods, and of course the documentation we provide online for you will teach you how to encrypt everything.

But what data should you be taking more care of? Well, simply, anything you wouldn’t show to a random person on the street! This can be anything at all, from a novel you’re working on (this is exceptionally important, as this is something you may not have yet established copyright on, yet) to your O2 Broadband username and password – not fun if the person manages to start taking over your home Wi-Fi network at three in the morning.

When thinking about encyption, it’s also much easier to use software to encrypt rather than relying on archaic methods or worse, DIY with little experience, as you may find that the end result is you being locked completely out of your files, with no way back in – a rather ironic end to the noble goal of keeping your data safe!

We offer a great range of software that will help you achieve the level of encryption required to stop nonchalant data-thieves, so relax, enjoy your computer, and keep safe – you never know when you might next find yourself surfing on public Wi-Fi!

Ajax without jQuery

Like many before me, I was introduced to jQuery before I was even remotely proficient in vanilla JavaScript. And while I think a web designer can do very well with basic jQuery skills, the further one moves into web development, the more important it is to have an understanding of plain JavaScript.

Since coming to understand this, I’ve put myself on a strict no-jQuery diet, in order to better understand the language. So far, I have learned a lot, one of the many lessons being just how much work jQuery does for you behind the scenes.

So there I was, on my no-jQuery diet, when I came across a problem. I needed to use AJAX. Specifically, I needed to get data from Dribbble’s REST API and display it on my website. This was a problem because I couldn’t just $.getJSON my way to safety. This time I had to do it the hard way. So I gritted my teeth, swallowed my pride, and did what any web developer does when they reach a problem: lot’s of googling.

The first thing that caught my eye was a grouping of keywords, CORS, JSON, and JSONP. I knew what JSON was, but I was unsure of the other two. As it turns out, they’re both pretty important, and worth a quick review.


JSONP, or JSON with padding, is used when you need to get JSON data from an external domain. This is prohibited when using regular JSON due to possible security implications. You can read more on JSONP here. As it turns out, JSONP isn’t a special version of JSON, like I had originally thought. Instead, JSONP is a way to use cross-domain JSON data without having to worry about the browser preventing you from doing so. JSONP takes advantage of the fact that browsers don’t implement the Same-origin policy on script tags.

To use it, we need to create a script tag that has a callback function appended to the end of its source attribute. We then use that function to manipulate our JSON data. The whole process is relatively simple and only requires a few lines of JavaScript.


CORS, or Cross-Origin Resource Sharing, is another method that enables cross-domain JSON. For more nitty gritty details, checkout

CORS introduces a standard mechanism that can be used by all browsers for implementing cross-domain requests. The spec defines a set of headers that allow the browser and server to communicate about which requests are (and are not) allowed. CORS continues the spirit of the open web by bringing API access to all.

Simply put, if a server supports CORS, you don’t have to worry about the same-origin policy and you can make a standard JSON request. Here’s a demo that makes a request to the Github API, which supports CORS. If everything goes correctly, you should see URL that points to a Github issue. Note that this code is also jQuery free (I’m still on my jQuery fast).

Of course, not all browsers act the same, which means that sending a CORS request over any browser under IE10 means that a bit more code is involved. Telerik offers a great tutorial that explains how to write a function that supports CORS requests for IE8 and up.

Hopefully the quick overview above has given you a little insight into the powers of plain JavaScript if you come from a jQuery background.

JavaScript Date Tips

The other night at the Hudson Software Craftsmanship meeting at the Falafel Software training center in Hudson, Ohio, I did the Red Pencil Kata using JavaScript. Although I’ve run into it in the past, I was stuck for a little while (I was the odd man out without a pairing partner to help find these things faster) due to one of JavaScript’s “fun” date conventions. Being a C# developer primarily, there are many small things I have to remember that are different between JavaScript and C# (like where to declare variables, for instance). In this case, it was the code for generating a particular date that bit me. At one point, I wanted to generate a date that was over 30 days in the past (relative to the current date, which was 16 July 2014), so I wrote this:

var day1 = new Date(2014, 6, 14); // javascript

If I were in C#, this code would have worked fine:

var day1 = new DateTime(2014, 7, 11); // C#

You see, the folks who wrote C# were not insane, and so they didn’t arbitrarily make the middle ‘month’ parameter 0-based, like the JavaScript folks did. In my kata, it was important that certain things happen around the 30-day window, and of course my silly mistake had created a date that was only 3 days in the past, not 32. Oops. Of course, you should be able to avoid this by using a string, right? That’s what some of my fellow developers suggested. What do you suppose this yields?

var day1 = new Date(“2014-07-01”); // javascript

If you answered 30 June 2014, you’re right! Of course, that’s just what you would expect, too. WAT?

Of course, if you use something hideous like this, it works correctly (in the United States, which expects M/D/Y format):

var day1 = new Date(“7/14/14”); // javascript

This, too, will give you what you expect, though it’s a bit verbose:

var day1 = new Date(“July 14, 2014”); // javascript

Go ahead and play with these options yourself here:

function log(x)
    $("#output").append(x + '

(function () {
    var day1 = new Date(2014, 6, 14);
    log("day1: " + day1.toDateString());
    var day2 = new Date(2014, 0, 1);
    log("day2: " + day2.toDateString());
    var day3 = new Date("2014-07-01");
    log("day3: " + day3.toDateString());
    var day4 = new Date("7/14/14");
    log("day4: " + day4.toDateString());