sbisker
Joined 19 years ago
Joined 19 years ago
I suspect this practice is a bit disingenuous of the bootcamps, a way to pad their “successfully employed” rates while keeping labor costs low. But it is hard for me to fault the candidates for putting those experiences in their resume. They need that money to keep their job searches going, and recruiters are always biasing against gaps on the resume.
If you’re being paid by them for any reason, put it on your resume. (And if you’re not…move it to the education section, where it belongs.)
Maybe it’s generational, but I was taught to avoid using names in puns. I definitely grew up with people who would make last name puns like this to put undue emphasis on race.
If folks doesn’t even see why that would be a problem these days, I’ll take it as a win for society - but I think the question was in good faith.
We are looking to hire all sorts of positions, but my team in particular is seeking a full-stack feature engineer and a backend application platform engineer (think APIs and microservices). We're a highly collaborative team that focuses on learning, pairing, teamwork and using technology to build great things together. In this case, those things are typically around making the order and delivery experience of our fitness products as seamless and engaging as possible. We ensure our newest members have a fantastic experience "from checkout to first workout".
Recruiting was kind enough to give us this blurb to describe what we do: Peloton uses technology + design to connect the world through fitness, empowering people to be the best version of themselves anywhere, anytime. We have reinvented the fitness industry by developing a first-of-its-kind subscription platform. Seamlessly combining hardware, software, and streaming technology, we create digital fitness and wellness content and products that Members love. In 2020 Peloton committed to becoming an antiracist organization with the launch of the Peloton Pledge.
Senior Backend Engineer - https://boards.greenhouse.io/peloton/jobs/3080311
Mid-Level Full-stack Engineer https://boards.greenhouse.io/peloton/jobs/3316248
Excited to hear from people!
Doctors don’t have to relearn everything on the boards every time they talk to a new job, and that definitely helps combat ageism in that field.
It “felt” more uncommon that someone actually turns down an MIT offer after they see the package, as they do their best to provide student work aid and students tend to be optimists about debt - but I only saw the people who said yes, so my data is totally biased. I’ll note that one common situation is folks who can technically “afford” MIT, but are offered a full ride elsewhere - a lot of folks I knew who joined felt some pressure to save money by taking the scholarship elsewhere, and struggled to turn it down.
Now, he obviously had talent to even get into a top engineering school at that age, so there is some correlation as well as causation here. Still, unless he wasn’t admitted yet or actively hid the fact from YC, it seems highly unlikely it didn’t carry some weight - especially at that age, with so much less track record to look at.
As for asynchronicity, I totally get that something will be lost. The question is whether enough will be lost as to render the participant totally unable to learn those values over, say, the next few days and catch up. But something might be gained as well - it’s possible that these synchronous moments are an actual bottleneck. Experimenting with async could result in them handling more students with less staff.
I understand people have to draw the line somewhere, but any time “exceptions can be made in an emergency”, that is a sign that an experience can, albeit maybe with considerable pain, be made asynchronous. In a remote first world, I think more and more things will be forced to become asynchronous, whether we like it or not.
I’m reminded of make-up tests. Professors dread making them, they take real time, and they indirectly “reward” those who can’t make the first sitting (with more study time, etc). Some do refuse to do it. Still, universities compel teachers to do it because the value of having each student tested is considered a crucial part of the mission.
I get that this is a different situation; there’s a social unity component, some experiences can’t be exactly recreated. But is completely booting someone for missing one initial meeting in spirit with the mission? Is so much lost from a recorded version that it is truly better for that seat to stay empty for 6 weeks and one less person to be able to join the next batch as a result of a time zone gaffe? And is it really fair to say that because no one else had this problem, the six months of evolution post-COVID should match the same intentionality and strictness of running an in-person program for a decade?
I hope that at the very least, folks over there are looking at what happened with an empathetic lens - especially if they are truly willing to take this person for the next batch, and want to see them succeed.