Engineering
Cut integration time 30% and query latency 15% on a rebuilt automotive platform
AutoStream 2.0 · Toyota Lanka (PVT) LTD · Nov 2024 – Apr 2025
Context
AutoStream started as a WordPress MVP for vehicle pricing, buying, selling and maintenance. Marketing wanted campaign-ready features the MVP could not support.
Problem
Requirements were undocumented and the MVP architecture made every new integration slow and error-prone, blocking Phase 1 marketing commitments.
My role
Associate/assistant product-engineering role: requirement gathering, scope definition for Phase 1, and backend service delivery alongside two internal developers and an external vendor.
Constraints
- Fixed Phase 1 launch date tied to a marketing campaign
- Existing MVP data had to be migrated without downtime
- Small team, shared with other Toyota Lanka initiatives
What I did
My contribution
- Ran requirement sessions with marketing and after-sales stakeholders and wrote the Phase 1 requirement set
- Designed the modular service boundaries and secure API contracts (NestJS + MySQL)
- Built core backend services and reviewed the external vendor's integration work
- Tracked Phase 1 scope, flagged risks weekly and kept the release aligned to the campaign date
Owned by the wider team
- Frontend implementation in ReactJS was owned by two internal developers
- QA test plans and regression cycles were owned by the QA engineer
- Infrastructure provisioning was handled by the internal IT team
What I'd do differently
- I would write acceptance criteria per requirement earlier — vendor rework came from ambiguity, not effort.
- I would instrument the platform on day one so the latency gain was measured continuously, not sampled.