Martin Landa Software Engineering Manager

Engineering management

Leadership for enterprise work that is messy before it is measurable.

The value is not heroic certainty. It is turning fuzzy AI, product, and quality work into clear next decisions, explicit ownership, and evidence people can trust before decisions get expensive.

Back to the route map
01

Ambiguity

Separate product unknowns, quality risk, and ownership gaps before the team spends weeks optimizing the wrong thing.

02

Scope

Turn broad AI, reporting, or platform work into smaller commitments with visible evidence and exit criteria.

03

Clarity

Make the next useful decision inspectable: who decides, what proof is needed, and what risk remains.

04

Ownership

Make stewardship explicit: who owns the outcome, who executes the work, and who follows external dependencies.

05

Delivery

Protect team flow with useful constraints, feedback loops, and calm escalation when trade-offs become real.

06

Lower Risk

Lower surprise by making quality, operational load, and stakeholder expectations visible before release pressure peaks.

Where I help

I am useful where teams have capable people but unclear routing: AI feature uncertainty, cross-team dependencies, late quality risk, stakeholder proof needs, or fuzzy decision rights.

  • Translate ambiguous initiatives into small, reviewable commitments.
  • Create ownership models that survive vacations, incidents, and shifting priorities.
  • Make delivery and quality risk discussable before it becomes an emergency.

How I lead

I prefer operating clarity over performative urgency. People should know what matters, what does not, where to escalate, and what trade-off they are being asked to make.

  • Adult-adult communication with explicit expectations.
  • Evidence over impressions when evaluating progress or performance.
  • Psychological safety that helps people surface risk without removing responsibility.

What the evidence supports

Recent evidence is strongest around Oracle/NetSuite work: AI-enabled product delivery, quality strategy, reporting modernization, search/indexing validation, and team operating models.

  • Strong public positioning: Senior engineering manager direction in AI-enabled enterprise software and quality systems.
  • Keep older career claims conservative until older-role artifacts are found.
  • Avoid Director-level or company-wide impact claims until span, mandate, and outcome metrics are confirmed.