bmajz
Polly is a fast growing company that has one of the largest enterprise user bases in both Slack and Microsoft Teams. Our mission is to empower teams to measure and understand every aspect of their work, and we're doing it by bringing new levels of automation to the old way of running surveys.
We're looking for US/Canada remote full-time Senior Full Stack Engineers. We're a product-led company of 17 that supports millions of enterprise users. Come in and have significant impact on the product, the architecture, and the company. Our stack is Typescript/Node/AWS/Mongo, but for our candidates we don't care about your stack history, just your ability to produce clean, high quality code and solve complex problems.
We offer our remote employees a sweet hardware setup, budget for home office or a local coworking spot, and 99% of your insurance premiums covered for you and dependents. We also offer fully-paid 16 weeks of maternity leave.
Apply here: https://www.polly.ai/careers#open-positions or email [email protected] and reference HN.
Note: You can also work out of our Seattle or our soon-to-be Vancouver, BC office.
Amazon experiments with tech teams consisting entirely of part-time employees
Looking for: Software Engineer
Polly is reimagining enterprise applications through the medium of chat. Currently, our Slack bot helps companies measure processes through quick polls and lightweight conversation. We are looking for someone new to join our team and we think you'd like to come here because: * We've already got great traction including the #1 spot in the Slack App Directory's HR and Bot categories and paying customers! * We have some really exciting technical challenges ahead of us, with hard problems like natural language processing for our chat interface and cluster management across thousands of realtime connections to chat clients
For devs: Our stack is primarily in Node.js and Meteor running on AWS, but we're totally cool with other backgrounds.
Apply by sending an email to jobs @ <company name>.ai
Canadian Families Forming Independent Support Groups for Syrian Refugees
(Yes, we have the .com!)
Looking for: Software Engineer and UX Designer
Subcurrent is reimagining enterprise applications through the medium of chat. Currently, our Slack bot helps companies measure processes through quick polls and lightweight conversation. We are looking for someone new to join our team and we think you'd like to come here because:
* We've already got great traction including the #1 spot in the Slack App Directory's HR category and paying customers!
* We're starting to build out a personality and chat dialogue for our bot, so you get to moonlight as a scriptwriter and critic
* We have some really exciting technical challenges ahead of us, with hard problems like natural language processing for our chat interface and cluster management across thousands of realtime connections to chat clients
For devs: Our stack is primarily in Node.js and Meteor running on AWS, but we're totally cool with other backgrounds.
“Eat food. Not too much. Mostly plants.”
https://www.nytimes.com/2015/04/21/upshot/simple-rules-for-h...
"Salesforce is now working on as many $100m+ deals as it can try to close. Because once you adding > $1 billion in ARR a year, you need a few Really, Really Big Enterprise deals to move the needle. And a handful of $50m-$100m deals are, by definition, the new target to really move the needle at that scale.
Given that … does it make any sense to pursue the $9 a month market? Or the $2000 ACV market? I mean, not really. And Salesforce isn’t.
So the bottom 10% of this $10 billion market, or $1 billion, isn’t even being addressed by Salesforce."
Personally though, it went fine in terms of productivity and energy. Trying to work out without that nap was pretty brutal but fasts are long enough to fit it in after work.
Bay Area is almost rock bottom in housing creation
1. We will probably eventually need SQL
2. It might not make sense to be so JS heavy, especially since we are enterprise focused and may have to support older browsers for extended periods
3. General performance issues at scale that I would have with any new framework
Planning on solving these problems when we hit them - for now, fast is best.
We picked it because it enabled us to move much faster than anything we had used in the past and while it has issues that I foresee being problematic, it seems premature to optimize for them. The Meteor team is doing a great job maintaining compatibility and not forcing us developers on to make any changes to our apps as they're rolling out exciting new stuff. Granted, I did jump on when the platform was (relatively) mature late last year.
Very happy with decision so far and looking forward to building more stuff on their platform!