bryanh

9 ms·

61.
by bryanh 9y ago
Also Python -- both as triggers and actions. https://zapier.com/help/code/ https://zapier.com/help/code-python/
62.
Zapier is hiring a remote infrastructure/devops engineer(zapier.com)
1 points by bryanh 9y ago
63.
by bryanh 9y ago
Basically it's saying for every extra dollar you want to earn in consulting you must hire more engineers. For traditional software you can continue to sell the same bits over and over and not hire an extra engineer for the Nth sale.
64.
by bryanh 9y ago
This is mostly out of date -- Zapier has lots of ways to do this without custom connectors: * Formatter -- https://zapier.com/help/formatter/ * Filters -- https://zapier.com/help/filter/
65.
by bryanh 9y ago
Yeah, Zapier has multi-step workflows https://zapier.com/learn/getting-started-guide/multi-step-za... .
66.
by bryanh 9y ago
Funny you say that -- engineers are one of Zapier's best customer personas. Quicker and easier to implement functionality than deploying code to the cloud. Plus, non-engineers can take over maintenance so engineers can work on more int
67.
by bryanh 9y ago
This is very similar to what we've done to bootstrap the Zapier CLI and developer platform -- especially relative to repurposing AWS Lambda. Wrote a bit of behind the scenes just the other day https://zapier.com/enginee
68.
by bryanh 9y ago
Definitely look into 100% remote tech companies as well.
69.
by bryanh 9y ago
REMOTE ONLY Zapier (YC S12) | https://zapier.com/ | Infrastructure Engineer About you -- You can cross systems, DevOps, and application software boundaries. You have a history of shipping high-quality production code in P
70.
Zapier (YC S12) is hiring an Infrastructure Engineer to work from anywhere(zapier.com)
1 points by bryanh 9y ago
71.
by bryanh 9y ago
Nice little Python script I whipped up to poll Amazon Prime Now to get my Switch: https://gist.github.com/bryanhelmig/3225bf42e5d2b8fb0cb4b720...
72.
by bryanh 10y ago
Be sure to turn on the subtitles - he narrates through CC what he is doing which is often very interesting.
73.
by bryanh 10y ago
I have heard that is getting much, much better - but another annoyance we've heard for "browser-centric" development has been tooling integration (CI, tests, etc). Probably more so for teams with existing infrastructure and p
74.
by bryanh 10y ago
Building the CLI and the backend that powers it was a lot of fun. I want to write up a technical post on how it works, but the gist of it is: * Node.js CLI that builds deployable zips * AWS Lambda behind the scenes running the cod
75.
by bryanh 10y ago
We're fully remote - always have been and plan on staying that way. If the experiment "fails" - we'll just stop offering this for new employees.
76.
by bryanh 10y ago
We've certainly not heard of any.
77.
by bryanh 10y ago
I think there is a bit of hesitation for some VC's in backing a remote first company - but some are all for it. Investors aren't as much a hivemind as one might think - they all have different theses that impact how they interpret
78.
by bryanh 10y ago
We try not to downscale raises/promotions based on location either. For what it is worth - we're not out to benchmark against "Bay Area rates". We generally will lose in head-to-head compensation with any large, on-site
79.
by bryanh 10y ago
We are already 100% remote and have been for the entire life of the company. Time differences haven't been a big issue - it can be tricky to get everyone on a call when they need to be - but usually a little flexibility by all parties
80.
by bryanh 10y ago
Correct. We won't be able to compete purely on compensation with Google no matter where you are located. However, you can expect an experienced engineer in St. Louis proper to be paid similarly well (6 figures, healthcare, retirement)
81.
by bryanh 10y ago
We consider this as just part of running a remote business - eventually it'll plateau as we are present in all the locations. For example, we have way more employees in Texas alone than in Idaho, Montana, North Dakota, South Dakota, et
82.
by bryanh 10y ago
We're certainly not perfect - but we try very hard. Thanks for the kind words Kirill!
83.
by bryanh 10y ago
I don't think we'd be against that at all - but we probably could not help with the visa situation.
84.
by bryanh 10y ago
We do not adjust salaries when employees move. We try to pay similarly regardless of location.
85.
by bryanh 10y ago
Literally none of this has been our experience.
86.
by bryanh 10y ago
Definitely a legitimate question - we often see people moving from various locations (I think like 60% of Zapiens have moved during their tenure, or something like that). As an experiment, we wanted to start with the obvious high cost of li
87.
by bryanh 10y ago
We're considering other places with outrageous cost of living as well - but as an experiment - we wanted to start with the Bay Area only.
88.
by bryanh 10y ago
We haven't fleshed out all the nitty gritty details - but no - we wouldn't prefer Pittsburgh to Moab.
89.
by bryanh 10y ago
I think that may be true and is worth consideration when making any career or geographical move. In central Missouri - you certainly won't find $2400 studio apartments either! To be honest - I wish more companies were remote welcome.
90.
by bryanh 10y ago
Zapier CTO & co-founder here. Much like Stripe's "hire a team" experiment - this is an experiment to pay people to "de-locate" from the Bay Area. Don't get us wrong, we absolutely love the Bay Area (I liv

More ›