We are a small startup (< 20 employees), looking for a mid-senior level backend Go engineer to develop features on our backend server, which is 100% Go. We use Postgres as our primary data store. Prior experience in Go preferred but not required. Experience with SQL preferred.
Job is remote, company is based in USA and most employees are in North America.
This is for a position with core engineering, a new engineering team at Bread. This is a great opportunity to be one of the first engineers on a team dedicated to building high impact services at an established company.
Tech Stack: Go + Postgres + Kubernetes + SOA
Knowledge of Go is preferred, but any strong background in backend engineering will do.
As a self taught developer I can say your point assumes self teaching is all about following your interests. This is simply not true. Self teaching is a combination of following your interests and figuring out your areas of weakness and attacking them. Part of my self learning involves browsing college degree requirements or graduate programs to identify must know topics, I learn them regardless if I have a particular interest. If college is the only thing forcing you to think outside the box, what hope is there for your long term learning.
Interesting, Ive had the opposite experience while driving back to NYC from other east coast cities. Google generally takes into account that traffic will increase as I approach NYC, but the initial estimate is always off by at least 1-2 hours.
I completed my bootcamp exactly 3 years ago (python), currently I am a Systems Engineer at a competitive start up in NYC, before that I was a Backend Software Dev at a fast growing start up in Seattle. There was some luck involved but overall my career change couldnt have gone better.
I think my bootcamp prepared me about as well as anyone could reasonably ask, 8 weeks included 1) decent introduction to algos + data structures, 2) overview of django / flask / pyramid, 3) introduction to machine learning + data science with python, 4) 2 portfolio projects, 5) overview of relational databases, 6) intro devops (i.e. deploy python app to aws). Probably missing a few things, but this was most of it.
That said I had done a significant amount of self directed learning prior to the bootcamp, 2-3 CS courses on EDX + a lot of tinkering. I think I eventually would have arrived at the same skill set without a bootcamp, but it was undoubtedly the right decision to go.
I cant account for everyone, but I believe most of my bootcamp cohorts are working as devs (at least, I run into them at conferences / see their updates on FB / etc). It took me about 10 weeks to find a job, the people with no prior coding experience took a bit longer.
Am happy to answer any more questions you may have.
A lot of his arguments (good party console, hardware doesnt always matter, etc) also apply to Nintendo consoles. Ive always loved the Wii for similar reasons (the fact that it is easy to softmod doesnt hurt either :P )
People learn in many different ways, and therefore I dont think you can make the sweeping statement:
"Learning, IMO, doesnt happen like this."
I have always been someone who prefers self directed learning to the classroom (this coming from someone who spent 7 years in college / grad school), I think MOOCs are great and I get as much out of them as I did many college classes. I found the freedom to study any topic whenever I wanted to very liberating; I ended up studying more. Some MOOCs are certainly better than others, but you could say the same of regular classes.
There is definitely no replacement for office hours with professors, but facebook groups, community TAs, and Skype actually close the gap more than you'd think.