ENGINEERING
CAPABILITIES.
Work that spans interfaces, applications, backend systems, data, infrastructure, integrations, automation, testing and connected hardware.
This page maps what can be built and where it sits in a system. It is working capability, not a proficiency ranking.
- Primary
- JavaScript
- System focus
- Full stack
- Environment
- Web / Server / Linux
- Approach
- Build / Integrate / Test / Operate
Technology Distribution
Column- Languages6
- Frontend11
- Backend5
- Data8
- Infrastructure12
- AI / LLM15
- Testing14
- Security13
- IoT7
- Integrations4
Engineering Scope
Donut| Domain | Listed entries |
|---|---|
| Application | 15 listed technologies |
| Server & Data | 13 listed technologies |
| Infrastructure | 12 listed technologies |
| AI & Automation | 15 listed technologies |
| Quality & Security | 27 listed technologies |
| Connected Systems | 9 listed technologies |
| Integrations | 4 listed technologies |
The listed technologies
Languages
Languages and syntax used across the stack
- JavaScriptLanguageWeb / backend / automation / system logic
- TypeScriptLanguageTyped application development
- JSX / TSXSyntaxReact component code
- Shell / SHScriptingAutomation / server tasks
- C++LanguageHardware / lower-level development
- PythonLanguageProjects / tooling
Frontend
Interfaces, component systems and styling
- React.jsFramework / LibraryApplication interfaces
- Next.jsFrameworkWeb applications
- Material-UIUI systemComponent systems
- Ant DesignUI systemComponent systems
- AntV X6VisualizationGraph / diagram interfaces
- BootstrapUI systemLayouts / components
- TailwindStylingUtility-first styling
- ShadCNUI systemComponent systems
- HTML5MarkupInterface structure
- CSS / CSS3StylingInterface presentation
- LESSStylingStylesheet pre-processing
Backend
Runtimes, frameworks and communication protocols
- Node.jsRuntimeServer / application logic
- ExpressServer frameworkHTTP services
- REST APIProtocolClient → server communication
- WebSocketsProtocolBidirectional / real-time
- JSON-RPCProtocolSystem-to-system calls
Data
Persistence, caching and data access
- MongoDBDatabaseDocument store
- PostgreSQLDatabaseRelational
- MySQLDatabaseRelational
- SQLiteDatabaseRelational / embedded
- LevelDBDatabaseKey / value / embedded
- RedisDatabaseCache / fast state
- SQLQuery languageRelational access
- NoSQLData modelNon-relational access
Infrastructure
Hosting, Linux, networking and operations
- Google CloudCloud platformHosted systems
- AWSCloud platformHosted systems
- VultrCloud platformServer hosting
- IBM CloudCloud platformHosted systems
- NgrokTunnellingExposing local services
- LinuxOperating systemServer administration
- Reverse proxyConfigurationRouting / TLS termination
- Process managementOperationsService supervision
- PM2Process managerNode process supervision
- DockerContainerizationPackaged environments
- Raspberry Pi networksSystem infrastructureDistributed devices
- Cloud-based systemsArchitectureHosted application systems
AI / LLM
Models, agents, automation and model hosting
- LLM integrationIntegrationModels inside applications
- AI agent architectureArchitectureAgent systems
- Multi-agent systemsArchitectureTask division / coordination
- Prompt designDesignInstruction structure
- Agent-role designDesignRole and task allocation
- Model routingOrchestrationSelecting models per task
- Local LLM integrationIntegrationSelf-hosted models
- Cloud LLM integrationIntegrationHosted model APIs
- AI workflow automationAutomationBusiness processes
- Linux server preparationInfrastructureModel hosting
- Local inference servicesDeploymentRunning models locally
- GPU / CPU / RAM planningCapacityResource planning
- API endpointsIntegrationExposing inference
- Performance optimizationOperationsThroughput / latency
- Cost optimizationOperationsInfrastructure cost
Testing
Tools, workflows and coverage planning
- SeleniumToolUI testing
- CypressToolE2E / integration testing
- PlaywrightToolE2E testing
- PostmanToolAPI testing
- BashToolScripted checks
- API testingTestingEndpoint behaviour
- Integration testingTestingConnected components
- E2E testingTestingFull flows
- Regression testingTestingChange safety
- Functional testingTestingRequired behaviour
- UI testingTestingInterface behaviour
- Performance testingTestingLoad / response
- Test scenariosPlanningCoverage design
- Acceptance criteriaPlanningDefinition of done
Security
Threats, controls and verification
- DDoS / DoSThreatAvailability
- PhishingThreatSocial engineering
- Brute-forceThreatAuthentication abuse
- MalwareThreatSystem compromise
- SQL injectionThreatInput / query safety
- XSSThreatClient-side injection
- CSRFThreatRequest forgery
- Authentication securityControlIdentity
- Session securityControlSession handling
- Role / access controlControlAuthorization
- 2FAControlSecond factor
- Vulnerability analysisTestingAttack surface review
- Security testingTestingControls verification
IoT
Devices, sensors and connected processing
- ESP32DeviceMicrocontroller
- SensorsHardwarePhysical input
- VL sensorsHardwareProduction-environment project
- Computer visionProcessingImage analysis
- Image processingProcessingJavaScript-based
- Raspberry PiDeviceDistributed environments
- Distributed networksInfrastructureRaspberry Pi-based
Integrations
External payment and service APIs
- VISA APIIntegrationCard payments
- MasterCard APIIntegrationCard payments
- Binance PayIntegrationCrypto payments
- Cryptocurrency integrationIntegrationOn-chain / wallet flows
How the technologies connect
A request moves through layers. Representative technologies are derived from the same dataset above.
What the work covers
Interfaces, applications, backend services and connected systems.
System structure, data flows, integrations and infrastructure planning.
Traditional and AI-driven automation, agents and workflows.
APIs, payment systems, external services, models and hardware.
API, integration, UI, E2E, regression and performance workflows.
Authentication, access control, session security and vulnerability analysis.
Linux servers, reverse proxy, process management and resource planning.
Requirements, planning, documentation, deployment and iteration.
| Capability | Web | Server | Data | Infra | AI | IoT | Quality | External |
|---|---|---|---|---|---|---|---|---|
| Build | ||||||||
| Architect | ||||||||
| Automate | ||||||||
| Integrate | ||||||||
| Test | ||||||||
| Secure | ||||||||
| Operate | ||||||||
| Deliver |
Categorical coverage · a dot means at least one listed entry with that capability in that area · not proficiency
AI, testing and security span every layer
Models and agents are treated as one part of a system, connected to backend logic and local or cloud infrastructure.
- LLM integration
- AI agent architecture
- Multi-agent systems
- Prompt design
- Agent-role design
- Model routing
- Local LLM integration
- Cloud LLM integration
- AI workflow automation
- Linux server preparation
- Local inference services
- GPU / CPU / RAM planning
- API endpoints
- Performance optimization
- Cost optimization
Verification applies across API, integration, UI and end-to-end behaviour, not only at one layer.
- API
- Integration
- UI
- E2E
- Regression
- Functional
- Performance
Security is a cross-system concern, informed by ISO/IEC 27001 principles.
- Authentication
- 2FA
- Session security
- Access control
- Secure API practices
- Security testing
Practical knowledge of principles — not certifications.
Where the work runs
Operating environments, not programming skills.