IT Messe Wien — System Analysis Challenge (triscon) | Systems & Embedded Software Engineer

🏆 Result#

Reached maximum score in a browser-based challenge at IT Messe Wien
Won: Nintendo Switch

🧠 What Made This Interesting#

The challenge imposed no restrictions on how the score could be achieved.

Instead of optimizing gameplay, I treated it as a systems problem:

Where is validation actually enforced?

What does the backend really trust?

How does score flow through the system?

📖 Overview#

I analyzed the client-server interaction with a focus on trust boundaries and score flow rather than UI behavior. That turned a simple browser game into a systems analysis exercise.

🔧 Technical Highlights#

Analyzed the client-server interaction model
Identified where validation occurred and where it did not
Observed trust assumptions between frontend and backend
Evaluated how score state was processed and accepted
Reached maximum score without bypassing authentication or exploiting vulnerabilities
Relied on system behavior analysis, not external manipulation

💡 Key Lessons#

Frontend is UX, not authority
Client-side constraints are presentation logic, not security boundaries
Undefined constraints create architectural opportunities
Most real-world issues come from misplaced trust, not complex exploits
Thinking in systems is more effective than interacting at interface level

⚡ Engineering Takeaway#

This project reinforced a core engineering question:

Where is validation actually enforced?

🛠 Technologies#

Browser DevTools
HTTP request and response inspection
Client-server architecture analysis
Frontend rendering and backend validation flow analysis
Standard browser inspection capabilities only

Flowchart

Details

The challenge rewarded system thinking rather than surface interaction. There were no method restrictions, only a target outcome. The important shift was from player perspective to system observer perspective. The useful questions were: - How the score was generated - How it was transmitted - Where it was accepted - Whether backend validation was independently enforced The backend behaved consistently with its trust assumptions, which made the same maximum score reproducible without bypassing authentication or exploiting vulnerabilities. The value of this project is not a trick. It is the engineering mindset behind it: Ignore the interface. Understand the trust boundary. Go straight to how the system actually works.

Gallery

3 images