Preparing for a Junior Ruby on Rails Interview?

Question

Ruby on Rails

In May I have an interview for the position of Junior RoR Developer. I have already learned Ruby, RoR, I am familiar with git, JQuery, Boostrap, I know HTML, CSS.
And what to learn next?
It's possible to delve into Ruby, or learn SQL and a few databases.
I ask for advice.
And what questions are asked in interviews?

Answer 1

I already learned Ruby, RoR

I still can’t say that I learned rails and ruby ​​=)
According to
the REST, MVC subject, project structure, what folders are in, including the config folder.
what is representation, parshials, according to models completely - scopes, associations. validations, callback
controllers - before_action, which is already in the
Unix ApplicationController - what is the application, process and port. What to do if at the start of the server it says that port 3000 is already in use.
Ruby - idiom @a ||= b, blocks, loops, what does attr_accessor do, what is a symbol, ruby ​​constants.
By databases - please give examples of what requests this or that chain of DSL ActiveRecord generates, for example
User.where(id: 1), User.where(id: [1]), User.where(id: []) And there are a lot of such options, it makes no sense to try to memorize, you need to understand.
Regardless of knowledge, the general advice is this. If you are sure of some knowledge, do not be afraid to explain in your own words. If you are not sure, be honest about it right away, without guessing.
In addition, I propose a banal thing - go through the basics of railsguides and make sure that you understand the conventions of the framework correctly. Rails is built on conventions and those who are good at them have a high chance of getting a job.
For example, when asked what the view name index.html.erb means html in, most candidates answer that it is the markup language in which the response will be returned. Those. they just build a logical assumption and do not try to check it. And I have a whole bunch of such seemingly simple questions. In most cases, the candidate leaves with the understanding that he really does not know anything.
PS It's better to know one thing well than a little bit of a lot.
But every company is different.

Answer 2

It all depends very much on the company. Usually, according to the job description or the test task, you can make an assumption about what will be asked in the interview. My interview for the position of junior RoR developer looked something like this:
- What did you use before?
- php
- Do you want to work with us?
- Yeah!
In any case, the junior position suggests that the employee needs to be further trained and follow what he writes.

Answer 3

Our interview goes according to the following scheme
1. General questions on technologies (HTTP protocol, outlook on patterns)
2. Ruby questions (How to make a DSL, about the MVC model and a couple of questions on Activerecord - according to the mood and level of the candidate, either a complex join, or polymorphic relationship)
3. Repair the tests in the project in a task specially prepared for the interview.
It takes about one and a half to two hours, while the candidate writes the code for an hour.

Answer 4

There are enough materials where questions and requirements for applicants are written on the part of the employer. Here you can read in detail about Ruby on Rails Developers