About me
The engineer behind the work.
How I approach problems, the tools I reach for, and what I do when I'm not shipping.
What I Bring
What I bring to an engineering organization
I combine software engineering, quality engineering and business understanding to deliver systems that are reliable, maintainable and ready for real-world constraints.
- 0
I Think Beyond Code
Software succeeds when it satisfies business requirements, operational constraints, security expectations and quality standards — not only when it compiles. I work with business stakeholders to turn requirements into working systems that fit the organisation.
Business–IT AlignmentSDLCEnterprise Architecture (TOGAF) - 1
I Automate What Shouldn't Be Manual
Automated testing across web, desktop, API and performance layers, integrated into CI/CD — cutting manual testing effort by over 80% at Gulf Bank Algeria.
SeleniumFlaUIPostmanJMeterPlaywright - 2
I've Worked Where Failure Matters
Banking, payments and interbank settlement in a highly regulated environment: SWIFT/ARTS integration for real-time settlement, nationwide branch deployments, regulatory compliance from launch.
SWIFT / ARTSRegulated bankingCritical systems - 3
I Measure Outcomes
Responsibilities are cheap; verified results are not. 177 branches served by one platform, 80%+ manual testing effort removed, compliance held from day one of launch.
177 branches80%+ manual testing removedCompliance at launch - 4
I Improve Engineering Culture
Defining testing standards and quality governance, integrating SonarQube into pipelines to enforce code quality and security, mentoring junior developers, and working close to development teams so regressions surface early.
SonarQubeCode reviewMentoringAgile - 5
I Connect Business & Technology
Business requirement → technical solution → quality validation → production. IT governance, strategic IS planning and data-driven decision making are part of how I scope work, not an afterthought.
IT GovernanceCOBITBI & Analytics
How I Work
A lifecycle, not a hand-off
The same six steps whether it is a nationwide platform or a regression suite.
- 01
Understand
Understand business requirements, regulatory constraints and what failure would actually cost.
- 02
Design
Translate requirements into a practical technical approach: architecture, integrations, data, boundaries.
- 03
Build
Develop maintainable software with SOLID principles, clean architecture and reviewed code.
- 04
Validate
Automate the critical paths and validate functional, API, desktop and performance requirements.
- 05
Deliver
Use CI/CD and quality gates — SonarQube, automated suites — so delivery is repeatable, not heroic.
- 06
Improve
Monitor production, reduce incidents and technical debt, and feed findings back into the next cycle.
Engineering Toolbox
Technology, organized by capability
No proficiency bars. These are the tools behind the outcomes above.
Quality Engineering
SeleniumPlaywrightPostmanJMeterFlaUISonarQubeTest AutomationDelivery & DevOps
Azure DevOpsCI/CDDockerJenkinsGitProgramming
C#.NETASP.NET CoreREST APIsJavaReactJSNextJSArchitecture
MicroservicesMonolithicMVCMVVMSOLIDClean ArchitectureDesign PatternsData
SQL ServerOracle DatabaseMySQLPostgreSQLBI & Data WarehousingDomain
BankingPaymentsSWIFT / ARTSRegulated environmentsCritical systems
Beyond the Stack
Engineering quality is decided long before the framework is chosen
- Architecture
- Application architecture and scalable system design, monolith or microservices, chosen for the constraint — not the trend.
- Maintainability
- SOLID, clean architecture, design patterns and code review practices that keep systems changeable.
- Testing
- Automated UI, desktop, API and performance coverage treated as part of the product, not a phase.
- Security
- Cybersecurity risk awareness, secure integrations, and static analysis gates on every pipeline.
- Performance
- Performance optimization and load validation before production discovers the limit.
- Observability
- Production support, incident reduction and traceable flows in critical systems.
- Delivery
- CI/CD, DevOps culture and automation so releases are repeatable and boring.
- Business impact
- IT governance, business–IT alignment and data-driven decision making tie engineering to outcomes.
Leadership
I don't just deliver — I help teams improve
Quality is a team property. Most of my impact comes from what other people ship afterwards.
Mentoring junior developers
Experienced in mentoring junior developers and raising the baseline of what the team ships.
Quality governance
Defining testing standards and quality governance for banking applications in production.
Cross-functional collaboration
Working with development teams, QA and business stakeholders from concept to production.
Agile & change management
Agile project management, stakeholder management, change management and design thinking.
Two ways to read this page
The Short Version
For recruiters, in 20 seconds
- QA Automation Engineer & Full-Stack Software Engineer
- Banking · Payments · SWIFT/ARTS · Critical systems
- Test automation · DevOps & CI/CD · .NET and React engineering
- Gulf Bank Algeria (current) · Banque de Développement Local
- Platform live in 177 branches · 80%+ manual testing removed
- MBA in Management Information Systems (in progress)
- Master's in Computer Science & Artificial Intelligence
- Algiers, Algeria
If You're an Engineering Manager
Go straight to the depth
- How I think and deliverUnderstand → Design → Build → Validate → Deliver → Improve
- How I testUI, desktop, API and performance automation in CI/CD
- How I approach architectureMicroservices, clean architecture, SOLID, integration design
- What changed on my teamsImpact per role, not a duty list
- How I work with peopleMentoring, quality governance, Agile delivery
Get in Touch
Tell me about the problem you're solving
Whether you're improving an existing platform, building a critical system, or looking to strengthen engineering quality, let's talk about the problem — not the job description.
salahedsmati@gmail.com · Algiers, Algeria