3 ms·
We actually tried to be fairly explicit in what you will be doing for our team: https://www.themuse.com/jobs/capitalone/machine-learning-software-engineer-6c73
by lettergram 8y ago
We actually tried to be fairly explicit in what you will be doing for our team:
https://www.themuse.com/jobs/capitalone/machine-learning-software-engineer-6c7338 https://www.themuse.com/jobs/capitalone/machine-learning-sof...
We even set the requirements to match what we felt could do the job. The roll has actually been fairly difficult to fill though. Recruiting decks I have seen actually suggest creating more requirements and being vague in an attempt to lure more applicants. After this experience, they are probably correct. Lure them in then explain more after they meet the team (i.e. get them excited)
- dsr_ 8y agoNo, the problem is that you are looking for a unicorn in the first half of the requirements, then subverting it by asking for someone with only one year of experience in three things, then double-subverting it by suggesting that you want an academic who has nonetheless designed microservices and done machine learning. And it doesn't really help that you're in a large stodgy bank. Let me rewrite this into two different job openings: 1. Junior Machine Learning Software Engineer Bachelor's Degree or equivalent experience / At least 1 year working with statistics, mathematics or engineering programming / At least 1 year programming in Python and one or more of Ruby, R, Matlab, C++, Scala or Java / At least 1 year of experience working on full stack solutions 2. Machine Learning Software Architect Master's Degree or PhD / At least 2 years of experience with cloud software design using microservices / At least 2 years of experience with machine learning libraries such as TensorFlow, Pytorch or Keras / Demonstrated original research in this or related area Do you see how different those two are? But you set up the ad to switch between them.