Philosophy

Fluid Attacks does not measure only what you know today. Fluid Attacks measures how quickly you can learn something new. The company looks for talents who like to learn and who learn without help. Discipline, dedication and hard work are as important as technical ability, or more important.

NOTE: The Academy is more than a technical evaluation. It also shows your tolerance to frustration, your written communication, your ability to obey instructions, your reading comprehension and other qualities.

Pillars

These are the four main pillars of the program.

1. The internet is generous

The internet has more material than you can read. You must find it.

2. Autonomy

Fluid Attacks looks for talents who work without help, who like this work and who want to solve problems. The challenges let Fluid Attacks measure these abilities:

• Your reading comprehension.
• Your ability to obey instructions.
• Your written communication.
• Your problem-solving mindset.
• Your honesty and your humility.
• Your knowledge of Git.
• Your work with CI/CD.

3. Learn by doing

You keep knowledge better when you use it than when you hear it in a class. Fluid Attacks looks for talents who like to learn by doing, and who do not always need a teacher.

4. Agnostic

The language or the technology that you know today is not important. What you do not know is more important, because it shows how quickly you learn and how you control frustration.

Implementation

The Academy is the practical form of these four pillars. The practical exercises show how well you agree with this philosophy. You solve online technical challenges and you send your solutions to the repository on GitLab.

The challenges have these functions:

• Talents solve the challenges that have no solution.
• Talents learn without a teacher.
• Fluid Attacks measures your speed and the quality of your work with the GitLab infrastructure, while you adapt to the process.
• You learn the tools Git, Linux, AsciiDoc, Nix, Gherkin and others.
• You learn the concepts of automation, unit tests, continuous integration, linting and others.
• The Fluid Attacks teams and the community can see your results.

Challenges

The platform has three types of challenge:

• vbd-hacking — you show that you can bypass security controls.
• ctf-hacking — you show that you can solve problems in an environment that you do not know.
• programming — you show that you can read source code quickly.

Fluid Attacks gives you a policy for your profile and your preferences. The policy sets your objectives:

• A hacker solves only vbd-hacking challenges or ctf-hacking challenges.
• A developer solves only programming challenges.
• A talent with a mixed profile solves any type of challenge.

For more information, read the policy data file¹.

Footnotes

1. You can read this file only after you have access to the repository. ↩