Honeywell is a global industrial technology company spanning aerospace, automation, building technologies, and performance materials. Its India engineering hubs hire software and embedded systems engineers to build avionics, IoT, and industrial control products for customers worldwide.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Honeywell India does not publish one eternal CGPA for every requisition. Campus cells usually print a number; off-campus Software/Embedded Engineer I posts list degree + batch + skills. Read the mailer.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, college % list, sometimes GD | Aptitude + technical bar |
| careers.honeywell.com | Requisition ID (e.g. SE I / Embedded I at RMZ Ecoworld) | Same interview flavour when invited |
| Referral | Visibility | You still sit the test |
Off-campus does not mean easier quant. It often means more ECE/CS applicants who already interned on C/RTOS.
Is 7.0 CGPA enough? It matches many campus JDs (or 70%). Older Hitbullseye language used 65% in 10th, 12th, and graduation with no backlogs. If your mailer says 65% throughout, a 7.2 B.Tech with 62% in 12th can still fail the cell filter. A 7.1 who finishes the technical MCQs and can talk through a UART driver beats an 8.8 who only memorised OS definitions.
What helps the resume screen: One embedded or systems project, any internship, C on the skills line if the role is firmware. Certifications are optional after the OA, not instead of it. See certifications.
Academic snapshot
Marks: 7.0+ CGPA or 70% on many campuses; 65% throughout on some older pages
Degree: B.E./B.Tech/M.E./M.Tech as listed (CS/IT/ECE/EEE common)
Backlogs: None active at joining
Year: Final year campus; 2024-2026 batches on many 2026 off-campus posts
Skills they actually filter
OA: Aptitude speed + branch/core MCQs
Embedded: C/C++, RTOS, microcontrollers, peripherals
Software: DSA easy-medium, OOP, CS fundamentals
Languages: C, C++, Java, Python
| Item | Typical expectation | Reality check |
|---|---|---|
| Graduation | 7.0 / 70% on many JDs | Mailer wins |
| 10th & 12th | 65%+ on older pattern pages | Keep scans |
| Branches | CS/IT/ECE/EEE | Broader BE on some fresher guides |
| Backlogs | None active | Clear before joining |
| Experience | 0-2 or 0-3 years on some I-level posts | Freshers welcome when the JD says so |
Good fit: You like constrained software (timing, memory, safety), you can finish 30 aptitude questions without a calculator meltdown, and you will relocate to Bengaluru or another listed hub. ECE students with real C lab work clear embedded I every year.
Harder path: You only practiced LeetCode hard graphs; you freeze on digital/microcontroller MCQs; you want pure WFH product work. Honeywell HR is polite and blunt on site and domain. A high CGPA with zero C is a common embedded-track fail.
Branch myth: CSE is not auto-selected for Embedded Engineer I. Firmware interviews still ask bitwise and RTOS. ECE is not blocked from Software Engineer I if DSA and OOP are real.
Gaps: One year is often discussed; longer gaps need a story. Full-time degrees. Active backlogs are a campus-cell hard stop more often than a “case by case.”
Download 2026 Honeywell placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Honeywell does not publish a permanent official paper set. “Previous year papers” here are pattern trainers for the aptitude + technical written and for interview themes. They are not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Aptitude (30/30) | Quant, logical, English under a hard clock |
| Technical (35/30) | Branch/core MCQs; C output; OS/DBMS/CN light |
| Coding (if present) | Easy arrays/strings, not contest graphs |
| Technical interview | Projects, C/embedded or DSA, circuits/CS |
| HR | Why Honeywell, relocate, 5-year plan |
Think of papers as simulators for 60-minute stamina. Honeywell reuses themes (percentages, blood relations, C snippets, digital gates) more than exact clones. If you can finish a 2024-style 65-question paper cleanly, a 2026 written will feel familiar even when the microcontroller question is new.
| Theme you saw in a set | What to drill next | Why Honeywell asks it |
|---|---|---|
| Time-work / percentages | Speed without silly arithmetic | 30-minute aptitude |
| Syllogism / seating | 45-second skip rule | Same |
| C output / pointers | Dry-run on paper | Technical + embedded interview |
| Digital / MCU | Gates, timers, ADC | ECE technical half |
| OS / DBMS MCQs | Process vs thread, keys | CSE technical half |
| Arrays / two pointers | One complete function | Coding add-on / software interview |
Honeywell hires freshers through campus cells, honeywell.com careers, and referrals. After eligibility, the shape is conglomerate: a timed aptitude+technical paper, then a domain interview, then HR on city and commitment.
Campus recruitment
PPT → resumes via cell → written/OA on campus or remote → technical → HR. Sometimes GD on older playbooks.
Online applications
honeywell.com careers. Search Software Engineer I / Embedded Engineer I. Upload resume; wait for assessment mail.
Referrals
Help the screen. You still need the 30/30 aptitude clock and a technical cabin you can survive.
College list vs 7.0/70% (or 65% throughout). Branch match. This is a gate. Put C projects and internships above a 12-line objective.
| Section | Questions | Time | What shows up | Pass habit |
|---|---|---|---|---|
| Aptitude | 30 | 30 min | Quant, logical, English | Skip after 45 seconds |
| Technical | 35 | 30 min | Branch/core, C snippets, CS/ECE MCQs | Eliminate options |
Student tip: 30 minutes for 30 aptitude is not “easy.” The fail mode is one DI table that ate 8 minutes. Drill percentages and one seating skip rule until they are boring.
No stable public cutoff percentage. Aim to clean the easy 70% of each section; the last 30% separates people who guessed.
Deeper OA notes: Honeywell online assessment.
Older pages put GD between written and PI. If it appears: one clear point on industrial automation or aviation safety, listen, do not filibuster. If the 2026 mailer has no GD, skip debate-club prep.
Software Engineer I: projects, OOP, DBMS, one coding question (binary search, two pointers, strings), OS light.
Embedded Engineer I: C memory model, volatile, interrupt vs polling, RTOS task vs ISR, a peripheral (UART/SPI/I2C), maybe a schematic-level question. DO-178C is a plus on aerospace posts, not a quiz of the entire standard.
Both: “Walk me through this project.” What failed in lab?” About 70% of OA survivors who can explain their own code clear this if they do not freeze on basics.
Why Honeywell (aerospace/automation/buildings, not “I like coding”), relocate to Bengaluru / Hyderabad / Madurai, strengths, 5-year plan, joining vs exams. Communication in complete sentences. Around 90% of tech-clear candidates get offers if location is honest.
| Phase | Duration | What happens |
|---|---|---|
| Resume / cell list | 3-10 days | Shortlist |
| OA / written | 1 day | 60-minute style paper |
| Interview scheduling | 2-14 days | Technical + HR |
| Offer | 1-7 days | Letter + background |
Total: often 2-6 weeks for campus batches; off-campus requisitions can sit longer in ATS.
| Minute | Move |
|---|---|
| 0-30 | Aptitude: easy first, mark hard, never start a 5-minute puzzle |
| 30-55 | Technical: C/core first, guess only after eliminating two |
| 55-60 | Review marked; submit |
You can apply to both requisitions if the portal allows. You cannot prep both at GATE depth in 14 days.
If embedded I is the goal: 60% C + RTOS vocabulary, 25% aptitude, 15% digital/MCU. Write a 50-line driver-style C program (ring buffer, state machine) and be able to explain it.
If software I is the goal: 40% aptitude, 30% CS MCQs, 20% one coding language, 10% HR. Finish easy-medium arrays under 25 minutes.
If the JD is mixed: default to C plus one DSA pattern. Honeywell would rather hear a clean linked-list story than a fake Kubernetes tour.
If Embedded Engineer I is on your form, practise answering these out loud in under 90 seconds each:
static on a function vs on a local variable.volatile on a status register?printf, blocking locks)?If you cannot answer 1-5, you are not interview-ready even if your OA score was fine. Write a 50-line ring buffer or cooperative scheduler and be ready to draw it. That beats a “RTOS project” that was a vendor demo.
Honeywell software interviews are not Codeforces-style contests. Finish:
Narrate complexity. Test n=1. That is the bar.
You do not need a private-pilot licence. You need one honest sentence.
Saying “I have not worked DO-178C; I understand it is a safety-process standard and I can learn the team’s checklist” is adult. Quoting a random DAL level you saw on Reddit is not.
10th and 12th marksheets, all semester sheets, ID, resume one page, internship letter if any. Services-style cells still fail people on a missing 12th PDF. Honeywell background checks will match names and dates. Keep a charger and the assessment login email.
You do not need a 400-page CAT book. You need no silly blanks and a technical half you can still finish.
Volatile: “Tells the compiler the value can change outside the program, e.g. a hardware register.” I would not use it as a substitute for a lock.”
RTOS vs bare metal: “Bare metal loop if the product is simple; RTOS when I have multiple timing-critical tasks and need priorities.”
Why Honeywell: “I want to write software that sits next to hardware and safety constraints, not only CRUD.” Aerospace/automation is that.” Vague “Fortune 100” answers underperform.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Honeywell invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Honeywell sits around ₹8-15 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Campus and fresher guides commonly cite 7.0+ CGPA or 70% (some older pattern pages listed 65% throughout 10th/12th/grad) with no active backlogs. Degrees: B.E./B.Tech/M.E./M.Tech, often CS/IT/ECE/EEE for Software Engineer I and Embedded Engineer I. Final-year and 2024-2026 batches appear on 2026 off-campus posts. Always verify the campus JD or Honeywell careers requisition.
What you are training for: Typical fresher loop: resume screen → Honeywell Online Assessment (historically aptitude 30Q/30min + technical 35Q/30min) → technical interview → HR. Older Hitbullseye notes also mention a GD. Campus and careers.honeywell.com off-campus use the same technical bar; embedded roles add C/RTOS depth. Timeline often 2-6 weeks.
Short version of the prep split: Split time: 40% timed aptitude (30 questions in 30 minutes), 35% branch/core technical MCQs or C/embedded, 15% one coding language you can defend, 10% HR (Why Honeywell, relocate). Embedded track: C, RTOS, peripherals. Software track: DSA easy-medium plus OOP. Full plan: /honeywell/preparation-guide/.
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Honeywell previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Honeywell drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Honeywell usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Honeywell?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Honeywell-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Honeywell story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Honeywell papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Honeywell papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Honeywell-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Figures are candidate-reported India bands as of August 2026. Honeywell often does not print CTC on public fresher posts.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer I / Embedded Engineer I | ₹8-15 LPA | Primary band for this hub; city and team vary |
| Intern (software) | Stipend, not CTC | Separate requisition; some public posts cite a wide monthly range |
| Experienced I/II | Higher | Not campus default |
Confirm base vs bonus vs ESPP on the written offer. Do not treat Instagram “₹8-16 LPA” as a negotiation floor before you have a letter.
Health insurance (self and family in public explainers), performance bonus, learning platforms, ESPP on some offers, on-site Bengaluru campus facilities. Site is still the real filter: embedded teams are office-heavy.
Know ₹8-15 LPA as the chatter band. Ask split and joining date. Honeywell is not a services GET where everyone hears the same 4 LPA slide.
Two named fresher titles
Software Engineer I and Embedded Engineer I keep showing up on 2026 Bengaluru posts (RMZ Ecoworld). Prep the one on your application.
Written still conglomerate-shaped
Aptitude + technical MCQs (30+35 in 60 min on cited pages) remain more common than a 2-question HackerRank-only screen.
GD is optional
Older 3-round (written-GD-PI) notes exist. Many recent loops skip GD. Read the PPT.
C is not optional on firmware
RTOS, peripherals, and C++ on embedded JDs. DSA-only prep is the wrong sport for those requisitions.
Net for 2026: do not wait for a “new coding-only pattern.” Time the 30/30 split. Pick embedded or software and build one honest project story.
Yes. Free Honeywell placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
Cited Hitbullseye split: Aptitude 30Q/30min + Technical 35Q/30min (65Q/60min). 2026 guides also mention quant, logical, English, coding, technical MCQs. Confirm your email. Details: online assessment.
Older pages yes (written → GD → PI). Many 2024-2026 campus notes skip GD. Follow the PPT, not a 2018 blog.
Resume → OA/written → technical interview → HR. Same ladder campus and off-campus; embedded vs software changes the technical cabin. Often 2-6 weeks.
Usually 3 (OA, technical, HR). Count GD only if your drive lists it.
Both titles are active on 2026 India posts. Read the requisition. Do not send a pure DSA resume to a firmware JD.
Commonly 7.0+ CGPA or 70%, listed engineering degrees, no active backlogs. Some older pages: 65% throughout 10th/12th/grad. CS/IT/ECE/EEE appear most. Verify the JD. Criteria are in the same band as recent cycles unless your mailer changed.
C/C++ for embedded; Java/Python also for software. Assembly is a plus, not an OA default.
Yes. ECE is a natural embedded I fit. Software I is open when the JD lists ECE and you can do DSA/OOP.
Prefer zero active. Campus cells usually pre-filter. Clear before joining either way.
Candidate-reported (August 2026): about ₹8-15 LPA for SE I / Embedded I. Confirm the letter. Locations: Bengaluru, Hyderabad, Madurai.
Bengaluru (including RMZ Ecoworld), Hyderabad, Madurai. HR will ask relocation. Embedded is usually office-first.
Time 30/30 aptitude+technical mocks, then C/RTOS or DSA by track, then one project diagram. Guide: preparation guide.
Make the 30-minute aptitude skip rule automatic, then drill C or core MCQs for the technical half. In interview, tie your project to a sensor, controller, or safety constraint.
All four hire India engineering freshers into industrial/embedded-ish work. Honeywell and Bosch/Siemens lean product/conglomerate domain; LTTS is more ER&D services. Prep C + aptitude for all; add the specific OA clock for Honeywell (30+35).
No. Awareness is a plus on some aerospace JDs. A working C project beats a paid certificate with zero lab work.
One page. C/C++ or Java/Python matching the requisition. One project with a constraint (timing, memory, lab bug). Internship module first if you have one. No 12-line objective. No fake RTOS.
Different clock: 30+35 in 60 minutes on cited pages, heavier branch/core MCQs, lighter than a 2-question product OA. Aptitude skip rules still decide the first half.
Detailed public 2025-2026 Honeywell campus blogs are thinner than TCS write-ups. Use the notes below as vibe checks, then return to timed mocks. Full pages: interview experience.
Hitbullseye pattern page (still the most cited written): 65 questions in 60 minutes, 30 aptitude + 35 technical, plus an older 3-round (written, GD, PI) and 65% academic filter. Takeaway for juniors: even if your 2026 drive drops GD, the clock on aptitude is the first killer. Practice 30 questions in 30 minutes until it is boring.
Embedded Engineer I off-campus chatter (2026 Bengaluru posts): JDs emphasise C/C++, RTOS, peripherals, sometimes DO-178C as a plus, 0-3 years. Students who only prepared HackerRank arrays report a rude shock in technical. Takeaway: read the requisition title. Firmware is a different sport.
Software Engineer I cabin (composite): Project walkthrough, OOP vs C, one easy coding on a shared editor or paper, “why Honeywell not a services company.” Candidates who named aerospace/automation with one concrete interest (avionics software, building controllers, industrial IoT) sounded more hireable than “global brand.”
What to steal: 60-minute split; C on paper for embedded; one block diagram; honest relocation.
What to ignore: Memorising a 2018 GD topic list; quoting ₹16 LPA as guaranteed; skipping 12th marksheet because B.Tech CGPA is high.
Selected vs rejected patterns: Helped: complete technical MCQs, calm C explanation, site yes. Hurt: blank aptitude, fake RTOS experience, surprise at Bengaluru office norms.
Campus written composite: Students who treated the technical 35 as “GATE ECE entire syllabus” ran out of time. Students who treated it as 35 medium MCQs (C output, one digital, one OS) finished and still had review minutes. Takeaway: breadth with skip rules, not a PhD on one timer question.
Internship-to-I-level: Some 2026 posts list 0-2 or 0-3 years on Engineer I requisitions. A 6-month embedded intern with a driver story can beat a 8.5 CGPA with only academic labs. Put the intern module first on the resume, not the club secretary line.
Office-first surprise: Candidates who asked for full remote on an MCU team in the HR cabin created an awkward silence. Ask about hybrid after you have the letter if the JD is firmware. Asking “is Bengaluru mandatory” is fair; pretending you did not read RMZ Ecoworld is not.
GD if it appears: one industrial point (why automation needs software plus hardware), listen, invite a quiet teammate in. Do not filibuster. If 2026 mailer has no GD, do not invent one.
Honeywell is a conglomerate engineering hire. The people who clear treat the 30-minute aptitude clock as a skill, treat C as a language they can dry-run, and treat Bengaluru as a real city they will move to. The people who fail treat it as a services aptitude mill or as a remote LeetCode company. Pick the right sport this week. Use timed papers on this site, then the preparation guide for the calendar. Keep the interview experience page for cabin notes and the HR page for Why Honeywell and relocate stories. Do not cram a new RTOS book the night before. Error-log only. Sleep. Bring marksheets. That is the whole job once eligibility is done.
If two industrial offers arrive (Honeywell vs Bosch/Siemens/LTTS), compare team (embedded vs software), city, and whether you will actually write C. A higher CTC on a pure ticketing team may be the wrong five years. Ask the hiring manager what the first project is. “Controller firmware” and “internal web tool” are different careers that share an Engineer I title. Read the requisition twice. Then decide. Keep every email. Background check will match 10th and 12th. A missing scan is a silly way to stall after you cleared the 65-question paper. Name spelling must match Aadhaar and marksheets. That is not optional bureaucracy; it is the last filter. If a recruiter calls with a different city than the requisition, get it in writing before you decline another offer. Verbal city changes are how people get stranded. Screenshot the JD. Save the PDF. Then join or walk. Either is fine. Confusion is not. If the letter lists RMZ Ecoworld and a friend says “Hyderabad is also possible,” wait for HR email, not WhatsApp. That one habit saves a wasted resignation. Screenshot the requisition ID with the city before you decline anything else.