Internship Application System and Posting Management

An internship application is not the same record as a job application. It lives in its own table and gets its own tab in the panel. In daily use that means two things: internship applications never pad out the list while you review job applications, and job applications never cut in once you move to the internship side.

The split is about the questions, not about tidiness. The internship form asks for fields a job application never carries: year of study, grade average, internship length, internship type, whether the school covers the insurance, and career goals. Four of those come from closed lists, so the same information arrives in the same shape on every application.

Closed lists pay off in the list view: the internship screen offers filters that have no counterpart on the job side. University, department, city, district and internship type. The options are built from that company real applications rather than a fixed catalogue, so a university nobody applied from never shows up in the filter.

The insurance field is a data field, not a legal calculation. All the product knows is the option the candidate ticked and the internship type label; it makes no interpretation of the regulation.

• CV required, PDF only, 5 MB maximum
• Transcript optional, under the same two rules
• KVKK notice and explicit consent are mandatory; the moment both are given is written onto the application record as a timestamp
• The form carries bot protection
• A second internship application from the same email address inside 24 hours is refused; this check runs per company, not per posting

An internship posting is a record of its own. Next to the title, department, location and role description it carries the quota, a minimum grade average, preferred departments, weighted requirements, preferred qualities and an application deadline. The status is one of three values: Draft, Active, Closed. Quota, minimum average and deadline are optional; the deadline can be left open ended.

A posting past its deadline does not stay Active. Closing does not depend on a separate scheduled job: every time the public posting list, the posting detail or the hiring status of the career page is read, expired postings are pulled to Closed. There is no in between state where a posting is expired yet still looks open.

The quota is informational. It says how many interns you plan to take on, it puts no ceiling on applications; the public form does not close once that many applications arrive, and your team picks from the whole pool. The minimum average does not lock the form either, it turns into a mandatory criterion on the evaluation side.

Moving a posting to Active is refused when the deadline has already passed, so an expired posting cannot go back out. A posting that is already Active stays editable.

Setting an internship posting to Active spends one of the slots your plan allows for open postings, and that allowance is shared with job postings: Mini 1, Starter 3, Professional 25, Enterprise unlimited. With three slots you can run two job postings and one internship posting. If you move to a smaller plan, postings that are already Active stay editable and no new posting can go live.

You do not have to write the posting text yourself: the panel can draft it with AI. The draft never goes live on its own, it lands in the form for you to edit and save. Draft generation is open on the Professional and Enterprise plans and during the trial, and closed on Mini and Starter; it also needs the AI analysis switch in company settings to be on. While it is off, postings are simply written by hand.

• Status: Draft, Active, Closed
• Requirements are a weighted list; Preferred qualities and Preferred departments carry no weight
• Requested skill tags stay on the face of the posting, they are not turned into scored criteria

There used to be a global panel that opened and closed internship applications, and it was removed. Today the answer follows from the postings: applications are open while at least one internship posting is active and inside its deadline, and closed when none is. Moving the posting to Draft, or letting the deadline pass, closes applications without any separate switch.

The check runs per company. With no active internship posting, even an application arriving through a valid posting link is refused; the system turns it away with an internship applications are closed response.

The same outcome shows on the career page. The internships link is only drawn in the menu while an active internship posting exists, and while it is there it carries an open for internships badge. The state refreshes at most once every sixty seconds, so the link appears shortly after you publish a posting and disappears on its own once the posting closes.

A page called internship settings still exists in the panel, but its content changed: it now holds departments and internal position managers. There is no internship screen for locations, periods or notifications; every internship setting lives on the posting itself.

Every active internship posting is published at its own public address, and the page ships with a machine readable JobPosting record. The employment type is marked as an internship, and the page also emits breadcrumb data.

Indexability rests on two gates, both identical to job postings: the posting must be Active, and the page body must pass 300 characters. The 300 character threshold was not guessed, it was measured on live postings. On 1 August 2026 there were 13 active postings live; the shortest body was 310 characters and the median was 489, with nothing under 300. The threshold eliminates no posting that is live today, and it does stop a body that was genuinely left empty.

Active internship postings enter the sitemap posting by posting, straight from the live database. The internship section keeps its own address in the map even on a day with no postings at all. Whether a page is picked up, and where it ranks, is up to Google; what is promised here is that the data is produced correctly and completely, not a ranking.

A closed posting address dies: the public page of an internship posting that is no longer Active returns not found. The applications stay in the panel; only the public page closes.

The application is saved, the CV and the transcript if there is one are written to storage, and the candidate receives a confirmation email. CV analysis is queued in the background: the candidate never waits for it, the confirmation screen appears right after they press submit.

The analysis runs on the same track as a job application, but it knows it is looking at an internship. The seniority label the model returns is capped at junior on internship applications. The minimum average on the posting becomes a mandatory criterion. Preferred departments are written to the preference side as a single studying in one of these departments item rather than one item per department; otherwise every candidate would lose points over departments nobody asked for.

The model produces no numbers here either: it answers whether each item is evidenced in this CV, and the code does the arithmetic. An item with no evidence found is not counted as half a point, it leaves the denominator. The decision mechanism is unchanged: AI never moves an internship application to another status on its own, a person always makes that change.

An internship application goes well past evaluation. You can schedule an interview, open document and information requests, and create an employment period and an employee record. Those chains run on the same system as job applications; no second mechanism was built for internships.

Permissions are separate on the internship side. Viewing, updating, creating, changing the status of, noting and deleting an internship application; viewing, creating, updating and deleting an internship posting; exporting internship applications are all granted individually. You can open job applications to a user and keep the internship side closed.

These are three different jobs with three different outcomes. Closing only changes the status of the posting and leaves applications untouched. Archiving closes the posting and takes the applications off the list as well. Deleting removes the record entirely and does not run at all on a posting that has applications.

Archiving should not be treated as a reversible edit: candidates in Pending, In review and Interview receive a real rejection email. Emails go out in groups of five.

That is why you take a preview first. The preview counts how many applications sit in each status, how many will be rejected, how many will be archived and whether emails will go out. When no application is up for rejection, no email is sent at all.

The rule on deleting is plain: an internship posting with applications cannot be deleted directly. The applications move to another internship posting first. The move and the delete run as one operation and report how many applications were moved. The step cannot be skipped, because otherwise records would be left without the posting they belong to.