Flexiple spent good amount of time understanding our requirements, resulting in accurate recommendations and quick ramp up by quality developers.
Overall Flexiple brought in high-level of transparency with quick turnarounds in the hiring process at a significantly lower cost than any alternate options.
Flexiple has been instrumental in helping us grow at a fast pace. Their vetting process for engineers is top notch and they connected us with quality talent quickly.
Flexiple Developers are reviewed on their experience and complexity of products built. Those who display depth and have worked on end-to-end projects are given an introductory call.
Over a call, the developer’s ability to communicate in an articulate manner is tested. A deeper understanding of the candidate’s technical experience and also motivation to freelance is achieved.
Over one or more F2F interviews, the developer’s involvement and performance in building complex software products are assessed. This sets the platform to delve deeper into technology-specific discussions.
Developers' mental agility and problem-solving abilities are tested through a coding test involving algorithmic as well as skill-specific problems. A mixture of live evaluation and timed coding tests is used.
The live experience of working with developers is verified by reaching out to past clients and/or employers. Inputs on various qualitative factors such as reliability, punctuality, communication and responsiveness are received.
Performance during each engagement is continually assessed. Our developers are expected to maintain Flexiple standards across all engagements with our customers.
The concept of front-end development has been around since the beginning of programming. However, during the earlier years, this was limited to the HTML and CSS on a webpage. The present definition of front-end development came into existence around the same time that JavaScript started being taken seriously. This was around the year 2009-10, when web and mobile development became mainstream. Prior to this, programmers weren’t differentiated based on area of expertise.
Over the years, the distinction between front-end and backend became clearer. JavaScript frameworks such as BackboneJS, AngularJS became quite popular and a lot of developers took to working on them. The front-end developer job role kept gaining momentum and is now among the most desirable job roles.
If you are wondering how to hire a freelance front-end developer, this blog is just the right place for you. We have compiled all the details you need to know about hiring front-end developers to help you find the perfect fit.
We have broken the sections into the following parts:
1. Introduction to front-end development
2. Why is front-end development widespread?
3. Writing the Job Description
4. Interview questions for hiring a front-end developer
- Basic Questions
- Advanced Questions
- Data Structures/Algo Questions
Here are some key points to mention in the job description when you wish to hire a front-end developer. We have compiled these here at Flexiple after trial and error - a process of filtering through over 15,000 developers.
Even with a quality JD, it can be tricky to find the best fit and evaluate the skills of your applicants. To assist you, we have created a pool of questions that good front-end developers need to be comfortable with. We have compiled questions across frameworks such as Angular, React and Vue.
Note that the ability to answer these questions doesn't imply that you have a top quality candidate. But it definitely is a big step in that direction.
We have categorized the questions into three parts to help you navigate easily:
A. Basic concepts: Includes all basic concepts used across languages. This will give you an understanding of how strong their programming foundation is.
B. Advanced concepts: Includes all concepts that someone with higher expertise should know.
C. DS/Algorithm questions: To test the logical capability of the candidate.
var variable = 0 if (true) { var variable = 100 } { { var variable = 1000 } } console.log(variable)
let variable = 0 if (true) { let variable = 100 } { { let variable = 1000 } } console.log(variable)
const obj = { name: "Flexiple", city: "Bengaluru" } obj.name = "Flexiple" console.log(obj)
const obj = { name: "Flexiple", city: "Bengaluru" } obj = { company: "Flexiple" } console.log(obj)
func = function() { return "end" }
func = () => { return "end" }
func = () => "end"
var url = "http://localhost:3000/id:"+id
var url = `http://localhost:3000/id:${id}`
func = function(param1, param2) { param1 = param1 || 20 param2 = param2 || true }
func = function(param1 = 20, param2 = true) { }
var req = { body: { username: "flexiple", email: "freelance@flexiple.com" } } var username = req.body.username var email = req.body.email
var req = { body: { username: "flexiple", email: "freelance@flexiple.com" } } var { username, email } = req.body
{
"flexiple": {
"top": "1%",
"location": "remote"
},
"blog": {
"topic": "engineering",
"title": "What are stable coins and how do they work?"
}
}
<?xml version="1.0" encoding="UTF-8"?> <root> <blog> <title>What are stable coins and how do they work?</title> <topic>engineering</topic> </blog> <flexiple> <location>"remote"</location> <top>1%</top> </flexiple> </root>
Valid JSON
Few of the rules to remember while handling JSON are that:{"name":"John Doe","age":32,"title":"Vice President of JavaScript"}
["one", "two", "three"]
// nesting valid values is okay
{"names": ["John Doe", "Jane Doe"] }
[ { "name": "John Doe"}, {"name": "Jane Doe"} ]
{} // empty hash
[] // empty list
null
{ "key": "\uFDD0" } // unicode escape codes
{ name: "John Doe", 'age': 32 } // name and age should be in double quotes
[32, 64, 128, 0xFFF] // hex numbers are not allowed
{ "name": "John Doe", "age": undefined } // undefined is an invalid value
// functions and dates are not allowed
{ "name": "John Doe",
"birthday": new Date('Fri, 26 Jan 2019 07:13:10 GMT'),
"getName": function() {
return this.name;
}
}
JSON.stringify()
It takes a Javascript object or array as input and returns a serialised string form of it.const obj = { name: "Flexiple", city: "Bengaluru" } const jsonStr = JSON.stringify(obj) console.log(jsonStr) // output is {"name":"Flexiple","city":"Bengaluru"}
let cost = { candy: 5, bread: 20, cheese: 100, milk: 15 } let func = (key, value) => { if (value < 15) { return undefined } return value } let arr = ['candy', 'bread'] let jsonStrWithFunc = JSON.stringify(cost, func) console.log(jsonStrWithFunc) // Output is {"bread":20,"cheese":100,"milk":15} let jsonStrWithArr = JSON.stringify(cost, arr) console.log(jsonStrWithArr) // Output is {"candy":5,"bread":20}
let cost = { candy: 5, bread: 20, cheese: 100, milk: 15 } let jsonStrWithNum = JSON.stringify(cost, null, 2) console.log(jsonStrWithNum) // Output is // { // "candy": 5, // "bread": 20, // "cheese": 100, // "milk": 15 // } let jsonStrWithStr = JSON.stringify(cost, null, 'xx') console.log(jsonStrWithStr) // Output is // { // xx"candy": 5, // xx"bread": 20, // xx"cheese": 100, // xx"milk": 15 // }
const obj = { "nest1": { "ex": "ex", "nest2": { "nest3": { "ex": "ex", } } } } console.log(obj) // Output is { nest1: { ex: 'ex', nest2: { nest3: [Object] } } }
const obj = { "nest1": { "ex": "ex", "nest2": { "nest3": { "ex": "ex", } } } } console.log(JSON.stringify(obj,null,2)) // Output is // { // "nest1": { // "ex": "ex", // "nest2": { // "nest3": { // "ex": "ex" // } // } // } // }
JSON.parse()
It takes a JSON string and converts it into its respective data structureconst jsonStr = '{"name":"Flexiple","city":"Bengaluru"}' const obj = JSON.parse(jsonStr) console.log(obj) // output is { name: 'Flexiple', city: 'Bengaluru' }
Cloning Objects in Javascript
These 2 functions of JSON can be used together to clone javascript objects.const obj = { "prop1": { "ex": "ex", "prop2": { "ex": "ex" } } } const objCopy = JSON.parse(JSON.stringify(obj)) console.log(objCopy) // Output is { prop1: { ex: 'ex', prop2: { ex: 'ex' } } }
+ axios@0.21.0 added 1 package from 1 contributor, removed 1 package and audited 2154 packages in 16.811s found 0 vulnerabilities
found 105 vulnerabilities (104 low, 1 high) in 371 scanned packages run `npm audit fix` to fix 102 of them. 3 vulnerabilities require semver-major dependency updates.
Low Prototype Pollution Package lodash Dependency of mongoose Path mongoose > async > lodash More info https://npmjs.com/advisories/1523
+ lodash@4.17.20 updated 4 packages in 24.002s fixed 102 of 105 vulnerabilities in 371 scanned packages 1 package update for 3 vulnerabilities involved breaking changes (use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)
# Run npm install nodemon@2.0.6 to resolve 3 vulnerabilities SEMVER WARNING: Recommended action is a potentially breaking change Low Prototype Pollution Package minimist Dependency of nodemon Path nodemon > chokidar > fsevents > node-pre-gyp > mkdirp > minimist More info https://npmjs.com/advisories/1179
=== npm audit security report === found 0 vulnerabilities in 206 scanned packages
Difference between Cookie and Local Storage
Primarily both function in similar ways - i.e. both involve persistent storage in the browser. The differences come in slight nuances of their functioning:Vulnerabilities
Local storagefunction palindrome(myString){
var removeChar = myString.replace(/[^A-Z0-9]/ig, "").toLowerCase();
var checkPalindrome = removeChar.split('').reverse().join('');
if(removeChar === checkPalindrome){
document.write("<div>"+ myString + " is a Palindrome<div>");
}else{
document.write("<div>" + myString + " is not a Palindrome <div>");
}
}
palindrome('"Madam"')
palindrome('"Star Wars"')
palindrome('"7,10,7,8,9"')
The output of the above code will be: "Madam" is a Palindrome "Star Wars" is not a Palindrome. "7,10,7,8,9" is not a Palindrome.
var p = 2;
var q = 4;
var r = 6;
if (p > q > r)
document.write("true");
else
document.write("false");The answer is False. It may look like the output can be true because 6 > 4 > 2 is true, but PHP evaluates $z > $y first, which returns a boolean value of 1 or true. This value (true or 1) is compared to the next integer in the chain, bool(1) > $z, which will result in NULL and echo “false.”
We will talk to Arjun and get back to you with their availability, fee details and detailed resume within 24 hours!
Just share your contact details :')
