I'm Ali Aslani
I’m a software engineer who enjoys turning complex problems into simple, maintainable, and scalable software.
My strongest focus is backend engineering and software architecture, while I’m comfortable working across the full stack—from APIs, databases, and distributed systems to modern frontend applications and deployment pipelines.
I care about more than just making software work.
I care about why it works, how it scales, how it can be maintained, and how developers can build on it tomorrow.
love(Space, music, code, truth, fun);
- 🎓 M.Sc. in Computer Engineering — Information Technology
- 💻 Software Engineer with 5+ years of hands-on development experience
- 🏗️ Strong focus on Backend Engineering & Software Architecture
- 🌐 Full-stack experience building real-world web applications
- ⚙️ Experienced with .NET / ASP.NET Core, Node.js, JavaScript & TypeScript
- 🗄️ Comfortable designing and working with relational databases and APIs
- ⚛️ Experience with modern frontend development, especially React
- 🐳 Interested in DevOps, CI/CD, Linux, Docker and cloud infrastructure
- 🤖 Building automation systems, Telegram bots and AI-powered applications
- 🔬 Constantly exploring software architecture, developer tooling and emerging technologies
- 📚 I enjoy learning, teaching, documenting, and sharing what I discover
I particularly enjoy building:
- RESTful APIs
- Business-oriented backend systems
- Authentication & authorization systems
- Background services and workers
- Integration services
- Automation platforms
- Data-intensive applications
- Modular and maintainable architectures
Although backend engineering is my primary direction, I believe a good backend engineer should understand the entire product.
That means understanding:
Browser → Frontend → API → Business Logic → Database → Infrastructure
rather than treating the backend as an isolated box.
I enjoy database design, query optimization, data modeling, and understanding how application architecture affects database performance.
I'm particularly interested in the space where software engineering meets infrastructure:
- CI/CD
- containerization
- Linux servers
- reverse proxies
- deployment automation
- cloud infrastructure
- observability
- reliable production systems
I'm especially interested in:
Software Architecture
↓
Backend Engineering
↓
Distributed & Scalable Systems
↓
APIs & Integrations
↓
Databases & Data
↓
Automation
↓
AI-powered Software
↓
DevOps & Infrastructure
Some areas I'm continuously exploring:
- Clean Architecture
- Domain-Driven Design
- SOLID principles
- Modular monoliths
- Microservices
- Distributed systems
- Event-driven architecture
- API design
- Performance engineering
- Software testing
- Developer experience
- AI-assisted development
- LLM applications & agents
- Automation
One of the things I enjoy most is taking a repetitive process and asking:
"Why are we doing this manually?"
I've built and experimented with systems involving:
- Telegram bots
- Web scraping
- automated content processing
- notification systems
- API integrations
- scheduled jobs
- GitHub Actions
- serverless workflows
- AI-powered assistants
- LLM integrations
I like automation because it sits at the intersection of software engineering, problem solving, and creativity.
A few things I've built or worked on:
A system for verifying financial transactions and automating transaction-related workflows.
Technologies: APIs · Automation · Telegram · Backend Services
A collection of automation projects involving Telegram bots, channel monitoring, message processing, scraping, forwarding and notification workflows.
Technologies: Node.js · Python · Telegram API · GitHub Actions · Cloudflare Workers
I also enjoy building software around Persian-language data and developer tooling—from Persian text processing to projects involving Iranian platforms and localized software experiences.
Not every project needs to become a startup.
Some projects exist simply because I had a question:
"Can I build this?"
Those experiments have led me into areas such as:
- AI
- LLMs
- cryptography
- networking
- cloud infrastructure
- automation
- browser extensions
- data processing
- developer tools
Some become products.
Some become libraries.
Some become lessons.
All of them teach me something.
I believe one of the best ways to understand something deeply is to try explaining it to someone else.
I've worked on educational and mentoring initiatives around programming and software development, with an emphasis on:
- practical programming
- project-based learning
- backend development
- frontend development
- full-stack engineering
- preparing developers for real-world software jobs
I occasionally write about things I've learned while building software.
Topics I'm particularly interested in:
- Backend development
- .NET
- JavaScript
- React
- Software architecture
- Clean code
- Performance
- Databases
- DevOps
- AI & LLMs
- Developer productivity
I prefer writing about things I've actually encountered while building, rather than simply repeating documentation.
I'm currently interested in opportunities where I can work on serious backend and software-engineering problems.
I'm particularly excited by teams that care about:
- engineering quality
- scalable architecture
- clean and maintainable code
- developer experience
- automation
- technical ownership
- continuous learning
My long-term goal is to become the kind of engineer who can move comfortably between:
code → architecture → infrastructure → product
and understand the trade-offs at every level.
If you're interested in software engineering, backend development, architecture, automation, AI, or just building interesting things, feel free to reach out.
- 💼 LinkedIn: linkedin.com/in/aliaslanik
- 🐙 GitHub: github.com/aliaslany
- 💬 Telegram: @Aliaslanyk
- 📸 Instagram: @aliaslanik
- ✉️ Email: a77aslani@gmail.com
Good software isn't just code that works. It's code that keeps working when the system, the team, and the requirements change.
Keep learning.
Keep building.
Keep questioning.
— Ali Aslani