Skip to content

Hi, I'm

AnuragKumar Bharti

I build systems that have to survive reality.

I build across software, intelligent systems, automation, and hardware-driven engineering. Here, I share not only what I build, but also the decisions, trade-offs, challenges, and lessons behind the work.

01

About the journey

I like understanding how things work before deciding how they should be built.

My path started with electrical engineering and gradually moved through automation, robotics, software, and intelligent systems. I still think of those areas as connected rather than separate.

Anurag Kumar Bharti
I keep noticing how places, systems, and people change the way a problem needs to be approached.

I'm drawn to the parts of engineering where software has to respect physical constraints, systems have to remain understandable as they grow, and good solutions depend more on sound decisions than on chasing the newest tool.

Travel has shaped that thinking more than I expected. Different places make you notice different infrastructure, habits, trade-offs, and ways of solving everyday problems. I tend to carry those observations back into my work, whether I’m thinking about software architecture, automation, interfaces, or how people interact with a system.

This portfolio is where I bring that journey together: the projects, decisions, mistakes, experiments, and ideas that have influenced how I work.

01

Forward with purpose

I try to understand how the parts influence one another before deciding what should change.

02

Build with curiosity

I prefer clear decisions, maintainable structure, and evidence over unnecessary complexity.

03

Move with intent

Moving across software, automation, hardware, AI, and new environments keeps changing how I think about engineering.

02

Experience

I've moved between industrial systems and software environments, and each one changed how I approach engineering.

From substations and automation systems to full-stack product development, I've learned to look at problems through both physical constraints and software architecture.

Professional route

Bettiah(BR) → Patna(BR) → Bettiah(BR) → Nagpur(MH) → Dolvi(MH)

  1. NIT Patna

    B.Tech · Electrical Engineering

    Engineering foundation and multidisciplinary project work

    Patna, Bihar
  2. NBPDCL

    Industrial Trainee

    33/11 kV substation operations and maintenance

    Bettiah, Bihar
  3. Remote Intern

    Web Development Intern

    Full-stack application development and deployment workflows

    Nagpur, Maharashtra
  4. JSW Steel Ltd.

    Graduate Engineer Trainee (Electrical & Automation)

    Electrical & Automation in an industrial operating environment

    Dolvi, Maharashtra
Loading selected projects
04

Engineering domains

My work sits where several engineering disciplines meet.

I do not think of these as separate skill lists. Software, intelligence, automation, and hardware often become different parts of the same system, and understanding those connections is where I find the work most interesting.

DOMAIN 01

Software

Software Engineering

I build full-stack applications with an emphasis on maintainable architecture, clear data flow, secure boundaries, and production-ready delivery.

Capabilities

  • TypeScript
  • React
  • Next.js
  • Node.js
  • REST APIs
  • PostgreSQL

DOMAIN 02

Intelligence

AI & Intelligent Systems

I use AI where it improves the system rather than treating it as a feature on its own, combining retrieval, orchestration, computer vision, and application logic.

Capabilities

  • RAG
  • Semantic Search
  • Prompt Orchestration
  • Computer Vision
  • AI Integration

DOMAIN 03

Automation

Electrical & Automation

My electrical engineering foundation keeps me connected to physical systems, controls, machines, industrial environments, and the constraints software eventually has to respect.

Capabilities

  • Electrical Systems
  • Automation
  • Control Systems
  • Electrical Machines
  • Industrial Systems

DOMAIN 04

Embedded

Embedded Systems & Robotics

I enjoy the boundary where software becomes physical: sensors, controllers, embedded computation, autonomous behavior, and robotic systems.

Capabilities

  • Arduino
  • Raspberry Pi
  • Sensors
  • Embedded Control
  • Robotics
  • Autonomous Systems

One connected engineering system

05

Current waypoint

A small place for what I'm working on right now.

Think of this as a field note rather than an announcement wall: one current update, kept short and visible.

Pinned dispatch

Field note / 001

Current build record

I’m open to the right engineering challenge.

I’m especially interested in work that brings software, automation, applied AI, and real-world engineering constraints together.

Current focus
Engineering roles
Status
Available
Waypoint
India · Remote
CURRENT WAYPOINT

Daily Reflection

दैनिक संस्कृत चिंतनम्

प्राचीन ज्ञान, आधुनिक जीवन

आज का चिंतन तैयार हो रहा है

Preparing today's reflection using your local date.

कल फिर एक नया चिंतन

06

Meet Aeva

Instead of making you search through everything, I want Aeva to help you find the part of my work that matters to you.

She is the disclosed intelligence layer across this portfolio: a focused assistant that connects projects, experience, writing, engineering decisions, and the context behind how I build.

A different way to explore

A portfolio usually asks the visitor to follow its structure. I'd rather let the visitor start with their own question.

A recruiter may care about experience. An engineer may want architecture and trade-offs. Someone else may be interested in robotics, AI, or what I'm currently building. Aeva is intended to become the route between those questions and the relevant parts of this site.

MODE
Contextual exploration
SOURCE
My work and knowledge
STATUS
Available now
Talk to Aeva
AI-generated fictional portrait representing Aeva

Aeva

AI portfolio guide · available now

Available now

Start somewhere

What would you like to understand about my work?

Start with a question. Aeva answers from approved portfolio sources, or from cited live web results when you choose to enable them.

Evidence first

Ask naturally, inspect the cited sources, and let Aeva say when the available evidence is not enough.

Got a problem worth building around?

Interested in collaboration?

Let's talk

Next destination

Have a role, project, or engineering problem worth discussing?

I'm interested in work where engineering judgment matters: systems that need to be understood properly, built carefully, and improved with evidence rather than noise.

Good
engineering
travels far.

Start a conversation

Same curiosity.
A brighter tomorrow.

Looking for

Meaningful engineering work and difficult problems.

Open to

Roles, collaboration, research, and serious ideas.

Current route

Building AKB Studio and continuing to learn across systems.