Does Android developer experience matter to a Java EE employer?

Question

Java

Good day to all.
To begin with, I set myself the goal of becoming a Java EE developer. Like any normal person, I understand that without the basics, i.e. without Java SE, you should not climb into the wilds.
Since I had already graduated from university, I had to look for a job. But without the basics of Java EE, no one takes the position of Junior. But they hired an Android developer.
Having a good knowledge of SE and the SDK documentation, it was not difficult for me to get comfortable in Android, I even tried myself in C # / Xamarin.
But I still burn with the desire to become a Java EE developer and in my free time I read the necessary literature, portals, so that in the future (about a year later) I will try my luck again to get a job with them.
And I'm wondering if this work experience of mine plays any positive role. Indeed, on the one hand, there are completely different platforms, but if you look from the other side, then such factors as teamwork, "deadlines", project management systems should be considered as pluses.
I would especially like to hear answers from those who have encountered such a situation or are Java EE employers and can answer my question in the first person.
Thank you very much for your attention and replies.

Answer 1

A year and a half ago, I got a job as a Junior Java EE developer in Moscow.
Not only did I not have Java EE development experience, I didn’t even have a work book.
In the summary, I wrote: they say there is no Java EE experience, but I heard about Java, read all sorts of springs,
well, I attached a link to my repository on github with an open source library in Java (nothing special, a simple wrapper over the site API, a day or two work).
My feeling is that if you don't have experience in Java EE, then you don't have experience in Java EE and they don't care what you did before.
At the interview, they didn’t even ask me what I wrote (except for the above library), what projects I did (before that, I freelanced a little on php)
and from what I decided that I know Java. They gave a paper test in Java and SQL. Then we talked about the basics of java: collections, threads, synchronization, etc.
by databases: types of relationships (one-to-one/one-to-many/many-to-many), transactions, ACID and stuff like that, and in general: processes, streams, http protocol.
Apparently, I didn’t swim too much in questions, or maybe they were simply satisfied with my modest requests for salary (by the way, I don’t advise being modest, it will turn out sideways, but that’s another story).
They took me.
instead of a postscript.
I learned more in a week of work there than in a couple of months of independent study of spring and Java EE in general.
Java EE is actually a very broad area, and Java SE is just the tip of the iceberg.
The brains really boiled from the amount of new data coming in, along the way I had to read books at home and get the basics where they weren’t enough.
Another funny thing, in Java EE, for 5 lines of java code, there were 20 lines of xml configuration: D Apparently, therefore, they don’t really drive around Java itself. You spend more time setting up and linking all sorts of frameworks and servers.
In general, lean on the basics, read and, most importantly, write.
When you start writing, a lot of nuances and incomprehensible java expressions immediately pop up (where without them).
And yet, if you have problems with English, lean on English. All documentation in English.
In Russian, either it does not exist at all, or it is extremely small, or it is already outdated.
Answering your question (IMHO, according to my feelings and from the experience of reading forums): the experience of an Android developer _over_ a Java EE employer will not give you much.
The Android platform has little in common with Java EE, but it certainly won't be any worse.
Sorry for the many books, Ostap suffered.