Skip to content

Instantly share code, notes, and snippets.

@talentdeficit
Last active December 19, 2018 22:34
Show Gist options
  • Save talentdeficit/28171950a3b51d7a1acad6d7a7fff45b to your computer and use it in GitHub Desktop.
Save talentdeficit/28171950a3b51d7a1acad6d7a7fff45b to your computer and use it in GitHub Desktop.
Bandstock | Remote (San Francisco Based) Elixir / Phoenix Backend Developer (Mid to High Level)
About us :
Bandstock is a digital collectibles game that helps musicians raise money and connect with their fans.
It is a crowdfunding platform, a merch sales platform and a live-music digital collecitbles marketplace
for fans to play and engage with live music venues, performing musicians and other fans in real-time.
We are in the early stages of starting up. Cultivating a working demo of the game is key at this stage.
We are focusing on proof of concept and stunning visuals so we can get investors on board with this
'ripe and ready' live music market.
See www.bandstock.net for more details
What you'll do :
Move an existing project forward to create visual demos that encourage investment.
Help solve an interest priority-queue puzzle to deliver concurrent, time-synced updates to large amounts
of clients.
Be part of a team of game and music lovers seeking to make the live music scene even more fun, enjoyable
and profitable.
Provide a backend interface using Phoenix Channels for consumption by a javascript/three.js front end
Continue development of a real-time game engine that sends game packets to clients and processes
player-actions concurrently
Collaborate with game developers, game designers, sales staff and others who have key pieces of the
puzzle
Longer Term: Help prepare recommendations for a good rewrite from scratch - according to Elixir/Phoenix
best practices
Help Integrate Bandstock with the OpenSea API platform to use the Ethereum ERC-721 (blockchain)
standard.
What we expect :
Examples of your code on github
Ease and Fluency with Elixir, Erlang, Phoenix
Your code is unit tested
Git chops
Good knowledge of PostgresQL, MongoDB, Neo4J or similar to optimize in a high traffic context
Motivated to learn and create a work of art in code
What we'd like :
Live Music Enthusiast.
Experience with high traffic web applications
Experience with NoSql databases, especially Redis
Deep understanding of the modern web protocols, stacks and architectures
Excellent attention to details and knowledge of coding/application design best practices
Excellent ability to communicate with diverse groups of users and developers
Knowledge of Front-End development (HTML5, CSS3, Three.js)
Location:
We are a remote team of "purpose-agents" and freelancers with members in San Francisco CA, Austin
TX, Brisbane Australia and London England. We use purpose driven organization philosophies,
including Holacracy (www.holacracy.org).
Compensation:
We are using the "Slicing Pie" dynamic equity model for funding (www.slicingpie.com).
We are currently in the "Dynamic Equity Phase" of our development.
This means compensation comes in the form of "D-Units" at a rate of 2X fair market value for work
performed. When funding waves come through, the company buys back outstanding "D-Units". This means
you accept risk that you will not be paid if the company fails to receive funding, but enjoy double
pay if it does. Alternatively, D-Units can be converted into "A-Units" which are similar to equity
shares in a traditional company. A-Units entitle you to dividend-like payments for the life of the
project when it becomes profitable.
When the Dynamic Equity Phase ends, D-Units and A-Units will no longer be available. At that time
we will return to a more traditional salary model.
Your performance as a developer and ability to produce working demos will have a large impact on
the teams ability to procure funding! We need your help!
Starting Date: as soon as possible
If you would like to partner with Bandstock as a developer, send a message to mattdavis1337 on
Slack or email support@bandstock.net with your proposal for partnership.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment