Volley develops voice-controlled games and entertainment apps for Amazon Alexa and Google Assistant. Our voice apps are world-class and attract millions of users every month. We’re a 45-person team based in San Francisco.
We believe voice control will be the main way people access entertainment in their bedrooms, kitchens, living rooms, and cars, and our goal is to build a destination for voice-controlled entertainment, as Netflix did for television.
Volley (volleythat.com) makes voice-controlled games and entertainment for Alexa and Google Assistant. We are a 12-person Series A startup based in SF near Union Square.
Volley develops voice-controlled games and entertainment for Amazon Alexa and Google Home.
We are the #1 voice-first game company with 10+ titles and exponential month-over-month growth. We've raised from top institutional investors in the gaming industry and we are starting Y Combinator in early January.
We are seeking a Lead Engineer or Head of Engineering to build out game engines and design the backend infrastructure for our games. You will help us conceptualize and build proprietary voice-controlled game engines, scale our infrastructure from hundreds of thousands to millions of users, and manage other engineers in a collaborative small-team environment. Founders are both technical from Harvard and Stanford.
Our software stack includes:
-- AWS Lambda (Node.js)
-- AWS DynamoDB
-- Alexa Skills Kit
-- Google Cloud Functions
-- Firebase
Stuff you may have done before:
-- Game development
-- iOS / Android development
-- Engineering role at a gaming company
-- Engineering role at a consumer software company
-- Engineering management experience
-- AWS experience
-- Serverless Lambda experience
-- Alexa / Google Home / voice interface experience
Check out our top rated games for Alexa:
-- "Song Quiz" (http://songquiz.com) - A name-that-tune music trivia game in which you must correctly identify the title and artist of popular songs.
-- "Yes Sire" (http://yessire.com) - A choose-your-own adventure story-driven game set in a medieval castle.
How are you calculating the 'risk of any one person being killed by violence' today? To make that claim you need to consider tail risk and black swan events that are possible but have little precedent. What weight are you giving the likelihood of a person dying by nuclear weapon?
Yes - there are different ways I could see it work, but right now, effectively, the amount of money you contribute determines the number of votes you have on ANY action of the endowment. Anyone within the DAO or not can submit investment proposals to the DAO to vote on.
Of course, 51% attacks become possible with anything decentralized, so there are provisions to split the endowment itself or pull out your share of the funds whenever you desire (another benefit vs existing charities and endowments).
Check out Stephan Tual on Medium for more info on how his DAO supporting the Ethereum ecosystem awards votes to token-holders and incorporates 51% attack protections (https://medium.com/@stephantual).
I'd be interested in ways to non-linearly scale votes with donations (such as quadratic voting: http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2003531) but that would require some sort of decentralized identity to prevent dupe accounts.
Text our phone number and we'll do whatever we can to make your job-search experience less stressful and more successful including actually searching for jobs on your behalf.
Thanks for checking out clivebot! I appreciate the feedback and agree we need to make the instructions clearer going forward.
@clivebot: follow [team_name] — This is equivalent to 'following' someone in Twitter, except in this case, you are following an entire Slack team. Once you follow that Slack team, you will be automatically notified whenever that team starts a live-blog.
@clivebot: go live — You're right that this starts transmitting everything your team writes in the channel. Other teams have to follow your Slack team first (as described above) in order for them to receive your live-blog.
@clivebot: stop — This is the command to end your live-blog. You can also use this same command to mute other teams if they are currently live-blogging.
Clivebot can be added to any channel but can only "go live" from the #live channel you chose when you installed.
Clivebot does allow for two-way inter-team Slacking. After you "go live", say @clivebot invite [team_name] to let another Slack team join the live-blog with you. It's kind of trippy actually.
Volley develops voice-controlled games and entertainment apps for Amazon Alexa and Google Assistant. Our voice apps are world-class and attract millions of users every month. We’re a 45-person team based in San Francisco.
We believe voice control will be the main way people access entertainment in their bedrooms, kitchens, living rooms, and cars, and our goal is to build a destination for voice-controlled entertainment, as Netflix did for television.
https://www.volleythat.com/
https://www.volleythat.com/careers