4 ms·
The "I would not know what kind of a spot ... what if I didn't like the app" doesn't strike me a strange situation at all. The agency I work for, we do it all
by steven777400 13y ago
The "I would not know what kind of a spot ... what if I didn't like the app" doesn't strike me a strange situation at all. The agency I work for, we do it all the time. We hire developers, at least half of them, into a developer pool and just assign as needed to projects as they come and go.
Sure, after you've worked for a while you have "your" projects, but we generally don't know which ones those will be in advance.
When I was hired, the recruitment was extremely vague about what kinds of apps I would be working on. During the interview, I asked for more detail, and didn't get it. Similar situation: the apps I'm working on are whatever apps the business customer and I decide are needed to be worked on.
Some candidates do ask during interviews what projects they'll be working on. I'll be frank with them. I'll tell them "these are our current top priorities, but you'll be working on whatever is needed, helping out other developers and teams as needed, and generally filling in all over the place for at least the first six months." I actually like setting it up that way. Have a developer work with different teams, on different apps, before they "settle down" to the maintain and develop "their" apps. (If that ever even happens)
- grey-area 13y agoSome people view passion as an important part of motivation in a job - as in a passion for robotics meaning a programmer spends more time and energy in solutions for a particular team that makes robots than they would otherwise in any other position. Clearly, given your process, you won't be hiring people who are passionate about certain areas, though they will be happy to work on anything, so the hiring process suits you and finds you generalists who are happy to work on any project (exactly what you want), but it will put off some potential employees.