Is it enough to complete these two courses in Java to get settled at least Junior? And what to study later?

  1. http://www.specialist.ru/course/dzhv1-a
  2. http://www.specialist.ru/course/dzhv2-a

Closed due to the fact that off-topic participants aleksandr barakin , Vladimir Martyanov , insolor , pavlofff , Vladimir Glinskikh 26 Jul '15 at 5:50 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • " Questionnaires are forbidden on Stack Overflow in Russian . To get an answer, rephrase your question so that it can be given an unambiguously correct answer." - aleksandr barakin, Vladimir Martyanov, insolor, pavlofff, Vladimir Glinskikh
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • Checked on your IDEA - also not reproduced. - Nick Volynkin ♦
  • @NickVolynkin and it has magically worked for me, although I haven’t done anything. Magic ... - Denis Ramus September
  • clear. Good. Then they did the right thing to remove the question. - Nick Volynkin ♦

2 answers 2

The text is not mine, I found it on another forum, but I think this is quite an accurate description of the necessary knowledge for Java Junior. In general, these things are sure to be asked at the interview:

1) Types in Java, inboxing, outboxing, as primitives are transformed into each other.

2) Collections, hierarchy of interfaces and implementations, than ArrayList "better" LinkedList. Mandatory question on HashMaps, what is a hash function, internal device.

2.5) Lines are very often asked for loops, control structures, which appeared in JDK 7 compared to the 6th. On the 8-ku there are still few who have switched.

3) Interface, Abstract class, 3 principles of OOP, several design patterns.

4) Servlet, JSP, JSTL, Tomcat or another Servlet container, the life cycle does not go anywhere and how it all works.

5) Advanced topics for June: version control systems Git, Svn, build systems Maven, Gradle, Spring, Hibernate, Web-services (usually REST), are not atrocious, but a bold plus.

6) Sometimes, to fill up they ask about the memory device, what is a stack or a heap, where objects are created, why the garbage collection is needed, JVM startup parameters, so read JVMS . Why to fill up? Because oddly enough, many middle / senior don't even speak about the djunas.

7) Basic SQL, subqueries, what is entity-> communication, design 2 labels and execute queries on them. noSQL may also be asked.

8) From web development, sometimes they will ask for basic JS and CSS. HTML and so everyone should know. Well, if you know the main types of HTTP requests, what is their purpose and difference.

9) JDBC, where without it, once in 2-3 years when you go on interviews you have to remember how to manually create a connection, cram a statement, preparedstatement, subtract data into a result-set, run through it, close the connection.

10) Multithreading is sure to ask how wait, notify, notify all work, why you cannot use sleep, how to create a dead-lock, around what happens synchronization. This topic is very important, because they are asked at each interview, but most often on the project either a normal implementation from the concurrent package, or you do not encounter them at all.

11) What are static methods and variables. The simplest example from the film is the 9th company. Snow White is a static public variable, and Prapor is a static public method.

12) I / O streams, basic things, read the line from the console, what are the filters.

13) English is essential for outsourcing.

PS it is desirable to hear something about TDD, JUnit.

  • It seems not only Java Junior. This is what Java Senior will do if it’s all practical to use. This is how I understood for outsourcers. A Full-time programmer and an outsourcer differ in requirements. But GREAT ARTICLE - Saidolim
  • one
    Well, probably, different campaigns may have different requirements, but all this will not be superfluous :) - Kostya Bakay

As a teacher, I can say that this is the bare minimum.

This is just a theory. And in practice you will be more difficult, because not always the tasks are set specifically with the answers. So that,

in practice, I know: A person learns 8 months of basic programming. Then he does various projects and in the third year, after hard work, he can say that he is a Junior programmer.

So, I can advise to study

  1. Basics of algorithms (what is Algorithm and how to eat it)
  2. Basics of the language. In your Java example (syntax, how it works, bugs and fixes, etc.)
  3. Take any small project and do it in half. (You need to learn how to work in a team !!)
  4. Make the 2nd project yourself.

Now you can say what you want to be Junior Programmer