Hi. This is my portfolio.

↓

Dikshant Dwivedi · Software engineer

I like entering unfamiliar systems, asking what the abstractions are hiding, and eventually making something useful happen.

What I enjoy

The part where the diagram stops helping.

Backend, cloud, integrations, infrastructure, product delivery—and the useful work between categories.

Broad by circumstance · Deeper by choice

Not a claim to know everything. More a demonstrated willingness to find out what the system is actually doing.

Selected work

Real work · Fake labels

Fake achievement 01 · Fancy Pants Company

Found the behaviour nobody documented.

Legacy access-control work, reconstructed without pretending I single-handedly saved civilisation.

Fake achievement 02 · Fancy Pants Company II

Moved the old thing into the cloud.

Storage decisions, scheduled work, CI/CD, infrastructure, and the connections between them.

Fake achievement 03 · Serious Enterprise Ltd.

Made the system explain itself.

Centralised logging across on-premises Kubernetes services using OpenSearch and Fluent Bit.

Things I built without being assigned them.

$ ls personal-projects
portfolio-that-asks-where-the-projects-are/

$ cat status.txt
Coming soon, immediately after I stop designing the section where they will go.

$ echo $AMBITION
unreasonably_high

Experiments · Personal projects

Eventually: runnable systems, technical experiments, build journals, failures, findings, and no tutorial e-commerce application in a trench coat.

Current interests · Learning

Things I refuse to understand approximately.

01 · NetworkingTCP, ports, sockets

02 · SystemsContainers, processes, boundaries

03 · ArchitectureCloud, delivery, trade-offs

Status · Actively becoming more annoying

The questions continue until “the framework handles it” becomes an explanation rather than an evacuation route.

Notes from looking closer.

Field note · Draft 01

Question
What does “listening on port 3000” actually mean?

Method
Follow the abstraction downward.

Current result
A better mental model and several new problems.

Writing · Build journals

Technical explanations can borrow a research-paper treatment when it helps. The entire website does not need to cosplay as academia.

About · Brief edition

A person, not a catalogue of technologies.

2022 · Intern

Started building backend APIs

2023—Now

Built, migrated, investigated, supported, communicated

India → NZ

Trusted with client-facing delivery in Auckland

Full biography available without third-person narration

The longer version includes experience, working style, leadership, location, and one photograph that does not occupy the entire website.

Testimonials · One currently exists

This section will contain nice things people said.

Right now it is just me, which would make the testimonial structurally questionable.

Continue to a perfectly normal contact page →

Work · Evidence replacing adjectives

Things shipped in the presence of constraints.

Professional work

Real projects. Temporary names.

Each finished case study will explain context, constraints, my actual contribution, decisions, outcome, and what I would do differently. No confidential pantomime.

Fancy Pants Company 01

Fake achievement 01: recovered an access-control workflow

Fancy Pants Company 02

Fake achievement 02: migrated an old Python application

Very Important Enterprise Ltd.

Fake achievement 03: centralised all the logs

Personal · Pending existence

Fake achievement 04 would be dishonest even here

0%Fake statistic, animated like a real one

3×Arbitrary multiplier for impact

12kLarge number deliberately missing a unit

Personal projects

Proof that nobody had to ask.

Currently a beautifully typeset accountability mechanism. The plan is to replace this sentence with ambitious, demonstrable work rather than lower the type size.

Notes · Experiments · Build journals

Writing produced by refusing the short explanation.

Field notes

Ideas in various states of being understood.

Some are explanations, some are experiments, and some are a written record of an assumption being dismantled in public.

Networking · Draft

What a listening socket is actually doing

Framework → runtime → socket → operating system.

Containers · Planned

A process with a deliberately limited view

Namespaces, filesystems, resources, and the word “isolated.”

Experiment · Pending

Watching DNS fail in several educational ways

A controlled demolition of confident assumptions.

Meta · Unfortunately real

Building the portfolio before filling the portfolio

You are currently participating in the research.

A research paper when useful. A normal page otherwise.

Editorial content mode

Abstract
Question
Experiment
Observation
Revised mental model

No decorative footnotes were harmed.

Presentation follows material

Editorial styling is a tool for deep technical reading—not the costume worn by every page.

About · Human-readable edition

I like building things. I like understanding them more.

Dikshant · Auckland, New Zealand

Broad experience. Deliberate depth.

I started as an intern building backend APIs and grew through a suspiciously varied collection of projects: legacy systems, cloud migration, access-control integrations, observability, infrastructure, frontend delivery, technical support, and client communication.

The common thread is not a technology list. It is entering unfamiliar work, developing an accurate picture of it, and helping move it somewhere better.

Fancy Pants Company 01

Backend engineering intern

Fancy Pants Company 02

Software engineer and client-facing delivery

Next chapter

Stronger systems depth, ownership, ambitious work

Contact · No flashing availability badge

Interesting problem? Excellent.

For thoughtful engineering, product, or collaboration conversations. This is deliberately an invitation—not a public declaration that I am conducting a covert job search.

email@will-exist-here.example →

Good reason 01Serious engineering opportunity

Good reason 02Ambitious project or product

Good reason 03Interesting collaboration