What should be your own project for getting a job?

Question

Ruby on Rails

I want to get a job as a Ruby/Rails programmer, I have no commercial experience, I just have a great desire to do something worthwhile (subjectively) on my own and look for it already.
Let's say the average salary of juniors is $700. How realistic is it to claim something more with one such project?
PS Does it matter if I try to repeat the functionality of an existing project (dropbox for example) and demonstrate my code and skills on this?

Answer 1

You can and should show your projects. And the best thing is not just to show, but to talk about how the development went, what problems you encountered and how you solved them. If you want to increase your chances of getting a job in this way, then the project must show that you are good at the subject both from a theoretical and practical point of view. I'm not even talking about Ruby here, interesting things can be written in any language.
What you need to pay attention to:
- Architecture . A well-designed system is the key to the success of the entire enterprise.
– Performance . Here you can show both algorithmic training and the ability to work with databases, as well as knowledge of the features of a particular language. -Testing and Documentation
. Test coverage and description of functionality, starting from the main modules and ending with individual functions, is the ideal that all companies that respect their development try (but cannot) achieve.
If colleagues have any additions, please (:

Answer 2

Best of all, you will demonstrate your skills directly at the place of work! You choose a suitable organization with a suitable salary for a trial period. During the trial period, you work in a real team with real tasks, you grow yourself, and if the team leader and other members see your desire, then the salary after the trial period will definitely increase! This point can also be discussed as a condition when applying for a job. Stop doing house-fucking and doing things no one needs! The teams need you! Rails programmers are in short supply!

Answer 3

It is worth looking for a job and doing a project in parallel. Do anything to your taste so that it is interesting to implement from a technical point of view. Working with external APIs, own API with token access, email notifications to users, solving an interesting problem with the service. It will be appreciated.
Also keep a blog. This is also often a plus.

Answer 4

Commits to serious open-source projects are much more convincing than homemade toys (at least for me)

Answer 5

Nobody will demand your project from you.
Its presence can be both a plus and a minus, depending on the quality of the code.
And his absence will not be a minus.

Answer 6

In the right direction, you think that your projects are worth doing, one nuance is that it takes time, but if you have it, then do it.
Take the task from the net, full of idea forums or just people ready to generate a good service idea. Or your personal problem, the problem of friends, which needs and can be solved.
And do it, the main thing is not to stop and bring it to the end.
Important points, let it be at the forefront of technology and do not forget:
- work with external APIs, even background tasks, even individual services
- do not forget about tests (rspec, capybara, jasmine, karma)
- plus, if you still show the front on the frameworks ( backbone, angular)

Answer 7

Read more about job requirements, knowledge of what technology gems they need.
The answer is in their own questions.
For example:
jobview.monster.com/Ruby-on-Rails-Engineer-Ruby-on...
coub.com/jobs
require knowledge of gems - eventmachine, Rspec and testing tools like FactoryGirl, Capybara, Cucumber, and Selenium
google something like "most popular gems in development" example
www.devinterface.com/blog/en/2013/12/le-15-miglior...
Read what these gems do and use these gems in your project.
Think about how you can cleverly group these gems to get something more or less whole.
When you write a project that uses many (not all :) ) gems, then the output will be a more or less good project.
Your site doesn't have to be innovative with a unique idea, remember your project is just a demonstration that you know how to work with these gems/technologies.
And then at the interview say: yes, I know Rails and this set of gems, I know how to work, I used them in my project :)
ps and write on GitHub to demonstrate that you know how to work with Git, and it is addictive :)

Answer 8

Make and upload on github, create a profile on Linkedin/hh.

Answer 9

Now rails junior in Omsk, this is someone who can immediately start doing projects on Odesk. I have no idea, at the moment, how people are arranged. Apparently only those who already have a good background in development.