Preparing for a meetup tomorrow on engineering your CV.

A reminder that there are things that could matter just as much as your skills:
- Your location (for many companies, still)
- Referrals
- Visas

The less senior you are & the more "local" the company, the more these matter.
The meetup is this one:…

And the graphics are from my book (free for any engineer currently out of a job).
You might wonder "why bother applying for local companies or ones that don't support visas when many of Big Tech does"

Well, one important part: competition. The companies hiring worldwide, offering remote work? They'll see a huge number of candidates & it's hard to stand out.
Even with Big Tech, there is a *lot* of risk with long visa processes.

I've seen a candidate send a note 2 months into the 3-month visa process we started telling us sorry, they changed their mind.

At a large company, we absorbed this. But why would a small company risk this?

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Gergely Orosz

Gergely Orosz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @GergelyOrosz

16 Feb
The 12 most important pieces of information and concepts I wish I knew about equity, as a software engineer.

A thread.

1. Equity is something Big Tech and high-growth companies award to software engineers at all levels. The more senior you are, the bigger the ratio can be:
2. Vesting, cliffs, refreshers, and sign-on clawbacks.

If you get awarded equity, you'll want to understand vesting and cliffs. A 1-year cliff is pretty common in most places that award equity.

Read more in this blog post I wrote:…
3. Stock options / ESOPs.

The most common form of equity compensation at early-stage startups that are high-growth.

And there are *so* many pitfalls you'll want to be aware of. You need to do your research on this: I can't do justice in a tweet.…
Read 9 tweets
3 Feb
Building well-performing (native) mobile apps: a thread.

As I'm writing the chapter on mobile performance in Building Mobile Apps at Scale, I'm doing a lot of reading on this topic.

A collection of the 9 most interesting iOS and Android app performance pieces.
1. Building a blazing fast Android app from @LinkedInEng:…

I love this overview: it seems so... simple. Try doing it and you realize it's far from it. Iterating *so* key for a performant mobile app.

Bonus: they use Nanoscope! (cc: @LelandTakamine )
2. Grab speeding up their "super app":…

Pretty cool to see the top "lower hanging fruit" they saw: app startup, tile caching, animations, binary optimizations, and detecting performance regressions.

A years' work summarized in a short article.
Read 10 tweets
25 Jan
Writing is one of the best things you can invest in, as a software engineer. The more experienced people become, the more they tend to realize this.

Here's a thread on the 6 best writing resources I've found - both to "convince" you to write more and to help you "level up":
1. My extended thoughts on why writing is an undervalued software engineering skill, and the tools (Grammarly, Hemmingway) and books (Writing Well, Sense of Style) that helped me improve my writing.

Writing becomes *so* important at larger companies.…
2. It's time to start writing by @alexnixon_uk . I like the story about making a technical decision, gathering around to talk.

What if they wrote instead? It would be more durable, scalable, and - with COVID - much more feasible.…
Read 8 tweets
23 Jan
How do you bring up the topic of promotions with your manager?

My 7 pieces of advice (thread)
1. Understand how proms work at your company.
2. Talk with your manager: get them on your side. If you don't bring it up: don't expect it to happen. ImageImage
2. (Cont'd) It's in all managers' interest to have people promoted who are already performing at the next level. Makes the manager look good! You're on the same team.
3. Be realistic about what it takes to be promoted above the senior levels. These are usually far more difficult. Image
4. Set goals to "close the gap" that you have compared to the next level. Act like you would like if you had the title. Keep a work log.
5. Find a mentor within the company. Ask for regular feedback. ImageImageImage
Read 4 tweets
17 Jan
A list of tech companies and their experimentation platforms. If you're an engineer and use (or want to use) experimentation / AB tests/feature flags, this is worth a read. A thread.
1. Uber. Lots of articles on Uber's engineering blog, from the platform itself (…), through analyzing outcomes (…) and a talk on decoupling experimentation logs from business metrics (…)
2. Doordash. Reading most of this was "deja vu: this is *so* similar to what we are doing at Uber!" It's a good writeup :…

Considering how fast Doordash went from <10% market share to market leader in the US, they definitely know how to experiment well.
Read 13 tweets
14 Jan
One of the challenges at Uber was building monitoring and alerting that worked reliably.

The problem was how Uber was (is) city-based and global alerting would not catch regional (city/country-level issues).

Two stories on why this is difficult:
1. A PayPal employee on a Japan business trip alerted us in 2016 that PayPal is not working there. He was right: it wasn’t working for 2+ months, across the country. How did we miss it?

There were 20 PayPal trip attempts/day only, and Japan was one of 60+ countries.
In the global scale, this accounted for a tiny fraction.

So we did what makes sense: added country-level alerting.

First, this became a data cardinality problem. 1,000 cities x 15 payment methods... not trivial to track all. We settled on countries & top cities.
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!