PayGarden | Full-stack | SF | Full Time | ONSITE (preferred, sponsor visa) + REMOTE (some positions)
What: With PayGarden merchants can accept major brand gift cards as payment - imagine Stripe, but instead of credit cards, your customers can pay with Starbucks, Walmart, Amazon (& 100 more) gift cards.
See our partnership with Watsi [0] turning major brand cards into life-changing healthcare for people, or Private Internet Access [1] making VPN payment anonymous.
How: Our systems handle millions of dollars, built primarily with Clojure/Script & a dash of Rust.
Us: If you've ever done any work with Clojure, you've likely seen someone from our tiny, incredibly high-leverage team of Xooglers & YC alumni. We've:
- contributed to the cljs compiler [2],
- built cool open-source Clojure/Scripts apps [3],
- given [4] dozens [5] of talks [6] on [7] fun and cutting [8] edge development
- run the #sfcljs & ReasonDojo meetups
You: Love working with others, taking ownership over business concerns while jumping into other parts of the stack to help out. An internal drive to continuously improve, while remaining humble.
jobs@paygarden.com with "HN" in the subject, & link us to your favorite project!
At Yelp we used MOE to tune the advertising system, optimizing thresholds for when to display certain types of ads, and how to rank the advertisements. More info can be found in this talk [1] and slides [2]. Tuning these thresholds across hundreds of categories, device types, and related dimensions would be impossible to do by hand, but is exactly what this system is built for.
Netflix has used MOE to optimize their deep learning systems (talk at MLconf [3], slides from NIPS [4]). Yelp was also able to leverage it to tune the hyperparameters of various machine learning systems in advertising and search.
SigOpt takes this work and related research and puts it behind an easy-to-use API and web interface. We want to bring these powerful tools to everyone and optimize everything.
Dwolla did not perform a "background check" in the sense that you may think. When dealing with online fraud, it's common to use identify verification services like IDology (and a few others) that basically provide an API to generate these types of questions based on public records matching your name/address. Many banks use the same verification services.
This. Experian provides the same service, it's usually ~$3/pop if I remember right. This gives you those "Did you live with a Paul Foo at 378 Combinator Way from 2006-2009?" questions.
Thanks for the feedback, you're right that we can simplify the initial pages. We've been focusing on clear explanations of the coverage on insurance plans and taking the headache out of all the forms later in the process, so we'll definitely keep your suggestions in mind as we refine the top of the funnel.
Having historical pricing data seems particularly interesting. I've thought about building a fashion site that predicts pricing trends so you can predict when to buy items on sale, and it seems like this could serve as the pricing infrastructure.
I wonder how I can tell what product sources are available, and whether new ones appear? I.e. is this only going to cover amazon.com, or does it know about nordstrom.com too?
That's a great idea. Pricing trends analysis could be done through the historical data we provide across the different merchants.
We do provide the affiliate purchase links to the products, available under the 'offers' field. Currently you can only figure out when new merchants appear by polling the product ('pull' mechanism). One idea which we have been toying around has been a 'push' mechanism where you can subscribe to a particular product through our API and we would notify if there has been any change (price change or new merchant selling it or product has been discontinued). Drop me a mail at varun <at> semantics3.com if you want more details or wish to bounce off ideas.
Thanks, I didn't catch that cap change. We debated going into FSAs versus HSAs in the article, but it was already getting long - I think it's worth looking at in more depth separately.
FSAs are only available to people choosing an insurance plan from their employer. So, they're not applicable to the situation we cover in this article where somebody is buying insurance individually.
It looks like FSA caps are reduced from a previously employer-determined limit (often e.g. $5000) to a federally mandated $2500, but HSA caps are increasing from $3100 to $3250 (for individuals).
