GreenPark Sports | greenparksports.com | ONSITE (SF Bay Area - Burlingame) | Full-time | Base + equity
We’re building the future of Fan Engagement experiences for live sports. It’s a frenetic, all-in, raise-the-stakes and show-your-passion mobile game experience where the best fans win. Our fast-growing team loves both sports and eSports and we’re not afraid to show it. We've closed a healthy Seed Round with investors that represent all major leagues that believe as passionately as we do in our future of sports and fan engagement.
GreenPark Sports is looking to hire a mobile engineer to work on a mobile sports game. We're a stealth, seed stage startup founded by well-known names in Silicon Valley.
We're building the mobile app in Flutter. Flutter experience not required. Just be interested and willing to work with Flutter.
We're based on Burlingame. Just a 10 min walk from the Caltrain station. Small company of just 6 people. This is a great ground floor opportunity for someone who enjoys building apps from nothing.
Too bad he's silent for the past year when these issues were obviously going to happen. He allowed it to happen. And now he's quietly giving Trump lip service behind closed doors. He (Travis + Uber) doesn't give a damn about anyone. As long as they can get some Uber-friendly policy from Trump they'll continue to let him do whatever he wants. They are enabling him by working with him on other issues while ignoring this.
Such PR bullshit. Trying to look good in the public eye.
What kind of reply would you want? Would a simple "no thanks" be enough?
I have been in the situation before where replying to everyone with anything meaningful is simply not feasible. Maybe for a recruiter whose full-time job is that but not for a hiring manager who also has to balance their regular duties as well.
I have spent much more time on the applicant side of things than the hirer side so I understand the goal. It can be frustrating to not get anything. If it is a job you really want you may be inclined to hold everything else off until you hear something just on the hope that maybe they haven't gotten to your resume yet. So a little closure would be nice.
So maybe a better question for you is what are you trying to accomplish by getting hiring managers to reply to all candidates? Give them closure or provide feedback? If the former than maybe a simple "no thanks" will do.
By the way, I am speaking clearly to the scenario where a candidate sends in a resume and doesn't hear anything back. In my opinion, even if the hiring manager or recruiter does a phone call the candidate deserves a clear "no" email at a minimum.
Any reply would be good. Even if it's a pre-canned copy/paste. It answers the questions that comes up if you don't hear anything: "did my email not send properly?", "did they miss me?", "are they ignoring me on purpose?" etc.
It takes almost no effort, and shows that you care about the people around you. If someone came up to you and asked you in person, would you ignore them and keep walking?
Now to be honest - we use greenhouse, and their tooling for recruitment workflow is not bad. A decision to accept/reject will always trigger an email. Of course we've templated our own custom responses, but editing the outgoing email before sending is also easy enough.
As for interview feedback, I personally write my interview notes in such a way that if the candidate asks for more detailed feedback, the notes can be pasted pretty much as-is. When the hiring workflow and candidate communication are intricately linked, things are less likely to fall between the cracks. Everyone feels better.
Lever (YC S12) is a modern Talent Acquisition Suite, and we hear from our customers that writing rejection emails is really difficult, especially when you want to leave a good impression. Here are some tips we wrote up: https://www.lever.co/blog/how-to-write-human-rejection-lette...
Tip 3 is really a bad advice. It's not a good idea to say why you rejected the candidate, you have no idea how it could be taken, especially if you are facing a litigious person.
Best to write some "you were not an exact match for our needs" reply.
Agree this is definitely true in many cases, especially with applicants. Where it can be OK to give candidates feedback tends to be when you have gotten to later in the process with them and built more of a relationship. The article was meant more for the general case. I totally agree a lot of judgement is needed.
Yup because I once applied to a big company and to this day I still don't now if a human was actually involved in any part of the process... Given the company and given the job it's quit possible that the HR people just filtered out the result using standardized fields and never gave an eye at the CV & resume I took 5 hour to write.
Months later I learn that they fire half of their HR externals contractors (maybe for the best).
So in the end yes, a simple "I read, not interested" would be great.
And if applicable a variation that could be "not for this job, but maybe try another one" or even "you need more experience" would actually be even more useful.
PS: What I learn though is that for big company hiring process is broken. My best chance of being recruited is to build a great project and communicate about it at my current job (but that's not easy if you are at the bottom of the stack and writing code under copyright...), but now I'm even less tempted to even apply to theses big Co.
Virtually every recruitment tool in existence already does this. Any company that doesn't send a"sorry" email to applicants is either not using any technology at the point of screening (unusual for anyone of any size) or has a screwed up recruitment process (common in large companies).
You'll need to find other secret sauce.
Your goal could be to find a way to encourage managers/recruiters to provide more genuine feedback.
How about tiered responses, and tools to track and prompt when the tiers are not being used correctly?
Once had Google kill a Spark job after it was running for about 12 hours because they thought we were doing something nefarious. It cost us thousands of dollars in wasted time and Google spend because their automated system made a mistake. They never attempted to fix it, refund us or even seem concerned.
And you compare that to the many stories you hear about Amazon waiving invoices when people inadvertently ran up multi thousand dollar AWS bills by accident or when credentials were exposed. (Happened to an ex-colleague of mine years back - AWS creds committed to a public git repo - minutes later there's like 40 10xlarge or g2.8xlarge or whatever instances mining bitcoin. First thing he knew about it was Amazon ringing him up saying "this $10,000 spike in your typical use, that's not really you, right?" and shutting it all down for him and reversing the charge...)
Then you consider this when you decide whether to base the next big business decision on an AWS or Google Cloud platform…
Should an infrastructure company be advertising the fact that it didn't research the technology it chose to use to build its own infrastructure?
All these people saying Mongo is garbage are all likely neckbeards sysadmins. Unless you're hiring database admin and sysadmins, Postgres (unless managed - then you have a different set of scaling problems) or any other tradition SQL store is not a viable alternative. This author uses Bigtable as a point of comparison. Stay tuned for his next blog post comparing IIS to Cloudflare.
Almost every blog post titled "why we're moving from Mongo to X" or "Top 10 reason to avoid Mongo" could have been prevented with a little bit of research. People have spent their entire life working with the SQL world so throw something new at them and they reject it like the plague. Postgres is only good now because they had to do some of the features in order to compete with Mongo. Postgres been around since 1996 and you're only now using it? Tell me more about how awesome it is.
My goal in writing this post was not to convince people to use or not use MongoDB, but to document an edge case that may affect people who happen to use it for whatever reason, which as far as I could tell was inadequately documented elsewhere.
Only the first line was directed at you - and it was more in jest. Everything else was directed more at the other commenters and Mongo detractors in general.
San Francisco, CA | on-site only | relocation possible.
Looking for a Javascript engineer to own all of our browser based projects including out JS library used by our clients, our dashboard, admin site, integrations with 3rd party libraries and future integrations and libraries.
Building and own a complex Javascript used on high traffic websites in every possible browser and OS combination possible should be a project that you're excited about.
We're not looking for a "front-end" engineer. The person we're looking for is passionate about Javascript - no matter where it runs.
Some experience required.
We're still a small team of just 7 (almost 8) (2 full-time engineers). You'll be in at the ground floor during an exciting period of growth.
Email Travis at travis[at]outbound[dot].io if interested or use the job listing to apply.
San Francisco, CA | on-site only | relocation possible.
Looking for a Javascript engineer to own all of our browser based projects including out JS library used by our clients, our dashboard, admin site, integrations with 3rd party libraries and future integrations and libraries.
We're not looking for a "front-end" engineer. The person we're looking for is passionate about Javascript - no matter where it runs.
We're still a small team of just 7 (almost 8) (2 full-time engineers). You'll be in at the ground floor during an exciting period of growth.
Email Travis at travis[at]outbound[dot].io if interested or use the job listing to apply.
On any platform other than iOS, Safari is the 3rd best browser on its best day. Just because something is pretty, doesn't make it good. This guy is clearly a student of the Jony Ive school of thought.
If they lose significant eyeballs, they can't charge a premium for the ad space. With less premium, they make less money. With less money, they can't write the articles.
At least with ad block and non-adblock eyeballs, they could say we get "XXX"k traffic per day/month/year. Less traffic overall will be bad in the long run.
Not to mention they lose all the viral follow-on effects. If Jane never reads another article of theirs, then Jane never shares another article of theirs, and never refers a new reader or subscriber, and on goes the cascade multiplied by however many people stop reading. They end up cutting off their own oxygen.
The people commenting here that Wired doesn't need to care about ad-blocking readers, are entirely ignoring this critical element. It's a big component of how new people get introduced to Wired.
I hope you did not think that the advertisers aren't capable of running a little estimation program on all those clicks going 'in' to wired that did not result in the displaying of an ad tag?
If there is any party that is aware of how many people on wired's web property are running an ad blocker it is the advertising networks.
Wired is not telling them that they get 'XXX'k traffic per time unit, they're being told what their traffic is and what percentage of them has an ad blocker installed.
I hope the advertisers realize that we have not even come close to hitting a critical mass of people that install adblockers in the first place. I am amazed by how many people don't run adblockers. I tell everyone I know to run them... Remember it is only 1 out of 5 right now... It will be much higher as the tech illiterate are taught how to install them.
The truth is, I can always just go outside. Go for a run, Go for a hike with my kids... collect some rocks, smash rocks looking for geodes, play catch, play hide and go-seek, cook, drink. All will be much better than me sitting on my computer reading articles on Wired.com
No, they cannot say that they have xxx users per day/month/year, the reports of the adservers are the one that are read by the advertisers (and the editors), the number of visitors is useless if you can't serve them ads.
If that's how they think they should probably take a class explaining network effects and how the ability to share a link can help spread their product.
Most of the content I read comes through places like HN. If Wired loses many of the more active participants on HN (who are probably more likely to run adblockers), their articles will get posted less and upvoted less, so they'll lose many of the people who aren't running adblockers too. Would be very interesting to see how much impact those active participants have overall on their readership - my guess is it's a lot.
Actually, this can almost completely wipe out Wired from google search results.
One metric that is used to rank sites is the bounce rate. If ad blocking users simply go back to Google and look for another result, then they will get penalised by Google.
We’re building the future of Fan Engagement experiences for live sports. It’s a frenetic, all-in, raise-the-stakes and show-your-passion mobile game experience where the best fans win. Our fast-growing team loves both sports and eSports and we’re not afraid to show it. We've closed a healthy Seed Round with investors that represent all major leagues that believe as passionately as we do in our future of sports and fan engagement.
We've also just announced a deal to deliver our game for the League of Legends Championship Series (LCS) -> https://blog.greenparksports.com/lcs-image/
We are hiring for the following Engineering roles:
For full role descriptions/listings: https://boards.greenhouse.io/greenparksportsThanks and Play ball!