From Microcontrollers to Mobile: How Ilia Gutu (Genetec) turns challenges into momentum, thinks hybrid, and urges us to start now

Introduction: What we heard in “Ilia Gutu, Mobile Developer at Genetec”

Every so often, a short session captures an entire engineering mindset. In “Ilia Gutu, Mobile Developer at Genetec,” Speaker: Ilia Gutu (Company: Genetec) shares a compact, yet vivid arc: tinkering with Delphi as a teenager, taking on the hard edges of electronics and microcontrollers in automotive, freelancing to broaden horizons, and then embracing responsibility for bringing Android and iOS apps to life—ideally from one codebase.

As the DevJobs.at editorial team, we were struck by a simple throughline: a love of challenge, backed by pragmatic action. Gutu doesn’t romanticize the journey. He states it plainly: he gets bored without challenges, he prefers iOS yet is exploring hybrid development to ship from a single codebase, and he believes the path to experience is to stop waiting and start building. Around that core belief, he’s built everyday learning habits—reading, watching conferences, and listening to content even while biking or walking. The result is a mindset that many engineers will recognize: curiosity, scale-aware thinking, and the courage to move.

The early spark: Delphi, tricks, and learning by doing at 16

Ilia Gutu started programming at age 16. One of his first books was about Delphi, and his experiments explored how to do “tricks” with the computer using that language. That beginning matters because it signals three durable patterns:

• Curiosity as a driver: Don’t wait for a perfect course or project—try what you can do today.
• Practice-first learning: Learn by building, not by theory in isolation.
• Systems thinking through tinkering: Making “tricks” work forces you to understand how things behave under the hood.

From our vantage point, this phase is the seed of everything that follows. Motivation doesn’t always come from grand plans; it often starts with small, tangible experiments that train the mind to deconstruct and reassemble systems.

The hard school of electronics: Microcontrollers and automotive

After graduating in electronics, Gutu worked in electronics development, programming microcontrollers, including in the automotive area. He calls it one of his “biggest and hardest programming experiences.” That line tells us a lot:

• Tight constraints: Embedded and automotive software impose strict resource limits, timing precision, and rigorous quality requirements.
• Hardware proximity: Programming microcontrollers demands awareness of system behavior down to registers and peripherals.
• A serious error culture: Bugs here have real-world impact, shaping a disciplined approach to building.

We see that discipline carry over into mobile. If you’ve built under constraints and with high stakes, you bring exactly the kind of rigor modern apps need—stability across devices, thoughtful performance, and careful power usage.

Freelancing and the intentional pivot to mobile

After a freelancing period, Gutu realized he wanted something different from hardware and tried mobile development. His first experience here was on Android. The move is telling:

• Adjust the path when the work you’re doing no longer matches what you want.
• Transfer the deeper skills—system thinking, debugging rigor, quality mindset—into a new domain.
• Expand step by step: Start somewhere concrete (Android), then broaden the scope.

The pattern we observe is challenge-seeking without chaos. He takes on new terrain deliberately, building on what he already knows while staying open to where it leads next.

Responsibility across platforms: “Bringing all mobile platforms to life”

Gutu says he’s responsible for “bringing all the mobile platforms to life,” releasing Android and iOS apps at the same time. That phrasing is important:

• Parallel platform ownership: Coordinating feature parity, releases, quality expectations across both ecosystems.
• Product thinking: “Bring to life” implies more than writing code—it’s about usability, stability, performance, and a path to production.
• Process maturity: Two platforms mean doubled integration, testing, and store workflows—under tight time constraints.

For teams in similar situations, the friction points are familiar. What stands out is that Gutu embraces them as his chosen arena.

“I like challenges”: Why a unified codebase is compelling

Gutu makes it clear: he loves challenges and gets bored without them. One challenge that motivates him is the idea of “one code base working for everything.” In practice that means:

• A target architecture for shared logic, with platform-specific layers where necessary.
• Consistency in behavior and quality across platforms, driven by shared abstractions.
• A realism check: a shared core doesn’t erase platform differences; it requires careful boundaries and thoughtful APIs.

From an editorial perspective, this is a hallmark of engineers who blend product and architecture: the challenge isn’t for its own sake, but as a lever for speed, quality, and maintainability.

Preference meets pragmatism: iOS affinity and a hybrid outlook

Gutu states that iOS is his favorite technology. At the same time, he’s “looking into hybrid development” to write one codebase for all his apps. The tension here is productive:

• Keep your strengths: Lean into the platform you love and know well.
• Expand the toolbox: Explore hybrid approaches when they can reduce duplication.
• Architecture before framework: Design the shared core and boundaries first; tools serve the design, not the other way around.

Practically, this means you can think cross-platform without compromising platform quality—if you invest in the right abstractions, tests, and interfaces.

“Don’t wait—start doing something”: A clear stance on learning and growth

One of Gutu’s strongest points is about getting started:

We read that as a three-part playbook:

• Momentum over perfection: The longer you wait, the more you lose. The sooner you start, the faster you learn.
• Abundant resources: Unlike a decade ago, access is rarely the blocker; action is.
• Practice creates experience: Reading is useful, but building is what compounds into expertise.

It’s a message we’ve seen drive many careers forward: do one small thing today. The rest follows.

“Think in scale”: Anticipate growth from the outset

Gutu also urges engineers to “think in scale.” Specifically:

• Anticipate the next feature: How will your codebase absorb it?
• Draw structural boundaries: Which pieces should be reusable, testable, and replaceable?
• Grow with intent: Even an MVP can be designed with later expansion in mind.

Here’s how we translate that into practice:

• Lean on clean abstractions: Separate domain logic from UI and platform-specific concerns.
• Invest in tests: Safety nets let you move fast without breaking what matters.
• Treat releases as part of architecture: Versioning and feature management are structural concerns—especially across platforms.

