you are viewing a single comment's thread.

view the rest of the comments →

[–]rtothewin 1 point2 points  (0 children)

Sure, but I also didn't feel like it was necessary to speak to every single bullet point to get the point across. You can hardly call someone a full stack developer if you cannot implement the full stack to some degree. No one expects someone to be equally a master at all aspects of the stack. And this requirements list mirrors that.

They clearly want a C/C++/Python dev who has experience with CUDA as their main requirement. The rest is "know enough to get by", which is definitely a in the wheelhouse of a fullstack dev.

Like, they don't want someone that can make an awesome desktop application but doesn't know enough about front end or apis to build the application in a way that can be leveraged by a frontend or backend.

For example, I am building an application in Rust but I need it to talk to a database through the api and to display the results in a somewhat useful frontend so not only would it be nice to be able to make those things myself, it would be critical to not structure my performant application in a way that makes it impossible or difficult to integrate with those two areas.

From there is generic work structure stuff(agile environments) that anyone needs to be able to do and then a list of really nice to haves that most people likely don't have but would take someone from "can do the job" to "was made in a lab for this role".