Bidgely Recruitment Process
Interview Experience
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other as...
Full Details
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other aspirants, and the portal where you can apply. Table of Content About Company Recruitment Process Academic Criteria Written Round Technical Rounds HR Round About Company: Bidgely is used by electric utilities around the world to transform how they engage with consumers. The SaaS-based service applies machine learning to utility meter data to itemize the amount and cost of energy used by various home appliances. With consumer-friendly Web and mobile communications, Bidgely provides personalized and actionable insights that help consumers save energy and enable utilities to build enduring customer relationships. Bidgely is funded by leading cleantech investor Khosla Ventures, as well as strategic investment from some of the largest utilities in the world – RWE, E.On, and Constellation. Bidgely, a technology company offers disaggregation-powered utility solutions. It offers HomeBeat, a cloud-based load disaggregation software that provides appliance-level energy consumption. Bidgely, an energy analytics platform also offers energy efficiency and consumer engagement solutions for utilities markets. The company serves utilities that serve residential customers worldwide. Bidgely was formerly known as MyEnerSave Inc. The company was founded in 2011 and is based in Mountain View, California with an additional office in Bengaluru, India. Bidgely won the Vendor To Watch award at the 2014 Municipal Smart Grid Summit. Bidgely and Chubu Electric Power are working together to become the first to bring residential disaggregation technology to Japan. Recruitment Process: Bidgely conducts 4-5 rounds to select freshers as Software Developers in their organization. Written Round Technical Round 1 Technical Round 2 Technical Round 3 Technical Round 4 HR Round Academic Criteria: 65 percent or above in B.Tech, Class X and XII. No backlogs at the time of interview Written Round: The Written round consists of two major sections namely General Aptitude Test and Coding Test. The General Aptitude Test has a mathematical reasoning part and a logical reasoning part. The coding section generally consists of 2 problems.
NOTE: You have to solve at least one coding question to go to the
next round. It doesn’t matter how many MCQs you have solved. Technical Rounds: The students who clear the written round are called for a Technical Interview. To clear this round you should be clear with your basics. You should be prepared with Data structures and Algorithms, DBMS, Operating Systems, Networking, and OOP concepts. Students will be expected to write codes in the interview. They also ask questions about resumes. You may be asked puzzles in this round. To be prepared for puzzles you can practice from our Puzzles section.
HR Round: In this round, you can expect general HR questions like: Why do you think this role is best suited for you? What is the need for the tester when there is already a developer? Difference between tester and developer. Tell your 3 strengths and 3 weaknesses. Interview Experiences: It is always beneficial if you know what it is to be there at that moment. So, to give you an advantage, we provide you with the Interview Experiences of candidates who have been in your situation earlier. Make the most of it. Bidgely Interview Experiences Questions Asked in Bidgely: What is user acceptance testing? What are phases in RAD model? Are linked lists considered linear or non-linear data structures? What are functional and non-functional requirements? Where to Apply ? Bidgely careers Bidgely Official Website
About Bidgely Interview Reports
This question was reported by a candidate who interviewed at Bidgely. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Bidgely are the higher-signal extractions to take from this report.
For broader preparation context, the Bidgely interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Bidgely reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Bidgely Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Bidgely reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.