<p>If I may digress, and at the risk of restarting a rather bloody war flame war that I was engaged in full bore not that long ago, you don't need a hard science or engineering degree to be a patent lawyer, or even to argue a case in front of the PTO. Don't get me wrong - it helps. It's certainly the most straightforward way to go about being a patent lawyer, I agree. But you don't absolutely need it. </p>
<p>First of all, most patent lawyers have no need to argue a case in front of the PTO anyway. And second of all, even for those that do, the PTO publishes a long list of various ways that you can be accepted as a viable lawyer who can argue cases in front of it, and having an undergraduate degree in science or engineering is just one of the ways. Another way is to pass the EIT/FE exam, which is certainly not easy, but if you're good enough to pass the Bar exam, and you have some scientific acumen, then you should be good enough to pass the EIT exam if you just keep studying for it and taking it over and over and over again until you finally pass (and besides, if you don't have any scientific acumen, then you probably won't be able to successfully complete an undergraduate science/engineering degree anyway, so the point is moot). </p>
<p>Another way is to simply 'work' as an engineer. Now I know what some of you are thinking - how the heck can somebody work as an engineer without an engineering degree? However, if you think about it, it's really not that amazing in the least. I know one guy who is in law school right now intending to be a patent lawyer. Prior to law school, he worked as a software engineer for various Silicon Valley tech companies, and I can confirm he's a very very good software engineer. Does he have a CS or a EE degree? Nope. His degree is in English. What happened is that he never knew that he liked programming until he was a junior in college, when he got a summer job with a dotcom, but by that time, it was too late for him to switch majors. So he just learned programming on the side as a hobby and used it to pick up extra money as a part-time developer. By the time he graduated, he had racked up a strong body of programming work and hence had many developer/software-engineer offers. In fact, he actually had better software-engineering offers than some EECS graduates, because he actually had strong real-world experience upon graduation. Did that for a couple of years, moving up the ranks, then got interested in patents. </p>
<p>Now I agree that he is an unusual case. But the point is, I think it's hard to argue that this guy was not a true engineer, despite the fact that he does not hold a formal degree in enginering. To be perfectly honest, he's a better software engineering than a lot of guys with EECS degrees. After all, he got better offers than and was later promoted over lots of guys with EECS degrees. {In fact, I once talked to him about this whole law-school admissions obsession with GPA, and he said that he really really lucked out. On the one hand, he studied English, which he himself concedes was a whole lot easier than engineering, and so he had the ridiculously super-high GPA that helped him gain admission to the elite law schools. On the other hand, he has a full-blooded engineering professional background from his job. In other words, he got an engineering background without having to go through the rigors and the harsh grading of a formal engineering curriculum. So basically, he had his cake and he ate it too.}.</p>