theoretical versus applied bookkeeping

<p>If you have job postings that don't ask for previous experience, pays like 15-17/hr, states bookkeeping as a duty on top of other things like "ability to navigate computers", spreadsheet and data handling stuff, are you a fit (in terms of summer employment)?</p>

<p>Let's say I theoretically know how to do bookkeeping off of books and Wikipedia, with the whole double-entry system, etc. I've never taken any accounting courses. Of course, I've never actually practiced it beyond practice problems that I could do.</p>

<p>Can you "mug" or cram for job qualifications? </p>

<p>I remember once my gf crammed for PHP and ASP qualifications within two weeks, when she had never encountered non-Java languages before, hahahaha. She got the job, stating that she was "fluent" in those programming languages. But then again, she's a genius.</p>

<p>Is there even such thing as theoretical bookkeeping?</p>

<p>Yes, but it goes by [another</a> name](<a href=“http://en.wikipedia.org/wiki/Library_and_information_science]another”>Library and information science - Wikipedia).</p>

<p>You should be able to learn how to do double entry bookkeeping in a short amount of time.</p>

<p>I think it’s possible.</p>

<p>I learned on the job for my internship. I was told the job would be web programming in PHP, but when I got there it turned out to be some bizarre variant of PHP which, in my five years of coding, I’d never seen before and had to learn it on the job. And I’ve manage to keep my job for almost a year now, and now know this bizarre little language. I still want to hit whatever genius intern decided to use it instead of “normal” PHP.</p>

<p>Just don’t let on that you don’t know what you’re doing.</p>

<p>i’m sure that applied accounting requires knowledge of industry tricks and conventions that you wouldn’t find in a textbook but i’m also sure that entry-level jobs expect you not to know much of that. its not all just adding up debits and credits so you should probably let your employer know you’re inexperienced but eager to learn.</p>

<p>Hmmmm which is the better option:</p>

<p>

</p>

<p>I mean, the former doesn’t sound so bad if I know you can successfully mug or cram for a skill.</p>

<p>Depends what you did on your interview, I suppose. If you insisted that you understood the tasks and were qualified, then the former might apply.
But if you said that you’re familiar with the tasks, but by no means an expert, the latter might apply.</p>

<p>It also might depend on what your employer expects of you. Mine is pretty lenient and has “don’t care as long as it gets done,” attitude, so I got away with being mildly clueless as long as I picked it up eventually.
If s/he’s more on the strict side, proceed with caution.</p>

<p>Both are risky, though.</p>