Ilija

Curious. EM at @Stripe. Previously: @scribd, @catawiki, @siyelo.

[Ilija @stratechgist]

@eric_x1ng @Tempo_Labs Ignore me. I had my ProtonVPN up with some blocking/protection in place that caused the problem. Once I disabled it https://t.co/1wNPtgJUNV works just fine.

[Ilija @stratechgist]

@eric_x1ng @Tempo_Labs hey, thanks for checking! That's quite weird, https://t.co/1wNPtgJUNV returns the same HTTP 403 page as well.

[Ilija @stratechgist]

@dqmonn so basically @GergelyOrosz 's podcast? :-)

[Ilija @stratechgist]

This structured approach shows you've done your homework while making it easy for your manager to provide the right kind of support. (6/6)

[Ilija @stratechgist]

My manager once told me bluntly: 'I have 5 direct reports and a dozen projects. If you don't tell me you're blocked, I assume everything's fine.' A wake-up call for my stoic approach. 1/6

[Ilija @stratechgist]

Before each 1:1, identify your top blocker using this format:
• Blocker: [issue]
• Impact: [consequence]
• Attempted solutions: [efforts]
• Requested action: [help needed] (5/6)

[Ilija @stratechgist]

Topics might include architecture decisions, career specialization, or team dynamics.

The focused format leads to more meaningful insights than trying to cover everything superficially each week. 5/5

[Ilija @stratechgist]

One-on-ones become stale when they follow the same script every week. In my third year as an engineer, our team adopted a rotation of different one-on-one formats that dramatically improved their effectiveness. 1/5

[Ilija @stratechgist]

Here’s how to spice up your one-on-ones:

Propose a monthly "Deep Dive" one-on-one where you select a single topic to explore thoroughly. Prepare by documenting the current state, desired outcome, and specific questions. 4/5

[Ilija @stratechgist]

[A plastic example: "The refactoring I completed this week demonstrates architectural thinking because it separated concerns between the data and presentation layers, something expected at Senior level."]

[Ilija @stratechgist]

After missing a promotion, I realized my mistake after reviewing 6 months of 1-on-1 notes: I focused 95% on immediate technical challenges, neglecting visibility and impact.

My manager knew I solved problems but had little evidence of my broader contributions.

[Ilija @stratechgist]

Here’s how to avoid making the same mistake as me:

Create a "Growth Evidence" document mapping your recent work to your desired level's requirements. Each week, add concrete examples and share one during your one-on-one.