🔸Unpacking Software Architecture

I help people deploy more value with less code.

Mike Thornton

CTO | Author of Engineering Leadership newsletter (65k+ subscribers) - Helping you become a great engineering leader!

I am an engineering leader with a passion for solving complicated problems with innovative concepts. I love learning about new technologies, sharing my knowledge and teaching others. 

I have a proven record of successfully managing Agile teams, setting the correct direction and culture as well as creating right processes and continuously improving them. I have overseen hiring and building up the teams as well as have strong emphasis on coaching and mentoring to direct reports.

You can reach me at info@gregorojstersek.com.

Gregor Ojstersek

In today’s AI era, being a great engineer is no longer defined by your individual contribution alone.

Being a great engineer is defined by the ability to make others around you better, to deliver projects successfully, and to create impact that moves the whole organization forward.

There are many ways to multiply your efforts:
- making your whole team better,
- to work well across different teams,
- be a multiplier through systems,
- multiply and scale through people.

These are all archetypes of multipliers, where each provides immense impact in its own specific way.

Learn more in this Engineering Leadership article: https://lnkd.in/eDyTMzes

CTO | Founder of Engineering Leadership newsletter (180k+ subscribers) - Helping you become a great engineering leader!

This is what happens when you do 10k lines of code per day with AI :)

Happy Friday and have a good weekend!

The speed of writing code has never been an issue.

You can write 10,000 or 20,000 lines of code, but if you are building the wrong thing for the user, it means nothing.

Once you know you’re building the right things, then you can bring in AI tools to speed up the delivery.

This is far more important than just typing faster or producing more code.

While most teams are bragging about how fast they ship code, your focus should be somewhere else:

Focus on building the right things, first.

Then, use technology to accelerate the rate at which you produce new value.

That's how you win in tech in 2026.

What makes a great engineer in the AI-era?

As tools for development got better, the desired skills for engineers have moved from just pure knowing programming languages and frameworks (expected) to problem-solving abilities and people skills.

It's less about the tasks, but how big an impact you can create.

And engineers who can create the biggest impact have the multiplier mindset.

It's the mindset where you focus less on just your pure individual tasks, but you focus on how you can make things better for your whole team, organization, and, of course, the customers (users).

Learn more in this Engineering Leadership article: https://lnkd.in/ezWydu8T

As an engineer, I didn't properly use 1:1 meetings with my manager.

I didn't use my 1:1 meetings for my career growth, instead, I used them to give a status update.

I was missing out on so many different learning opportunities, which I could use the 1:1 meeting for:
- I could talk about career goals,
- work through plans for the promotion or
- ask for specific coaching and feedback situations.

Lesson learned: 
It’s a lot better to use 1:1 meetings to help you be successful in your role and with your overall career growth.

P.S. To learn more -> join engineers and leads from Meta, Google, IBM, Revolut in my cohort-based course here: https://lnkd.in/exsYfM54 (24 hours left to sign up!).

Meetings don’t create alignment. Decisions do.

If no one leaves the room knowing:
- what was decided
- who owns it
- what happens next

It wasn’t a meeting, it was a calendar placeholder.

Make sure to respect people’s time.

End meetings with decisions, or don’t have them at all.

Learn how to create meetings that engineers will love in this Engineering Leadership article: https://lnkd.in/ekZcdgGu

“My work speaks for itself”

Assuming that everyone knows that you are doing good work is in most cases, going to be a wrong assumption.

There are 2 things I like to say.

1. You can do the best work in the world, but if the expectations are not managed correctly, it will not be perceived that way.

2. Doing great work is only half of the work, making sure that everyone knows about it is the other half. You need to do both.

Learn how to build a successful engineer <> manager relationship in the latest Engineering Leadership article that we did together with Shehab Abdel-Salam here: https://lnkd.in/dhJ4qAyD

Coinbase scaled their hiring to 150 engineers per month over the pandemic.

How did they do it?

1. They standardized the searches

Previously, for every new hire, it would be required to draft a “job spec”. With standardization, you could only hire a frontend engineer, a backend engineer, a crypto engineer, an infra engineer, or an ML engineer (and a few others).

2. They moved from hiring in SF only to nationwide

And later to 10+ countries. This resulted in a massive increase in talent pool size.

3. Interviewing became centralized

Candidates weren't screened by their future hiring manager or peers anymore, but rather by any Coinbase engineer. This massively opened up the interviewer capacity.

4. From hiring manager round-ups to centralized hiring panels

Each day with a rotation, one Coinbase leader would host a hiring panel (with 5-6 senior managers), where all the interview packets feedbacks were reviewed and decided which ones would move to offer and which ones would be rejected.

This gave them the ability to process 40-50 candidates at the pre-offer stage a day.

5. The offers became standardized and non-negotiable

No back and forth with the candidate. Both base salary and equity were directly related to the level you would be hired in, no exceptions allowed.

To learn more, make sure to not miss tomorrow's Engineering Leadership newsletter.

Luca Bonmassar, Former VP of Engineering at Coinbase, is sharing a lot of interesting insights on how they scaled hiring.

To not miss tomorrow's article, make sure to join 180k+ engineering leaders here: https://lnkd.in/eNSKBMUf

Structure stories with CARL instead of STAR for a behavioral interview.

This is what Austen McDonald recommends, and here is his reasoning.

CARL stands for:
Context: The background of what was happening and why it mattered
Actions: The specific steps you took (plural, not singular)
Results: What changed and the impact you made
Learnings: What you learned or would do differently

The key difference is that CARL combines Situation and Task into Context, eliminating the mental energy wasted trying to separate them.

And it adds Learnings, which gives you a platform to demonstrate the depth of wisdom that separates senior engineers from less experienced ones.

Learn all about how to nail behavioral interviews in the latest Engineering Leadership article: https://lnkd.in/eN5qJy7g

taplio

The Battle

Mike Thornton

Gregor Ojstersek

Followers

Posts

Engagements

Likes

Performance ScoreGregor Ojstersek's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Mike Thornton

Gregor Ojstersek

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Gregor Ojstersek's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreGregor Ojstersek's LinkedIn Performance