(Remote work depends on the role -- some are onsite only, others may be available to remote workers.)
Planet Labs has a large number of positions open. We're a collection of electrical, mechanical, aerospace, software, science, etc. folks looking to image the whole planet on a daily basis with a large number of small satellites. It's a terrific bunch of folks doing what we call "agile aerospace".
I've personally been with the company for over a year, working on "Mission Control", an internal web app for managing the satellites and make life easier on our "Spaceship Captains" -- the operators who manage them. This is definitely one of the most interesting and fun roles I've had in my career (and I've had a few).
Python (Flask, Django) and Javascript (React, Backbone) are used heavily in the web projects. We of course have systems programming to do for the onboard software. Plenty of other interesting work from the satellite design and various subsystems, manufacturing, georectification of images, image corrections, dev ops, site reliability engineers, and heaps of possibilities with a supremely interesting dataset that we're growing.
Hi, I applied for one of Planet's open positions a few weeks ago, and I've been trying to get in contact with someone. The phone number for the SF office goes straight to voicemail. What's the best way to contact the appropriate person for a software position?
Applying via the website is the best and only way. We've been updating our tooling and process with the aim of being better about responding moving forward, but it goes with pretty much any company -- even if it doesn't work out with one position, there will be others and it can make sense to keep looking and keep trying. The larger the company, the more likely for this to be the case.
I'll check, but in general if a company is hiring you to work in a specific office/locale, then they're likely willing to help with the process of being employed and employable there.
Really hard to say. Could be a number of things from the engineer reviewing the code being swamped to the coding sample not being strong enough to needing more time. If it's been a few days, it's ok to send in a nice email to the recruiter, even something simple like
"Hi! Just wanted to check if you received my coding sample and if there's any feedback. Thanks so much!"
Understood. I'm an engineer at the company, not a recruiter, but I'll pass the word along. Either way, thanks for the feedback and sorry for the inconvenience. A "no" response is better than no response.
Just saw this -
Thanks! For what it's worth, I think the team there does some really neat things with the doves. Not sure HN'll allow you to amend the post to include an INTERN keyword, but you should add it in subsequent whoishiring's. :)
(Remote work depends on the role -- some are onsite only, others may be available to remote workers.)
Planet Labs has a large number of positions open. We're a collection of electrical, mechanical, aerospace, software, science, etc. folks looking to image the whole planet on a daily basis with a large number of small satellites. It's a terrific bunch of folks doing what we call "agile aerospace".
I've personally been with the company for over a year, working on "Mission Control", an internal web app for managing the satellites and make life easier on our "Spaceship Captains" -- the operators who manage them. This is definitely one of the most interesting and fun roles I've had in my career (and I've had a few).
Python (Flask, Django) and Javascript (React, Backbone) are used heavily in the web projects. We of course have systems programming to do for the onboard software. Plenty of other interesting work from the satellite design and various subsystems, manufacturing, georectification of images, image corrections, dev ops, site reliability engineers, and heaps of possibilities with a supremely interesting dataset that we're growing.
Full list of jobs at https://www.planet.com/careers/#openings