Work & campus
One is now: full-stack delivery across three product lines. The other was an internship running and extending a live system.
2025 — 2026
AI Full-stack Engineer
CurrentSmart-parking / smart-community / digital-asset custody SaaS company
Company name withheld by agreement; available on request · 2026.08 — Present
Full-stack owner of three product lines — smart parking, smart property, and digital-asset custody: a Spring Boot multi-module backend, a B-side admin console, and several WeChat mini programs (resident and guard). Requirements are delivered AI-first, from design docs and API design through frontend implementation and automated regression. I also run production: account systems, the security baseline, release rollback, and remote access to the internal Gitea.
Delivery surface
- Mini programs
- 2 clients
- Resident (uni-app) · guard (native)
- Mini-program pages
- 390+
- Five subpackages plus access, charging, invoicing
- Admin console pages
- 190+
- Vue 2 + Element UI, permission-driven routing
- Backend endpoints
- 170+
- Spring Boot monolith, 1,400+ Java files
Product lines
03- P-01
Smart Parking
Temporary parking, monthly/short-term passes, space rental and sharing, reservations, barrier-free payment, e-invoicing, and the cloud gatehouse (guard app with live video and barrier control).
TemporaryMonthlyRentalGatehousePayments - P-02
Smart Property & Community
Unit binding and member management, owner/tenant certification, property and parking-space fees, visitor invitations, access control, repairs and inspections.
Unit bindingCertificationFeesVisitorsAccess - P-03
Digital Asset Custody
Custody and managed operation of parking-space assets: custody contracts, lease signing and renewal, deposits and move-out review, revenue-split rules, billing and reconciliation.
ContractsRenewalDepositsRevenue splitReconciliation
Work experience
Work experience
02AI Full-stack Engineer
2026.08 – PresentSmart-parking / smart-community / digital-asset custody SaaS company · AI Full-stack EngineerCurrent
- Three SaaS product lines share one account, tenancy, permission and payment foundation, serving six roles — driver, guard, lot operator, property manager, asset owner and tenant; one order and one billing rule must stay coherent across four clients
- Shipped core backend paths inside a Spring Boot 2 multi-module monolith (~170 controllers, 1,400+ Java files): monthly renewal, self-service space-management fees, temporary-parking toggle, payment-record aggregation and callback period extension, with the API contract handed to all four clients
- Payment overhaul: unified six entry points — temporary exit, monthly renewal, reservations, space-management fees and more — from redirecting to the Lakala cashier into in-app WeChat Pay (main-scan), handling validity extension on callback, channel-accurate status queries, zero-amount orders and distributed locks, with old and new channels coexisting per lot for a gradual cutover
- Custody loop end to end: rent / deposit / service / property / space-management fees in one order at signing, split by contract on callback; renewal extends the original expiry; move-out passes review before the deposit refund fires; split recipients and ratios configured in the console, and every settled amount traces back to contract, order and payment record
- Worked across the resident mini program (uni-app, 390 pages, 5 subpackages): home rebuild, monthly-pass lookup and renewal, vehicle certification, Lakala main-scan migration, unified session-expiry handling; moved 1,152 KB of static assets to OSS and recompressed to clear the 2,048 KB package limit
- Built admin-console screens on the Vue 2 console (190+ pages): gatehouse video and barrier permissions, real-time lane notifications, monthly-pass validity, merged arrears payment, split-recipient and deposit-refund review, with permissions delivered by role
- Multi-tenant security: phone numbers unique per account domain, cross-tenant and cross-level access limits, four-dimensional authorization (identity × role × app center × tenant), duplicate-plate interception across users
- Delivery and quality: every requirement starts with a design doc whose claims point at a `file:line`, every change ends with static checks and explicit activation prerequisites; 179 regression cases cover API / web / mini program, write results back to Yunxiao and file defects automatically
- AI engineering: two toolchains — Modao design-source ingestion (MCP server) and Yunxiao-driven automated regression — wired into daily delivery, so reviews, integration and regression leave executable artifacts rather than chat logs
Spring BootMyBatis-PlusMySQLRedisVue 2uni-appNative WeChat mini programMQTTLakala / WeChat PayOperations Development Engineer (Intern)
2025.06 – 2026.04Shangrao Yajie Construction Engineering Co., Ltd. · Operations Development Engineer
- Handled daily operations and secondary development of the internal business system (Spring Boot + Vue)
- Wrote scripts to automate routine ops tasks and boost efficiency
- Participated in API integration and data report development for business analytics
- Monitored system performance, diagnosed and resolved lag issues to keep the system stable
Spring BootVueShell ScriptingMySQL
Education & campus
03Nanchang University · Computer Science
2022.09 – 2026.06School of Mathematics & Computer Science · BSc
- Transferred into CS Class 223 in Feb 2024; graduated June 2026
- Core courses: Data Structures, Computer Networks, Database Systems, OS, Software Engineering
Data StructuresNetworksDatabasesOSSoftware Engineering
Counselor Assistant · Class League Secretary
2022.09 – 2026.06CS Class 223
- 2024.02–2026.06: transferred to CS 223, concurrently Class League Secretary
- May 2023: joined the college party branch via party school; Nov 2024: branch assistant
Student Union · Quality Development Dept.
2022.09 – 2023.09College Student Union
- Co-organized campus development activities; owned planning and on-site execution
How I work
These are not slogans — they are rules committed into the team repository, and the standard I judge a delivery by.
- 01
Design before code
Every feature starts with a design doc: goals, evidence, APIs, data model, blast radius, risks, verification.
- 02
Evidence over assertion
Claims must point back to a file and line. Unknowns are marked "to confirm" rather than smoothed over.
- 03
Deliverable change
Every change states what a human must do to see it: rebuild, restart, re-login, recompile the mini program.
- 04
Automated regression
Scripts for APIs, Playwright for web, the official CLI for mini programs — one command, results written back.