I had a conversation with our product architect and I'm not sure how I should react to it. My apologies if this isn't the right thread.
We're looking for another software test engineer, someone whom I would manage. This is my first time sitting in on the technical question part of the interview. We asked him to implement %X, path elision, and some general questions regarding control flow graphs. I was fine with the first one, it's pretty simple and you can hang a lot of test-related questions on it. Path elision, well, I hadn't even heard of that outside of that scenario, so I had trouble with it myself. And I haven't touched control flow graphs since college. I'm not even sure I did that in college(computer engineering), maybe just bits and pieces I've picked up working here.
So, I'm getting kind of annoyed, why are we asking this guy questions that aren't directly relevant? If I did this stuff frequently, they would be familiar and easy to me. I want to see how he handles questions relating to testing and QA. After confirming with the product architect(he's not my superior, but pretty much is in a de facto manner) that these are the questions he wants asked, he tells me he wants a good programmer so that he doesn't have to edit the test system for us. He does this from time to time when the task at hand is large and complicated enough.
I'm pretty pissed at this point, but I argue that trying to fix this situation through hiring only is a flawed approach. Why not try to improve the skills of those already hired as well? He says we're overworked(which is true) so there's no time for that. It's like this pseudo catch 22: I want to get better because I'm tired of this prick making everyone feel bad(he's a huge fan of negative reinforcement) for not being as good as him, but there's no time to do that. I spend maybe 10% of my day coding.
He told me to go take some computer science classes. I dropped the matter at that point. I feel like he's pretty much evaluated my skills and isn't going to make any effort to invest in them.
I don't know how to frame this to my manager that would actually be productive(more time coding).
I always want to code more, that's the fun part of the job. But a job's a job, I understood the requirements when I took a managerial position. I may have written that from a personal standpoint but there are two other people on the QA team that he's insulting too. I want him to stop working on the test system too. All(within reason) test system coding should be done by QA. That doesn't have to mean me. I'm fine with it falling to the other people on the team.What do you want to do? Do you want to code more?
Definitely. One of them has said he wants to move to a developer position, multiple times.As a manager, maybe you should hire as many people as they let you. More people = more money for you.
Have your QA subordinates people express desire/skill on learning more coding?
Who makes the ultimate technical decision in hiring the Qa guy?
I'm of the mind that test engineers should be good developers too. Our test system is a mess for a variety of reasons, but mainly because QA is understaffed and we haven't been hiring people that are good developers. I'm trying to fix that.Control flow graphs in a test engineer interview? Is he trying to hire an architect or a developer? This guy sounds like a typical technical prick who tries to lord his knowledge of the mundane and functionally useless over people to make himself seem smarter.
"We need someone who's going to get their head in the weeds and never be able to actually perform the tasks they were hired for!". Control flow graphs... hahaha.
yeah then you get carried away with it and it all becomes somewhat of a shitshow when you start destructuring into object keys which for random reasons are in brackets? My current react app has like 10 calls to a single function per page that I copy paste everywhere:
JavaScript:updateState = (stateName, value) => { this.setState({[stateName], value}) }
I'm of the mind that test engineers should be good developers too. Our test system is a mess for a variety of reasons, but mainly because QA is understaffed and we haven't been hiring people that are good developers. I'm trying to fix that.
To be fair, control flow graph theory does come up from time to time. We(and by we, I mean he) just redid our spider, implementing a Markov chain to improve coverage while reducing overall time. I'm not really sure you needed control flow graphs to get to the point he ended up, I mean, how could I, nobody in QA worked on that code. But I do know that's what he used.
I assumed that was your point, just wanted to be sure. And I do agree, we're having trouble finding people that just plain want to do QA. If you program your test system with enough complexity and automation, it can be quite the development task. That Markov chain I mentioned? That was a good 2-4 week task for a regular developer. The interesting programming work is there, if employers are smart enough to not just turn QA into a test review factory.You're going to have a hard time finding people who are good developers AND want to be QA. But the point I was making was that typically only an architect would concern themselves with control flow graphs. After they architect a solution they'd just go to the developers with deliverables. So asking control flow graph questions in a technical interview to a developer, any developer, seems pointless and self congratulating.
Do you use Redux action/reducers at all? i've been just using that, seems a lot more efficient but this is entirely a learning process building this app for me. I'm not looking forward to making this app correlate with Xcode's restrictions, i haven't even looked into that at all yet, hnnngh.
Hell i cant even get the simulator to launch for android yet lol
So, some developmental duties have finally fallen on me.
I need to write a website or web based application that will query a database every X minutes, dynamically update corresponding data on a website, and re-order based on Y conditions.
I'm thinking PHP is going to be my go-to language for this.
Am I on the right track?
You're going to have a hard time finding people who are good developers AND want to be QA.