Staff Software Engineer · Platform & Backend Architecture · Security-Minded Systems

LinkedIn · Portfolio · Technical Writing

I am a Staff-level software engineer specializing in backend platforms, modular APIs, and security-aware system design.

My work centers on building systems that:

• Scale across teams and products
• Remain understandable under pressure
• Prioritize clarity, documentation, and long-term ownership
• Enable engineers to move fast without breaking trust

I’ve worked across startups, production systems, and security-focused environments, often in roles where I was responsible not just for code—but for how teams succeed on top of that code.

• Obsidian Control Plane
  A multi-tenant engineering workflow backend designed to support multiple companies under a shared platform.
  Focus areas: org/company tenancy, membership-driven RBAC, audit logging, and documentation-first APIs.

• Pathscribe
  API detection and generation tooling to reduce friction between backend implementation and documentation.
  Built to support modular architectures and improve delivery velocity.

• NeuroTerp Index
  Structured data modeling and indexing project focused on clean schemas, ETL-friendly pipelines, and reference-grade data.

• Wicked Crimson
  Cybersecurity training and tooling initiative focused on practical defense, monitoring, and education.

When designing software, I optimize for clarity, longevity, and team scalability over novelty.

Good architecture reduces cognitive load.

• Clear module boundaries
• Predictable data contracts
• Documentation that lives with the code

If a system requires tribal knowledge to change, it will fail as teams grow.

I prefer building platform foundations that support multiple products and teams.

• Shared authentication and authorization
• Reusable domain models
• Consistent observability and audit trails

This mindset informs my work on Obsidian Control Plane and my backend leadership at GunKustom.

Systems should be safe and usable by default.

• Secure-by-default APIs
• Explicit permissions (RBAC)
• Sensible error handling and logging

If a mistake is easy to make, it will be made—eventually.

Documentation is not an afterthought.

• API contracts are written alongside implementation
• Architectural decisions are captured near the code
• New engineers should ramp without direct hand-holding

This philosophy directly informs Pathscribe.

Software exists in human environments.

• Engineers get tired
• Context switches happen
• Stress exposes weak abstractions

I design systems to remain understandable under real-world conditions.

Lead Backend Engineer → CTO

• Architected and delivered a modular backend platform with a strong engineering team
• Focused on maintainability, secure boundaries, and long-term ownership
• Prioritized mentorship, documentation, and continuity as the system scaled

Tech: NestJS, TypeScript, MongoDB, Mongoose, OAuth, JWT, Swagger, Jest, Render

Backend Engineering Lead (Delivery to Production)

• Led backend engineering delivery under real timelines
• Implemented the majority of backend services
• Collaborated closely with product and business stakeholders to ship reliably

Tech: Node.js, Express, MongoDB, Redis, Twilio, Jest

• Delivered features and refactors across authentication, reporting, notifications, and metrics
• Focused on observability, UX clarity, and operational reliability

• M3n0koOg Learning Lounge — open-source classroom for software engineering & cybersecurity
• 1Kloc — practical apps built in ≤1,000 lines of code, focused on real-world features
• NetReaper — contributor to unified network/security tooling

• JavaScript / TypeScript
• Python
• Node.js
• SQL & NoSQL (MongoDB Atlas, relational experience via Supabase)

• NestJS, Express
• Mongoose
• Firebase Authentication
• REST / OpenAPI
• Modular service design

• Docker
• Suricata
• Splunk / Google Chronicle
• Kali Linux
• Automation & observability tooling

I write about:

• Software engineering growth
• Backend architecture
• Learning through building
• The human side of technology

👉 Medium: https://medium.com/@jefftkddan

I’m open to:

• Platform & backend roles
• Architecture-heavy projects
• Teams that value clarity, documentation, and long-term ownership

If something here resonates, reach out via LinkedIn or email.

Staff-level engineer focused on building platforms that scale teams, not just codebases.