Aurora | Staff TLM, Cloud Platform | Full Time | Hybrid in SEA, Bay Area, PIT | $189-302k | https://aurora.tech
Aurora is building autonomous trucks. We’re scaling to MVP and are building a developer platform to increase developer productivity, happiness and reduce cognitive load. The ideal candidate would help lead and build this effort.
Skills and experience we’re looking for:
- 5+ years demonstrated experience shipping commercial products and services, preferably in Go
- Deep experience with Kubernetes. You’ve built custom controllers and/or operators to solve automation problems. If you can demonstrate this we really want to talk to you!
- Experience leading a small team of infrastructure engineers
- Experience designing and implementing services in Go, Python or C++
- Experience building CI/CD pipelines, using tools like ArgoCD and Spinnaker
Aurora | Senior Software Engineer, Cloud Platform | Full Time | Hybrid in SEA, Bay Area, PIT | $168-252k | https://aurora.tech
Aurora is building autonomous vehicles. We’re scaling to MVP and are building a developer platform to increase developer productivity, happiness and reduce cognitive load. The ideal candidate would help build this effort.
Skills and experience we’re looking for:
- 5+ years demonstrated experience shipping commercial products and services, preferably in Go.
- Experience building developer platforms/frameworks (Backstage.io, Cortex, Humanitec, score.dev, etc) for companies past the initial start-up stage.
- Demonstrated ability implementing a large, multi-quarter initiative that spans across teams and disciplines.
Aurora | Staff Developer Platform Engineer | Full Time | Hybrid in SEA, Bay Area, PIT, DEN or Bozeman | $(189-302)
Aurora is building autonomous vehicles. We’re scaling to MVP and want to build a developer platform to increase developer productivity and happiness. The ideal candidate would champion, drive and help build this effort.
Skills and experience we’re looking for:
- 5+ years demonstrated experience shipping commercial products and services, preferably in Go.
- Experience building developer platforms/frameworks (Backstage.io, Cortex, Humanitec, score.dev, etc) for companies past the initial start-up stage.
- Demonstrated ability to drive a large, multi-quarter initiative that spans across teams and disciplines.
Aurora | Service Mesh Engineer (and lots more!) | Hybrid (Bay Area, Seattle, Pittsburgh, Bozeman) | VISA | Full Time | https://aurora.tech
At Aurora, we’re on a mission to deliver the benefits of self-driving technology safely, quickly, and broadly. It all starts with the Aurora Driver, a platform created from industry-leading hardware and software and designed to adapt across a variety of vehicle types and industries.
As we prepare to go public this year, we’ve been pulling back the curtain on our technology and progress in self-driving - you can watch our engineers talk about our perception, simulation, hardware stack and more at https://aurora.tech/ai.
As we work towards building our first product, the Aurora Driver, my team is looking for someone to lead our service mesh effort.
What you’ll do as a Service Mesh Engineer:
Connect, secure, control, and observe traffic in Kubernetes clusters for our long-running services and APIs. You will work on our key ingress, as well as manage our services' authentication and telemetry. This person will have a huge impact in establishing a service mesh at Aurora and determining how distributed systems will work at our company.
When we’re back in the office, Aurora will run on a hybrid model. This particular role may also be open to remote (US only) for the right candidate.
We have tons of jobs open across Software and Hardware engineering - you can check them all out at https://aurora.tech/careers!
Be careful though - we use Aurora PG and it's great for what it does, but they do not support managed upgrades across major PG versions yet! We're stuck on 9.6.x because the time to dump and restore our large DB is a non-starter with the rest of the business.
Everyone uses the more mild version of dehumanizing language, reduction to abstraction [1], because it's more efficient to consider groups of people and it removes emotions from decisions.
For example, when considering latency you might say:
The service is experiencing 3 seconds of latency at the 99th percentile with periodic timeouts.
You wouldn't say
Alice wasn't able to buy medicine because the transaction failed.
As I understand it, this has to do with who was asking for a thing and what they wanted.
The upper class spoke French and when they asked for beouf, they wanted meat, not a cow. Likewise when they asked for poulet, they wanted a cooked chicken, not a live one.
The lower classes spoke German and gave us cū (kuh in modern German) for a cow and cīceb (Küchlein in modern German) for chicken.
As English grew from both of these roots, the different words remained.
I thought this too for the longest time - turns out it's actually not true (assuming Wikipedia is to be believed). There aren't any age restrictions on what can be sold as 'lamb', so most American 'lamb' is what the British would call mutton.
Nevertheless, s0rce is correct on the original linguistic point: that the Norman food-word is "mutton", whereas "lamb" is the Germanic word for the young animal.
interesting, thanks for informing me! I checked wikipedia before commenting but I didn't read far enough, didn't know there was no legislation on lamb age. I wonder how old the "lamb" in the grocery store is? Might explain why there is so much variation in flavor. I can't remember if the lamb was "younger" tasting when I lived in Canada.
I, indeed, did find it interesting and to which I respond, "'dafuq?" I grew up in the U. S., and growing up actually raised sheep. And when you are served adult sheep, you are served "mutton". IOW, the term "mutton" was not "uncommon in the United States" in my part of the country at the time I was growing up.
But that's another time and another place; I'm kind of curious about when the change came about. Partly because, were that article written thirty years ago I would have argued that it is wrong. But I've since become a vegetarian, and might not have gotten the memo when the change came about. Or maybe I've always been wrong, along with all the other hicks I grew up with. :-)
This has more to do with classist beliefs than it does with dehumanization. The origin of those words relate to the aristocracy using the french/latin forms, while those poor farmers used the orginal english/germanic forms. Notice what the french words are for a pig or oxen/steer.
At this point you might be right, but the origin is about wanting to fit in with the new french overlords.
For some reason, in the French language itself the same distinction eventually appeared.
In regular language, you would call porc the meat that comes from a cochon, and bœuf the meat of a vache.
It's not as clear cut as in English, as a bœuf is also an ox, and you can also call a pig a porc, but I think it indicates that the linguistic distinction between an animal and its meat is indeed at its core a dehumanizing process, it might just have been helped by the French-speaking rulers of England, but it still happened in France eventually, more recently and without exterior intervention.
"Dehumanizing" isn't the proper word here, since we're literally talking about non-human entities. If you want to talk about inter-species empathy, it should be pointed out that most predatory species aren't relating to their prey animals (they typically go after the weakest prey; young, elderly or sick animals which humans would likely empathize with). The odd behavior is that we ascribe human traits to things we plan on killing and eating which aren't objectively demonstrating them.
"but I think it indicates that the linguistic distinction between an animal and its meat is indeed at its core a dehumanizing process"
Why? I feel absolutely no emotional difference between "cow meat" and "beef", and would be surprised to hear that it really made a difference to pretty much any non-vegetarian... Further, it seems nobody has felt the need to introduce a different word for 'lamb' - it's still an extremely popular meat despite the word literally meaning 'baby sheep'...
I think it's drawing a really long bow to think it's desensitising language (dehumanisation isn't really the right word, since cows, sheep etc. aren't human). At the end of the day, I think it's just a quirk of language development...
MightyAI | Data Science, Front and Backend Engineeners | Seattle, Boston | ONSITE | mty.ai/hiring
Seeking the adventurous and the bold to help us build a great company and shape the future of AI and autonomous vehicles.
We have strong institutional backing from Madrona Venture Group, NEA, and Foundry Group. We're building Mighty AI to last.
Our stack is Ruby on Rails on the web side, Python on the Data Science side, postgres is the DB and everything is on AWS.
Don't feel like you need an ML background to apply - we're especially looking for senior engineers (Rails preferred) who have broken apart a monolith and scaled a site to millions of users.
Seeking the adventurous and the bold to help us build a great company and shape the future of AI and autonomous vehicles.
We have strong institutional backing from Madrona Venture Group, NEA, and Foundry Group. We're building Mighty AI to last.
Our stack is Ruby on Rails on the web side, Python on the Data Science side, Postgres is the DB and everything is on AWS.
Don't feel like you need an ML background to apply - we're especially looking for senior engineers (Rails preferred) who have broken apart a monolith and scaled a site to millions of users.
Aurora is building autonomous trucks. We’re scaling to MVP and are building a developer platform to increase developer productivity, happiness and reduce cognitive load. The ideal candidate would help lead and build this effort.
Skills and experience we’re looking for:
- 5+ years demonstrated experience shipping commercial products and services, preferably in Go
- Deep experience with Kubernetes. You’ve built custom controllers and/or operators to solve automation problems. If you can demonstrate this we really want to talk to you!
- Experience leading a small team of infrastructure engineers
- Experience designing and implementing services in Go, Python or C++
- Experience building CI/CD pipelines, using tools like ArgoCD and Spinnaker
If this sounds interesting to you, apply below!
https://aurora.tech/jobs/staff-tech-lead-cloud-infrastructur...
We also have other open roles in engineering at https://aurora.tech/careers!