Jira nucleus
Issues, boards, workflows — the gravitational center.
ATLASSIAN ENGINEER · SYSTEMS LAYER
MIDYA RAHMANI
I engineer the substrate — Jira workflows, Confluence graphs, JSM queues, REST contracts, and automation that survives production traffic.
0yrs stack depth
0core products
0uptime mindset
Engineering vectors
-
01
Workflow engine
Conditions, validators, post-functions — transitions that stay truthful when concurrency spikes.
-
02
Automation mesh
Rules + webhooks + idempotent handlers. Every side effect logged, every retry bounded.
-
03
Search & schema
Fields, contexts, indexing — JQL that scales when portfolios multiply.
-
04
Platform ops
Upgrades, plugin matrix, observability hooks — Friday deploys without panic.
-
05
JSM fabric
Queues, SLAs, assets, portals — service desks engineered like product surfaces.
-
06
Dev graph
Bitbucket ↔ Jira links, build status, deployment events in the work graph.
Build pipeline
SPEC
SCHEMA
AUTOMATE
OBSERVE
SHIP
From issue type design to production automation — one continuous engineering loop.
Live event stream
tail -f /var/log/atlassian/events
Cross-product lattice
Confluence
Docs ↔ issues linked in one truth.
JSM
Incidents, changes, assets.
Bitbucket
Commits, PRs, deployments.
AI substrate
Clean events + structured fields so copilots stay accurate.
UPLINK // OPEN
Transmit signal
Platform engineering, automation deep-dives, or incident response — open a channel.
© Midya Rahmani · midya.ca