01Frontend leadership · React and Django delivery
XDR and EDR interfaces
I build enterprise XDR and EDR interfaces, lead the frontend team, and review architecture and delivery.
- React
- TypeScript
- Tailwind CSS
- Django
XDR / EDR
Build theinterface.Ship thesystem.
I design and build software from the interface to production.
Eight frontend engineers · roughly 30 repositories · React to delivery
Project index · 01—14
Selected work
Project studies of enterprise security, telecom systems, internal tools, and developer tooling. Each one explains the system, my role, and the work behind it.
02Architecture and end-to-end delivery
Network discovery and device visibility
Core architecture, backend services, and management interfaces for discovering and acting on managed, unmanaged, IoT, and OT devices.
- React
- Django
- Python
- Network monitoring
- Device control
DISCOVERY / VISIBILITY
03Internal team tooling
Shared rules for coding agents
Instead of making Codex or Claude rediscover each repository, we give them the project rules, bounded MCP tools, and checks they must run.
- Codex
- Claude
- MCP
- TypeScript
- Python
AGENT / REVIEW
04Complete frontend implementation
Web application firewall management
Complete React and Vite frontend ownership for configuring protection rules and operating web-application security workflows.
- React
- Vite
- TypeScript
- API integration
- Reusable UI
WAF / CONTROL
Project ledger
More systems. Different problems.
Telecom, operations, automation, and the tools around the work. Open a project to see my contribution.
Telecom & RBT
Remote React and Next.js work for RBT and network integrations, connected to telecom services over gRPC.
React / Next.js / gRPCAsset discovery
An internal application for finding internet-facing assets, plus OSINT and penetration-testing tools for investigation work.
Python / React / OSINTHopper operations
Frontend features and targeted backend integration for logistics and store-operation workflows.
Frontend engineering / Backend integration / Operational workflowsMoshaar
Project delivery and hands-on development for task tracking, project timelines, and team workflows.
Project delivery / Frontend / Workflow designInternal HR & ERP
A business application that turns HR and departmental processes into one set of operational workflows.
Business workflows / ERP / Department operationsPharmacy ERP
A C# and .NET management system joining inventory, prescription tracking, and billing in one application.
C# / .NET / InventoryCompany websites
Responsive website delivery for SGSTel, Azka Moka, and DeepSafer across English and bilingual presentation work.
React / Tailwind CSS / Responsive designPolyrepo manifest
I built a manifest inspired by Android repo so an engineer can see the repositories they need and prepare the workspace with one command.
Git / Manifest tooling / AutomationONIST tools
A side project where I collect scripts and small interfaces instead of leaving useful operations scattered across notes.
React / TypeScript / AutomationLegal scheduling
A side project that keeps session dates, duration, and follow-up in one place instead of spreading them across messages and spreadsheets.
Django / React / PostgreSQLOriginal interface studies — not production screenshots.
Experience
Work experience.
Software Engineer Team Lead
DeepSafer
- Present
- Lead technical delivery for eight developers, translating product requirements into application designs, implementation tasks and sprint priorities while remaining hands-on with core features.
- Define application structure and frontend/backend boundaries; develop Django services and React interfaces and resolve architecture and integration issues across the stack.
- Direct engineering work across endpoint protection, network discovery and security tooling, coordinating feature implementation with developers and project managers.
- Design how the team works with AI coding agents: prepare developer environments, define orchestration workflows, and author reusable skills and project rules.
- Manage developer environment setup and Python automation; use Git and GitLab to coordinate code changes and shared engineering workflows.
- Review implementations, mentor engineers, resolve frontend/backend defects and refactor legacy components to improve maintainability and support continued feature development.
Frontend Developer (Part-time)
SGSTel
- Present
- Own frontend feature implementation in React, Next.js and Tailwind CSS, translating product requirements into responsive application screens and reusable components.
- Integrate interfaces with backend services through gRPC, coordinate frontend/backend behavior and investigate integration defects during feature delivery.
- Improve usability and frontend performance through component refinement, responsive layouts and bug resolution, working with product and engineering teams.
Full Stack Software Engineer
DeepSafer
-
- Delivered end-to-end features for enterprise cybersecurity applications, implementing Django backend functionality and React interfaces from requirements through frontend and backend integration.
- Investigated and resolved critical defects across application layers, tracing issues between frontend behavior and backend logic to restore reliable feature operation.
- Refactored legacy code and improved application architecture, strengthening maintainability and performance while supporting continued development of the cybersecurity platforms.
- Contributed to shared code quality standards and implementation conventions, helping the team extend existing products with consistent, maintainable functionality.
Frontend Engineer
DeepSafer
-
- Built responsive React interfaces for enterprise cybersecurity platforms, translating product requirements and UI designs into interactive screens and user workflows.
- Developed reusable components and modular frontend structures aligned with design-system conventions, enabling shared interface patterns to be reused across product features.
- Collaborated with design and product teams to improve usability, accessibility and frontend performance, refining components and responsive layouts to address product feedback.
Capabilities
From interface to release.
Four connected parts of my work. Follow the feature, or choose where to look.
Interface
Frontend engineering
React and Next.js are the centre of my work. I also use TanStack Start and Astro when their trade-offs fit the product.
React · Next.js · TypeScript · TanStack Start · Astro
Illustrative feature · saved viewsStart with what people use.
The happy path is only one state.
Saved views
Open items
Status: openOwner: me
Review the interfaceReady
Connect the serviceIn review
UI / STATESDesigned for the in-between
LoadingEmptyErrorKeyboard
Services
Backend and services
I follow features through Django and Flask services, gRPC boundaries, PostgreSQL, and the failure states users eventually see.
Django · Flask · Python · gRPC · PostgreSQL · Lua
Illustrative feature · saved viewsGive the interface a contract.
Typed inputs. Explicit failure states.
rpc GetSavedView (ViewRequest)
returns (SavedView);
message ViewRequest {
string view_id = 1;
string owner_id = 2;
}
Response shape
{ name: "Open items", filters: ["open"], can_edit: true}Validate at the boundary
InputPermissionFailure
Agents
AI-agent workflows
I build project skills, shared rules, and bounded MCP tools for Codex and Claude, then keep linting, type checks, E2E tests, and human review in the path.
Codex · Claude · Cursor · Qoder · Ollama · OpenRouter
Illustrative feature · saved viewsGive the agent useful context.
Project rules in. Reviewed changes out.
- ↳ AGENTS.md
- ↳ skills/system-design.md
- ↳ components / tokens
System-design skillThe rules travel with the task.
Checks before review
TypesLintE2E
Human reviewThe agent does not approve its own work.
Delivery
DevOps and release work
I handle the Docker, GitLab CI, nginx, scripting, and release troubleshooting needed to get a change beyond a local browser.
Docker · GitLab CI · nginx · CI/CD · Automation
Illustrative feature · saved viewsCarry the change into a release.
Repeatable checks, with a human in the loop.
$ docker build .
→ compile application
→ package runtime
$ run checks
→ types · lint · e2e
› human review
Release path
- Build
- Verify
- 03Review
- 04Release
Ready for handoffContainer · configuration · rollback plan
Scroll to move through the layers. Select one to explore at your own pace.
You’re in control. Choose any layer above.
Writing
Notes from work I actually did.
Short posts about agent-ready libraries, secret handling, and frontend performance—the same problems that shape the work above.
View LinkedIn posts01When a component library can explain itself to an agentWhy agent-readable components, props, templates, and design tokens are becoming part of the library contract—not an optional AI layer.Open on LinkedIn↗02A private repository is not a secrets vaultA compromised developer tool can cross the boundary people trust. The response starts with revocation, rotation, and stricter control of where code lives.Open on LinkedIn↗03When the codebase—not React—is the performance bugMemoization, caching, and local refactors only went so far. The lasting fix was to separate data access, business logic, and UI instead of patching symptoms.Open on LinkedIn↗
Contact
Bring the real problem.
Tell me what you are building, where the workflow breaks, and what the team is working around. A rough first message is enough.
Start with the context
No polished brief required.