The "no bootable device" failure has always historically indicated whether or not the system found a disk with a bootable partition present.
At boot, the BIOS will obtain a record of all devices that could potentially contain bootable media. It will go through this list in a particular order, and once it finds one containing a Master Boot Record (MBR) partition with bootable code, it loads it and starts executing it, eventually loading the operating system or whatever other software you might be running.
There are multiple reasons why you might get the error you are seeing, though:
You have a faulty connection to the drive and/or it is underpowered.
This could happen if your SATA cable is faulty or has a loose connection, either to the motherboard or the drive itself. It could also be that the drive is underpowered or not powered at all. Check all connections between the drive and the motherboard and PSU. Ensure that connections are tight and that cables aren't kinked or stretched. Try different SATA and power cables to see if there's any difference.
You have a faulty SATA port on the motherboard.
These headers are soldered onto motherboards and can experience strain or stress as you dig around inside of it. You might put strain on a cable and pull it such that the soldering cracks or breaks. The electric connection between the contacts could still occur, but it will be unreliable, as moving the device around, or atmospheric conditions, could change the conductivity of the space between them (or how large it is). If there are other SATA ports available, try switching to one of those. Chances are at least one of them will work. If not, either they are all broken or are all working fine and the reason for your problem lies elsewhere.
You have some buildup of dust.
I've seen dust do all sorts of strange and mysterious things to computers. It carries static, and can interfere with the electronics inside a computer. Anything is on the table when dust is involved. Give it a good shot of compressed air and see if anything changes. It doesn't even have to be particularly dusty or visible to still have an effect.
The drive is actually faulty.
It seems you've ruled it out, already. But it's good to ensure that the drive actually responds to reads and writes correctly. This is the only reason that can be detected by testing the disk, physically. Everything else can happen regardless of the physical health of the device.
There is a misconfiguration in the BIOS.
The BIOS is software, and can be configured. It has to know how to talk to the onboard devices and where to look for bootable partitions. You can often configure the list of where it looks for a bootable device, and the order. Only until it checks the whole list will it report the error you're seeing. Make sure that it's actually trying to boot from your SSD at all. And make sure that the BIOS settings are persisting between boots. (If they are not persisting, you might have a faulty motherboard or may need to replace the CMOS battery, if you have one.)
Additionally, you should make sure that whichever mode the BIOS is accessing the drive in (RAID, AHCI, PCI, etc) is the same mode that was set when installing the operating system. Usually computers are shipped with AHCI as the default. If you change this setting, oftentimes the computer will fail to boot properly. Additionally, if you're in RAID mode, you might need to run a separate configuration to set up your RAID volumes. (I suspect this isn't the issue if it's a laptop.)
The operating system installation could be hosed.
Pretty simply, if the operating system wasn't installed properly, or someone tried to reconfigure it and messed up, the operating system just would fail to load. Since it isn't finding a bootable device at all, it's possible that the MBR could have been damaged itself. If the operating system's files became corrupted, but the MBR was loaded just fine, you would likely see an OS-level error, rather than your BIOS-level message.
Addendum:
I wrote this from the perspective of building a desktop computer, but laptops also apply. They have a different form factor, but the general principles all still apply. Given your issue is intermittent, I'm leaning more towards a loose/faulty SATA connection (port or cable), power, or a faulty drive. I don't know what Fry's does to test, but often I suspect places like that do a bare minimum or just brute-force, opting to reinstall the OS if it's any more complicated than a simple fix, or just replacing the device completely. I've seen one shop (not Fry's) even do a simple test by plugging a drive into an existing computer and seeing if it was detected by Windows by showing up in My Computer (a horribly limited test method). SMART tests are also not reliable methods in cases of drive failure. It will catch some reasons but not all.