eero (https://eero.com) | San Francisco, CA | Full-time | ONSITE We're looking for backend, data, mobile, firmware, and hardware engineers. We are also looking to hire senior PMs and designers. Our mission is to be the gold standard in Wi-Fi and to become the backbone for your smart home. Our stack includes but not limited to Scala, C, Python, React, Swift, Java, Go. Apply at https://boards.greenhouse.io/eero or email me at [email protected].

eero | San Francisco, CA USA | Full-Time | On-Site | https://eero.com/jobs

I'm Josh and I work on the Data team here at eero. We rely on data to inform and drive product decisions, improve network and mesh performance, set marketing strategies, enhance factory testing, provide better customer support and much more.

Our real-time data platform is critical to providing high performance, adaptive networks for our customers and actionable operational insights for the company, requiring a strong and scalable data infrastructure. We are a small company but with a large data challenge! For our data infrastructure we strive to choose technologies that build for our current and future data growth, creating a platform that makes use of technologies such as Kafka, Spark, HBase, and Parquet on AWS S3 as well as our own custom in-house low latency scalable data infrastructure.

We have a ton of open positions right now, but on the data team we're really excited about finding Sr. Data Engineers, Software Engineers with a focus on distributed data systems and infrastructure, and Data Scientists to work with our product and engineering teams.

Full Job list: https://eero.com/jobs

Keyword soup: Machine Learning, Scala, Spark, Kafka, HBase, Python, Mesh Networks, Go, Kubernetes, Sensor Data, ETL, anomaly detection, Redshift

The page mentions there is a shuttle service, where does it pick up from and when does it run?

Does ageism have as much of a perceived presence in tech culture in regions other than the valley?

I do not see it much in the southeast US. .Net and Java dominate the programming language culture here, and you do not just jump in and learn all of .Net or Java in a year or two. For all of its many shortcomings, the south does seem to have a reverence for age and experience (which might contribute heavily to aforementioned shortcomings).

Even at startups, I would guess that the average programmer is over 30 in my area (Charleston, SC). An older programmer here can pretty much live like a king/queen on their salary with nearly limitless employment, assuming they keep somewhat up to date ("up to date" being more like "knows how to use OOP and a standard ORM", not "has a prolific Github profile and uses TDD"). In fact, many of the top programmers you see here are people who left SF or NYC for more stable employment in finance, cushy consulting, and better real estate prospects.

[Disclaimer: I am neither an older programmer nor a .Net/Java dev, but this has been my anecdotal experience]

We're currently charging $5 device per month that you've registered through the RPi. The first two devices are free.

Granted, we're still getting a feel for what our pricing structure should be, do you have any feedback about our pricing structure currently?

So, if I built out 10 RPi based thermometers, that would be $40/month just to get a quick API?

If I added a humidity sensor, that would add another $50/month?

That's pretty steep. Granted, you could be targeting corporate and this starts to make some sense. That kind of pricing really does make it impractical for home users. You're already targeting an audience with some tech savvy and it doesn't take much to write a Python app to serve an API.

Thanks, this is great feedback. We are considering a community tier of pricing aimed more at hobbyists to suit what you're talking about. We're currently targeting startups who are building creative IoT apps and want to iterate quickly and for whom enterprise platforms don't make sense. We're trying to help them move as fast as possible while they optimize their product/market fit.

Another Crowsnest founder here. We're bouncing around the idea of incentivizing contributors to be involved in the community with additional free devices (assuming we can mitigate abuse). For example, if someone contributes the integration library for a specific device then there number of free devices per month increases by 5. Good idea / bad idea? Hoping to get feedback on this.