Pamylla Ostermann

Backend • Middle • Florianópolis, Brazil • UTC-03:00 • Fully remote • Work permits: Brazil • Citizenship: Brazil • English: B2 • Can start in a week • from $5k per year

Frontend Developer

6+ years exp

JavaScript

TypeScript

Node JS

API Design: 4/10

Invite to interview

Download CVCV

Overview

Technical skills

Timeline

Roles

Overview

A Middle-level frontend engineer focusing on Vite+React SPAs and tight integrations with backend services for health-intelligence workflows. The strongest proven skill is server-state and API integration evidenced by apps/web/src/api/queries.ts together with the backend job/worker wiring (apps/api/src/modules/jobs/pg-boss.queue.ts and apps/api/src/modules/extractions/extraction.worker.ts). There is limited public evidence of measured web-performance programs, thorough a11y engineering, or broad e2e/performance benchmarks.

Phone

Technical skills

Languages

JavaScript

TypeScript

Node JS

Frontend

React.js

Angular

Bootstrap

Apollo Client

Angular Material

GraphQL

Storybook

Lighthouse

React Query

Web Components

Other

Cypress

Jest

Figma

Claude Code

Nest.JS

AWS

PostgreSQL

Next.js

Tailwind CSS

Claude

Amazon S3

MySQL

React Native

Redux

Vitest

Prisma

RxJS

Vite

GitHub

GitHub Actions

NgRx

Docker

Git

GitLab

GitLab CI

Rest API

Copilot

Webpack

PostCSS

CI/CD

RAG

Prompt Engineering

Timeline

Senior Frontend Engineer • Senior

Audaces • Full-Time

Feb 2020 to Present 6 Years 8 Months Florianópolis Partially remote

Owned frontend architecture and technical decisions across multiple Audaces products, including greenfield and enterprise SaaS modules. Led modernization work such as REST-to-GraphQL migration using Apollo Client, and introduced Angular Signals to reduce client-side technical debt. Built a reusable design system with Web Components and Storybook, improved performance using Lighthouse-driven optimizations, and strengthened quality with Jest/Cypress and CI/CD workflows. Implemented an AI-assisted development workflow using Claude Code that was adopted by a large engineering group.

React.js

Angular

TypeScript

JavaScript

GraphQL

Apollo Client

Web Components

Storybook

Lighthouse

Jest

Cypress

Claude Code

Technical Education Mentor • Middle

SENAI/SC • Full-Time

Mar 2022 to Jan 2024 1 Year 10 Months In office

Mentored developers through Angular and software engineering bootcamps, supporting both technical growth and career progression. Created and reviewed training materials and provided feedback on hands-on projects with a focus on architecture and code quality. Helped participants apply engineering best practices to real-world projects.

Angular

SENAI

Bachelor's Degree • Systems Development

2019–2021 Santos, São Paulo

Software Development Intern • Junior

Minerador (Claro Empresas CRM) • Internship

Feb 2019 to May 2019 3 Months In office

Implemented and maintained features in an internal CRM platform using AngularJS. Worked on frontend functionality and supported ongoing improvements to the application during the internship period.

Angular

Middle Backend Developer Confidence: Medium API Engineer

API-focused Node.js backend engineer at a Middle level specializing in well-tested service-layer logic and API contract fidelity. The strongest proven skill is service-layer correctness and defensive state transitions as demonstrated by apps/api/src/modules/extractions/extractions.service.test.ts which validates owner-scoped lookups, idempotent discard, and conflict rejection. The public code shows limited evidence of production-grade operational concerns such as migration chains, tuned SQL, distributed-resilience patterns, or end-to-end queue/worker instrumentation.

API Design

4/10

How well APIs are designed

Clear, consistent API contracts and error semantics at the service layer are present, with explicit 404/409 handling and a mock client that mirrors the API surface. No evidence of advanced versioning, global pagination strategy, or idempotency-key patterns at HTTP boundary.

Evidence

apps/api/src/modules/extractions/extractions.service.test.ts: asserts extraction lookup scoped to owner and returns mapped review; tests for ConflictException and NotFoundException

apps/web/src/api/MockApiClient.ts: full ApiClient implementation mirroring endpoint surface (getBatch, getBiomarkers, uploadReport, getExtraction)

Data Layer & Database

2/10

Working with databases

Basic data-layer interaction is exercised via well-written service tests that mock Prisma calls and validate correct queries and updates. There is no visible migration history or evidence of tuned queries, explicit transaction boundaries, or isolation-level considerations in the scored files.

Evidence

apps/api/src/modules/extractions/extractions.service.test.ts: mocks prisma.extraction.findFirst and prisma.extraction.update and asserts correct where/data shapes

Scalability & Performance

1/10

Handling load and speed

Little to no evidence of production scalability measures: no caching/invalidation strategy, no queue consumer tuning, and no load-test artifacts in the human-authored files. The frontend mock simulates latency but that is only for UX testing.

Evidence

apps/web/src/api/MockApiClient.ts: LATENCY_MS simulation used for UI latency only

System Architecture

3/10

Overall system structure

Module and service separation is deliberate and test-focused with a clear client-server contract and service-layer tests, showing reasonable modularity for API and review workflows. There is not yet evidence of multi-service choreography, service decomposition trade-offs, or resilience boundaries in the scored files.

Evidence

apps/web/src/api/MockApiClient.ts: implements ApiClient interface and mirrors server contract

apps/api/src/modules/extractions/extractions.service.test.ts: focused service-layer testing for extraction review, updateItem and discard flows

Security & Auth

2/10

Protecting data and access

Some boundary security checks are implemented at the service level (owner-scoped lookups, rejecting edits when status changed), showing basic auth/authorization attention. There is no evidence in the scored files of token lifecycle, refresh/revocation, secret management, or explicit SQL injection/SSRF mitigations.

Evidence

apps/api/src/modules/extractions/extractions.service.test.ts: verifies lookups include userId scope and rejects unauthorized edits

Reliability & Observability

3/10

Stability and monitoring

Reliability is addressed at the code and test level with idempotency checks and guarded state transitions (e.g., discard idempotency and rejecting edits once extraction leaves review). There is no visible retry/backoff, circuit-breaker configuration, structured correlation logging, or graceful-shutdown logic in the human-authored files.

Evidence

apps/api/src/modules/extractions/extractions.service.test.ts: tests for idempotent discard, rejection of edits when status is confirmed, and 404 handling

Expertise

Microservices & API Architecture• Middle

Node.js• Middle

Industries

Health Care• Middle

Technologies

Node JS• Middle

Rest API

Nest.JS

GraphQL• since 2020

Prisma

Recommendations

Implement and document explicit transaction boundaries and migration history for Prisma flows, then add tests that assert transactional invariants during multi-step operations.
Harden operational resilience by adding timeouts, retries with backoff, and graceful shutdown hooks for any worker/queue consumers; add tests or integration checks for these behaviors.
Expand API design artifacts: add explicit versioning rules, pagination contracts where applicable, and a documented error-contract (shared zod schemas) consumed by both MockApiClient and real controllers.
Add a small performance/observability spike (structured logging with correlation ids, basic metrics) around the ingestion/extraction pipeline to prove end-to-end reliability and make production issues observable.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

BIOX Beach-App

Middle Frontend Developer Confidence: Medium Fullstack

UI Component Architecture

4/10

How interface parts are built

Component boundaries and a small design-system foundation exist, but most UI work looks scaffolded or conventional rather than a bespoke component library with advanced composition patterns.

Evidence

apps/web/src/ui/cx.ts

apps/web/src/ui/fonts.ts

docs/03-design/BIOX App.html

Responsive & Cross-browser

3/10

Works on all screens and browsers

Basic responsive/layout concerns and type/fonts are handled (Vite + web fonts, SVG thumbnail), but no clear evidence of container queries, RTL or deliberate cross-browser feature-detection work.

Evidence

docs/03-design/BIOX App.html

apps/web/vite.config.ts

apps/web/src/ui/fonts.ts

Performance Optimization

2/10

Speed of the interface

Some sensible defaults (Vite, tsup, React Query) and a monorepo build are present, but there is little public, measured performance work (bundle-analysis, RUM, LCP/INP before/after) or advanced runtime tuning in the frontend artifacts.

Evidence

apps/web/package.json

packages/shared/package.json

Accessibility & Semantics

2/10

Usable for everyone

A few static design artifacts and sensible HTML exist, but there is minimal explicit a11y engineering (focus management, ARIA on custom widgets, axe/eslint-a11y CI) surfaced in the human-authored frontend files.

Evidence

docs/03-design/BIOX App.html

apps/web/src/features/auth/session.ts

State Management & Data Flow

5/10

Managing data in the app

Clear, pragmatic server-state and data-flow discipline is present: React Query on the client, a push/pull ingestion pipeline, pg-boss job queue and a worker for extraction; this shows real end-to-end thinking about server-state and async flows.

Evidence

apps/web/src/api/queries.ts

apps/api/src/modules/jobs/pg-boss.queue.ts

apps/api/src/modules/extractions/extraction.worker.ts

UX & Visual Polish

4/10

Look and feel quality

Good product-level polish and mock fixtures plus a documented design thumbnail exist, and there are controlled UX flows (upload, review, mock API), but thorough UX edge-state coverage (measured skeletons, undo/rollback patterns everywhere) is not consistently surfaced.

Evidence

docs/03-design/BIOX App.html

apps/web/src/api/MockApiClient.ts

apps/web/src/api/fixtures.ts

Expertise

Frontend Architecture & Build Tools• Middle

Industries

Health Care• Middle

Technologies

JavaScript• since 2020 • Senior

TypeScript• since 2020 • Senior

Redux

Webpack

Tailwind CSS

Next.js

GitHub Actions

RxJS

GitLab CI

Angular• since 2019

CI/CD

Git

AWS

Docker

React.js• since 2020

Vite

React Query

Storybook• since 2020

Apollo Client• since 2020

PostCSS

Web Components• since 2020

NgRx

GitHub

GitLab

Amazon S3

Recommendations

Build UX-critical SPA features that integrate server-state (React Query) with backend workflows and job queues (upload/extraction/review flows).
Implement and maintain health-focused dashboards and design-system components for clinical data (biomarker catalog normalization and review UI).
Develop ingestion and worker-backed backend integrations (pg-boss, extraction workers, storage adapters) alongside the web UI wiring.
Tackle component-level accessibility and measured performance optimizations (Lighthouse/RUM-driven improvements and bundle analysis).

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

BIOX Teste-Audacces