EMILIANO PISHAJ / PRACTICE

Practice and approach

Rather than presenting fictional case studies, I explain how I approach technical decisions. Approved examples may be added later.

Understand

Clarify objectives, stakeholders, dependencies and risks.

Decide

Evaluate options with transparent criteria.

Deliver

Work iteratively with feedback and quality gates.

Selected professional experience

These examples describe documented professional responsibilities, not customer testimonials or independently audited performance results.

Technology leadership and cloud modernization

Context

Technology advisory engagement in an international business environment, 2021–2022.

Responsibilities and contributions

Interim CTO responsibilities, technical leadership across four engineering teams, cloud migration, information security and API platform initiatives.

Evidence and limits

Grounded in a written professional reference. Customer metrics and detailed architecture information are excluded pending approval.

Engineering leadership and Java platform quality

Context

Java chapter in a software-intensive organization, 2025–2026.

Responsibilities and contributions

Technical and line management for approximately 22 engineers, architecture, engineering quality, DevSecOps, standards and people development.

Evidence and limits

Responsibilities documented in an employment reference. Internal project details remain confidential.

AI platform and international engineering collaboration

Context

Engineering management in an international education business, 2022–2025.

Responsibilities and contributions

Engineering-team leadership, architecture and system design, code reviews and technical advisory across functions.

Evidence and limits

Drawn from professional records and an employer reference. No unverified business impact figures are presented.

These are summaries of professional experience, not published original references. Customer logos, direct quotes and success metrics require separate permission.