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).
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.
It was ultimately Bezos' API mandate that made this (and the cloud as we know it) happen:
> 1. All teams will henceforth expose their data and functionality through service interfaces.
>...
>5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
us-east-1 is made up from several availability zones, it is extremely unlikely to go offline for months. If a catastrophe of a scale to do that happened, some datacenters being offline wouldn't be the headline news.
Consider getting an at-home sleep study, you may have sleep apnea. I did, and I did, and now I wear a device (not a CPAP machine!) that helps significantly. I don't sleep any longer but my sleep is less interrupted and I get more deep and REM sleep. I feel 1000 times better for it.
How are you measuring your sleep? I have an Oura ring and while it's not the most accurate thing in the world it does a pretty good job of total sleep and phases for me. The readiness scores are also really useful as a yardstick and comparison against how rested you feel. I got one because I have mild sleep apnea and wanted to be able to track the efficacy of the solutions I was trying out.
I recently went on a break from caffeine, and while the withdrawals weren't bad (I was only ever a one coffee in the morning person), I have since noticed how INCREDIBLY sensitive I am to caffeine. Now that I have no tolerance, having one coffee at any point during the day will completely ruin my sleep for that night (from ~7h down to ~4h with lots of awake time).
I'm at a point now where I don't think coffee is for me - I love the taste and the effect but not at the expense of a good night's sleep!
This is a really good point, there is no good reason to have millions of devices phone home for permission on every single app open. If Apple's claim is to be believed there are a million patterns that make more sense for achieving this goal. Blacklists, whitelists, caching, etc.
I get "never attribute to malice what can be explained by incompetence", but this is Apple. Are we to believe that this public, unencrypted endpoint was set up and is being called tens of millions of times a day because Apple engineers were too incompetent to come up with a better solution for something so fundamental (to Apple) as the security of the software running on their devices? And flying so blatantly in the face of their claim to protect user privacy?
This whole incident is completely bonkers. People should be getting fired over this and there should be an apology and a massive step back from this horrible, horrible approach.
In general a lot of Australian forest does need to burn, we know this. Record drought and record high temperatures over the past few years created the catastrophic fire conditions we have seen this year. Controlled burns cannot be carried out when conditions are dry and hot - the fire gets out of control. Thus there have been very few burns of this nature over the last several years.
Climate change means it's getting more and more difficult to carry out these type of controlled burns for forest management in general. Our fire seasons are longer, hotter, drier and more dangerous, and these types of burns can and do get out of control.
If you can't answer this, you are going to have a very bad time when you retire.