“It’s not about specific skills—it’s about your attitude and wishes”

Gutu emphasizes attitude over any particular skill list. That implies:

• A learning posture: Keep moving, stay curious, and set up routines that make learning habitual.
• Responsibility: Quality isn’t optional when your software enters the real world.
• Challenge-seeking: Lean into hard problems as the fastest path to growth.

Skills matter. But attitude determines how quickly you acquire them, how you handle setbacks, and how consistently you deliver over time.

Observe, read, listen: Everyday learning in motion

Gutu keeps himself up to date by reading a lot and watching conferences—and he’s “always listening to something,” even when biking or walking. He subscribes widely to stay on top of trends. One detail stands out: his bookmarks are “really full,” around 1,000 items. He doesn’t read everything immediately, but he keeps links for the future—“something in my pocket when it comes to this situation.”

We see three simple, effective habits here:

• Continuous micro-learning: Use in-between moments for audio and short-form content.
• A curated archive: Bookmarks as a personal knowledge base—ready when needed.
• A trend radar: Subscriptions as signal filters to spot shifts early.

These habits translate curiosity into a repeatable system.

Actionable takeaways for engineers

From Ilia Gutu’s story, we extract concrete moves you can apply today:

1. Start today

• Pick a mini-project: a small app feature, a prototype, a refactoring experiment.
• Commit to one focused hour—no perfectionism.
• Log what you learned: brief notes, commit messages, a lightweight journal.

1. Think in scale—even in small steps

• Separate logic from UI and platform specifics early.
• Ask: If feature X lands tomorrow, what breaks? Where do we need an interface?
• Write a single test for the most critical logic. One test is infinitely better than zero.

1. Structure hybrid code with intent

• Identify what can be shared (e.g., data models, business logic) and what must remain platform-native.
• Embrace platform differences instead of hiding them.
• Create clear seams between shared and platform-specific layers.

1. Build a learning routine

• Use commute or walking time for audio or short conference clips.
• Create a bookmark system: topical tags, quick notes, periodic reviews.
• Reserve a weekly “trend window” to scan the most relevant signals.

1. Nurture attitude

• Treat each hard problem as training for the next one.
• Celebrate small, consistent progress—compounding beats bursts.
• Share learnings with your team: group learning accelerates individual growth.

What inspires us most about Gutu’s path

• Relentless practice: From Delphi experiments to mobile responsibility—always building, not just planning.
• Embedded discipline: Scarcity, precision, and quality mindsets that fortify mobile products.
• Scale-aware architecture: Anticipate features, set boundaries, and build for growth.
• Hybrid as a challenge worth taking: Not a tool-first decision, but an architectural aspiration.
• Everyday learning: Constant inputs, smart knowledge capture, and staying tuned to trends.

These aren’t lofty slogans—they’re working habits. That’s why they stick.

Quotes and lines that stay with us

No theatrics—just substance. A working philosophy for sustainable growth.

Applying this lens to team and product work

While Gutu speaks from his personal perspective, the team and product implications are clear:

• Plan for platform parity: Parallel Android and iOS delivery needs a roadmap that explicitly considers both.
• Build release and quality discipline: Testing, monitoring, and crash analysis matter twice over when you ship twice.
• Turn personal learning into team leverage: Make insights visible and usable across the group.

In hybrid or shared-core contexts, clear ownership, clean seams, and aligned quality metrics are non-negotiable. Gutu’s love of hard problems is well-suited to this reality: architecture has to be chosen, not assumed.

Conclusion: Build, scale, stay curious

“Ilia Gutu, Mobile Developer at Genetec” highlights a mindset we’ve seen power many engineering journeys: start early, practice consistently, think in scale, and weave learning into daily life. Gutu doesn’t promise shortcuts; he models routines and a taste for demanding goals—like a unified codebase across mobile platforms.

If you’re starting out in mobile or realigning your path, the message is simple and strong: start now, think ahead, structure deliberately, and keep your trend radar on. The rest compounds through practice, perseverance, and a genuine love of the challenge.

• 

  

  Stephan Sutor, Product Group Director at Genetec

  Product Group Director bei Genetec Stephan Sutor spricht im Interview über Domain Driven Design und wie dieses Prinzip im Team angewandt wird.

  Watch now
• 

  

  Florian Matusek, Product Group Director at Genetec

  Product Group Director bei Genetec Florian Matusek erzählt im Interview über die Aufgaben des Teams und woher der Spitzname "Wrecking Crew" für die Abteilung kommt.

  Watch now

• 

  

  Moemen Saad, Senior Software Developer at Genetec

  Moemen Saad von Genetec spricht im Interview über seine Anfänge mit C#, was ihm an seiner aktuellen Arbeit am besten gefällt und gibt Tipps für Neueinsteiger.

  Watch now
• 

  

  Rafal Dabek, Back End Developer at Genetec

  Rafal Dabek von Genetec erzählt im Interview wie er zum Programmieren gekommen ist, was das Spannende an seiner aktuellen Arbeit ist und spricht darüber, was seiner Meinung nach wichtig für Beginner ist. Mehr zum Team von Genetec: https://devjobs.at/team/genetec devjobs.at IT Career Days Playlist: https://www.youtube.com/playlist?list=PLxwoARCP1-pStxUV52y__-iN43N8BMJ2P

  Watch now
• 

  

  Spandana Kanadam Ravindranath, Computer Vision Developer at Genetec

  Spandana Kanadam Ravindranath von Genetec redet im Interview über ihre ersten Berührungspunkte mit dem Programmieren, was ihre aktuelle Arbeit als Computer Vision Developer umfasst und gibt Tipps für Leute, die ebenfalls in diesem Berufsfeld starten möchten.

  Watch now