What project to start developing to demonstrate your knowledge to the "employer"?

Question

Project management

A very important interview is coming up in 2-3 weeks (I won't name the location). I want to start developing some interesting project for myself, which I can then show to the "employer". The fact is that before that time, there was no time to deal with their own projects, but now they are impatient. I would love to hear your ideas on this. Maybe you want to do something now, but your hands do not reach. Goal: A practical application of medium complexity for a developer with little experience in production. About my skills: C++, boost, Qt, knowledge of various algorithms and data structures (not a basic level).

Answer 1

Developers often itch to roll something of their own. And it's not always just some practical projects. More often, these are just examples of how some approach works, some tests, some sketches. And often it all falls down in the personal space of the github.
It is projects like this that matter to me. I always consider it a plus if the person himself, at the first contact, immediately gave a link to his public repository. In this case, I'd rather keep myself busy reading this dump of code than give a test and torment the candidate. Although there are exceptions everywhere.
It is such a dump of arbitrary code, created with a creative approach, created purely for oneself (and not for interviews), without restrictions in decisions from above, that gives the best idea of ​​\u200b\u200bthe knowledge and abilities of a person.
I advise you to choose a project according to your desires. From what the hands itch to take.
And if you want not for yourself, but for interviews, then I personally advise you to immediately begin to be ashamed of such a project and not show it to anyone.
And I also advise you to read this: blog.gamedeff.com/?p=64 The relevance of the text lies far beyond game development.

Answer 2

In 2-3 weeks, nothing serious will be developed anyway! No need to throw dust in your eyes!

Answer 3

I often interview candidates. Such "projects" are rather a minus. Experience in a couple of weeks you will not gain in any way. People who say that they will master something serious in a week are naive and inexperienced. It is dangerous to trust them with serious work. Rather, I will take a person who honestly says that he has no practical experience, but at the same time has a realistic plan for his professional development. He can be trusted because he is honest with himself and knows how to soberly assess the work ahead. It's easier to teach him.

Answer 4

What you yourself need or simply lack - then develop it. It's best to go.

Answer 5

I think the goal needs to be reformulated. Do the project not for the interview, but for yourself. It is quite possible to pass the interview without your own project. Now, not every potential employer reads the resume to the end, and even more so, he will not delve into the code on the github.
PS: 2-3 weeks is really not enough for a serious project.

Answer 6

1. What matters to the employer is not what you do or can do, but what you have done, i.e. results.
2. It is more important for the employer what you do specifically for him than what you have done for others.
3. Find out the needs of the employer and proceed from this.

Answer 7

Go through your term papers and theses and show them if the employer wants to look at your code. It is clear that the employer is not impressed with the bubble sort, but they will be able to appreciate the codestyle in general.