Amazon Grocery Tech | Full Time | ONSITE Hybrid (in-offce 3 days p/w) | Brisbane, Australia
I'm a developer in grocery working in Brisbane. We're currently hiring for grads / recent grads (<24 months exp, with some flexibility there). We mostly write software for outbound grocery (delivery + pickup) worldwide, for both Amazon and 3P brands. We have fun and exciting challenges to suit all interests. Feel free to email me if you want to learn more.
The office in Brisbane is a beautiful place to work (there are flexible working options blending at home and in office), and I can personally vouch for the teams in Brisbane being awesome to work for, with interesting and fulfilling work.
From our job ad:
> ... The features you build have direct impact on customers lives. You will work with scientists and engineers to optimize fulfillment processes, reducing costs and improving quality. You will experiment with new ideas, turning the successful ones into full production systems whilst failing fast and learning from those which are not. We obsess over reducing the time and cost in fulfilling a customer's order.
> Maybe there should be a system to filter actual complex cases up layers of specialty
I mean, this is normally your GP referring you to a specialist, and 99% of the time that works. But when your specialist doesn't even know enough to know where to refer you next you end up in a weird space that is incredibly challenging to navigate. It would be good if there was an "expert diagnosticians" group that you could go to when even specialists are stumped. They could help navigate referrals to specialists, tests-of-treatment and enrollment in trials (which is a whole other minefield).
They'd be discoverable by search or linking. The distributed web is compatible with feeds. It's what's happening on this site too. Except the content would be packaged and redistributable and wouldn't disappear when the original service goes down or such.
Sure, but (gen-pop) search itself has been degraded / hijacked beyond recognition compared to two decades ago, and walled gardens heavily discourage linking. Factor in that most people access internet from devices designed to consume in very specific ways from a controlled list of sources and we may as well be lamenting that nobody's finding the one physical copy of your book that's sitting on a shelf in a brick and mortar library in Omaha.
It feels like a chicken and egg problem to me -- realistically you need to meet people where they're at and appeal to the current channels' algorithms to get your content discovered, but in doing so you also reinforce the strength of the walled garden itself and participate in the diminishment of both search and the "wild" internet at large.
Mhh dunno, I don't think it helps to think about the unfortunates stuck to their media feed at this stage. Might as well make the dweb about something us nerds want. It's gonna be good... and then it'll be about keeping the parasites out that live off that cultural capital.
Something durable, censorship-resistant, network-agnostic, optionally trust-based. Maybe a bit of IPFS + i2p + content-adressable, composable, cross-linkable, multimedia documents + federated services? I feel the components already mostly exist actually...
This is the hardest part about trunk based development - changing your way of thinking. Everything needs to be decomposed into much smaller changes, and you need to think about the impact of each of them being deployed into production (since that will happen). New features should exist behind some kind of feature gating or dial-up capability, or a new API version with restricted access, etc.
That seems painful but it's less painful than merge hell or deploying a change with a massive delta to production and needing to roll it back and unpick what went wrong.
It actually makes sense for Amazon integrating this with the whole browser based shell thing (which is a sensible secure default for a lot of people).
Having something with autocomplete that works seamlessly with their services seems like a better idea than a plain prompt if you're going to use their shell. Hopefully they do something sensible and customer-centric with the telemetry stuff, that seemed to be the big drawback for many.
Amazon Grocery Tech | Junior + Senior Software Development Engineers | Brisbane, Australia | Onsite, WFH friendly | Full-time
My group (Grocery Tech Team based in Brisbane) is growing at an exceptional rate to create software that will delight customers worldwide. We're currently hiring for junior and senior roles. We mostly write software to assist with outbound grocery (delivery + pickup) worldwide, for both Amazon and 3P brands. We have fun and exciting challenges to suit all interests. Feel free to email me if you want to learn more.
The office in Brisbane is a beautiful place to work (there are flexible working options blending at home and in office), and I can personally vouch for the teams in Brisbane being awesome to work for.
If you can't answer this, you are going to have a very bad time when you retire.