DEV Community

Discussion on: The Insecure Developer

Collapse
 
janux_de profile image
Jan Mewes • Edited

Thanks for sharing this experience.

However, I have recently come to know also the other side of the coin. One of my team-mates left us and now we are searching for a new colleague. We as developers have a good say in the process whether we make an offer to an applicant or not. Beside the one how didn't accept our invitation to an on-site interview we rejected all applicants so far.

The point to consider is that we are working in challenging environment, with high demands on all of us. I am personally working hard to wrap my head around the various moving parts of the Spring framework, test infrastructure and Kubernetes deployments; while trying to keep the software design in order.

What do you suggest to find out whether an applicant is a passionate (junior) software developer and can learn to work successfully in a challenging environment or whether he/she will hamper our own productivity?

(Maybe we are wrong about trying to find elite people and should rather fix the system's complexity + develop a better training program. But that is too hard and I'll try to ignore it for now ^^ .)