3 ms·
In my opinion, it is not so much about the "type of projects" but more about the "understanding of your work" and ability to explain why/what you built. I have
by codegeek 5y ago
In my opinion, it is not so much about the "type of projects" but more about the "understanding of your work" and ability to explain why/what you built.
I have interviewed candidates who supposedly had a great Github Repo of apps they built but couldn't answer simple questions like "Why POST, why not GET. Can you do GET instead of POST. If yes, why. If yes, Why not". They got mad at me and told me "haven't you looked at my Github". I replied "I did and that's why I am asking how you built that project".
If I am hiring entry level, I wouldn't care if you built a Game or a CRUD App. I would care how you built it and how far can you explain the process of building it. How much do you really understand of what you built. For example, let's say you built a "Contact Form". I want to understand do you really know the difference between GET vs POST requests (you will be surprised how many candidates fail at this). I couldn't care less if you can just memorize how to add a GET API. I am more interested in your understanding of it. I want to know how the form gets submitted to the server (lot of candidates don't know how an http Request is formed, header vs body etc). Lot of candidates truly don't know how an AJAX request works. For example, if you submit a Form using Ajax vs Regular action, whats the difference ?
So, build anything which you can explain and walk through the process of. I would at least hire you.
- sander1095 5y agoI am curious. What is the difference between an ajax and form post
- Sohcahtoa82 5y agoForm post always causes a page load. An AJAX request is done asynchronously without changing the page until the request either succeeds or fails, at which point what happens depends on the code on the page.
- schwartzworld 5y agoYou can submit a form without JavaScript
- 908B64B197 5y agoI've seen this pattern from BootCamp/self-taught candidates. If you end-up interviewing candidates from the same bootcamp "batch" they'll all have the exact same portfolio project (and if you diff them there's going to be little to no difference between the different ones!) because they all followed the same tutorial to do it. So yeah, unsurprisingly, none of them could answer why use a POST vs GET operation.
- chakkepolja 5y agoYou are probably going to be downvoted, but this is the sad reality of the time when GitHub projects have become a measure. I have seen lot of people making exact same project from seeing some tutorial and putting it on GitHub. And that was a college, not a bootcamp.
- b20000 5y agoso once they answer your questions, are you going to have them do the leetcode BS? let me guess…
- codegeek 5y agoI personally don't :). We are not FAANG and unless I have that level of demand from candidates, I wouldnt do it
- bjourne 5y agoYou must have lots of qualified candidates to choose from if a game or a CRUD app isn't a shoe-in for an entry-level position. Many developers who call themselves senior would struggle with writing such programs. People have holes in their knowledge. Some people don't know how the difference between GET and POST, others can't explain hash tables, why merge sort is preferable over quick sort for disk-based storage, or the difference between a lambda and a closure, and so on.
- thrashh 5y agoI have fortunately not yet had to work with a senior web developer who would struggle with such a basic question about how the web works. Now if I hired a firmware engineer, sure they might not know about GET vs POST.
- xu3u32 5y agoAre you looking for something as simple as GET is for fetching data and POST is for inserts? Or something beyond that (state, idempotency,...)?