Cheng Ye
Software Developer
Node JS
PHP
Java
C#
JavaScript
Python
SQL
TypeScript
Active 3 days ago
+41 (32) 64008
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
UI-focused frontend engineer working on interactive TypeScript-based game UIs and web interfaces with solid hands-on implementation skills. Strongest proven skill is building interactive game UI and runtime systems, evidenced by the Cocos Creator TypeScript Fight_UI implementation with object pools, game-camera updates and Observer-driven UI flows. Public code does not demonstrate large-scale backend architecture, measurable performance benchmarking, or systematic a11y/CI-driven accessibility work.
Technical skills
Node JS• Middle
PHP• Middle
Java• Junior • 3y+
C#• Junior
JavaScript• Middle
Python• Junior
SQL• Junior
TypeScript• Middle
Java
Maven
Spring Boot• 3y+
Spring Cloud• 3y+
C#
ASP.NET Core
Entity Framework Core
Databases
PostgreSQL
Redis
MySQL
Frontend
JQuery
Bootstrap
React.js
DevOps
Azure
Azure DevOps
CI/CD
Docker
Jenkins
Rest API
QA
Playwright
Postman
QA
Timeline
Founder & Software Engineer
Mobile app
Designed, developed and tested a WeChat Mini Program game using TypeScript and WeChat Cloud Development, attracting over 500 registered users through continuous feature releases and product iterations.
Built core application features including WeChat authentication, an in-game shop and leaderboard, alongside gameplay logic for 12 unique enemy mechanics, 9 distinct emoji projectile behaviours and a dynamic boss generation system.
Software developer
Website
Tested 18 REST API scenarios using Postman and DevTools, validating authentication, request/response data, HTTP status codes and error handling across core application workflows.
Built Playwright E2E automation in JavaScript for registration, login, cart and checkout, covering the full user journey from dynamic account creation to successful payment.
Designed and executed 45 functional and regression test cases across authentication, cart and payment workflows, identifying and documenting 5 UI and API defects in Jira.
Software Engineer (Part-time)
•
Middle
Outlier AI
•
Part-Time
Developed and debugged Java and Python backend APIs to execute and process code submissions, including runtime error handling and capturing execution results. Improved code evaluation and scoring logic by analyzing outputs, failed cases, and edge conditions across thousands of samples. Optimized MySQL queries and indexes to reduce execution query time and lower the volume of slow queries. Supported Jenkins CI/CD pipelines by troubleshooting build issues and validating changes before deployment to maintain stable releases.
Java
Python
MySQL
Jenkins
CI/CD
Rest API
University of Queensland (UQ)
Master's Degree •
Information Technology
Software Engineer (Full-time)
•
Middle
Kingdee
•
Full-Time
Built payroll calculation and compliance modules using C#/.NET with Entity Framework Core and SQL Server, automating salary, overtime, and tax for employees. Implemented RESTful APIs integrated with a React and TypeScript frontend to sync leave and attendance updates into payroll records at high transaction volumes. Supported Azure DevOps CI/CD workflows with Docker by validating build, test, and deployment processes to shorten release cycles.
C#
Entity Framework Core
SQL
Rest APIsince 2024
React.js
TypeScript
Azure DevOps
Docker
CI/CDsince 2024
Software Engineer (Intern)
•
Junior
SUNMI Technology
•
Internship
Developed and tested an RFID-based apparel management SaaS using Java, Spring Boot, and Spring Cloud for inventory tracking and warehouse operations across stores. Implemented security testing for internal microservice APIs using JWT and RSA for stock transfers and inventory scans. Focused on validation and troubleshooting of service behavior to reduce recurring authentication errors.
Javasince 2023
Spring Boot
Spring Cloud
Wuchang Shouyi University
Bachelor's Degree •
Electromechanical Engineering
Middle Backend Developer
Confidence: Medium API Engineer
Backend engineer (3 yrs estimated) focused on web admin tooling and API scaffolding with a strong practical grasp of framework-driven CRUD generation and auth lifecycle management. The most proven skill is building schema-driven CRUD and API metadata tooling as shown in application/admin/command/Crud.php and the Api Extractor/Builder artifacts. There is limited evidence of production-grade operational engineering such as secure password hashing, migration histories, distributed systems design or observability pipelines.
API Design
3/10
How well APIs are designed
API surface and generation tooling are present (API doc/annotation extractor and a CRUD controller generator) showing attention to route naming and method metadata, but there is no evidence of API versioning, formal error contract, idempotency handling, or pagination strategy beyond framework defaults.
Evidence
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Api/library/Extractor.php: parseAnnotations / getMethodAnnotations
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Api/library/Builder.php: generateHeadersTemplate / generateParamsTemplate
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Crud.php: generation of controller routes and getControllerUrl logic
Data Layer & Database
3/10
Working with databases
Code shows direct database schema inspection, primary key validation and relation handling which is useful for schema-driven code generation, but lacks explicit transaction boundaries, migration history, or evidence of hand-tuned queries and index work.
Evidence
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Crud.php: information_schema query and primary key checks (SHOW TABLE STATUS / SELECT from information_schema.columns)
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/library/traits/Backend.php: imports of think\Db and db-related exception handling
Scalability & Performance
2/10
Handling load and speed
Small touches for performance appear (menu caching and some generation-time decisions), but there is no clear work on caching invalidation, queue-based decoupling, connection pooling tuning, rate limiting or documented load-tested optimizations.
Evidence
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/library/Auth.php: getSidebar uses cache("__menu__")
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Crud.php: generation of fixedColumnsJs and code paths that adjust generated output based on column counts
System Architecture
3/10
Overall system structure
Clear module separation (controller, model, validate), tooling to scaffold modules and relation-aware code generation indicate deliberate organization, but service decomposition and cross-service contracts are not present.
Evidence
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Crud.php: getParseNameData / getControllerData / getModelData implement module-aware parsing
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/controller: consistent controller/model/validate structure under application/admin
Security & Auth
3/10
Protecting data and access
There is explicit auth handling and lifecycle logic (login token, keeplogin cookie, safecode, IP and unique-login checks) showing security awareness, but cryptographic choices (MD5-based password handling) and lack of modern password hashing reduce the overall security posture.
Evidence
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/library/Auth.php: login, autologin, keeplogin, getKeeploginKey, getEncryptSafecode
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/controller/Ajax.php: imports think\Validate and input boundary handling
Reliability & Observability
2/10
Stability and monitoring
There is basic error handling (try/catch and exception propagation) and some use of framework exceptions, but deeper reliability and observability practices like structured logs with correlation ids, timeouts/retries with backoff, metrics or graceful shutdown hooks are not evident.
Evidence
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/command/Crud.php: try/catch around major generation flow with ErrorException handling
Scott-yc/Micro_Emotion_Game/服务端/admin.emoparty.com_C8sti/admin.emoparty.com/application/admin/library/traits/Backend.php: imports of specific DB and validation exceptions
Expertise
PHP• Middle
Node.js• Middle
Industries
Gaming• Middle
Technologies
PHP• Middle
Node JS• Middle
MySQL
PostgreSQL
Redis
Recommendations
- Harden authentication: migrate from MD5-based password handling to a modern KDF like bcrypt/argon2 and add explicit token revocation and refresh flows.
- Add Operational Observability: integrate structured logging with request correlation ids and expose basic metrics for API request/DB latency to drive performance improvements.
- Introduce explicit DB migration history and transaction boundaries for non-trivial write flows to demonstrate schema evolution competence.
- If expanding backend scope, add retry/backoff and idempotency for external calls and document pagination/versioning strategies for APIs.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium UI Engineer
UI-focused frontend engineer working on interactive TypeScript-based game UIs and web interfaces with solid hands-on implementation skills. Strongest proven skill is building interactive game UI and runtime systems, evidenced by the Cocos Creator TypeScript Fight_UI implementation with object pools, game-camera updates and Observer-driven UI flows. Public code does not demonstrate large-scale backend architecture, measurable performance benchmarking, or systematic a11y/CI-driven accessibility work.
UI Component Architecture
5/10
How interface parts are built
Component-like architecture for a Cocos Creator TypeScript game with modular classes, object pools and event-driven UI components.
Evidence
Micro_Emotion_Game/前端/表情派对-前端源码/biaoqingdazuozhan-game/assets/Script/Fight_UI.ts: usage of BulletPool/EnemyPool, imports of ManagerUI/Tip_UI/Observer and cc.Component-based UI class
dogpark/DogParkList.js: modular DOM functions (fetchDogParks, displayParks, applyFilters) showing component decomposition
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive CSS and breakpoints are applied in admin and site stylesheets with mobile media queries and layout adjustments.
Evidence
Micro_Emotion_Game/服务端/.../public/assets/css/backend.css: multiple @media rules and mobile adjustments
dogpark/DogParkList.css: media queries and responsive navbar/header behavior
Performance Optimization
5/10
Speed of the interface
Practical runtime optimizations like object pooling, delta-time movement updates and paginated/fallback network fetching are present; no measured perf reports or bundle analysis.
Evidence
Micro_Emotion_Game/.../assets/Script/Fight_UI.ts: BulletPool and EnemyPool reuse, update(dt) patterns and delta-time movement
dogpark/MapFunctions.js and dogpark/weather.js: paginated fetchPage pattern for API pagination and incremental loading
Accessibility & Semantics
3/10
Usable for everyone
Some semantic form labels and tooltips exist and templates include label elements, but explicit ARIA, keyboard focus management for custom widgets and CI a11y checks are not evidenced.
Evidence
Micro_Emotion_Game/服务端/.../application/admin/command/Api/template/index.html: labeled form controls and tooltip usage
Micro_Emotion_Game/服务端/.../application/admin/view/general/config/index.html: form labels and control markup
State Management & Data Flow
4/10
Managing data in the app
Event-driven client state and flows are implemented (Observer pattern, PlayerMessage, scheduled updates and NetWork callbacks) but no advanced server-state caching, request cancellation or optimistic update machinery is shown.
Evidence
Micro_Emotion_Game/.../assets/Script/Fight_UI.ts: Observer.on usage, PlayerMessage state mutations, scheduled updateEnemy/updateGameTime flows
Micro_Emotion_Game/.../assets/Script/work/NetWork.ts (import referenced in Fight_UI.ts): network callback usage pattern
UX & Visual Polish
5/10
Look and feel quality
UX-focused details like tweens, tip UI, pause/resume and resurrection flows are implemented for good perceived experience; there are also real E2E test scripts for web flows.
Evidence
Micro_Emotion_Game/.../assets/Script/Fight_UI.ts: tween sequences, Tip_UI calls, pause/resume scheduling and in-game feedback
Toolshop_Testing/Automation/checkout.spec.js: full-playwright E2E flow validating registration, cart and checkout
Expertise
Frontend Architecture & Build Tools• Middle
PWA & Web APIs• Middle
Technologies
Bootstrap
React.js
JQuery
Recommendations
- Lead development of small-to-medium interactive games or gamified features (mobile/web) where Cocos Creator/TypeScript expertise and runtime optimizations are required.
- Expand ownership into frontend test and CI pipelines by converting Playwright scripts into maintainable test suites and integrating them into automated CI runs.
- Harden frontend engineering practices by adding explicit accessibility fixes, request cancellation/error handling, and documented before/after performance measurements for key flows.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: Medium Automation Engineer
A mid-level automation-focused engineer specializing in Playwright-based end-to-end UI automation. The strongest proven skill is E2E Playwright automation demonstrated by playwright.config.js and the checkout.spec.js and cart.spec.js test suites. There is little public evidence of contract testing, CI pipeline integration, performance testing or test infrastructure for isolated fixtures and mocks.
Test Automation Frameworks
5/10
Building automated tests
Solid E2E automation foundation with Playwright configuration, parallelization and selector discipline (data-test). Lacks custom fixtures, mock servers, isolated test data factories and advanced flake-handling; some tests use waitForTimeout which reduces robustness. Good basic test infra but needs investment in test isolation and infrastructure.
Evidence
Toolshop_Testing/playwright.config.js
Toolshop_Testing/Automation/checkout.spec.js
Toolshop_Testing/Automation/cart.spec.js
Test Coverage & Strategy
4/10
What and how to test
Reasonable test strategy for functional and negative paths with explicit end-to-end flows and assertions. Missing risk-based tagging, boundary/property-based tests and mutation or coverage-honesty tooling; several sleeps/timeouts suggest opportunity to improve flake engineering. Tests show selector discipline and meaningful assertions rather than purely assertion-free scripts.
Evidence
Toolshop_Testing/Automation/checkout.spec.js
Toolshop_Testing/Automation/login.spec.js
API & Integration Testing
1/10
Testing how parts work together
Minimal evidence for API or contract testing; an API testing markdown exists but contains no concrete contract checks. Game code calls NetWork APIs but there is no schema validation, contract tooling or containerized integration tests present.
Evidence
Toolshop_Testing/API_testing/API_testing.md
Micro_Emotion_Game/前端/表情派对-前端源码/biaoqingdazuozhan-game/assets/Script/Fight_UI.ts: NetWork.getPlayMessage usage
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
2/10
Running tests automatically
Playwright config is present and CI-conscious flags are used, but there are no CI workflow files, selective test-on-diff rules, quarantine mechanics or historical artifact storage. Basic readiness for CI exists but needs concrete pipeline integrations and artifact collection.
Evidence
Toolshop_Testing/playwright.config.js
Toolshop_Testing/package.json
Expertise
SDET & Test Engineering• Middle
Technologies
QA
Python• Junior
JavaScript• Middle
Java• Junior • 3y+
TypeScript• Middle
SQL• Junior
C#• Junior
Rest API
Playwright
Maven
Spring Boot• 3y+
Azure DevOps
Postman
Azure
CI/CD
Jenkins
Docker
ASP.NET Core
Entity Framework Core
Spring Cloud• 3y+
Chrome DevTools• mentioned only
Postman• mentioned only
Recommendations
- Replace waitForTimeout calls with deterministic waits and add per-test isolation (fixtures or data factories) to remove flakiness.
- Add CI pipeline integration (GitHub Actions/GitLab CI) that runs playwright tests, captures traces/screenshots and supports selective runs and quarantine for flakey tests.
- Introduce contract/schema validation for API interactions and start small with a mock server or request-intercept fixtures for faster, deterministic tests.
- Invest in test infrastructure: shared fixtures, factories, parallel-safe seed/cleanup, and a plan for mutation or coverage-honesty checks to increase confidence.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: