Trying to build and program a robot with zero experience isn't the exception but it's the normal case. Most robotics projects are started with the aim to learn something which is new and to get detailed knowledge about Artificial Intelligence. For getting the maximum learning experience the project goal should be a little more complicated than the user is able to realize. This is equal to create a demanding quest which makes it likely, that the user needs additional knowledge.
The primary question isn't how to solve an existing robot task, for example to react to an audio signal, but how to formalize the challenge. The problem can become static by providing environmental constraints about the robot hardware, for example a certain Arduino kit, and for defining the software task, for example the robot arm should move 4 centimeter backwards (not more) in reaction to a handclap sound.
Carefully defined requirements for a robotic system will make the project much easier. It reduces the space of potential useful literature, reduces the effort to search for existing examples, and allows to identify missing skills. For example, if the task is that the robotarm should react to a handclap sound, but not to clicker sound produced by a dog training device, it's possible to determine if the project was a success or not.