• Breaking News

    Monday, June 28, 2021

    Every single interview question I was asked while changing my job. web developers

    Every single interview question I was asked while changing my job. web developers


    Every single interview question I was asked while changing my job.

    Posted: 28 Jun 2021 05:56 AM PDT

    Hello everyone.

    I've gotten a lot of use out of this forum, especially while I was starting out. So hopefully, this is my way of giving back a little bit.

    A bit of background:

    I've been working in development for a good few years now and recently decided I wanted a change from agency work. While the agency is full of great people, work-wise it wasn't what I was after.

    So cue a series of interviews which has thankfully led to a new position. I decided to note every question and technical task I had to go through in the hopes it would help people, new to the sector or not, to prepare for their next interview. I'll break it down into stages and won't go into too much detail about how I responded but will make any notes if anything stood out. For context, I was applying for mid-level roles in London.

    Stage 1. Screener Calls

    In almost all cases except for tiny companies, there was a screener call with an internal recruiter. One pattern I noticed is that they almost always aren't technical, they're short, and almost always follow this format. This should be the least stressful part of the application process.

    1. They'll tell you a bit about the role.
    2. Standard tell us about yourself question.
    3. Tell us about your current role?
    4. What tech stack do you use?
    5. Do you have any experience with X (Some tech listed in the job description)?
    6. Are you interested in X (Some non-dev skills listed in job description e.g. mentoring or design tasks)?
    7. What are you looking for in a new role?
    8. What's your current notice period?
    9. What salary are you looking for?
    10. Do you have any questions for us?

    That is generally it. I don't want to underplay the value of an internal recruiter but it seems like you apply and then makes sure you literally tick some boxes from the spec. If you do they'll pass it on to the team you'd potentially be joining.

    Step 2. Initial Interview

    If your details are passed on and the team like your CV you'll have an initial interview. These are the most varied. Some of them were basic chats and some of them included algorithm questions. One thing that became apparent to me is while some industries have a generic format for interviews like retail or sales, tech is absolutely just winging it. I think most will be surprised at the variety, and unfortunately, it makes it really hard to prepare.

    1. What does the deps array in useEffect() do?
    2. What do you know about the company?
    3. Tell us about yourself?
    4. Why hire you?
    5. How have you managed stress in the workplace?
    6. Tell us about a time you've led on a project?
    7. Tell us about your choice of CSS preprocessor?
    8. CSS Methodologies?
    9. What is a Linked List?
    10. What's the fastest way to find the middle of a Linked List?
    11. What does it mean when a function is idempotent?
    12. What is a pure function?
    13. What was a major change in React around 16.8?
    14. What's the difference between white/black box testing?
    15. What's the difference between unit, integration, and e2e testing?
    16. What is batching in React?
    17. Difference between props and state?
    18. What's the difference between classical and prototypal inheritance?
    19. What does good code look like to you?
    20. What's a piece of code/work you're proud of? (This one came up a lot)
    21. What are styled-components?
    22. What are the status codes for REST API calls?
    23. Tell me a bit about what Jest/Enzyme is used for?
    24. What's the difference between shallow mount and render in enzyme?
    25. What's your working style/ how do you work at your current job? (Might branch off into some agile questions?)
    26. What's your opinion of the React landscape?
    27. What are the pros and cons of working with Typescript?
    28. How would you go about clearing tech debt?
    29. What's your approach to testing?
    30. What is hoisting?
    31. Do you have any back end experience?
    32. How would you handle large data sets from the backend to the frontend?
    33. What are higher-order components?
    34. What are higher-order functions?
    35. Difference between let/var/const
    36. Benefits of styled components over traditional minified one CSS file.
    37. Benefits of class over function components?
    38. When would you use a class or function component?
    39. What is snapshot testing?
    40. What's the difference between a normal function declaration and an arrow function?
    41. What's your product release cycle like?
    42. Do you do sprints?
    43. What React hooks are you familiar with?

    I don't know if it's hard to see from just a list. But I felt like I'd prepare for an interview, only to have it be nothing like the previous one. Some were asking in the context of scaling to X thousand users. Some were just chats. Some people were friendly, some were desperate, some were obnoxious. I'd prepare to talk about unit testing for a job that listed it as very necessary only for them to never mention it.

    Stage 3. Tech Test

    Honestly, the most frustrating part. It felt like no matter how well I did in the initial interview they'd ask me to do a tech test. I could smash every question they threw at me. Point them to my previous work. Have worked on an X month-long project doing exactly what they require, and they would still ask me to do some work. Some of them even implemented the suggestions or work I did. So in essence I worked for free and they were farming stuff bit by bit from applicants.

    These are all the tests I was asked to do and I'm providing them as a reference, but I actually turned some of them down. One said knowing Vue isn't a requirement but then the test itself required building a large project using Vue. So it's a bit like... if I have to know it to pass the test then it is a requirement. People might argue well it filters out those who aren't willing to learn. Some people might be willing to give up the 2 days they get a week to learn a new framework to apply for a job that specifically said it isn't needed, but I'm not one of them.

    Some were good. Some were responsive to questions for clarification. Some had such a high turnover and then flipped their lid when I refused to do it which in hindsight is probably linked.

    Anyway, they obviously touched a nerve. I'll stop rambling now.

    1. Go through our site and tell us what you'd change (x2)
    2. Hit an API of fake products, display them, be able to add them to a basket.
    3. Make a node/express server with a DB, be able to add comments to a document, have them be persistent and saved to DB, make sure to unit test etc...
    4. An online algorithm/problem-solving coding challenge on HackerRank or Codility type of thing.
    5. Build a production-ready dropdown component for React.
    6. Build a Gmail clone (this is not a joke)
    7. Using the StarWars API (swapi), make a top trumps clone.
    8. Recreate this design in React, be production-ready (almost definitely just farming free work. Design was branded etc...)

    The biggest thing I took from this is writing tests wins you a lot of points. I guess cos they kind of demonstrate best practice, coding ability, etc... all in one.

    Stage 4. Final Interview

    These were the most stereotypical interviews. Once all the tech was out the way it just boiled down to generic competency-based questions. In no particular order.

    • Tell me about a time you've led on a project.
    • How would you break down an epic into granular stories?
    • How would you deal with a PM asking you to do something faster than planned?
    • How have you handled unexpected positive feedback?
    • How have you handled unexpected negative feedback?
    • How have you dealt with a time where everything is going wrong?
    • Why should we hire you as opposed to another candidate?
    • Why do you want to work here?
    • What are your ambitions over the next 1/2/5 years?
    • What are our company values?
    • What are you looking to get out of this role?
    • How do you see yourself improving the quality of our team when you join?
    • How do you work to maintain relationships with colleagues?
    • Do you prefer a slow introduction to things or prefer to be "thrown in the deep end"?
    • Have you ever stood strongly for something then changed your mind?
    • How do you deal with conflicts between the team and stubborn clients?

    Anyway, I know this might not be of huge help but I thought it might be good for some people to have an up to date interview reference thing if they're thinking of applying for the first time or even just changing role after a while.

    Things learnt from the process.

    • People love it if you know about unit/integration/e2e tests.
    • Saying you don't know is OK.
    • If they want to see a Github repo full of open-source commits every evening and weekend then I'd stay away from them.
    • If they're complaining about not being able to find good developers what they mean is they refuse to pay what it takes to get one.
    • If they're open to questions or feedback and value your time, then keep them on your shortlist. They're probably great to work with.
    • Don't be scared to ask for clarification.
    • If they want a React build, ask if they prefer using hooks maybe. Or ask how they manage their CSS.

    That's it! Hope someone somewhere gets some good use out of this.

    submitted by /u/Boofern
    [link] [comments]

    Anyone else tired of being forced to be a designer?

    Posted: 28 Jun 2021 05:22 AM PDT

    I'm a full stack developer at a small company, and have one other colleges that works on smaller projects.

    When a feature/task is being added to the software I am developing, I am just told what it is and a date it needs to be done. I am doing everything from start to finish including the design. This takes a majority of my time just thinking and planning how it should look. I don't enjoy doing it, and it slows me down. Am I good at design? It's debatable but I follow modern practices, but it's not something I have time to focus on bettering myself at.

    Is the common for this role to be added on top of development for the front end and back end role? Not to mention I handle DevOps on top of this.

    I'd probably get laughed at if I mentioned bringing on a web designer.

    submitted by /u/vazura
    [link] [comments]

    Nice to see a government website - with millions of users lately - not supporting IE11 anymore.

    Posted: 28 Jun 2021 03:36 PM PDT

    About learning lot of languages, my 2 humble cents

    Posted: 28 Jun 2021 01:34 PM PDT

    Hi everybody,

    I'm 38 years old and I started to learn and love HTML back (I believe) in 1998 when I was in high school. Then I started to learn PHP and CSS, and in 2004 I met a friend who loved Macromedia Flash and doing graphics assets with Photoshop. We started working together and we still are.

    After we said goodbye to Flash he started to learn HTML and CSS because he wanted to "visualize" his design without waiting me to do the coding. Now he does things that I probably would never do if I wanted to focus on all those languages, and in all those years I learned a lot of PHP.

    I know, I'm old, there are a lot of frameworks now, fighting each other to stand up, but I always consider myself a newbie since I try to learn something everyday.

    Why I started this thread? Because I read a lot of posts/blogs that suggests to young developers (wish them all the luck) to learn a lot of languages, being a full stack developer, quickly learn frameworks and whatsoever.

    In my humble opinion, I was way more happy and it was more satisfying to focus on few languages, PHP as the first one, then HTML/CSS/JS that I still occasionally write today. I also focused myself to learn the vanilla versions of all those languages, because I wanted to really understand each one of them. We built a CMS and we're still using it for all our clients.

    What do you think? Should young developers really learn a lot of languages?

    Sorry if the thread is dumb.

    submitted by /u/silentheaven83
    [link] [comments]

    Made a site to track how long it takes to hear back from companies

    Posted: 28 Jun 2021 06:38 AM PDT

    Reddit's disrespectful design

    Posted: 28 Jun 2021 06:28 AM PDT

    The Self-taught Web Developer: YouTube edition

    Posted: 28 Jun 2021 11:45 AM PDT

    Hello everyone 😊

    I have created this list of YouTube tutorials for learning web development for beginners. It's not completed yet and is still missing many topics that I have not added yet. Feel free to contribute to this small project of mine and star it if it helps you.

    If it's not allowed on this sub please tell me I'll delete my post.

    Here is the link on Github

    submitted by /u/Prize_Barracuda_5060
    [link] [comments]

    Marketing manager called me over every little thing, I told her to stop doing that because it interfered with my work process over trivial things, am I in the wrong?

    Posted: 28 Jun 2021 07:09 AM PDT

    I am a sole developer looking after an online store with legacy code, needless to say I've got enough stuff to take care of. There's one woman in marketing who keeps calling me over trivial things, minutes ago she called because she wasn't able to format text correctly in a WYSIWYG editor and asked if I could help with it. While in that particular moment I was just having a lunch, there have been times where she interrupted my workflow and thought process with trivial 'problems' which she could solve herself if she took any time to research. So I just told her that I could help but I would appreciate if she didn't give me any more calls over such matters and she sounded upset. Am I in the wrong for saying that? I get it, they're paying me to be their "computer stuff guy" but at the same time it's damn frustrating.

    submitted by /u/hookerabductor
    [link] [comments]

    Just created my first ever public Git Repo [NodeJS]

    Posted: 28 Jun 2021 12:58 PM PDT

    I wasn't sure where to post this so I hope this is somewhat relevant but I just posted my first ever public repo with an extremly simple utility with one function in mind. I wanted to know exactly how much space my node_modules folders were taking up on my machine! So I spent this afternoon flexing my newly acquired TypeScript skills. Any feedback is welcome!

    https://github.com/kierancrown/nm-sizer

    submitted by /u/kierancrown
    [link] [comments]

    Are there any JS frameworks that do all the 'magic' that Ruby on Rails can do?

    Posted: 28 Jun 2021 11:09 AM PDT

    Just learned some basic Rails and I am impressed with how it seems so easy to get an app up and running. I know Rails has fallen somewhat out of favor and I'm wondering if there are any similar frameworks in JS that come close to this level of 'magic'? If not, why not?

    submitted by /u/Cold-Fan
    [link] [comments]

    Random Blank Submissions in PHP Form

    Posted: 28 Jun 2021 02:26 PM PDT

    Hello there,

    I coded a website which has multiple PHP forms. The website has been working fine for over a year. A few days ago I started receiving blank submissions in the forms. I receive one or two of these blank submissions per day and so far none of the submissions end up being on the same form. Every field on the form is required so it shouldn't be possible to submit a blank response. Me and some friends tested out the forms shortly after this started and they all worked fine and never sent anything blank whenever we tried. My forms are formatted in the following way: I have an HTML page with content including the form at the bottom. When the submit button is pressed the inputted info is sent to a .php file so that it can be sent to me. The only way I've managed to send a blank submission was to paste the link to the the PHP page of each contact form directly into the browser but standard users wouldn't know the link to the PHP pages without specifically looking for them. Any ideas what could be causing these blank submissions?

    I haven't included any code yet because there are many forms and I'm not currently near the computer with the code saved but I can include it later if needed.

    submitted by /u/66EmperorPalpatine66
    [link] [comments]

    Do you think Go will eventually supersede PHP as the dominant server-side language?

    Posted: 28 Jun 2021 04:54 PM PDT

    What are the pros and cons of both would you say?

    submitted by /u/VSK-1
    [link] [comments]

    Opinions about my website

    Posted: 28 Jun 2021 04:48 PM PDT

    I am a self-taught web developer and i created a personal website so i can start freelancing as a front-end web developer, i am not much of a designer and i have chosen to go with a minimalist approach.

    Please feel free to give me your opinions regarding the overall looks of the website and if there is something you would like to see improved or changed.

    http://www.mezweb.tn/

    submitted by /u/MEZ_1995
    [link] [comments]

    react-query: A magical way to fetch data in React

    Posted: 28 Jun 2021 05:25 AM PDT

    Nice nginx features for operators

    Posted: 28 Jun 2021 04:35 PM PDT

    Google Lighthouse coverage vs. chrome coverage

    Posted: 28 Jun 2021 04:02 PM PDT

    I am trying to optimize a JS file, and have been using Chrome's coverage tool to find unused parts of the file and cut them out. After some work, the Unused Bytes are down to 20%.

    Fast forward a little bit, I am now working in Google Lighthouse and testing out performance and it is saying that same script is 90% unused.

    Why are Google Lighthouse and Chrome's coverage tools so different? Ultimately, I want to make the JS more performant, but I also have customers that use Lighthouse to determine if the scripts are causing performance issues.

    submitted by /u/cyphun
    [link] [comments]

    Build Static Websites with w3school spaces free hosting service.

    Posted: 28 Jun 2021 05:16 AM PDT

    Need career advice

    Posted: 28 Jun 2021 11:50 AM PDT

    I'm a webdev predominantly working in Front end especially react. I have had my episodes of little bit of backend with Django, node and stuff but currently, my company is offering me to switch to backend/full stack totally and I got three options

    1) node

    2) java

    3) Scala.

    I'm fine with all three but i still want to know which one would be a better career choice in long run.

    Bit about me. I'm 6 years experienced and have fairly expert level knowledge in JS. I keep in touch with Java even though I haven't worked on it in a few years. Scala I have to study from scratch.

    I would like to know you guys' take on these three. My concerns predominantly revolves around.

    1) how much market they have. If I leave this company after a couple years which one can be relied on more for a better job.

    2) I heard node is used every where but not a enterprise scale but just as some micro service while java is still industry leader.

    3) is java sustainable for next 5 years. I know they are giving away updates on a consistent rate but is the current enterprise market thinking of Java as THE standard or is it just living with java to maintain legacy stuff while moving away to something else?

    Thanks in advance.

    submitted by /u/Terminal_Monk
    [link] [comments]

    Can't scroll to overflown elements.

    Posted: 28 Jun 2021 03:04 PM PDT

    Basically, I have a div with 700px, the problem is that its items are overflowing outside the entire page (intentional), and since the div is 700px you can only scroll to see 700px worth of content. Even if I make the div's width 100% of the vw I still can't scroll to see all elements. Is there any way around this?

    submitted by /u/HasanTheSyrian_
    [link] [comments]

    How would you create a legend showing colors used in a project?

    Posted: 28 Jun 2021 03:03 PM PDT

    By a legend I mean like they have for graphs, where it shows that X color means this, and Y color means that.

    The project in this case is a path finding visualizer. So there's different colors for various things: start node, end node, obstacle nodes, path nodes, open nodes, closed, nodes, etc.

    I find it SUUUUUPER tedious to go in and manually create styles for each of these (I'd have to create a class for each: .start, .end, .obstacle, .path, .open, .closed, then set the specific colors of each class so the legend shows up correctly.

    Then what if I wanted to change what color the obstacle nodes are? I'd have to change it in my JS so the actual obstacles are different, then go into my CSS and change the .obstacle rule.

    This doesn't seem correct. What would be a better way of going about this?

    submitted by /u/Missing_Back
    [link] [comments]

    What measures can I take to avoid a web designer (freelance/agency) either giving me a design they have already used (or a 3rd party design) or giving away a custom design which they originally sold to me to another client later in the future?

    Posted: 28 Jun 2021 01:26 AM PDT

    that ^

    submitted by /u/lewz3000
    [link] [comments]

    Do you need intensive DDOS protection or captcha with social media login?

    Posted: 28 Jun 2021 08:24 AM PDT

    Do Facebook, Google, and Twitter handle this for me?

    submitted by /u/LGm17
    [link] [comments]

    Is there a course or video to learn advanced contemporary CSS?

    Posted: 28 Jun 2021 06:45 AM PDT

    I know how to use CSS, I use SASS all the time, but if it wasn't for bootstrap I'd still use floats to layout websites.

    I've been focusing exclusively on JS because the few tutorials I looked at for CSS flex and grid looked easy and so I thought I could ignore them.

    I just tried to design something and I realize I'm completely rubbish.

    I really don't want to go through individual concepts but some tutorial/course that teaches how to build a website. And along the way it teaches you when to use flex and when to use grid

    submitted by /u/Far_Leg4223
    [link] [comments]

    Is it normal for 2 newbies with 2 months of experience each to be doing everything on a project. It's not like we're not managing, however, I've been feeling kinda anxious because it's all on us. If we get stuck, there's no one to help us because no one else is familiar with the project or the API.

    Posted: 28 Jun 2021 02:04 PM PDT

    A couple of weeks ago, 2 other newbie teammates and I were put on a new project. We were given a couple of days to learn the documentation of a very popular CRM system and get familiar with the code of the project we had to improve. We were given a google document with a list of the problems that need to be fixed, and the features that need to be added. We couldn't really understand half the stuff written, so a call was scheduled and we had to write down a bunch of questions to ask during the call. Not long after, our third team mate got fired so only 2 of us were left.

    We didn't really have any documentation or thoroughly written requirements, so we had to interrogate the client and barrage him with millions of questions just so we could figure how everything should work and behave. During these discussions, a lot of the requirements became clear, a lot of them were scrapped because the API wouldn't allow them and some were left to be discussed at a later date because we needed to finish the rest first. We also get 1 call a week, so if I forget to ask something about a task, I'm screwed until next week. Also the client is not a a tech person, so sometimes even he wasn't sure how to answer some of our questions. Fortunately, he is a really chill guy and he doesn't mind us asking a lot of questions which is a blessing!

    The new features required some interface changes, but at the same time we weren't given a figma or photoshop design, so we were winging the design. We didn't know what color should buttons be, how the inputs/checkboxes/etc should look. They briefly showed us some figma design in one of the calls, and that's where I've been eyeballing the design from, but it's just not right. The design also included some assets, but we haven't received any of those so I've been using placeholders of google so far.

    I feel kinda anxious because I'm giving 100% focus throughout the entire day and yet I barely finish on time. At the same time, the original project is quite old, so we're writing jQuery and I'm just not used to this kind of DOM manipulation ( I'm SPA baby ), so I can only assume I'm writing some dank spaghetti bolognese code. I try to write as clean as I can, all things considering but I don't have time during the day to take a look at my code and try to clean it up because there are things to be done. We don't have QA for the project either, so every time we add a feature, I gotta go through the functionality and make sure we haven't broken anything

    In a way, everything about this project is on us. If we don't understand a requirement, we have to ask the questions ourselves, and if we don't ask the right questions we might not get the right answers. If we don't get the right answers, we don't figure out the requirement and when the boss asks us about that requirement, we get chewed. Also it's kind of hard asking the right questions when you're not quite sure about the requirement. If we get stuck on a task, we can't ask anyone for help because no one else is on this project, which means no one else is familiar with the code or the CRM API. My team mate has been stuck on one of the features for like 2-3 days now, just reading the API documentation, tinkering all day long and going in circles. We're not quite sure if what they're asking for is even possible.

    Is this normal procedure for newbies with 1 month of experience? During the first month, I was on a React project with proper daily calls, jira tickets, sprints, QA and all that good stuff, where I was mostly fixing bugs.

    submitted by /u/Bozhidar95
    [link] [comments]

    No comments:

    Post a Comment