[{"content":"","date":"3 June 2026","externalUrl":null,"permalink":"/","section":"Nina Ricci Marie Benite","summary":"","title":"Nina Ricci Marie Benite","type":"page"},{"content":" Technical Skills # I work across the full stack with a focus on building reliable, scalable systems.\n🧠 Systems \u0026 Backend Building event-driven and distributed systems that support real operational workflows. Rust Node.js Ruby on Rails GraphQL PostgreSQL MongoDB SQL Kafka RabbitMQ Microservices 🎨 Frontend \u0026 Product Engineering Building scalable, component-driven interfaces with a strong focus on usability, consistency, and maintainability. React React Native TypeScript Redux React Router Tanstack Query Jest TailwindCSS Playwright Storybook Experience in design system development and component-driven architecture, including close collaboration with design teams to translate UX direction into reusable UI primitives.\nContributed to an open-source design system, empowering engineers across teams to independently implement and extend UI components while maintaining consistency at scale. Focused on improving autonomy, reducing implementation friction, and increasing delivery speed across multiple products.\n☁️ Infrastructure \u0026 Reliability Ensuring systems are observable, scalable, and production-ready. Docker Kubernetes Jenkins CI/CD Grafana Datadog Helm 🧪 Testing \u0026 Quality Engineering Ensuring reliability through automated testing and predictable system behavior. Jest Playwright RSpec Unit Testing Integration Testing E2E Testing Test Automation Usability Testing User Acceptance Test Experience building test coverage across frontend and backend systems, including integration and end-to-end testing to ensure reliability in production workflows.\n📊 Data \u0026 Internal Systems Supporting decision-making and operations through data and internal tools. BigQuery Metabase Internal dashboards Workflow automation ⚙️ Engineering Principles Event-driven architecture System design thinking Cross-functional collaboration Observability-first development End-to-end ownership ","date":"3 June 2026","externalUrl":null,"permalink":"/skills/","section":"Nina Ricci Marie Benite","summary":"","title":"Technical Skills","type":"page"},{"content":"I’m a full-stack engineer focused on building systems that improve real-world workflows through thoughtful engineering, autonomy, and continuous learning.\nI care about building thoughtful features, and how they come together to form well-designed systems, especially in environments where engineering decisions directly affect operations, users, and business outcomes.\nOver time, I learned that strong engineering is not just about execution, but about understanding what to build and why it matters in the first place. This shaped how I work: I prefer ambiguous, real-world problems where clarity is discovered through iteration, not predefined.\nI also learned early that growth requires both independence and guidance. While self-directed learning has been central to my journey, meaningful exposure and mentorship helped shape direction when it mattered most.\nWhat I value # Ownership across the full stack: frontend, backend, and infrastructure Systems thinking over feature delivery Real-world impact over output volume Continuous learning as a core working principle Tools (including AI) as leverage for better engineering, not shortcuts The kind of work I enjoy # I work best in environments that are fast-moving, ambiguous, and outcome-driven, where engineers are trusted to take ownership and shape both the problem and the solution.\nI’m especially drawn to work that improves how people or teams operate in meaningful ways, not just incremental feature changes.\n","date":"3 June 2026","externalUrl":null,"permalink":"/about/","section":"Nina Ricci Marie Benite","summary":"","title":"About","type":"page"},{"content":"I came from a small province, Iloilo, in the Philippines with very limited exposure to modern tech companies.\nMy first real exposure to that world was during my internship at Synacy as a Frontend Web Developer Intern. That experience introduced me to startups for the first time, not just as a concept, but as a real environment where people were building and shipping products quickly.\nThrough that internship, and conversations with friends already working in the industry, I became aware of how different the startup ecosystem was compared to traditional development paths. Fast-paced, iterative, and deeply collaborative.\nThat was the moment I decided to intentionally focus on startups.\nI believed I would grow faster in environments where I could work closely with engineers, product teams, and real users, where feedback loops are short and learning happens quickly through shipping.\nAfter graduating, transitioning into that world was not straightforward.\nComing from a provincial background, opportunities in modern tech companies in the Philippines were limited, and competition was often shaped by factors beyond just skill. There were moments where it felt difficult to break into the kinds of companies I wanted to work in, especially without coming from more established universities in Metro Manila.\nStill, I kept building, applying, and improving.\nEventually, I was fortunate enough to join Quipper at the right time, an opportunity that became my entry point into real production-scale systems and professional software engineering.\nLooking back, it wasn’t a straight path. But it was a sequence of small opportunities, timing, persistence, and learning how to adapt quickly once I got in.\nFoundation (2012-2016) Philippines 🇵🇭 📍 West Visayas State University, Iloilo City Built the base Software development fundamentals First exposure to structured problem solving Learned discipline through engineering coursework In hindsight, formal instruction played a limited role in shaping my direction, with the notable exception of one course in DBMS that stood out for its practical depth.\nMost of my real growth during this period came from independent learning rather than structured teaching. I gradually realized that in fast-moving fields like software engineering, relying solely on being “taught” is not enough. You need to actively seek what to learn next.\nAt the same time, I also learned an important balance: independence does not mean isolation. Without exposure to real industry practices, it is difficult to even know what to learn or which direction to take. Early guidance, even small signals from mentors, peers, or occasional industry exposure, can significantly shape that trajectory.\nWith limited access to the tech industry at the time, I relied on small exposures and curiosity to gradually guide myself toward areas I found meaningful. Over time, this helped me develop a habit of self-direction: learning proactively, validating through practice, and adjusting based on feedback from real-world work.\nLater in my career, this perspective evolved further. I came to appreciate how important early exposure is for students who are in the same position I once was.\nBecause of that, I reached out to my college dean and several professors to help organize online talks with alumni and industry professionals, aiming to give students earlier exposure to real-world software engineering and career paths, something I personally lacked during my studies.\nFirst Job (2017-2021) Philippines 🇵🇭 📍 Quipper, Makati City My first real step into production systems. What I worked on:\nMigrated legacy systems (Backbone.js → React + TypeScript) Built reusable frontend architecture used across teams Delivered features for teachers and students (Quipper Create, Chat systems) Introduced observability with Datadog + scaling improvements Helped onboard and mentor new engineers What changed here:\nI learned how real users break things I learned scale is not theoretical I learned that frontend architecture is also system design Growth \u0026amp; Ownership (2021-present) Singapore 🇸🇬 📍 eyos → StashAway → Glints, Singapore This is where I shifted from “building features” to owning systems. 🧾 eyos\nBuilt SmartShopper (mobile-first web app) Led frontend architecture decisions Built scalable admin systems 💰 StashAway\nShipped MVP (Reserve) in a regulated fintech environment Worked with React Native + Node.js + event-driven systems Learned speed under constraint 👥 Glints\nThis is where I operated on systems-level ownership.\nBuilt and scaled:\nMulti-tenant Employer of Record (EOR) platform from scratch Backend services in Rust (APIs, workers, cron systems) Event-driven integrations (HRIS, CRM, ERP like HubSpot \u0026 NetSuite) Internal operational platforms used by HR, Finance, Ops, Sales Design system (`glints-aries`) used across multiple products Impact:\nReduced manual onboarding workflows significantly Improved cross-team operational efficiency Enabled expansion into new markets Improved system reliability via observability (Grafana, Datadog) Next Phase: System Ownership at Scale 🌍 Open to opportunities around EU Looking for environments where I can take end-to-end ownership of systems that directly impact how people and teams operate.\nInterested in roles that are:\nAutonomous and outcome-driven (not feature factories) Product and technically ambiguous Focused on real-world workflows, not just surface-level features Closely tied to business and operational impact I’m open to relocation and opportunities in EU where I can continue building systems that meaningfully improve people’s lives, while growing through complex, real-world challenges.\nIf you’re building something where engineering directly shapes real-world outcomes, I’d be happy to connect.\n🧠 What I’ve Learned Along the Way # Growth in engineering comes less from being taught everything, and more from learning how to actively find what to learn next Independent learning is essential, but early guidance and exposure are just as important in shaping direction Without context of real industry practices, it is difficult to even know what “good” looks like. Small signals and mentorship can change that trajectory significantly Systems matter more than isolated features. Long-term impact comes from how parts connect, not just what is built Real-world engineering is rarely about clear requirements. Interpretation, clarification, and alignment are part of the job Good engineering is often invisible (automation, observability, workflows, internal tooling that reduces friction) Cross-functional alignment is where most meaningful product impact happens, especially in operational-heavy systems Speed and correctness are not opposites. With the right architecture and discipline, they reinforce each other 🌱 How I Work Now # I do my best work in environments that are:\nAutonomous where engineers are trusted to take ownership end-to-end Product and technically ambiguous where problems are defined through exploration rather than fixed specs Focused on outcomes rather than output not feature factories, but systems that meaningfully improve how people work or live Close to the business where engineering decisions directly influence operational efficiency, user experience, or revenue impact System-oriented where ownership spans frontend, backend, and infrastructure rather than isolated layers I prefer building and owning entire problem spaces, from understanding the problem, to designing the system, to delivering and iterating based on real usage.\nI use modern tools, including AI, as leverage to accelerate understanding and delivery, not as shortcuts, but as part of a thoughtful engineering workflow.\n🚀 Closing Thought # From Iloilo to Singapore, the direction has always been the same:\nTo use modern technology and continuous learning to create meaningful impact in people’s lives\n","date":"3 June 2026","externalUrl":null,"permalink":"/journey/","section":"Nina Ricci Marie Benite","summary":"","title":"Journey","type":"page"},{"content":"","externalUrl":null,"permalink":"/categories/","section":"Categories","summary":"","title":"Categories","type":"categories"},{"content":"","externalUrl":null,"permalink":"/tags/","section":"Tags","summary":"","title":"Tags","type":"tags"}]