Understand first
I try to understand the system, dependencies, people, and constraints before proposing changes.
About Me
I like understanding how systems work — and finding ways to make them work better.
My background spans forestry engineering, infrastructure evaluation, electrical systems, engineering research, and AWS cloud technologies. The disciplines changed, but the way I solve problems stayed consistent: understand the system, gather evidence, simplify the problem, and validate the solution.
DK
Danilo KrgovicEngineering & Technical ProfessionalElectrical Systems · Infrastructure · Research · Cloud
My Story
A multidisciplinary engineering path
I started in forestry engineering, where I learned to work with complex natural systems, GIS, field data, technical analysis, and research. That foundation taught me to look at the whole system before focusing on individual details.
My infrastructure work added a different layer: field investigations, surveying, regulatory requirements, stakeholder communication, and technical reporting that supported real land-acquisition and development decisions.
Today, my work in electrical manufacturing focuses on testing, troubleshooting, pilot builds, wiring, electrical schematics, and continuous improvement. I regularly look for issues that can be simplified or improved before they become larger problems in production or the field.
Alongside engineering, I completed the AWS Cloud Institute Cloud Application Developer program and earned AWS Cloud Practitioner and AI Practitioner certifications. Cloud and data tools expanded how I think about automation, architecture, and decision-making.
How I Work
Structured thinking, practical solutions
Use evidence
I prefer decisions backed by data, research, testing, or direct observation rather than assumptions.
Keep it practical
I don’t believe the most complex solution is automatically the best one. If a simpler tool solves the problem well, use it.
Work with people
Good engineering depends on communication, respect, and understanding the perspectives of technicians, engineers, customers, and stakeholders.
Improve continuously
I enjoy finding the next improvement — whether it is a wiring route, research process, data workflow, or cloud architecture.
Validate
A solution is not finished because it looks right. It should be tested, reviewed, and confirmed in the real system.
Engineering Philosophy
“The best solution is when someone gives you 100 pages of problems and you give them one page of solutions.”
That idea is the foundation of Project Sequoia: simplify complexity without losing the important details.
What I’m Building Toward
Engineering roles with broader system responsibility
Project Sequoia
Deep roots. Continuous growth. Practical engineering.
My goal is to become the engineer organizations trust when the problem is complex, the system matters, and the solution needs to work in the real world.