iSAQB Software Architecture Gathering
1. Assuming AI threatens to perform work faster, cheaper, or even better than a person — how do we make ourselves irreplaceable?
In this day and age, we absolutely have a responsibility to make ourselves irreplaceable. But being irreplaceable doesn't mean that nobody else can technically do your job. AI will do many things faster, cheaper, and sometimes better than we can. So becoming irreplaceable means building value in two dimensions.
The first is how good you are at what you do. You need to become excellent at using AI, but also excellent at knowing where not to use it. Where does human judgment matter? Where does context matter? Where do I need to challenge what AI gives me rather than simply accept it? For developers, this becomes particularly important. AI can generate code, suggest solutions, identify bugs, and accelerate development. But someone still needs to understand the architecture, the context, the trade-offs, the risks, and whether the proposed solution actually makes sense.
The second dimension is something professionals often underestimate: It's not enough to create value. Your value needs to be recognized. You need people around you to know what you're good at. You need a reputation. You need relationships. You need people who trust you and would mention your name when an opportunity comes up and you're not in the room. I've worked across many countries and cultures, and I've seen this again and again: opportunities don't necessarily go to the most talented person. Very often, they go to someone who is talented and trusted, visible, and connected.
For a developer, visibility doesn't mean constantly promoting yourself. It can mean contributing an idea in a meeting, explaining why you made a technical decision, helping another team solve a problem, sharing knowledge, or making sure people understand the impact behind something you've built. Leaders have a responsibility here as well. Their job isn't simply to tell employees to adapt to AI. They need to give people opportunities to experiment, develop judgment, build relationships across the organization, and become known for the value they create. AI may make skills more accessible. But trust, reputation, and relationships still have to be earned. That's where our human advantage becomes incredibly valuable — and increasingly irreplaceable.
2. What does personal growth look like in an AI-driven work environment?
AI is creating an interesting paradox. We have more tools to help us grow personally and professionally than at any other point in history, but we also have more pressure to constantly keep up. There's always another tool to learn, another skill becoming obsolete, another way to become faster. And if we're not careful, we can start confusing personal and professional growth with permanent optimization. They're not the same thing.
Personal and professional growth isn't just becoming faster or learning another AI tool. Sometimes growth is becoming a better leader. Becoming more confident. Learning how to have a difficult conversation. Becoming better at asking for help. Learning to negotiate. Understanding yourself better. Becoming someone other people trust. This is where I talk about developing your Human Factor.
The World Economic Forum estimates that 39% of workers' existing skills will be transformed or become outdated by 2030. At the same time, alongside AI and technological literacy, employers continue to place enormous importance on human capabilities such as creative thinking, resilience, leadership, social influence, curiosity, and lifelong learning. That's fascinating because the more technology develops, the more intentional we need to become about developing ourselves.
For developers especially, there can be pressure to constantly learn the next framework, language, platform, or AI tool. Of course, technical learning matters. But your development plan shouldn't stop there. I encourage professionals to have two development plans. One is your technology plan: What do I need to learn to work intelligently with AI and remain excellent at my craft? The second is your human plan: What do I need to develop in myself? Maybe it's confidence. Maybe it's leadership. Maybe it's relationships. Maybe it's communication, curiosity, negotiation, or courage.
And that's where purpose and happiness come into the conversation. If all AI does is help me produce 30% more work, I'm not sure that's personal growth. The better question is: What am I able to do now that I couldn't do before? What am I learning? How am I contributing? And who am I becoming in the process? Growth is when technology expands what I can do while I continue expanding who I am.
3. Should there be guardrails for professional branding? And what about impostor syndrome?
We have completely misunderstood personal branding. Most people think personal branding means adding something or showing up as someone else. It actually starts by removing the things that aren't you. A professional brand isn't a performance. It's the process of identifying the value that already exists and making it easier for other people to recognize it.
I often ask people: What do people consistently come to you for? What do you do unusually well? What part of your personality improves the way you work? What experiences have given you a perspective other people around you don't have? And perhaps most importantly: What do you want your name to mean when you are not in the room? Because that's really your brand. It's not your LinkedIn page. It's the association living in someone else's mind.
For a developer, maybe you're the person people call when there's a complicated production issue. Maybe you're known for simplifying complex systems. Maybe you ask the question nobody else thought to ask. Maybe you're the person who can explain something highly technical in a way that product, sales, or a client can understand. Those things are part of your brand. If someone hears your name and immediately associates you with a certain expertise, strength, or value — that's brand.
The guardrail against becoming fake is simple: Don't communicate aspiration as accomplishment. You can say what you're becoming. You can say where you're going. But don't manufacture evidence that doesn't exist.
And impostor syndrome can be viewed slightly differently too. Sometimes feeling like an impostor doesn't mean you're in the wrong room. It means you've entered a room your identity hasn't caught up with yet. You've grown professionally faster than your internal image of yourself. There can actually be something valuable in that discomfort. It can keep us humble. It makes us check ourselves twice. It encourages us to ask whether what we're saying and doing is right and whether we have the knowledge to support it. So instead of allowing impostor syndrome to become a force that holds us back, we can use it as a force for growth. Ask yourself: Is there genuinely something I don't know yet? Then learn it. Or am I simply uncomfortable because I'm operating at a new level? Then give yourself time to grow into it.
4. How does strategic relationship building relate to personal sympathy? Is superficiality ever good advice?
This is one of the biggest misconceptions about networking. Strategic relationship building is not the opposite of authenticity. Manipulation is. Human beings have always progressed through relationships. Long before we called it networking, communities exchanged knowledge, resources, opportunities, protection, and support. And almost every meaningful relationship has some form of intention, which can also be called strategy.
An intention to learn something. To create something. To solve something. To achieve something together. A shared intention is at the heart of many relationships. We seek mentors because we want to learn. We approach a potential client because we believe we can help them. We connect with someone because we find them interesting. Having an intention doesn't make a relationship fake. What makes it fake is pretending your intention is something else. To me, authenticity means alignment between what I think, what I say, and what I do. So yes, I can strategically decide that I would like to know someone. But once I meet them, I still need to see a human being rather than an objective.
And one of the simplest lessons I've learned about likability is this: If you want people to like you, show them that you like them first. Show interest first. Say hello first. Ask the question. Show respect. When I was younger, I used to wait for other people to give me a signal that they liked me. Eventually, I realized that when I gave that signal first, people relaxed and opened up. That's not a networking trick. It's human permission.
This matters for developers too. Relationship building doesn't mean becoming the most social person in the room or spending your evenings at networking events. It can be as simple as building relationships with product, design, QA, sales, customer success, or another engineering team. Ask what they're working on. Understand what makes their job difficult. Share what you're learning. Help when you can. And not every professional relationship has to become a deep friendship. Some relationships are naturally lighter. Some are professional. Some are based on one shared interest or purpose. A relationship can be light without being fake. That's very different from superficiality.
5. What does it mean for a developer to become a strategic partner rather than a strong executor?
The difference is very simple: An executor understands the task. A strategic partner understands the consequence of the task. A developer may receive a request to build a feature. The technical question is: "How should we build it?" But the strategic questions are: Why does the customer need it? What problem are we actually solving? What happens if we don't build it? Does it affect revenue, retention, cost, customer experience, or risk? What assumption are we making? Could there be a simpler solution? That's when technical expertise starts becoming business influence.
Developers don't need to become salespeople or sacrifice their technical depth. Actually, the opposite. Context makes technical expertise more powerful. If I understand the customer's pain, I may architect something differently. If I understand the company's business model, I may challenge a feature that takes six months to develop but generates very little value. If I understand what sales or customer success is hearing from customers, I may identify an opportunity or problem before it ever reaches the product roadmap.
And this doesn't require turning your calendar into meetings. Start small. Once a month, talk to someone outside engineering. Sit in on a customer conversation occasionally. When product asks for a feature, don't only ask for the requirements. Ask what problem sits behind them. And whenever you're given a significant task, ask one extra question: "What business outcome are we trying to change?" You don't need an MBA. You need curiosity beyond your own function.
That curiosity makes you a better developer because you're making technical decisions with more context. It also changes how people see you inside the organization. Eventually, people stop saying: "She's a great developer." And start saying: "Bring her into the conversation. She understands the business." And that sentence is often the beginning of leadership.
Explore the full SAG 2026 program and secure your ticket for Berlin.
You need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from Turnstile to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Turnstile. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Vimeo. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Google Maps. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information