Gergely Orosz
@gergely.pragmaticengineer.com
35K followers 2.2K following 3.6K posts
Writing The Pragmatic Engineer (@pragmaticengineer.com), the #1 technology newsletter on Substack. Author of The Software Engineer's Guidebook (engguidebook.com). Formerly at Uber, Skype, Skyscanner. More at pragmaticengineer.com
Posts Media Videos Starter Packs
gergely.pragmaticengineer.com
and yet, native mobile engineering was not all that understood by leadership

also, Uber had (and has) 5x or more backend engineers than mobile engineers.

I wrote the book www.mobileatscale.com based on all the stuff I had to explain to eng directors at Uber about how mobile is different...
Building Mobile Apps at Scale: 39 Engineering Challenges
The guide for building large, iOS and Android native apps - with the challenges and common solutions across the industry.
www.mobileatscale.com
gergely.pragmaticengineer.com
My frustration btw was not with how the promo didn’t happen.

It’s that there was no feedback on what was the gap in professional skills or experience needed

The feedback was professionally incomprehensible and so not actionable

And my management chain + HR didn’t see this as a problem but I did
gergely.pragmaticengineer.com
… got promoted with a slam dunk the next cycle (the committees feedback was they didn’t understand why he was rejected the last cycle).

A few years later Apple recruited him and he ended up owning one of the big apps almost everyone on an iPhone uses daily
gergely.pragmaticengineer.com
Anyway it was this awkward situation where I as a manager told the engineer the system is broken; I tried but couldn’t fix it; the committee feedback is BS and can be ignored and I’m just as frustrated as them except I didn’t miss out on a promo.

I’m the end, he stuck it out…
gergely.pragmaticengineer.com
Yes - I basically told them the promo committee is unqualified, I went as high as I could to fix it, and they should have been promoted, and the feedback is garbage.

Then told them I can help them find new teams and understand / support also if they’d leave and will give them the best references
gergely.pragmaticengineer.com
It was a TON of documentation! Which accidentally worked in my team’s favour: we were on a smaller site (Amsterdam) working with the US a lot so documented *everyting* especially that a lot of work was across time zones. Plus I always push to write things down

And still was tons of writing!
gergely.pragmaticengineer.com
2. Scaffolding on mobile is more lines of code and more verbose than backend, and some of it was generated

It was so maddening
gergely.pragmaticengineer.com
The feedback I recall was eg hung up on how their diffs were often large

… but didn’t understand that it was

1. all stacked diffs (all small!) that were large because CI on mobile took an hour to run and reviews. They basically expected backend workflow on a mobile, totally different codebase
gergely.pragmaticengineer.com
As I understood the intention was good: having a committee who doesn’t know you

Mobile engineers in my team were known by the experienced mobile engineers on the promo committees, so they were not assigned

But the backend / native mobile divide was (probably still is!) very big…
gergely.pragmaticengineer.com
The feedback was so out of touch and recommendations on professional growth made zero sense so I took it to HR to get at least a single native mobile eng take a look at the package

HR then said the process must be followed and next cycle they’ll fix it… got a taste of large company processes
gergely.pragmaticengineer.com
Thinking about the time when Uber made changes to the promotion process to make it unbiased.

So the 2 mobile engineers up for promo on my team were reviewed by a committee of all backend engineers

And rejected them w arguments that showed they don’t understand native mobile dev
gergely.pragmaticengineer.com
And this is the a sympthom, not the root cause. (Also, talking with hiring managers and recruiters in tech: none of them told me they use AI tools for filtering. Inbounds are simply not being read often, because there are so much of them + low quality!)

www.theatlantic.com/ideas/archiv...
gergely.pragmaticengineer.com
"It's the weirdest job market in my 15 years in tech" -- from a Big Tech recruiter. But why is the job market so weird?

Talking to 30+ hiring managers and recruiters, it doesn't seem like AI. It seems more like.. interest rates.

My longer analysis: newsletter.pragmaticengineer.com/p/state-of-t...
gergely.pragmaticengineer.com
What makes a standout software engineer?

Charles-Axel Dein was engineer #20 at Uber, hired me there and was my manager for years (a great manager, I might add.) He answers, and also shares what a standout engineer looks like at CloudKitchens, today:
gergely.pragmaticengineer.com
And this engineer is one of those "invisible engineers" from the outside.

No social media footprint, GitHub pretty much empty the last 5 years

You cannot tell from the outside how insanely good of an engineer this person is - until you ask ex colleagues. Many such cases.
gergely.pragmaticengineer.com
This is the power of "network" when "network" comes from doing standout work wherever you work, helping colleagues even when not asked.

It's also why the only sure way to hire someone like this is via a referral: with so many solid options, they won't bother with applications.
gergely.pragmaticengineer.com
One of the best staff-level engineers I worked in the past with is on the market.

This is someone who will not fire off a single job application: already interviewing at companies where ex-colleagues heard he's on the market. Even if not hiring, they are creating space for him.
gergely.pragmaticengineer.com
Also, the same recruiter said compensation expectations for these same folks who are totally out of the loop with AI are jaw-dropping.

I guess a tip to eng leaders interviewing: if the recruiter knows more about applied AI thank you do, don't be surprised on not hearing back...
gergely.pragmaticengineer.com
From a recruiter at publicly traded tech company:

"Been hiring for eng leadership positions. Several engineering leaders I talk to claimed that they are building AI products at their current position. But when I drill down, all they know about AI is basically using ChatGPT...."
gergely.pragmaticengineer.com
Didn’t think we’d see incompetence at this scale.

The backup of the on-prem data center for the Korean government was in the same location as the primary one.

Any basically qualified tech professional knows that this is no resilient backup: and now all data is lost…
gergely.pragmaticengineer.com
Code repeating itself in a codebase slowly becomes a form of tech debt-and it’s tricky to avoid on larger projects, even at Google.

I wonder when using AI coding tools, duplication would start to become a problem sooner vs before?

From Code Health Guardian by Artie Schevchenko
gergely.pragmaticengineer.com
Behind the scenes of lots of AI startups that announced raising a large round of funding:

Rushing to hire more enterprise salesfolk: B2B sales is the only way to grow fast enough to raise a next round

Not sure it’s been a better time to be in enterprise sales than now…