Reach the Academy Office
Questions about module enrolment, project reviews, or which track fits your background? Write or call during office hours and we will point you to the right starting point.
Send a message
Questions about module enrolment, project reviews, or which track fits your background? Write or call during office hours and we will point you to the right starting point.
Send a message
Tell us when you would like to talk and what you are working on. If you are mid-module, mention the topic: routing, database models, testing, or deployment. That way the person who calls you back already knows which part of the curriculum to open.
Theo-Eigner-Gasse 53
4320 Ebenfurth
Requests sent before 16:00 on a weekday are usually answered the next working day. Weekend requests wait until Monday morning.
Before you commit time to a module, it helps to know what these terms actually cover here. Below are the definitions and boundaries we work with, so nothing about scope, prerequisites, or outcomes stays vague.
Neither. HiLoft Digital Academy is a structured learning platform, not an accredited institution. Completing modules gives you working knowledge and a record of what you covered, but no state-recognized diploma. If a job posting requires a formal degree, this is not a substitute for one. What it does offer is a clear sequence of topics and exercises you can point to when describing your own skills.
No. The introductory modules assume you have never written a line of code. They start with how a program is structured, what variables and control flow do, and how to read an error message without panicking. If you already work in IT, you can skip ahead to the application development and software tooling tracks, though the early material is a fair refresher on terminology.
The core path uses JavaScript and Python because both let beginners see results quickly and both appear widely in real projects. You will also meet HTML and CSS for interface work, Git for version control, and a code editor you configure yourself. We do not teach every language. When a module mentions a framework or a database, it is because that tool illustrates a concept, not because the platform endorses one stack over another.
Through the work you produce, not through scores. Each module ends with a small build task, a written reflection on what broke and why, and a review checklist you apply yourself. There are no rankings, no leaderboards, and no timed exams. If you want external validation, you would need to sit a separate certification elsewhere. Here, the measure is whether you can explain and rebuild what you made.
Things that show up the moment a project leaves a tutorial: how requests travel between a browser and a server, why data needs a schema, what happens when two processes touch the same file, and how to structure folders so a project stays readable after three months. It also includes reading documentation, naming things sensibly, and writing a commit message someone else can follow. These are not separate courses, they are woven into the build tasks.
Self-paced. You move through the material when your week allows, and nothing expires. That said, the modules are ordered for a reason: the application development track assumes you finished the fundamentals, and the tooling sections assume you have a project to apply them to. Skipping ahead is possible but usually costs more time than it saves. If you stall, the contact page is the right place to ask.