Location: Vancouver, Canada
Remote: Yes
Willing to relocate: Not at present, but open to Europe in the future
Technologies: Python, JavaScript (Vue, Node, React, others), Postgres, Unix, Golang, others
Résumé/CV: https://drive.google.com/file/d/1pNVtofK5t6PDyPHZE2Tpes1ftvZE6xIX/view?usp=sharing
Email: on Résumé
Thanks to user Decide for the following format:
Hi, I'm Luke. I find satisfaction in working with geospatial stuff and on tricky responsive interface problems, figuring out how to work with old code or new codebases, as well as learning from my colleagues and teaching when I can.
WHY TO HIRE LUKE:
I'm persistent when it comes to solving problems and troubleshooting, and consider myself fairly good at it; though I know there's a lot I can learn. I’ve done so on one major website that serves billions in transactions annually and for a tiny website that hosts research datasets.
I like to challenge myself technically and in terms of responsibility; probably not a rare thing to find here.
I'm approachable, usually quite humble, and don't let my ego get in the way of collaborative problem solving. Feedback and practice are the major ways to improve.
You want someone who is great in emergencies. I don't tend to panic, and have experience resolving issues that legitimately demand attention.
You want someone who thinks testing with users in real-world settings is worthwhile.
You need someone who values their own spoken communication skills. I have no experience in public speaking exactly, but I feel like I do ok when discussing or explaining things in a group context and find that it's an important thing to improve.
WHY NOT TO HIRE LUKE:
You need someone to communicate with customers or handle support inquires daily; not communication in general, just timely replies on a short cadence. This is not a strong point for me.
You can't let me have any agency over when or how I do work, and that work has little variety to it over a number of quarters. I'm a hard/smart worker, but I'm very cautious of burnout, and need to pick my battles carefully.
You want someone with experience in management or lots of leadership. I'm interested in taking on some higher level responsibilities, but I don't yet have those skills.
You want someone who has desirable stress responses to artificial emergencies (crunch time). What makes me good in real emergencies also makes me awful in imaginary ones (crunch time because of ill-considered deadlines).
You want someone who's been grinding leetcode problems. I have a brief and recent exposure to academic DS&A material, am interested in the subject and can build a priority queue, but I haven't yet passed Amazon's coding test :) (I also have a copy of CTCI, but it's rotting on a shelf)
Hi, I'm Luke. I find satisfaction in working with geospatial stuff and on tricky responsive interface problems, figuring out how to work with old code or new codebases, as well as learning from my colleagues and teaching when I can.
WHY TO HIRE LUKE:
WHY NOT TO HIRE LUKE: