frossie

My understanding is we do sponsor H1s. The vast majority of nationalities are fine, however we do have on-premises computing on a Department of Energy facility, and they bar citizens of the following countries from being granted an account on their systems: https://www.state.gov/state-sponsors-of-terrorism/ so a candidate with those nationalities would be at a disadvantage.

Unfortunately for reasons outside our control, remote work is only possible from residents of the following US states:

Arizona

California

Colorado

Florida

Hawaii

Maryland

New Mexico

Texas

Virginia

Washington

Washington DC

Here's a talk we gave at Influx Days on how my team uses InfluxDB that also gives background to the project: https://www.youtube.com/watch?v=Osy0dvFM674

The mission of the telescope is to carry out the Legacy Survey of Space and Time (LSST) and so if you search for Rubin LSST you'll get even better stuff I'm sure.

PS not a talk but here's my favorite video we have ever put out, it makes the hairs on the back of my neck stand up. https://www.youtube.com/watch?v=GicDYZXMboc "We'll be counting stars" as the song goes...

And now for something completely different.. (drumroll)... astronomy!

We're building a big telescope to carry out the biggest, faster, widest survey in optical astronomy. I run a small devops team in a much larger data management division - we do current data services work - lots of Python (3) data services (FastAPI) running on Kubernetes on Google Cloud and on-prem (ie sometimes in... actually clouds).

I have a number of refugees from well-known dotcoms in my team, here's why they tell me they work here despite, you know, the universe not handing out stock options:

* Sustained and humane software development, with opportunities to refactor code for incremental improvements and extend your codebase over multiple years

* No pager. If you want to turn off your phone after hours, fine (I keep mine on because fixing telescopes is actually fun to me but there's no on-call)

* No doing interviews as your job.

* 100% open source with many opportunities to upstream (all our code is on Github: https://github.com/lsst-sqre )

* Surprisingly (for academia) current toolchain and coding practices

* Benefits, stability w/ opportunity for growth. My full-stack engineer joined 8 years ago and is (still) doing better work every year. My most recent hire is a security engineer who has been with me longer than the average dotcom tenure and seems to think it's Christmas every time I tell him he's allowed to tidy up code we already have in production.

* Pay is decent, more so if you're not paying Bay Area rent. Not as much as you'd make as a Senior Engineer at Google. But:

* Nobody is the product. We stand on the shoulders of giants.

If you're interested: https://ls.st/square-job . And if you are a US taxpayer, thank you for funding our scientific mission!

At the Large Synoptic Survey Telescope (https://www.lsst.org) we are building an astronomical observatory that will map the sky at unprecedented speed and depth.

We are looking for a senior security engineer with strong devops chops (or alternatively, a senior devops engineer with strong security credentials). Less exciting version here: https://ls.st/zc5

This is academia, so salaries are not what you are used to up there in SV, but it's a chance to contribute to an awesome, if not historic, science project.

Don't let the incredibly sucky job application site put you off, it has nothing to do with what the rest of us do :-) Apply here http://ls.st/bo0 (I'm sorry, academia will have cool recruiting practices in, oh, 2045 or so). If you have questions drop me a line (email in the profile).

PS. You get to work with @astropixie in case you're a fan