Hi @giordifungula, @ksjazzguitar.
I applied to a bunch of jobs on indeed and got a few interviews. One company stood out in particular in that I really liked the conversation I had with the employer at the first interview. I ended up doing a total of 3 interviews with this company before receiving my offer. The first was the most casual, just a chat about what I was working on at that time (the employer had already looked at my Github profile before the interview). The second interview was a technical question which I had to whiteboard and then write code for. The third and final interview was mostly informal and more of a chat about the company, the work we do, etc.
What I needed for the job:
This is kind of hard to answer. I think my strongest asset was having all of my projects on Github. This gave my employer the opportunity to really gauge my knowledge. I think it is important to remember that you do NOT need to have EVERY single skill listed on a job posting. For instance, I had absolutely 0 redux experience when I was going through the interview process, but knew a good amount about React and thought I could always pick up Redux if and when necessary. If you think you may be a qualified candidate you should apply. Even if you don’t get the job it will be a good learning experience. I also have a university degree in an unrelated field (which I don’t think mattered very much).
Where I was at in the FCC curriculum when hired:
I have the front end certification. Did all the algorithms too (I agree these are difficult when you are first starting but when you are close to “job ready” they become much easier). I did most of the react projects (didn’t make the game). I did the API projects for backend and made one of the full stack projects (voting app). However I built a lot of things on my own (which i consider to be “full stack” projects) and didn’t follow the curriculum too strictly. I would say that doing the “dynamic web application” projects are probably the most valuable learning opportunities on FCC. Once you understand enough about the front end and back end individually doing these full stack projects really shows you the full picture. I would prioritize doing these projects way above learning about D3 for example.
- Be patient, you’ll get really frustrated at times (For met it was webpack, lol )
- There’s no real shortcut. You just have to spend a lot of time learning and making mistakes and being confused. Consider being hired a long term goal and try to enjoy the journey rather than stressing yourself out.
- Push your knowledge on every project. This is something I started doing fairly early on and looking back I think it was really helpful. For example, my first full stack project i used create-react-app to handle everything. The next full stack project I did the webpack config myself. The next one I did more webpack customization and also wrote test cases with jest/enzyme etc etc. Pushing your boundaries with each project really forces your knowledge to grow
- Have another hobby that you can use to recover mentally a bit. Exercise, baking, crafts, whatever it may be you do need some downtime from coding so you can refocus.
If you have any more specific questions let me know!