Hacker Newsnew | past | comments | ask | show | jobs | submit | more JakeSc's commentslogin

Life360 | iOS Growth Engineer | San Francisco, CA | Onsite

20 million monthly active users.

Doubled userbase year-over-year.

Tripled revenue year-over-year.

Bringing peace of mind to families with technology.

We're hiring an iOS engineer to join our newly-formed Growth team to help us scale up globally. If you know iOS, and have experience with different technologies like web / backend / Android, or are particularly hungry to learn, we want to work with you.

With over 20 million active users and $90 million in venture funding, Life360 is the world’s largest mobile app for families. Today, we are focused on location sharing and safety, but our mission is to become the must-have Family Membership that gives families peace of mind anytime and anywhere. From personalized location-based alerts that help make daily coordination easier, to advanced sensor tech that can detect a car crash and automatically send you an ambulance, we are leveraging smartphones to their fullest extent to reinvent how families get through the day.

- Full-time

- Location: San Francisco, California

- Competitive salary and stock options

- $200/month Quality of Life perk

- Great office in SOMA: dogs are welcome, tons of snacks, and great catered lunches

- Autonomous team with lots of support from around the company

Apply here: https://boards.greenhouse.io/life360/jobs/4247847002


Life360 | Android & Backend | San Francisco, CA | Onsite

15 million monthly active users.

Doubled userbase year-over-year.

Tripled revenue year-over-year.

Bringing peace of mind to families with technology.

We're hiring senior Android and Backend engineers to join our newly-formed Growth Team to help us scale up globally. Don't let "senior" scare you; if you know your way around Android or microservices, and have experience with different technologies like web / backend / iOS, or are particularly hungry to learn, we want to work with you.

With over 18 million active users and $90 million in venture funding, Life360 is the world’s largest mobile app for families. Today, we are focused on location sharing and safety, but our mission is to become the must-have Family Membership that gives families peace of mind anytime and anywhere. From personalized location-based alerts that help make daily coordination easier, to advanced sensor tech that can detect a car crash and automatically send you an ambulance, we are leveraging smartphones to their fullest extent to reinvent how families get through the day.

- Full-time

- Location: San Francisco, California

- Competitive salary and stock options

- $200/month Quality of Life perk

- Great office in SOMA: dogs are welcome, tons of snacks, and great catered lunches

Apply here:

Android - https://boards.greenhouse.io/life360/jobs/4154046002?gh_src=...

Backend - https://boards.greenhouse.io/life360/jobs/4158708002?gh_src=...


Life360 | Android | San Francisco, CA | Onsite

15 million monthly active users.

Doubled userbase year-over-year.

Tripled revenue year-over-year.

Bringing peace of mind to families with technology.

We're hiring a senior Android engineer to join our newly-formed Growth team to help us scale up globally. Don't let "Senior" scare you; if you know Android, and have experience with different technologies like web / backend / iOS, or are particularly hungry to learn, we want to work with you.

With over 15 million active users and $90 million in venture funding, Life360 is the world’s largest mobile app for families. Today, we are focused on location sharing and safety, but our mission is to become the must-have Family Membership that gives families peace of mind anytime and anywhere. From personalized location-based alerts that help make daily coordination easier, to advanced sensor tech that can detect a car crash and automatically send you an ambulance, we are leveraging smartphones to their fullest extent to reinvent how families get through the day.

- Full-time

- Location: San Francisco, California

- Competitive salary and stock options

- $200/month Quality of Life perk

- Great office in SOMA: dogs are welcome, tons of snacks, and great catered lunches

Apply here: https://www.indeed.com/viewjob?jk=785ae94c25f1bd67


15 million monthly active users.

Doubled our userbase year-over-year.

Tripled revenue year-over-year.

Bringing peace of mind to families with technology.

We're hiring a senior Android engineer to join our newly-formed Growth team to help us scale up globally. Don't let "Senior" scare you; if you have experience with different technologies like web / backend / iOS, or are particularly hungry to learn, we want to work with you.

With over 15 million active users and $90 million in venture funding, Life360 is the world’s largest mobile app for families. Today, we are focused on location sharing and safety, but our mission is to become the must-have Family Membership that gives families peace of mind anytime and anywhere. From personalized location-based alerts that help make daily coordination easier, to advanced sensor tech that can detect if you are in a car crash and automatically send you an ambulance, we are leveraging smartphones to their fullest extent to reinvent how families get through the day.

