That job listing is just so sad. Who starts a senior android role's requirements with "git workflows"?
It might seem trivial to you, but the last thing I want in a CI/CD pipeline is senior engineers that don't understand the underlying technology.
Believe me, I've interviewed lots of people for senior positions that just haven't had to properly learn revision control. It's not a given.
The only Android related things on the job listing are proficiency with the IDE (Android Studio) and generic "frameworks".
I am an Android engineer, I clicked this job listing earlier today when it was on HN because I was interested in it. From the perspective of a listing that tries to get a good funnel of candidates coming in, it does nothing for me.
Would you apply to that job listing? I spend a lot of my day to day helping companies optimize their job listings, especially when they have high view numbers but low application click through rates, so this is a pet peeve.
Basically I like job listings that include _specific_ information about the role at the company. Maybe that means listing some of the hard challenges the other people on the team have worked on recently, maybe it just means listing the frameworks and libraries they're using, but anything to help me differentiate their Android role from someone else's Android role.
I don't mean to put you down for you requirements but git is really really easy to learn. It would be a shame to miss out on a talented developer for something an otherwise well qualified developer could learn in a weekend.
Learning is not the same as memorising a few commands.
https://www.sequoiacap.com/article/trial-week-our-hiring-sec...
> I tell people that the worst case scenario is that they use a week of vacation, but because of the extra pay they can take a nicer vacation later on.
I mean, how can they, if they've already used their vacation time?