eero | Software Development Engineer | SF/USA/VISA/REMOTE
My team works primarily using Scala with some occasional Python. Most of us are currently in the Bay Area, but you can be anywhere.
eero is the first company to deliver a whole home WiFi experience using mesh technology to make sure you never have to worry about WiFi ever again.
Our mesh routers rely on a cloud backend built in Scala, backed by Postgres.
Our cloud-based backend allows our users to configure, maintain, and troubleshoot their devices and networks from anywhere. In a typical week, you will work closely with a cross-functional team including product managers, designers, and iOS, Android, and frontend engineers to prototype, design, and build core experiences for existing and future products.
You will also be defining APIs, reviewing technical proposals, and contributing to our internal tools and test frameworks.
Interested in learning more? Email me (Ryan): rkabir@eero.com
We're looking for an engineer and a marketing/growth hacker to help us change the way people think about volunteering their time for charity.
(The engineering position lists front-end, but a back-end/middle/generalist/whatever (we're on Rails) would be awesome - anything to take some load off of me :) )
We're super early, angel-funded, and since you'd be employee #1, for the right person, non-trivial equity is definitely on the table.
* Wake up (and get up) at my leisure: no alarm - I'm able to maintain this for the most part, unless of course there are specific commitments.
* Catch up on info-glut before breakfast - forces me to get through it all faster. Work-related email and information is included in this set. Anything not supremely important gets sent to Instapaper so I can get over my need to feel like I should read something, and promptly forget about it and move on with my life.
* 30-60 minutes of exercise (usually a jog or the treadmill, but swimming when convenient) that lets me digest the information I've just been exposed to if necessary, and think about what's important today. I take notes during.
* Shower / hygiene (also good for thinking)
* Breakfast (preferably alone and in quiet), while I outline my plan for the day.
* Work (repeat as necessary). I work while signed onto restricted IM accounts that make me available to very few people - namely, work associates and immediately close friends with whom I can be completely free to ignore or converse with at my leisure. When I need/want to focus, I ignore. When things are slower, I'll socialize more.
* Breaks - Sometimes I'll interrupt work with a longer form break. Sometimes a walk, sometimes a conversation. Never RSS/Twitter/Facebook.
* Stop for lunch / dinner when I'm hungry. Either meet up with people or read longer-form non-fiction if solo (picking off vignettes from Instapaper)
* Evenings (read: late night) before bed is for [optional] leisure. If I'm productive and enjoying my work, I won't stop and I'll cancel plans as appropriate. If I'm not enjoying my work but I'm behind schedule, I'll keep going if I can. Otherwise, I'll do any subset of {social, videogames, reading, watching, writing}.
* Sleep iff I'm at the point where I want to sleep more than whatever I'm doing.
Days of travel, guests, or otherwise special significance deviate from this quotidian rhythm.
I've been surprised at how seemingly minor changes in the relative cost of doing something can have major impacts on behavior.
I'd like to exercise in the AM, however I keep failing at it because it costs much more to go to work early, than to go to work, work until evening, and then walk downstairs to the gym.
What are the "good" things we should target for cost-reduction?
Cost reduction is relative. I don't go to the gym, I work out at home if possible, and supplement with music or audio streams that I find enjoyable. And I'll prefer social physical activity (swimming, badminton) to sedentary social activity.
I think it's important to make it easy to switch projects or life tracks. Some would say that it makes too easy to sit in a pool of confusion - but on the other hand it means when you're sticking with something, you want to stick it out.
My team works primarily using Scala with some occasional Python. Most of us are currently in the Bay Area, but you can be anywhere.
eero is the first company to deliver a whole home WiFi experience using mesh technology to make sure you never have to worry about WiFi ever again.
Our mesh routers rely on a cloud backend built in Scala, backed by Postgres.
Our cloud-based backend allows our users to configure, maintain, and troubleshoot their devices and networks from anywhere. In a typical week, you will work closely with a cross-functional team including product managers, designers, and iOS, Android, and frontend engineers to prototype, design, and build core experiences for existing and future products.
You will also be defining APIs, reviewing technical proposals, and contributing to our internal tools and test frameworks.
Interested in learning more? Email me (Ryan): rkabir@eero.com