SOFTWARE ENGINEER · BANGALORE, INDIA

Hi, I'm
Bhargav Ram.

I'm a software engineer at Honeywell Technologies. I build software that helps people work with building management systems.

I like solving problems, understanding how things work, and learning something new along the way.

Based in Bangalore, India

CONNECTED BUILDINGS
BANGALORE / INDIA A connected building, from devices to softwareBuilding automation, secure access, and protocol integration. Use the buttons below to explore each layer. AUTOMATIONNiagara 4 / HVAC SECURE ACCESS802.1x / RADIUS CONNECTED SYSTEMSBACnet / IP

Software tools for working with Niagara building systems.

MY WORK

A closer look at what I do.

My focus is software tooling at Honeywell. Building management is the domain those tools support.

01 / AUTOMATION

Tools for
building systems.

Building software tools that help engineers configure and work with building management systems.

Niagara 4 · Java · Tools team

What I work on

Developing features within Niagara tools, from design and implementation through delivery.

02 / SECURITY

Secure
network access.

Working on authentication features and protocol integration in building management software.

802.1x · RADIUS · Linux

What I work on

Implementing authentication features and working with other teams on protocol integration and security requirements.

03 / INTEGRATION

Systems that
work together.

Working with BACnet/IP to connect tools with building data and networked systems.

BACnet/IP · Niagara

What I work on

Developing software integrations across Niagara and BACnet/IP, with attention to how tools interact with the wider building system.

ABOUT ME

A little background.

I studied Electronics & Communication at Manipal Institute of Technology. After an internship at Honeywell, I joined as a software engineer.

I'm part of Honeywell's Tools team, where I develop software for building management systems. I like making complex systems easier to work with.

I enjoy getting into the details of a problem, trying different approaches, and figuring out why something works.

Download my resume
BhargavBANGALORE, INDIA

My path so far

AUG 2024 — PRESENT

Software Engineer I

Honeywell · Bangalore

Software development in Honeywell's Tools team, focused on building management systems.

FEB 2024 — JUL 2024

Software Intern

Honeywell · Bangalore

Worked on network security features and protocol integration.

CLASS OF 2024

B.Tech in Electronics & Communication

Manipal Institute of Technology

Product Security AdvocateSecurity Compass

ENGINEERING APPROACH

How I approach
the work.

My focus is software tooling. I work through the application behavior, the integrations it depends on, and the details that make a tool useful.

01

Software development

Taking features from design to delivery, with Java at the core of my work. My programming experience also includes Python, JavaScript, and C.

02

Tools & integration

Developing software features in Niagara and working with BACnet/IP and network authentication. Connecting tools to the wider building system.

03

Delivery & code quality

Using Git for version control, Jira to track work, and SonarQube for code quality. Working with other teams to get features ready for delivery.

PROBLEM SOLVING

What needs to get better?

A simple example: a tool takes too many steps to configure. I'd start by asking where the friction is.

A feedback loop for solving a software problem Understand the problem, simplify the approach, build a change, and verify it. Return to the problem with what you learn. 01Understand 02Simplify 03Build 04Verify A feedback loop for solving a software problem Understand, simplify, build, and verify. Learn from the result and return to the problem. 01Understand 02Simplify 03Build 04Verify
START WITH CLARITY

Where do people get stuck?

Map the steps and make the next action obvious. Clear labels and useful feedback come before extra features.

ENGINEERING PRINCIPLES

What I believe.

Good engineering is a series of thoughtful choices.
These are a few I try to make.

Useful, reliable, and easy to change Three overlapping circles represent software that solves a real need, handles failure, and stays easy to improve. Their intersection is labelled Worth shipping. Useful Solve a real need Reliable Handle the edges Easy to change Leave room to improve Worth shipping
Useful today. Understandable tomorrow.
01 / FEEDBACK

Ship small. Learn early.

Try a small, useful change. See how it works for people, then make the next one better.

02 / CONFIDENCE

Move fast. Keep a way back.

Make changes easy to check and easy to undo. A clear recovery path makes it easier to move forward.

03 / CRAFT

Clear code. Shared context.

Keep the solution simple and explain the choices. The next person should be able to pick it up.

INTERESTS

Beyond the day job.

Topics I keep coming back to,
outside my day-to-day work.

A small neural network Three input nodes connect to a hidden layer of four nodes, which connect to two output nodes. InputsHidden layerOutputs
A neural network, in miniature.
Deep learningOptimizationNeural networksComputer visionMachine learningMathematics for ML

CONTACT

Let's talk.

Have a project in mind, an opportunity to share, or just want to say hello? Drop me a message.

bhargavrampallapothu@gmail.com

Send me a note