Technical Interview Assistant and Collaborative Coding





How many technical interviews I had for a front-end developer, so many different methods and tools were used by interviewers.



Chat in one place, phoned in another, coding in the third. β€œOh, this service is not working, but share the screen. Oh, the solution code has fallen off, well, write again ... ”The already stressful situation for the candidate turns into an unpleasant carousel.



And according to the same scenario, the structure of the interview is built - more often chaos, jumping from topic to topic.



I am trying to make a simple, convenient and free technical interview service for both the interviewer and the candidate. Everything in one place for everyone: notes, a report and other features for the interviewer, and a convenient editor, full-fledged and beautiful feedback to the mail, etc. for the candidate.



So that everything is predictable and by standards, because so many articles about the correct conduct of an interview are written in HabrΓ©. There is something to be inspired by.



I named it Meet2Code .



What is at the moment:



  • A questionnaire for each section of the interview. Tasks, questions and points of knowledge - everything can be assessed, timed and left a note.









  • Collaborative coding in real time. Convenient work with tasks from the list: in one click you send them to the editor, measure the time, evaluate.









  • Creating templates for interviews - sections, questions, skills, tasks.









  • Well, actually, the report: general and for each section, task or question.









The current functionality still needs to be worked on, but I hope the basic concept is already clear. While there is no backup for storing data, I simply store everything in the browser's local store. For mobile, I also made a simple adaptive, for viewing "don't pluck your eyes", I haven't thought about the design.



If anyone is interested, I am writing a service in React, TypeScript, MobX.



Why I decided to write an article



The current state turned out in a month and a half on free evenings after work, then, as often happens, the excitement disappeared somewhere and for almost a month I did not touch the project at all.

It seems to me that the service is useful and it is a pity to leave it gathering dust. To move on, I want to know the real opinion of the community - is it needed or not. Because this is a non-commercial project, this method is the most realistic and accurate, I think.



What I am working on now and what features I plan to implement:



  • I would like to see my personal account as soon as possible.
  • Upgrade your code editor
  • The result report is clear and simple.
  • Running the code (so far only js and libraries).
  • Generate nice email feedback for a candidate.
  • Creating a library of questions, tasks, skills, so that templates can be assembled from ready-made components, primarily custom ones.
  • Convenience of creating and working with a template (sorting, editing elements).
  • Add tags about importance, time, difficulty, etc. to questions / tasks.
  • Integration with our services and with third parties (for example, hh).
  • And last but not least, calls from the browser.


... and then there are many more powerful features, the trello column with them is very high.



Of course, for this whole business in the forefront there will be tasks for creating an API.



In general, try this tool if you find it useful. I will wait for feedback, draw conclusions and in case of a positive reaction, I will forcefully embody my fantasies and your recommendations / wishes.



In the meantime, I will finish the current state.



beta.meet2code.com



All Articles