u/michaelnovati replied · ★ FEATURED
>So is the goal to present this final project as work experience?
In my experience talking to Codesmith grads about their projects, most could not talk about them at the Facebook, full blown SWE level behavioral bar for entry level roles. (I posted above but I worked at Facebook for 8 years as one of the most senior engineers, trained Facebook engineers on how to run these interviews and many of my current co-workers have as well). The projects are not run like real companies so people don't have real answers for many critical questions and raise a lot of flags.
A good example is a project where the team chose to rewrite their project using a brand new open source framework instead of a super reliable framework (not disclosing details to reveal anything personal). The team had no idea about the tradeoffs of using something stable and reliable for a large scale project vs using something brand new and buggy and didn't really know why the decision was made to use the latest and greatest framework.
Another example is when asked who how big the team was, the person said 20 people. I was impressed because that's a big engineering team! So I asked how many PMs there were, how many tech leads, how were standups run. The problem is that this project was no where near the level of what a real Facebook-level team operates at and it was a giant red flag to even consider them for Formation.dev. This person now works at Facebook btw after we worked with them at Formation.dev.
This is just my experience for this specific point about representing these projects as work experience, I have absolutely nothing against Codesmith and think that it's one of the bootcamps that has scaled significantly better than most others and would recommend looking at it for someone looking at bootcamps.