01
MQL4 / MQL5 Expert Advisor development
Custom Expert Advisors built from your trading rules — including the
parts that decide whether a strategy survives contact with a live account.
- Entry and exit logic
- Stop loss and take profit
- Break-even handling
- Trailing stops
- Partial closes
- Trading sessions and time filters
- Order management
- Strategy automation
- Broker-specific symbol handling
02
EA debugging & modification
Small, clearly scoped jobs are welcome. If you already have an Expert
Advisor that does not compile, behaves differently than intended, or needs one more feature, that is a
complete project in itself — it does not have to become a rebuild.
- Compiler errors
- Runtime errors
- Logic bugs
- Modifying existing EAs
- Adding trailing stops
- Adding break-even logic
- Fixing lot-size calculation
- Adding risk limits
- Changing entries and exits
- Preventing duplicate orders
- Repairing existing MQL4/MQL5 code
03
Risk management systems
A risk layer that sits between the strategy and the account and enforces
hard limits, independently of what the strategy wants to do.
- Risk per trade
- Percentage-based position sizing
- Daily loss protection
- Maximum drawdown
- Floating loss protection
- Equity protection
- Exposure limits
- Maximum number of trades
- Emergency shutdown
- Prop-firm risk controls
Read the risk-engine case study
Risk rules limit exposure. They do not decide whether a strategy is
profitable, and no risk layer guarantees that an evaluation is passed.
04
Backtesting & strategy validation
Testing that is set up so the result means something — with the costs
and assumptions written down rather than hidden.
- MT5 Strategy Tester
- Real tick tests
- Multi-year test windows
- Parameter testing
- Out-of-sample method
- Robustness checks
- Spread, commission and slippage assumptions
- Result evaluation
Read the backtesting case study
A backtest describes past data under stated assumptions. It is not a
forecast of future results.
05
Trading automation
The work around the Expert Advisor: getting tests to run by themselves
and turning their output into something you can actually read.
- MQL4 and MQL5
- Python
- MetaTrader automation
- Data processing
- Test orchestration
- Result processing
- Workflow automation
06
Expanding stack: TradingView / Pine Script
I am extending my toolset towards TradingView. To be accurate about it:
my project experience so far is in MQL4 and MQL5, not in Pine Script. I list this here as a direction I am
building out, not as years of delivered Pine work.
- TradingView indicators
- Pine Script strategies
- Alert logic
- Indicator modifications
- Indicator-to-strategy conversion
- Debugging existing Pine scripts
- Webhook-ready alerts
Target version: Pine Script v6.