05
Troubleshooting a live platform, often overnight
When uploads failed or results came back wrong during releases, I traced the logs to the cause and confirmed the fix.
- Role
- Full Stack Developer · Mavericks Tech Solutions
- When
- Sep 2025 – present
- Relevant for
- IT SupportCloud & InfrastructureTesting & QA
01 Run the same file through the same path until the failure shows up again.
My part
I reproduced each failure, found the log lines that explained it, and confirmed and documented the fix with the team, often overnight during releases.
Problem
A multi-service platform can fail in many places: an upload, a queue, a model endpoint, a database write. What the user sees rarely points at the cause.
Approach
Reproduce with the same file, follow its record ID through each service's logs over SSH, check the model endpoint and the network (ports, IPs, firewall), and narrow it to one service. Then write up the cause, the fix and how it was verified in Jira, and explain it to the team in plain terms.
Outcome
Each failure traced to its cause, and each fix confirmed and written up.
What I did
Reproduce first
Run the same file through the same path until the failure shows up again.
Postman
Follow the record
Trace one record ID through each service's logs over SSH.
LinuxSSH
Network checks
Ports, IPs and firewall rules when a model endpoint stops answering after a change.
Payload and mapping bugs
Payload and field-mapping failures between services.
Written up clearly
Cause, fix and how it was verified, in Jira, and explained to the team in plain terms.
Jira
Stack
- Linux
- SSH
- Application and server logs
- Postman
- Jira
- Azure
- Docker