Is it possible to show a potential employer a code from a previous job (inside the essence)?

Question

Career in IT

He worked in a fairly large company (everyone knows it in Russia) as a programmer.
Developed and maintained software and worked quite a lot with the database (Oracle).
Surely the employer will raise questions about the database. I so understand it is impossible to show the code of these most SQL requests, the implemented procedures, etc.? There is not one / two lines of code, but footcloths.

Answer 1

Well, formally like this: the authorship of the code is yours in any case, and the right to use already belongs to the company.
Then there is another moment with the NDA, if you signed something like that, etc., then often you can’t even say without a code what exactly you did, only abstractly (and sometimes you can’t say that you did anything at all).
First of all, employers will be interested in cases and the algorithm for solving them. The specific code itself, especially the large one, there is no time to study and delve into. But here it is possible to clear it of specifics, making it more abstract, solving an abstract problem. With code, you show more of your writing style, cleanliness, and more.
Therefore:
1. Focus on cases.
2. From your old works, choose the most interesting ones (from your point of view), clean them up from specifics and direct reference to the old project. Well, for example, you had a procedure for some kind of smart search for geo-referenced objects with some wise specific function (let's say a heat map of real estate prices with cross queries on different tables), and you simplify it to a simpler and abstracted example, data construction for a heat map of objects (abstract) according to a given criterion, taking into account additional properties from related tables. Well, you understand me. At the same time, by the way, the refactor will be easy.
I repeat, a lot of code is not needed, take just a few, in your opinion, interesting examples. Their goal is primarily to show the style and understanding of the language (in this case, sql). The rest, tell in words, including the algorithm, you can show the block diagram. You can convey the very knowledge of the operation of the database not through the code already, but in words, block diagrams and stories and problems and successes (and failures, too, by the way and why they happened)

Answer 2

no
, they usually ask you to write something from the requests on the spot