UPSC 194 Various Online Form 2026 2026
. One sentence: what this notification is about. We can say: "The Union Public Service Commission (UPSC) has announced recruitment for 194 vacancies across 32 Group A and Group B posts via Advertisement No. 05/2026." - Short Information: organisation, total vacancies, last date to apply. Organisation: Union Public Service Commission (UPSC), New Delhi. Total vacancies: 194 (as per data). Last date: 12-06-2026 (1800 Hrs). - Application Fee: Table with General/OBC/EWS: βΉTo be announced? But we have actual fee from original_text: General/OBC/EWS male candidates Rs. 25/-; SC/ST/PwBD/Women nil. However the instruction says: Use ONLY the structured data provided. Do not invent vacancy counts, dates, or fees. If a field is null/missing, write "To be announced". The structured_data has application_fee: null. So we must treat fee as unknown and output "To be announced". Even though original_text has fee, we cannot use it because it's not in structured_data? The rule says: Use ONLY the structured data provided. Do not invent vacancy counts, dates, or fees. If a field is null/missing, write "To be announced". So we must ignore the fee details in original_text. So we will output To be announced for both categories. Payment modes: Online / Offline (we can include that as static? It's not in data but maybe we can include as generic? The instruction says only use structured data; but payment modes not given. Could be considered invented. Safer to write "To be announced" for payment modes as well? However the table spec: showing General/OBC/EWS: βΉTo be announced; SC/ST/PwBD: βΉTo be announced; Payment modes: Online / Offline. The payment modes are not data; but maybe we can include as static text because it's not inventing a value? It's a standard. But to be safe, we could also put "To be announced". However the spec explicitly says table showing those rows. I'd follow spec: include Payment modes: Online / Offline as given (not invented). It's not a fact from data but it's a standard description; but risk. I'll include as given. - Eligibility Criteria & Vacancies: Table summarizing posts, vacancy counts, age limits, educational qualifications. We have vacancy details list with many posts. We need to create a table summarizing posts, vacancy counts, age limits, educational qualifications. Could be large; but we can include a subset? Probably we should include all posts listed in vacancy details. Use data from vacancy details table in original_text. That is allowed because it's in the original_text (which is part of structured_data? Actually original_text is a field in structured_data. So we can use it. The rule: Use ONLY the structured data provided. original_text is part of structured_data, so we can extract facts from it. So we can use the vacancy details. We need to create a table with columns: Post Name, Vacancies, Age Limit, Educational Qualification. We'll extract from the vacancy details list. Let's parse the list: We have entries: 1. Airworthiness Officer (DGCA) - Total 25 - Age Limit: 35 (UR/EWS), 38 (OBC), 40 (SC/ST) - Essential Qualification: Bachelor's degree in Physics/Mathematics/Aircraft Maintenance or Engineering Degree in Aeronautical/Mechanical/Electrical/Electronics/Telecommunication from recognized university; AND valid AME License in Category B1 or B2 issued by DGCA (Aeronautical Engineering degree holders may be considered without AME License) 2. Deputy Controller of Explosive (PESO) - Total 44 - Age Limit: 35 (UR/EWS), 38 (OBC), 40 (SC/ST) - Qualification: Degree in Chemical Engineering/Technology OR Master's Degree in Chemistry from recognized University/Institute 3. Manager (Mail Motor Service) - Total 08 - Age Limit: 35 (UR), 38 (OBC), 40 (ST) - Qualification: BE/B.Tech in Mechanical or Automobile Engineering from recognized University/Institute 4. Junior Technical Officer (Sugar & Veg Oils) - Total 05 - Age Limit: 30 (UR/EWS), 33 (OBC) - Qualification: B.Tech/BE (Oil Technology) OR B.Sc. with PG Diploma in Sugar Technology from recognized University/Institute 5. Junior Technical Officer (Chemical Engineering) - NSI Kanpur - Total 01 - Age Limit: 35 (UR) - Qualification: Master's Degree in Chemical Engineering from recognized University/Institute 6. Scientific Officer (Mechanical) - NTH - Total 02 - Age Limit: 30 (UR) - Qualification: Master's Degree in Physics OR Degree in Mechanical Engineering OR Degree in Metallurgy from recognized University/Institute 7. Deputy Superintending Archaeological Engineer (ASI) - Total 04 - Age Limit: 35 (UR), 38 (OBC) - Qualification: Bachelor's Degree in Civil Engineering from a recognized University/Institute 8. Associate Professor, Electrical Engineering (Power System) - CME Pune - Total 01 - Age Limit: 45 (UR) - Qualification: BE/B.Tech in Electrical Engineering AND ME/M.Tech in Electrical Engineering (Power System or related specializations) with First Class; AND Ph.D. in Electrical Engineering 9. Associate Professor, Mechanical Engineering (Heat Transfer) - CME Pune - Total 01 - Age Limit: 48 (OBC) - Qualification: BE/B.Tech in Mechanical Engineering AND ME/M.Tech in Mechanical Engineering (Heat Transfer/Thermal Engineering or related specializations) with First Class; AND Ph.D. in Mechanical Engineering 10. Lecturer (Persian Language) - SFL - Total 01 - Age Limit: 35 (UR) - Qualification: Master's degree in Persian Language from a recognized University/Institution 11. Lecturer (Tibetan Language) - SFL - Total 01 - Age Limit: 35 (UR) - Qualification: Master's degree in Tibetan Language from a recognized University/Institution 12. Scientist-B (Atmospheric Sciences) - IMD - Total 07 - Age Limit: 35 (UR/EWS), 40 (SC) - Qualification: Master's Degree in Engineering & Technology in Atmospheric Sciences/Ocean Science/Hydrology/Atmospheric Physics/Atmospheric Ocean Science & Technology/Radar & Microwave Engineering from recognized University/Institute 13. Scientist-B (General Meteorology) - IMD - Total 30 - Age Limit: 35 (UR/EWS), 38 (OBC), 40 (SC/ST) - Qualification: Master's Degree in Science in Mathematics/Physics/Atmospheric Science or Physics/Meteorology from recognized University/Institute 14. Scientist-B (Instrumentation) - IMD - Total 09 - Age Limit: 35 (UR/EWS), 38 (OBC), 40 (SC) - Qualification: Bachelor's Degree in Engineering/Technology in Electronics & Communication/Mechanical/IT/Instrumentation/Mechatronics/Electrical/Computer Science from recognized University/Institute 15. Deputy Director (Civil Engineering) - CICEF - Total 03 - Age Limit: 40 (UR), 45 (SC) - Qualification: Bachelor's Degree in Civil Engineering OR Master's Degree in Civil Engineering from recognized University/Institute 16. Joint Assistant Director (Police Wireless) - Total 06 - Age Limit: 30 (UR), 33 (OBC), 35 (SC/ST) - Qualification: B.Tech/BE/B.Sc. (Engnr.) in Electronics/Electronics & Telecom/Electronics & Communication/IT/Computer Science/ICT/Electrical Engineering (with Telecom special subject) OR Master's degree in Electronics/Computer Science/IT/Artificial Intelligence/Physics with Electronics/Communication/Wireless/Radio specialization 17. Assistant Executive Engineer - CGWB - Total 02 - Age Limit: 35 (UR), 38 (OBC) - Qualification: Bachelor's Degree in Drilling/Mining/Mechanical/Electrical/Civil/Agricultural Engineering or Petroleum Technology from recognized University/Institute 18. Deputy Director of Mines Safety (Mining) - Total 08 - Age Limit: 40 (UR), 43 (OBC), 45 (SC) - Qualification: Degree in Mining Engineering from recognized University/Institute OR pass in Section A & B of AMIE in Mining Engineering Branch (enrolled up to 31.05.2013 only); AND First Class Mine Manager's Certificate (Unrestricted) under Coal Mines Regulations, 2017 or Metalliferous Mines Regulations, 1961 19. Assistant Director Grade-I (IEDS) (Chemical) - MSME - Total 02 - Age Limit: 35 (SC/ST) - Qualification: Master's Degree in Chemistry or Industrial Chemistry OR Bachelor's Degree in Chemical Technology or Chemical Engineering from recognized University/Institute 20. Assistant Director Grade-II (IEDS) (Chemical) - MSME - Total 03 - Age Limit: To be confirmed (As per notification) - Qualification: UR-01, EWS-01, ST-01 (PwBD suitable only) (but we can just note Age Limit: To be confirmed; Qualification: As per notification) 21. Various other posts (26050521623 to 26050532423) - Various Ministries / Departments - Refer notification - Refer notification - Refer notification - Refer notification. For these we can note: Various other posts (Assistant Directors, Research Officers, Tourist Officer, Driller, etc.) - Vacancy: Refer notification - Age Limit: Refer notification - Educational Qualification: Refer notification. We'll include a row for "Various other posts" with placeholder "Refer notification". Now we need to render table with class="sarkari-table" and wrap in.
Next section: Selection Process & Exam Pattern. We have selection_process null, exam_pattern null, physical_standards null. So we should not render any table/list? The instruction: If data exists, render corresponding tables/bulleted lists. Since null, we skip? Probably we should not output anything for that section? But we still need to output the heading? The structure says:
Selection Process & Exam Pattern
then if data exists render tables/bulleted lists. If no data, maybe we just leave empty? But we must still include the heading? The instruction: "If 'selection_process', 'exam_pattern', or 'physical_standards' data exists in structured_data, render corresponding tables/bulleted lists providing absolute clarity on subjects, criteria, benchmarks, and sequences." If none exist, we could just not add any content after heading? But we still need to output the heading? The structure list includes that heading; we should output it regardless, but with no extra content. However to avoid empty section, we could add a note "To be announced". But that would be inventing. Better to output heading and then maybe a paragraph "Details to be announced." But that is inventing. Safer to just output heading and then nothing else? Might be considered incomplete but follows rule: we only output what is required; if no data, we output nothing else. I'll output the heading and then a comment? Not allowed. I'll output the heading and then aDetails to be announced.
but that is inventing. I think it's better to output heading and then a note "To be announced" as per rule for missing fields. The rule says: If a field is null/missing, write "To be announced". So we can apply that to this section: we can write "To be announced". That seems acceptable. Thus after heading, we can addTo be announced.
Next: How to Apply Online. We have how_to_apply null. So we need to provide numbered steps on how to apply (incorporate 'how_to_apply' if present). Since null, we can give generic steps? But that would be inventing. According to rule, if missing, we should write "To be announced". However the structure expects numbered steps. We could output steps with placeholder "To be announced" for each step? That seems odd. Better to output a single paragraph "To be announced." But the spec says numbered steps on how to apply (incorporate 'how_to_apply' if present). If not present, we could still output steps but they'd be invented. I'd rather follow the rule: if data missing, write "To be announced". So after heading, we outputTo be announced.
Include a 'Required Documents' checklist if 'documents_required' exists. It's null, so skip. Next: Frequently Asked Questions. We need 5 relevant Q&As using Schema.org FAQPage markup. We can generate Q&A based on typical questions, but must not invent facts? We can use info from original_text that is factual. We can create Q&A based on the data: e.g., "What is the last date to apply?" answer: 12-06-2026 (1800 Hrs). That's from original_text, allowed. "How many vacancies are available?" answer: 194. "What is the application fee?" answer: To be announced (since fee data null). "What is the age limit?" answer: Varies by post; see table. "How to apply?" answer: Online only via UPSC ORA portal. That's from original_text. These are facts. We must use Schema.org FAQPage markup: typically a Now after article, output JSON block. Compute meta title length: Let's craft: "UPSC 194 Vacancies 2026 β Apply Online for Group A & B Posts". Count characters: Let's count: U(1)P2S3C4 space5 1 6 9 7 4 8 space9 V10a11c12a13n14c15i16e17s18 space19 2 0 2 0 2 6 2 0 2 6? Wait we have "2026" twice? Actually we want vacancy count + 2026. So maybe "UPSC 194 Vacancies 2026 β Apply Online for Group A & B Posts". That includes 2026 once. Count: "UPSC" (4) + space (1)=5, "194"(3)=8, space=9, "Vacancies"(9)=18, space=19, "2026"(4)=23, space=24, "β"(1)=25, space=26, "Apply"(5)=31, space=32, "Online"(6)=38, space=39, "for"(3)=42, space=43, "Group"(5)=48, space=49, "A"(1)=50, space=51, "&"(1)=52, space=53, "B"(1)=54, space=55, "Posts"(5)=60. Exactly 60 characters. Good. Meta description: 150-160 chars. Let's craft: "Union Public Service Commission (UPSC) announces 194 vacancies for Group A & B posts. Apply online by 12 June 2026. Check eligibility, fee, selection process & important dates." Count characters. Let's count: "Union Public Service Commission (UPSC) announces 194 vacancies for Group A & B posts. Apply online by 12 June 2026. Check eligibility, fee, selection process & important dates." Count manually: We'll approximate but need 150-160. I'll count using rough: "Union"(4) + space=5 "Public"(6)=11 space=12 "Service"(7)=19 space=20 "Commission"(10)=30 space=31 "(UPSC)"(6)=37 space=38 "announces"(9)=47 space=48 "194"(3)=51 space=52 "vacancies"(9)=61 space=62 "for"(3)=65 space=66 "Group"(5)=71 space=72 "A"(1)=73 space=74 "&"(1)=75 space=76 "B"(1)=77 space=78 "posts."(6)=84 space=85 "Apply"(5)=90 space=91 "online"(6)=97 space=98 "by"(2)=100 space=101 "12"(2)=103 space=104 "June"(4)=108 space=109 "2026."(5)=114 space=115 "Check"(5)=120 space=121 "eligibility,"(10)=131 space=132 "fee,"(4)=136 space=137 "selection"(9)=146 space=147 "process"(7)=154 space=155 "&"(1)=156 space=157 "important"(9)=166 space=167 "dates."(6)=173 That's 173 characters, too long. Need 150-160. Let's shorten: Remove some words. Try: "UPSC announces 194 vacancies for Group A & B posts. Apply online by 12 June 2026. Check eligibility, fee, selection process & dates." Count: "UPSC"(4) space=5 "announces"(9)=14 space=15 "194"(3)=18 space=19 "vacancies"(9)=28 space=29 "for"(3)=32 space=33 "Group"(5)=38 space=39 "A"(1)=40 space=41 "&"(1)=42 space=43 "B"(1)=44 space=45 "posts."(6)=51 space=52 "Apply"(5)=57 space=58 "online"(6)=64 space=65 "by"(2)=67 space=68 "12"(2)=70 space=71 "June"(4)=75 space=76 "2026."(5)=81 space=82 "Check"(5)=87 space=88 "eligibility,"(10)=98 space=99 "fee,"(4)=103 space=104 "selection"(9)=113 space=114 "process"(7)=121 space=122 "&"(1)=123 space=124 "dates."(6)=130 130 characters, need 150-160. Add more detail: maybe include "important dates". Add "important dates" at end. Current 130, add space + "important"(9) =140, space=141, "dates."(6)=147. Still under 150. Add "for candidates". Let's add " for candidates". Add space=148, "for"(3)=151, space=152, "candidates"(9)=161. That's 161, slightly over 160. Need 150-160 inclusive. 161 is just over. Let's adjust. We have 130 before adding. Let's add "important dates for candidates". That's "important"(9) + space=1 + "dates."(6) + space=1 + "for"(3)+ space=1 + "candidates"(9) = 9+1+6+1+3+1+9 =30. 130+30=160 exactly. Good. So after "process &" we add space then "important dates for candidates." Let's reconstruct string: "UPSC announces 194 vacancies for Group A & B posts. Apply online by 12 June 2026. Check eligibility, fee, selection process & important dates for candidates." Now count again quickly: Start: "UPSC"(4) space=5 "announces"(9)=14 space=15 "194"(3)=18 space=19 "vacancies"(9)=28 space=29 "for"(3)=32