Every Product Solves a Different Problem.Every Project Teaches a Different Lesson.
Over the last thirteen years I've had the opportunity to build software across global consumer products, fintech, startups, and educational platforms.
Different industries. Different architectures. Different engineering challenges.
The common denominator has always been the same: building products that people genuinely use.
McDonald's
Senior iOS EngineerMcDonald's serves millions of users across multiple countries every day. Building software at this scale requires engineering discipline. Every release affects real customers. Every performance optimization matters. Every bug has consequences. Working on this project significantly changed how I think about production software.
- Feature development
- Production bug fixing
- Architecture discussions
- Code reviews
- Cross-team collaboration
- Performance improvements
FIFA World Cup 2022 Campaign
One of my biggest responsibilities was implementing campaign-specific experiences during the FIFA World Cup. The challenge wasn't simply displaying promotional content. The implementation needed to support dynamic marketing requirements while maintaining application stability and performance. Another interesting engineering challenge involved RTL (Right-to-Left) layout support. Building truly global products requires thinking beyond your own language and culture.
Large-scale products reward consistency. Processes matter. Testing matters. Code quality matters. Small mistakes become very expensive at scale.
Being part of an engineering team building software used by more than one hundred million users worldwide.
ABB Mobile
iOS Chapter LeadJoining ABB wasn't simply about building another banking application. It was an opportunity to help build the engineering organization itself. This meant defining standards rather than simply following them.
- Building the iOS team
- Technical leadership
- Architecture
- Hiring
- Mentoring
- Code reviews
- Engineering culture
- Collaboration across departments
Creating a Sustainable Engineering Culture
Instead of optimizing only for delivery speed, we focused on building long-term engineering quality. Documentation. Code review. Architecture. Knowledge sharing. Mentorship. These systems continue creating value long after individual features are released.
Leadership scales impact. Helping ten engineers become better creates far greater value than writing ten times more code yourself.
Building an engineering team from the ground up and helping shape one of Azerbaijan's leading mobile banking products.
Birbank Business
iOS Chapter LeadBusiness banking introduces significantly more complexity than consumer banking. Multi-user permissions. Approval workflows. Corporate accounts. Financial operations. Every interaction requires precision.
- Technical leadership
- Architecture
- Mentoring
- Hiring
- Engineering standards
- Cross-functional collaboration
- Strategic technical decisions
Balancing UX With Complex Financial Workflows
Many engineering decisions required understanding business logic before writing code. Transforming complex business requirements into intuitive mobile experiences without sacrificing security or maintainability was the central engineering challenge. This project strengthened my ability to connect engineering with business strategy.
Architecture becomes increasingly valuable as products evolve. Engineering is about making tomorrow's work easier — not just today's.
Building an outstanding engineering team while helping deliver a modern business banking experience.
Borderless eSIM
Founder · Product Builder · iOS EngineerBorderless wasn't created because I wanted to build another mobile application. It was created because I experienced a real problem. International travelers still struggle with expensive roaming, physical SIM cards, and confusing activation processes. Unlike my previous enterprise projects, there was no existing engineering team, documentation, or internal knowledge. Everything had to be learned, validated, and built from scratch.
- Product Strategy
- UX Design Decisions
- iOS Development
- Architecture
- API Integration
- eSIM Technology Research
- Provider Evaluation
- Product Roadmap
- Feature Prioritization
- App Store Release
Learning an Entire Industry From Scratch
The biggest challenge wasn't technical implementation. It was understanding an entirely new industry. Unlike mobile development, eSIM technology isn't widely documented. Learning required reading specifications, comparing providers, understanding activation flows, researching APIs, and performing countless real-world tests. Many answers simply didn't exist online. Instead of searching for tutorials, I had to understand how the entire ecosystem worked. The code became the easy part. Understanding the system was the real challenge.
Strong engineering fundamentals transfer across industries. You don't need previous domain knowledge to solve difficult problems. You need curiosity, systems thinking, persistence, and the willingness to learn continuously.
Building Borderless together with my co-founder despite having zero previous experience in the eSIM industry. Proving that engineering is ultimately the ability to understand complex systems — not memorizing technologies.
The AI-Powered iOS Engineering Framework
Creator · Author · EducatorAfter years of mentoring developers, leading engineering teams, and observing how Artificial Intelligence is changing software development, I noticed an important gap. Most AI education focuses on prompts. Very little focuses on engineering. Developers don't need another list of ChatGPT tricks. They need a complete engineering workflow.
I wanted to create the resource I wish had existed years ago. One place that combines engineering thinking, Swift, SwiftUI, Architecture, AI, Prompt Engineering, Debugging, Code Reviews, and real-world workflows. Instead of isolated lessons, everything follows one connected engineering process.
- Built by an engineer — not an AI influencer.
- Every lesson comes from production experience.
- Emphasizes thinking before prompting.
- Understanding before generating.
- Reviewing before accepting.
- Engineering before automation.
Teaching is another form of engineering. Designing a learning system requires the same systems thinking, architecture decisions, and long-term planning as designing software.
The Same Principles Across Every Project.
Although every project is different, the engineering process remains remarkably similar. Every successful product starts with understanding the problem — not choosing a framework, not choosing a programming language, not writing code.
Understand Before Building
Spend more time understanding the problem than implementing the solution. Questions are more valuable than assumptions.
Simplicity Scales
Simple architectures survive longer. Simple APIs are easier to maintain. Simple user experiences create happier users. Complexity should only exist when it creates real value.
Build for the Future
Every architectural decision should make future development easier. Avoid solving today's problem by creating tomorrow's technical debt.
AI Supports Engineering
Artificial Intelligence should remove repetitive work. It should never replace engineering judgment. The engineer remains responsible for every decision.
Continuous Improvement
Every project should leave the codebase — and the engineering team — in a better state than before. Improvement compounds over time.
Projects Have Taught Me...
- McDonald'staught me scale.
- ABB Mobiletaught me leadership.
- Birbank Businesstaught me organizational thinking.
- Borderless eSIMtaught me entrepreneurship.
- The AI-Powered iOS Engineering Frameworktaught me that teaching is another form of engineering.
Together, these experiences shaped how I think, build, and lead today.
Interested in seeing how I approach engineering?
Explore the AI-Powered iOS Engineering Framework, discover my engineering journey, or get in touch to discuss technical leadership, speaking opportunities, or product collaboration.