We're looking for a very special someone to lead our frontend team over at Parallel Markets, a fintech startup with solid traction and a great product team full of kind, senior engineers.
We're backed by Union Square Ventures and just raised our Series A. We use Elixir/Go/NodeJS on our backend and JS/React/Relay/GraphQL on our frontend. We deploy fresh code many times every day, and have made a concerted effort to optimize our processes for developer efficiency and happiness. We don’t use Jira, and our brief morning standup is the only meeting we have.
Our product is a re-usable identity for financial institutions (both via OAuth2 on web2 and a “non-transferable” NFT on web3).
Parallel Markets | Sr Frontend Engineer | Remote | Full Time | https://parallelmarkets.com
Parallel Markets provides a re-usable identity for financial institutions in both web2 and web3 contexts. We just raised our Series A from Union Square Ventures (https://www.usv.com/writing/2022/02/parallel-markets/), and we're growing our remote-first team with additional full-time/permanent hires. Our frontend is React/GraphQL/Relay. Our backend is Elixir/Phoenix — with a dash of Go and NodeJS — on PostgreSQL. We deploy on AWS, provisioned through Terraform.
Engineers here at Parallel love building products, emphasizing efficiency and developer happiness. We deploy at-will, many times a day, coordinated via Slack, GitHub, and Shortcut. As a remote-first team, we will always prefer asynchronous processes. As a result, our morning standup is the only recurring meeting and we Write Things Down™. That goes for requirements and documentation, but also our company handbook (https://about.parallelmarkets.com/handbook). Through collaboration, we prioritize the best answer — regardless who comes up with it — and believe "done" is better than "perfect."
We want to work with curious, self-motivated engineers who enjoy learning new technologies. We all learned Elixir on the job, for instance. So, instead of looking for people with "X years doing Y," we're glad to find those with opinions on a variety of languages and approaches. We're excited to know there's always more to learn; if you feel the same, let's work together!
Parallel Markets provides a re-usable identity for financial institutions in both web2 and web3 contexts. We just raised our Series A from Union Square Ventures (https://www.usv.com/writing/2022/02/parallel-markets/), and we're growing our remote-first team with additional full-time/permanent hires. Our frontend is React/GraphQL/Relay. Our backend is Elixir/Phoenix — with a dash of Go and NodeJS — on PostgreSQL. We deploy on AWS, provisioned through Terraform.
Engineers here at Parallel love building products, emphasizing efficiency and developer happiness. We deploy at-will, many times a day, coordinated via Slack, GitHub, and Shortcut. As a remote-first team, we will always prefer asynchronous processes. As a result, our morning standup is the only recurring meeting and we Write Things Down™. That goes for requirements and documentation, but also our company handbook (https://about.parallelmarkets.com/handbook). Through collaboration, we prioritize the best answer — regardless who comes up with it — and believe "done" is better than "perfect."
We want to work with curious, self-motivated engineers who enjoy learning new technologies. We all learned Elixir on the job, for instance. So, instead of looking for people with "X years doing Y," we're glad to find those with opinions on a variety of languages and approaches. We're excited to know there's always more to learn; if you feel the same, let's work together!
That ignores the effect of your friends sharing with their friends and so on. I added the final graph to illustrate this point - yes, having 2 entries is better than having 1, but the network effect of your friends pulling in their friends eventually kills your odds.
zck is right about failing to account for the friends votes - which does mean an asymptotic approach to 0.5 rather than 1. I updated the graph (and the example fractions). That does, however, change the conclusion, that you shouldn't share with friends at all.
"A/B testing is meant for strict experiments where focus is on statistical significance, whereas multi-armed bandit algorithms are meant for continuous optimization where focus is on maintaining higher average conversion rate."
Who cares about conversion rates, right? I'd much rather have statistical significance than more clicks on my buy button / signups for my site / etc.
We're looking for a very special someone to lead our frontend team over at Parallel Markets, a fintech startup with solid traction and a great product team full of kind, senior engineers.
We're backed by Union Square Ventures and just raised our Series A. We use Elixir/Go/NodeJS on our backend and JS/React/Relay/GraphQL on our frontend. We deploy fresh code many times every day, and have made a concerted effort to optimize our processes for developer efficiency and happiness. We don’t use Jira, and our brief morning standup is the only meeting we have.
Our product is a re-usable identity for financial institutions (both via OAuth2 on web2 and a “non-transferable” NFT on web3).
Find out more about open roles at our careers page: https://parallelmarkets.com/careers
Read more about our values and benefits in our handbook: https://about.parallelmarkets.com/handbook