- Full-time

- Location: San Francisco, California

- Competitive salary and stock options

- $200/month Quality of Life perk

- Great office in SOMA: dogs are welcome, tons of snacks, and great catered lunches

Apply here: https://www.indeed.com/viewjob?jk=aca25baafe248a83


This post is a high-level intro of the two-part architecture we are using for our mobile app. Feedback welcome.


As an engineer at Life360, I can tell you that we hear you loud and clear. We haven't always been the best at achieving high accuracy _and_ power efficiency, but we are improving the technology dramatically. Battery drain has been a major focus for our engineering team for a long time, and especially recently. Give it a try again and let me know how your experience is.


Are many consumer applications running with a multi-process architecture?


Ensuring physical security of CA private keys is expensive. This requires things like sturdy padlocks, closed-circuit security cameras, and up-to-date hardware and software.

These are the things you pay for when you buy a certificate from a CA. In fact, I would be 100% opposed to obtaining my website's cert from a CA if it were free-of-charge, because I know good physical security is expensive. However, I already trust the EFF and the Umich researchers (and their assurances of physical security), so I'm absolutely happy with obtaining a free certificate from them.


Good post, but is pinging the broadcast address really "passive network surveillance"? My definition of "passive" involves never sending new network traffic.


Yes, this is definitely an active scan. However, hooking in to DHCP syslogs would still be passive. It's nice that the author provided an active alternative in cases where you might not have access to the DHCP logs.


Thanks for posting this. One question I have is this: When, as the CTO, you approach an engineer with the intent on coding together or otherwise building some system, are there not organizational challenges with an executive working with a subordinate? I realize that this has been tremendously beneficial to you, but I wonder how this works mechanically--do you just say, "Hey Jeff, let's build this together."? I have to imagine that if you're ever wrong technically, an individual contributor-level engineer might hesitate to tell you.


I would suspect that their culture has evolved in a way that allows people to point out the CTO that they are wrong.

If he has always been involved and close to his team then pointing errors would feel more like giving feedback to a peer rather than giving feedback to a superior.


Yes, but it is a very difficult line to walk.

The difference between "have you considered using X?" and "I tell you to use X", the difference between "can we hit date Y?" And "we must hit date Y so start cutting corners"

Authority as a position is a difficult stick to carry - if you are telling people "my way or the highway more than once of twice a year" you are over doing it.

"I feel uncomfortable with this architecture" or "this will take longer than you hope" are all indicators you are doing it right. Stop hearing those and you should worry.


I think a lot of these cultural questions require you to say over and over what's important, and demonstrate that you really mean it. I always ask people what they think, and when I sense hesitance I work to draw them out. In the end a lot depends on your relationship with the individual; I make sure to spend time getting to know every engineer who joins.

More broadly, one point Marc often makes is, if someone does something you don't like/disagree with, let them know directly. (There are some exceptions to this, and sometimes it's helpful to role-play with a manager to get some practice before doing so, but we work hard to make direct feedback a core part of Stripe.)


I spent a few days in the Stripe office with my team (Hey guys!) and I can tell you with certainty that they have a very strong collaborative team. They actually have a really great culture that they actively try to build (thanks for including us while we were in town!). Fridays are particularly awesome.

Anyway, my point is that I never got the feeling like people say "it's going to be this way, no questions", but also got the feeling that if a superior did say "look, I know you guys feel this way, but we are going in this direction and the deadline is X" that the team would rally behind their leader and support their decision.

Stripe, from what I saw you have done a great job building out your team. Congrats, it's nice to see companies doing it right!


Yep, this is right.


I think it's precisely because he is known directly to the engineers that this works. No idea how well it will scale for them -- I wish them well.

In most "big" organisations, the C-levels are practically celebrities, everyone wants to be "connected" some how to them, but hardly anybody works "with" them. Everybody works "for" them (and even those direct reports/workers are imbued with some special celebrity powers by just saying the name). The hierarchical relationship of everybody working "for" you causes plenty of insulation -- communication grinds to a halt besides the cordial banter.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: