Aydin Mokhtary Professional IT

Senior BA · Requirements · Banking IT

IT Business Analysis · Requirements Engineering · Integration From requirement to stable operations.

Get in touch Book a meeting

IT business analysis for regulated enterprises and projects with complex software landscapes: technical depth, requirements engineering and stakeholder steering in one, so enterprise requirements translate into robust solutions and stable operations.

Fewer surprises after go-live: commitments and models that hold in delivery and operations.

  • Business & IT · shared language and robust requirements so acceptance stays testable.
  • Scope & acceptance · clear scope and tests before time pressure takes over interpretation.
  • Interfaces · APIs and data flows described so build and operations use the same track.
  • Handover & operations · support release until what was delivered works in daily operations, not only on paper.

Skills

Methods, technology, languages

  • Technology

    Application engineering · Java (SE), Spring (MVC, JDBC), REST APIs, Python, SQL, data models · Web · JavaScript (ES6), Node.js, Vue.js, Astro, HTML5, CSS3 · Cloud & operations · Azure AD, Microsoft 365 · monitoring and support of production systems · IntelliJ, Eclipse, VS Code

  • Business & delivery

    Business analysis & requirements engineering · process analysis (BPMN, use cases, user stories) · IT service management (ITIL), change/incident/problem · UAT, governance & audit · stakeholder & cross-team · agile (Scrum/SAFe) · escalation & prioritisation

  • Languages

    German · negotiation level (C2) · English · professional (C1) · Persian · native · French · basic (A2)

Roles & contexts

How clarity enters complex projects

  1. Business Analysis · Platforms

    Market and reference data under regulatory logic

    Ownership of central data platforms · data quality and traceable integration into application landscapes · migration and evolution of large market-data environments · change and performance management across many applications · ServiceNow and regulatory context · at an international wholesale bank.

  2. Freelance · Dev & IT

    Projects between delivery and operations

    Web and data-driven applications · specification, implementation and documented handovers in smaller mandates · later focus on IT service and support in production environments including 2nd/3rd level · Java and SQL for reporting and operational analysis · support for integrations and data validation between systems · change requests, escalations and improvement of technical workflows · including for financial services clients.

Thoughts from practice

What really derails projects.

  • Requirements

    Why requirements fail without decisions.

    Three typical patterns when specification does not become a binding decision, with a direct line to rework, acceptance and auditability.

    Kontext zur Karte ein- oder ausblenden
    • Missing owner and deadline: requirements stay open to interpretation; acceptance becomes negotiable instead of testable.
    • Contradictions in the business picture remain unresolved until delivery forces priority; then adjustments happen under time pressure.
    • Traceability breaks: changes and accountability are hard to prove; audit and regression risk rise first.

  • Business × IT

    The bridge few people build.

    A shared picture of goals, boundaries and priorities reduces rework cost and stabilises releases, instead of financing the same misunderstandings in every sprint.

    Kontext zur Karte ein- oder ausblenden
    • Silent assumptions can be defused once terms and models are consolidated between business and IT.
    • Less rework after business review, clearer escalation on conflicts: delivery gains speed and predictability.
    • Knowledge carriers change; documented decisions preserve context even when people or vendors rotate.

  • Provider steering

    Mistakes that really hurt mid-market companies.

    Three classic steering gaps between contract, delivery and operations, regardless of industry and toolchain.

    Kontext zur Karte ein- oder ausblenden
    • Target and actual diverge: scope in the backlog and service definition in the contract do not align; change orders without solid documentation become expensive.
    • Interface responsibility ends at project closure: in live operations grey areas remain; incidents accumulate after the handover workshop.
    • Go-live without hard acceptance criteria: escalation often starts only at visible damage; budget and reputation risk jump.

  • AI projects

    Why AI projects rarely fail on technology.

    Three non-technical bottlenecks that stop AI in practice sooner than any model architecture.

    Kontext zur Karte ein- oder ausblenden
    • Data basis unclear: quality, access, history. Demo and model run; the production path often does not.
    • The process does not carry the use case: SLAs, responsibilities and rework are not wired; island solution instead of leverage in daily work.
    • Roles, approvals, compliance: without an operational rulebook the pilot loses ground after the showcase, not because of the GPU.

C-LEVEL & STAKEHOLDER MANAGEMENT

The bridge between deep tech and board level.

Complex IT projects rarely fail on technology; they fail on missing translation. I connect deep technical expertise with strategic perspective. With experience working directly with executive stakeholders, C-level interfaces and cross-functional decision makers, I translate complex architectures into clear, measurable business decisions and reduce risk for stakeholders at every level.

  • Strategic translation · From code to decision paper: 100% aligned with business goals.
  • Expectation management · Transparent communication and realistic roadmaps that eliminate surprises at C-level.
  • Crisis-proof orchestration · Effective mediation between IT teams, business units and executive management.
  • DORA & compliance focus · Stakeholder reporting that meets the highest regulatory and security standards.

Contact

Let's clarify the context.

I'm open to a structured conversation around freelance work, project roles or recruiting context.

  • Direct exchange
  • Treated confidentially

Treated confidentially. No forwarding. No newsletter.

Terminwahl

Ein Slot für das Erstgespräch: Standard ist Google Meet (Link in der Google-Bestätigung). Telefon geht nach den Hinweisen auf der Buchungsseite — oder per kontakt@mokhtary.de bzw. Kontaktformular.