Questions people ask us.

ClockIN is a professional network built around work. You can show projects, take Skill Proof assessments, find opportunities and follow an application through the hiring process.

Yes. You do not need a login, email or payment to use the public ATS + Tools collection. You get the full result first. An account is only needed if you want to use the main ClockIN product.

There is an ATS resume checker, a resume parser view, resume-to-JD matching, a JD quality checker, a job-description decoder, interview readiness and an application-readiness checker.

No. There is no single universal ATS score. ClockIN checks whether a resume is machine-readable, whether the structure is familiar and how the resume lines up with a job description. It does not claim to copy an employer's private ranking system.

The public tools process the resume or job-description content needed for your result, but they do not store that content. We can keep a short-lived salted network fingerprint, the tool name and a request count to prevent abuse. A resume you intentionally submit with a ClockIN application is handled separately and can be stored privately for the hiring team.

Skill Proof is a ClockIN assessment for supported skills. It uses several kinds of questions and tasks, then reports an L1-L5 level based on what you demonstrated. Recruiters do not get to invent a minimum L1-L5 cutoff for a role.

The recruiter chooses the skills that matter for the role. If ClockIN has Skill Proof for those skills, that result can be part of the review. An interview can add more information when needed. The hiring team still makes the final decision.

No. Some interviews can use a model-assisted adaptive flow when the required service is available. If it is not available, ClockIN can use a fixed set of job-relevant questions instead. We do not invent an AI score for those fallback sessions.

If a role uses integrity monitoring and discloses it, ClockIN can record supported session events such as focus changes, device interruptions, clipboard attempts or recording interruptions. Those events are shown as context for review. They do not automatically lower a skill score or prove cheating.

No. Projects can be software, financial models, campaigns, design work, research, strategy, data work, hardware or other professional work. Add the project and your personal contribution first. GitHub is only one optional kind of evidence.

You can attach a public link or upload a local artifact such as a document, spreadsheet, presentation, image, video, dataset or other file. Evidence can be public on the project or marked for verification only. An attached artifact is evidence on the record; it does not automatically prove authorship.

Source verification is now an optional extra signal. If you complete a ClockIN challenge for a public repository or deployed site, it shows that you controlled that source at that time. It does not prove that you created the whole project or wrote every line.

Project Defence tests whether you understand the project you submitted and can explain your own contribution, decisions, trade-offs and validation. GitHub-backed projects can use bounded repository evidence such as files and recent changes; non-code projects are questioned in their own context. Uncertain cases can go to human review instead of being automatically rejected.

AI-assisted work is allowed. ClockIN does not try to guess whether a project was generated by AI. The important question is whether you can explain the work, the decisions and assumptions behind it, what you personally contributed and how you would validate or improve it.

ClockIN can use role skills, Skill Proof, work on the profile, preferences, location and work mode. The match should also show the reasons behind it, so you are not left with a percentage and no explanation.

The hiring team can review Skill Proof, interview evidence, integrity context and a screening recommendation. ClockIN can also prepare a candidate report. These help the team review the candidate; they do not make the final employment decision.

Yes. The older source-control challenge remains available as an optional trust signal and for compatible existing projects. It is no longer required before you can add or defend a project.

Yes. The skills catalog is broader than the Skill Proof library. A skill can be used on a role even when ClockIN does not yet have an assessment for it.

Application status stays visible on ClockIN, along with the response expectations for the role. The goal is simple: an application should end with an answer instead of disappearing into silence.

No. Your login email is account data and is not automatically copied to your public profile. Optional contact fields have their own visibility settings.

No. ClockIN is still in pre-beta. We are testing the product in small groups and changing it as we learn what works. If data handling or platform rules change in a meaningful way, the relevant Privacy or Terms page will be updated.