Do I get things in on time / under budget?
Do I avoid common programming pitfalls?
Do I solve more problems than I create?
Do I see simple solutions to complex problems?
Can I refactor terrible code to more easily maintained code?
Can I avoid terribly written code in the first place?
Can I effectively communicate with people in order to get the answers I need without wasting their time with needless questions?
Then you know you're effective when: You're asked for help often.
You're the go to person by the boss.
You're often asked for your opinion for engineering decisions.
Your opinion holds weight with others.Your four points on effectiveness happen to me on a daily basis, but I tend to see them as annoyances, mind you, I rarely refuse to help and advice. This gives a whole new light and meaning to all those interruptions.
Remote: Can be remote, can be on location, no preference
Willing to relocate: Yes, within Spain
Technologies: Mostly Python ecosystem. Comfortable with Azure, GCP or AWS. Mostly machine learning, data science and AI stuff
Résumé/CV: https://www.linkedin.com/in/hdkmraf
Email: rafael.perez@eol.solutions