About Me
Hi! I'm Javier Tay! 👋
I've been a builder for as long as I can remember. It started with LEGO bricks, where I spent hours figuring out how individual pieces could form a complex whole. That childhood curiosity evolved into a professional mission through my journey from ITE to Temasek Polytechnic, and now as a 2nd-year Computer Science undergraduate at Nanyang Technological University.
The time at my previous education institutes gave me a solid, hands-on foundation in technical problem-solving. It taught me that I don't just want to understand how things work - I want to build them. Today, I've traded plastic bricks for code, focusing on AI/ML Engineering to turn complex requirements into intelligent products that solve real-world problems.
Whether I'm developing a project between lectures or refining my skills, I bring a "builder's mindset" to everything I do. I'm currently seeking Software Engineering internships where I can contribute to shipping features and learn from experienced teams.
When I'm not coding, you'll usually find me on the badminton court or looking for the next challenge to tackle.
What I'm Looking For
💼 Role Type
Software Engineering / AIML Engineering Internships (Summer 2025 or immediate)
🎯 Focus Areas
Frontend & full-stack web apps, automation, developer tooling, AI-assisted workflows
My Skillsets
A curated set of tools I use regularly and keep refining.
TypeScript
JavaScript
React
Next.js
HTML & CSS
Tailwind
Node.js
ExpressMy Approach
How I think about building software that matters.
Start with the problem
I focus on understanding the core problem before jumping into solutions. This ensures that the products I build truly address user needs and deliver value.
Build small, Iterate fast
I believe in launching MVPs quickly to gather user feedback. This helps me learn faster and avoid locking onto wrong design early.
Design for clarity and change
I structure code around clear responsibilities, typed boundaries, and modular components so features are easier to extend and reason about as requirements evolve.
Debug, Reflect
When something is slow or broken, I rely on logs, and reproducible tests rather than guessing. After each project, I reflect on trade-offs and document what I'd improve next time.
Let's Connect
I'm always interested in hearing about new opportunities, collaborations, or just chatting about tech. Feel free to reach out through any of these platforms: