n
norberto1029

Norberto Joso

@norberto1029

Senior software engineer

Filippine
Inglese
Alcune informazioni sono riportate in lingua inglese.
Chi sono
Senior Software Engineer with 9+ years of experience building scalable web applications, SaaS platforms, internal systems, and customer-facing products using modern frontend and backend technologies. Specialized in scalable frontend architecture, dashboard systems, API development, realtime workflows, authentication systems, and performance optimization for production applications. Experienced in leading feature delivery from architecture planning to deployment and production support while collaborating closely with cross-functional teams in agile environments.... Continua a leggere

Competenze

n
norberto1029
Norberto Joso
offline • 
Tempo di risposta medio: 1 ora

Consulta i miei servizi

Applicazioni web full stack
I will build a web app using javascript frameworks and node

Esperienza lavorativa

Really_Really Good

Senior Software Engineer

Really Really Good • Part time

Jan 2026 - Apr 20263 mos

• Implemented RBAC-aware navigation and route guards across 14 admin routes and 4 permission tiers; cut “wrong screen / forbidden” support tickets on the new modules from 9 in the first 14 days of rollout to 2 over the following 45 days • Refactored the slowest data tables: capped page size at 25 rows, 300ms debounced search, skeleton states, and collapsed the first-paint data fetch chain from 8 sequential calls to 3 batched calls; p75 time-to-interactive on those views improved from ~1.9s to ~1.1s in Chrome Lighthouse runs on staging hardware • Partnered with US-based product and design on 22 scoped tickets with written acceptance criteria; 20 of 22 (91%) passed QA on first submission in the final 8-week window of the engagement • Added 38 Vitest + React Testing Library cases on the code paths touched, raised line coverage on those files from 54% to 81%, and removed 3 flaky tests that had been blocking ~40% of frontend merges on the main branch • Produced an 8-page handoff (local setup, 5 environment variables, smoke checklist, rollback notes) so the core team could own the shipped modules without a same-week knowledge gap

Southern_Cross Austereo

Senior Software Engineer

Southern Cross Austereo • Full time

Jan 2022 - Jan 20264 yrs

• Introduced a shared UI kit and dashboard layout patterns that cut duplicate frontend code by roughly 35% across three product teams and shortened new screen delivery by about one sprint on average • Owned REST and GraphQL APIs behind booking and reporting workflows; reduced average read latency on hot list endpoints by ~22% via selective fields, pagination caps, and PostgreSQL index tuning • Improved Core Web Vitals on the main customer app: ~25% better LCP and ~18% lower CLS after code-splitting, image policy changes, and fewer waterfall API calls on first paint • Hardened auth (JWT refresh rotation, RBAC checks on sensitive routes) and tightened validation so production auth-related incidents dropped from a handful per quarter to zero over the last 12 months • Worked async across product, design, and QA in Australian business hours with clear written RFCs, design handoffs, and weekly release notes for stakeholders • Mentored four engineers (junior to mid) through pairing, async reviews, and runbooks; two were promoted to mid-level within ~14 months • Ran on-call rotation and postmortems for production issues; mean time to restore for Sev-1/2 incidents the team owned improved by ~40% after adding dashboards, alerts, and repeatable rollback steps

LinkedIn

Full Stack developer

LinkedIn • Full time

Jun 2018 - Dec 20213 yrs 6 mos

• Delivered end-to-end features (React/Next.js UI, Node services, PostgreSQL) for admin dashboards, notifications, and reporting used by ~200–350 internal users depending on the account • Built a shared table/filter component set that removed ~30% of one-off list screens and made bug fixes in one place instead of six divergent copies • Implemented auth, email/SMS hooks, and scheduled jobs for nightly exports; cut failed export runs from ~8% to under 2% by adding retries, idempotency keys, and clearer error surfaces • Added indexes and query refactors on the busiest reporting paths, improving typical report generation from ~45s to ~12s for the top five queries • Refactored duplicated validation into shared server modules and trimmed inconsistent API responses, which reduced regression bugs in those areas by roughly half over two quarters (tracked in Jira) • Partnered with QA on reproduction steps, edge-case fixtures, and release checklists; kept average defect reopen rate under 10% for features the team owned • Joined remote planning, sizing, and design reviews; documented deployment order and config flags so handoffs to ops rarely needed same-day hotfixes • Supported production through logs/metrics, on-call windows, and small hardening passes (timeouts, circuit breakers on flaky third-party calls)