We view this closer to CFA, where it's not required (I don't think we'd ever get to this point anyway), but we want a world where many employers do recognize CSPA.
> Software Engineering is good right now because anyone, absolutely anyone, can dive in.
Yes, I wholeheartedly agree! CSPA actually bolsters this because there are no eligibility requirements to take the test. We believe there are a ton of great engineers WITHOUT a college degree and we want to surface them.
We're making it MORE accessible, not less. There's no real barrier to taking the CSPA, except the time commitment. Just register and take it.
Our initial goal is to replace the technical phone screen. We are asking companies to guarantee an interview (or skip the phone screen), if they score above a certain threshold.
Long term, we hope to replace as much of the onsite as possible. But we do acknowledge we can never fully replace it.
May seem like I'm shitting on your product, but I'm not. I do a good amount of hiring[0] and have had to use services that provide similar outcomes[1]. It's mostly a waste of time and am currently working on removing that part of the process. My main issue with your product is that I don't see how it would provide me with a better outcome than what's out there.
I want to like it enough to try it out and pay you, but dont see value proposition right now.
Re: GAN, we tried including ML in the Core exam, but have actually since removed ML since it wasn't working. We may introduce this as part of an ML specific subject test.
If you want to get involved designing questions, please consider applying to the TSC for next term: https://cspa.io/tsc/apply.
Thanks for the feedback! We try to have a good mix of trivial, novice, intermediate, and advanced questions.
Some of the multiple choice questions are fact-based and just require a Google search -- this is intentional, since proper Googling skills are still needed for the job :)
Problem solving questions are better formatted as open-response essay questions, which we do have.
Thanks for the tip! Can you elaborate? Do you mean teaching to the test, or something else? There's a whole research field for large scale assessment and evaluation methodologies.
Our third party proctoring service handles the KYC, as well as the LogMeIn. We did some vetting, and they are used by some well-known MOOCs and universities' online courses. It's a concern of ours as well, which is why we try to offer in-person proctored tests or appointments.
Currently the Core Exam is 50/50. It's designed for career-readiness. Our Technical Steering Committee is composed of majority of hiring managers, so it's intended to be useful for them -- that is, what are the qualifications desired in an entry level software engineer?
We are debating having a Core general exam, and separate per-subject tests, similar to SAT I vs SAT II.
We've found that that is indeed true. The more senior and knowledgeable you are, the most likely the answer is "it depends", because all the nuances and edge cases you know about.
We try to solve this with the standard "choose the BEST answer". We also do post-mortems and analyze the responses to disqualify or discount bad questions.
These are issues the CSPA Technical Steering Committee, which is responsible for the exam content, will deal with, in collaboration with our research advisor: https://cspa.io/about/team
(1) When we retire old exam questions, we will make them available for practice. We're working on creating more study materials! I can't promise anything before April though.
(2) Ah the 440 FE is a typo. We updated the scoring algorithm a few months back and didn't update those examples. Most people try completing all 6 subject sections. It's up to you, but we do discourage optimizing this kind of test taking strategy, and "teaching to the test" ;P
It sounds like this happened after I left Crunchyroll in 2015. The process I had in place was definitely not like that :/
Well FWIW, I personally wrote the coding exercise that you enjoyed (http://www.crunchyroll.com/tech-challenge/roaming-math/yourn...). I thought it was a good mix of basic algorithms (tree traversal) as well as some practical knowledge (CURL/http). I'm surprised they are still using the same one :)
My interview was in June 2015. Maybe you had left by then. It did seem disorganized.
I did really enjoy that coding challenge, though. Good job with it. It is the one thing I did like about the whole experience, and I still share it with people when they ask about what a good coding challenge might be. Tree traversal isn't particularly useful in web dev world, but it's a pretty intuitive task, so I think it's gives good insight into whether a programmer can reason logically about a task.
I'd rather see real-world challenges, though. Sometimes that's hard, though, depending on the company.
> Software Engineering is good right now because anyone, absolutely anyone, can dive in.
Yes, I wholeheartedly agree! CSPA actually bolsters this because there are no eligibility requirements to take the test. We believe there are a ton of great engineers WITHOUT a college degree and we want to surface them.
We're making it MORE accessible, not less. There's no real barrier to taking the CSPA, except the time commitment. Just register and take it.