C-DAC Jobs

The Centre for Development of Advanced Computing has opened a fresh June 2026 JIT recruitment cycle for contractual project staff across its centres. Current recruitment coverage lists more than 900 roles, with the application window running from 1 June to 20 June 2026 through the C-DAC careers portal.

This is both a government-jobs update and an IT hiring update. C-DAC is a scientific society under the Ministry of Electronics and Information Technology, and the current cycle covers project roles in domains such as AI, cyber security, high-performance computing, VLSI, embedded systems, full-stack development, quantum computing and administrative project support. Candidates should start from the [C-DAC website](https://www.cdac.in/) and the [current C-DAC recruitment summary](https://www.freejobalert.com/articles/c-dac-recruitment-2026-apply-online-for-951-project-engineer-project-manager-and-more-posts-3052155), then read the exact centre advertisement before applying.

## C-DAC has opened a June JIT hiring cycle

The strongest current signal is the date. The June 2026 JIT cycle opened on 1 June and closes on 20 June, according to current recruitment coverage. That gives candidates less than three weeks to choose the right centre, match the post, arrange documents and submit the form.

Because this is a JIT cycle, candidates should expect centre-wise detail rather than one simple vacancy table. Bengaluru, Chennai, Noida, Pune, Mumbai, Hyderabad, Delhi, Mohali, Kolkata, Thiruvananthapuram and CINE in the North East are among the centres named in current coverage.

## The roles are contractual project appointments

Candidates should read the appointment nature carefully. Current coverage describes the jobs as contractual project posts, initially tied to project duration or a fixed term, with extension depending on performance and project need. This is not the same as a permanent scientific post.

That does not make it weak. For the right candidate, a C-DAC project role can offer serious domain exposure in public-sector technology work. But applicants should understand contract duration, remuneration, project location and renewal conditions before applying.

## Project Engineer is only one part of the list

The recruitment includes role families such as Project Associate, Project Technician, Project Support Staff, Project Engineer, Senior Project Engineer, Project Officer, Project Manager and Project Head. Some roles are technical, some are managerial, and some support programme delivery or administration.

Candidates should not apply only by title. A Project Engineer role in AI may require a different file from a Project Engineer role in embedded systems or cyber security. A Project Manager post may ask for years of experience that a fresher cannot prove.

## C-DAC project staff posts sit inside India IT hiring

Pagalishor recently covered how [IT hiring in May 2026 is selective but active](https://www.pagalishor.in/articles/it-hiring-may-2026-gccs-and-tcs-nqt-shape-fresher-search). C-DAC's June cycle adds a public-sector technology route to that picture. It is not a campus mass-hiring drive. It is a domain-heavy project route.

That distinction matters for candidates. A fresher with only a basic project may be better suited to entry-level assessments or trainee roles. A candidate with a strong M.Tech, MCA, cyber security project, VLSI exposure, HPC background, AI/ML portfolio or domain internship may find C-DAC more relevant.

## Eligibility varies by centre and role

Current coverage lists a wide range of accepted qualifications across the centre-wise advertisements: BE, B.Tech, ME, M.Tech, MCA, M.Sc, Ph.D., ITI, diploma, graduation, MBA, CA, CMA, CS, LLB and other relevant qualifications. That range is broad because the roles are broad.

The useful action is not to ask whether C-DAC accepts graduates in general. The useful action is to open the chosen centre advertisement and check the exact post. Qualification, experience, age and domain wording should be read together.

## No fee is reported for the June cycle

Current coverage says C-DAC is not charging an application fee for this JIT June 2026 cycle. Candidates should still confirm that on the official careers page for the chosen advertisement before submission.

The no-fee point is also a safety signal. If a private message asks for money to secure a C-DAC project role, interview slot or shortlist position, do not pay. Use official C-DAC routes only.

## How to apply for C-DAC project staff posts

1. Open the C-DAC careers portal and locate the June 2026 JIT cycle advertisement.

2. Choose the centre and role family that match your qualification and domain.

3. Read the qualification, experience, age, remuneration, project duration and selection details for that exact post.

4. Prepare resume, education records, experience certificates, category documents, photograph and signature.

5. Submit the online application before 20 June 2026 and save the confirmation.

## Selection may involve screening, tests and interviews

Current coverage lists screening based on qualification and experience, followed by written test where applicable and interview for shortlisted candidates. Candidates should not assume every post has the same selection path.

Technical posts may examine project depth, coding, system knowledge, domain fundamentals or problem-solving. Managerial and senior posts may focus more on delivery experience, team handling, stakeholder management and project outcomes.

## Project resumes need evidence, not tool lists

C-DAC project roles are not helped by a resume that simply lists Python, Java, React, cloud, cyber security and AI. Candidates should show what they built, tested, deployed, analysed or maintained. A small but clear project is stronger than a long tool inventory.

For AI and data roles, name the problem, dataset type, model or method, evaluation approach and result. For cyber security, explain logs, controls, testing, identity, network or incident work. For embedded and VLSI roles, describe boards, tools, constraints and verification.

## Experience certificates can decide senior roles

Senior Project Engineer, Project Manager and Project Head roles are likely to depend on experience proof. Candidates should keep employer certificates, appointment letters, role records, project descriptions and relieving documents ready.

Post-qualification experience should be counted exactly. If the advertisement says experience after a required degree, earlier work may not count. Do not round up months or include internships unless the advertisement allows it.

## C-DAC centres may have different domain needs

One centre may need cyber security or full-stack staff; another may need VLSI, HPC, embedded systems, quantum computing, programme delivery or administrative support. That is why a single application strategy is weak.

Candidates should shortlist two or three centre-role combinations, then read the official details. Applying everywhere with the same resume can dilute the application and increase mistakes.

## Location should be checked before applying

The cycle covers multiple C-DAC centres and project sites. Candidates should check whether the post is tied to a city, project office, client site or all-India deployment. A candidate who cannot relocate should not ignore the location field.

Hybrid or remote assumptions should not be made. Unless the advertisement clearly says otherwise, treat these as on-site project roles and plan accordingly.

## Remuneration depends on role level

Current coverage lists a broad monthly remuneration range across role families, from lower project-support bands to senior project and management bands. Candidates should read the exact centre advertisement because pay differs by role, experience and domain.

Compare remuneration with contract duration, city cost, project exposure and next career step. A lower initial amount may still be useful if the role gives strong domain experience. A higher title may not be worth it if the candidate cannot meet the experience requirement.

## C-DAC differs from private IT fresher hiring

Private IT fresher drives often filter through aptitude tests and broad coding rounds. C-DAC project hiring can be narrower. The candidate may need to show domain fit earlier, especially for AI, security, systems, electronics, embedded, HPC or government technology projects.

Candidates also comparing company fresher routes can read Pagalishor's [IT fresher hiring 2026 guide](https://www.pagalishor.in/articles/it-fresher-hiring-2026-shifts-to-apprentice-roles). C-DAC is a better fit when the candidate can point to serious coursework, project work or experience in the advertised domain.

## Documents should be checked before 20 June

Do not wait for the last week to assemble records. Keep degree certificates, marksheets, CGPA conversion where needed, category proof, experience letters, resume, photograph and signature ready before starting the application.

Candidates with changed names, different institute names, backlogs, pending results or unclear experience timelines should read the advertisement carefully. If a required proof is not available, the form may not be safe to submit.

## Interview answers should be project-specific

If shortlisted, candidates should expect questions about their own work. Prepare two or three projects in detail: what the goal was, what tools were used, what problem appeared, what decision was made, and what result followed.

Do not claim work that cannot be explained. A panel can usually tell the difference between a candidate who built something and a candidate who copied a project title from a course.

## Administrative and support roles need the same care

Not every C-DAC role is a coding role. Project Officer, support staff, administrative associate and programme delivery roles can require finance, legal, HR, procurement, documentation, coordination or stakeholder experience. These applicants should not copy a software resume format.

Show process ownership, reporting, compliance, team coordination, document control and project follow-up. C-DAC project work can be documentation-heavy, and that is a real skill.

## Candidates should avoid duplicate careless applications

When a recruitment has many centre advertisements, it is tempting to apply quickly to every visible link. Slow down. If the portal permits multiple applications, each one should still be accurate and role-specific. If the advertisement restricts applications, follow that rule.

A careless duplicate can create confusion later. Keep a tracker with centre, post, advertisement number, submission date, login details and status.

## Frequently asked questions

Q: What is the last date for C-DAC June 2026 JIT recruitment? A: Current recruitment coverage lists 20 June 2026 as the last date. Candidates should confirm it on the C-DAC careers advertisement for the chosen centre.

Q: Is this a permanent C-DAC recruitment? A: Current coverage describes these as contractual project staff posts. Candidates should read duration and renewal details in the centre-wise advertisement.

Q: Which candidates should consider applying? A: Candidates with qualifications and domain fit matching the exact centre advertisement should apply. The cycle includes roles for technical, project, support and management profiles.

Q: Is there an application fee? A: Current coverage says no application fee is charged for the June 2026 JIT advertisements, but candidates should verify this on the official C-DAC page before submission.

## The best application is centre-specific

The C-DAC June cycle is large enough to attract casual applications, but the serious candidate will work differently. Choose the centre, choose the role, read the domain, then shape the resume around evidence.

If the post fits, apply before 20 June and keep the confirmation safe. If it does not fit, use the cycle as a map of where public-sector technology demand is moving and target a better-matched role next.

## Domain matching should happen before resume editing

C-DAC project posts can sound similar from the outside, but the domain labels can change the real job. AI, VLSI, cyber security, full-stack development, HPC, embedded systems and programme delivery are different tracks. Candidates should choose the track first, then edit the resume for that track.

A resume for cyber security should show logs, networks, identity, vulnerabilities, tools or incident handling. A resume for full-stack work should show a working application, database, API, deployment and debugging. A resume for VLSI or embedded work should show hardware, simulation, verification or board-level exposure where available.

## Freshers should be honest about role fit

Some project roles may accept early-career candidates, while others clearly need experience. A fresher should not spend the whole application window forcing a senior post. Look for Project Associate, Project Technician or junior project roles where qualification and project evidence fit better.

That does not mean underselling yourself. It means applying where the evidence is strongest. A clean junior application with a real project and clear documents is better than a senior application that cannot survive experience screening.

## Experienced candidates need a tighter project file

Experienced applicants should prepare a short project file before interview: project name, employer, duration, role, tools, domain, team size, outcome and one hard problem solved. Keep it factual and non-confidential. C-DAC panels may care about public-sector technology delivery, but candidates should not disclose restricted employer or client details.

If experience spans several employers, align dates and designations carefully. Screening teams often reject unclear timelines, especially when a role requires a specific number of years in a domain.

## The June 20 deadline leaves little room for correction

The window is current, but it is not long. Candidates should complete document checks well before 20 June, especially if they need experience certificates, category proof, CGPA conversion or updated resumes from older records.

Use the last two days only for final review, not first reading. A centre-wise project recruitment can contain small conditions that matter: maximum age, contract term, location, document upload size, interview mode and whether a written test may be called.

## Candidates should keep one application tracker

The June cycle can involve several centres and advertisement links. Keep a tracker with centre name, advertisement number, post title, domain, last date, submitted status, login ID and next expected communication. This helps candidates avoid missing an interview email or confusing one centre's rule with another.

The tracker should also record which resume version was used. If a candidate applies to AI, cyber security and project support posts, the same resume may not have gone to every centre. Knowing the submitted version makes interview preparation easier.

## Contract roles should be judged by learning value too

A contractual project role should be evaluated differently from a permanent post. Candidates should ask what the project teaches, which tools or systems it exposes them to, whether the city is workable, and whether the role improves the next job move. C-DAC can be valuable when the project domain is strong.

At the same time, candidates should read renewal and duration conditions plainly. Do not treat a project appointment as permanent unless the advertisement says so. A good application decision balances project quality, pay, city, contract length and future relevance.

## Shortlisted candidates should prepare for practical discussion

C-DAC interviews may move quickly from qualification to practical work. Candidates should be ready to explain a recent project without reading from the resume. What was the objective, what did you personally do, which problem appeared, and what changed after your work? Those answers should be clear in two minutes.

For senior applicants, prepare one delivery example and one technical example. For junior applicants, prepare one academic or internship project that can survive follow-up questions. Specific, honest answers are stronger than broad claims about many tools.

## Applicants should check official communication carefully

After submission, candidates should watch the email address and phone number used in the form. Shortlisting, test and interview communication may come with a limited response window. Missing a message can matter as much as a weak application.

Check the sender domain, keep attachments safe, and do not share login details with anyone offering paid interview help. A legitimate recruitment process will not need a private payment to move an application forward. Save every official message because interview schedules can change quickly. Keep a backup of the submitted resume, certificates and application confirmation in one folder so the same file can be produced when a centre asks for documents before interview. That habit prevents avoidable last-minute mistakes later too. Candidates should also keep the centre advertisement saved, because the interview panel or document team may refer to the exact role conditions later.