Full Stack Engineer
Hace 3 días
Tarragona, Cataluña, España
Albertine
Jornada completa
Gratis con email o Google
Guarda esta oferta y sigue tu búsqueda
Crea una cuenta gratis para guardar empleos, crear alertas y volver a esta oferta desde tu panel.
Gratis con email o Google
Al continuar, aceptas nuestros Términos & Política de Privacidad.
Albertine builds white-label digital concierge experiences for luxury brands and their members. The product runs on a multi-tenant TypeScript platform: a Hono API that powers member-facing concierge apps, LMT
- the internal platform agents use to manage members and operations
- plus payments, recommendations, messaging, and a growing set of third-party integrations. The frontend spans those same surfaces, shared component libraries, and the design system that keeps each brand distinct. The role We're hiring a full stack engineer to ship features across that platform. A membership change, a booking flow, an agent tool: you shape the API contract, implement the service and data work, and ship the React UI members and agents actually use. Both halves need to hold up in review
- sound data and API choices, and UI that feels finished. You're not here to paint tickets: you're here to improve the product. Concierge operations, memberships, bookings, and billing are real business logic with real edge cases. You'll be expected to push back on requirements, notice when a model or a flow is wrong, and care about what members and agents hit in production. Luxury detail matters on both sides of the stack: a clumsy empty state and a query that falls over under a bigger tenant are both broken experiences. We work AI-native. Coding agents are part of how we build, prototype, and refactor. You still own taste, judgment, and review. Speed without judgment isn't the bar. What will you do?
* Ship TypeScript features end to end: a vertical API slice on our Hono service
- OpenAPI-first contracts, generated types, integration tests
- and the React UI that consumes it
* Design the API contract for the features you own, in conversation with web, iOS, Android, and partner clients, including versioning and backwards compatibility when a shipped mobile app depends on it
* Model and query the data those features need in Postgres, with sound transactions, indexes, and consistency boundaries, inside the patterns the platform already uses
* Build the UI in Concierge, LMT, and shared web libraries: forms, multi-step flows, data-heavy screens, loading and error states, responsiveness, and accessibility that meets the existing review bar
* Follow the frontend architecture, design system, and design-token theming that other people own. Propose UX improvements with design and product; implement them in the patterns already there
* Wire integrations, webhooks, and background work when the feature needs them, following existing retry, idempotency, and observability patterns rather than inventing new ones
* Hand platform-scale problems
- tenancy isolation, long-running workflows, query performance at 10x, a new integration's failure modes
- to the people who own them, with a clear write-up of what you found
* Use coding agents as a default accelerator with clear specs, sharp review, and solid tests
* Communicate clearly for a remote team: design notes, PR descriptions, async updates What are we looking for? Must have:
* 5+ years building and operating production web products, preferably in TypeScript, with substantial work on both the API and the UI
* Strong product instincts: you can work from incomplete specs, push back on requirements and UX, and own outcomes
- not just tasks
* Enough backend judgment to design a feature's REST contract, schema, and tests and have them hold up: errors, pagination, transactions, indexing, and basic query diagnosis
* Enough frontend judgment to implement a feature in an existing React and TypeScript app and pass review: state, routing, caching, forms, responsive layouts, and the details that make a screen feel finished
* Comfort working inside an existing architecture on both sides. You extend the patterns; you don't replace them
* Production habits on both sides of a feature: integration tests for the API, and care for states, accessibility, and responsiveness in the UI
* Comfort operating what you ship: logging, tracing, and debugging a production issue whether it starts in the client or the service
* Comfortable with AI-assisted / agentic development as day-to-day practice: supervising agents, reviewing output, and knowing when to slow down and craft by hand
* Effective remote collaboration: proactive communication, async documentation, direct feedback Nice to have:
* Fluency with our frontend stack (Vite, TanStack Query/Router, Tailwind) and the shared design system, including Storybook
* Google Cloud familiarity (Cloud Run, Cloud SQL, Pub/Sub, Firebase)
* Identity and access: OIDC/OAuth2, Keycloak, or similar
* Experience with queues, scheduled jobs, webhooks, and third-party APIs
* White-label or multi-tenant product experience, on the API, the UI, or both
* Mobile client concerns: push notifications, offline behavior, long-lived app versions
* Motion and interaction craft in production UIs
* Migrating a domain off a legacy datastore without downtime Why Albertine?
* Join a fast-growing, technology-driven
- the internal platform agents use to manage members and operations
- plus payments, recommendations, messaging, and a growing set of third-party integrations. The frontend spans those same surfaces, shared component libraries, and the design system that keeps each brand distinct. The role We're hiring a full stack engineer to ship features across that platform. A membership change, a booking flow, an agent tool: you shape the API contract, implement the service and data work, and ship the React UI members and agents actually use. Both halves need to hold up in review
- sound data and API choices, and UI that feels finished. You're not here to paint tickets: you're here to improve the product. Concierge operations, memberships, bookings, and billing are real business logic with real edge cases. You'll be expected to push back on requirements, notice when a model or a flow is wrong, and care about what members and agents hit in production. Luxury detail matters on both sides of the stack: a clumsy empty state and a query that falls over under a bigger tenant are both broken experiences. We work AI-native. Coding agents are part of how we build, prototype, and refactor. You still own taste, judgment, and review. Speed without judgment isn't the bar. What will you do?
* Ship TypeScript features end to end: a vertical API slice on our Hono service
- OpenAPI-first contracts, generated types, integration tests
- and the React UI that consumes it
* Design the API contract for the features you own, in conversation with web, iOS, Android, and partner clients, including versioning and backwards compatibility when a shipped mobile app depends on it
* Model and query the data those features need in Postgres, with sound transactions, indexes, and consistency boundaries, inside the patterns the platform already uses
* Build the UI in Concierge, LMT, and shared web libraries: forms, multi-step flows, data-heavy screens, loading and error states, responsiveness, and accessibility that meets the existing review bar
* Follow the frontend architecture, design system, and design-token theming that other people own. Propose UX improvements with design and product; implement them in the patterns already there
* Wire integrations, webhooks, and background work when the feature needs them, following existing retry, idempotency, and observability patterns rather than inventing new ones
* Hand platform-scale problems
- tenancy isolation, long-running workflows, query performance at 10x, a new integration's failure modes
- to the people who own them, with a clear write-up of what you found
* Use coding agents as a default accelerator with clear specs, sharp review, and solid tests
* Communicate clearly for a remote team: design notes, PR descriptions, async updates What are we looking for? Must have:
* 5+ years building and operating production web products, preferably in TypeScript, with substantial work on both the API and the UI
* Strong product instincts: you can work from incomplete specs, push back on requirements and UX, and own outcomes
- not just tasks
* Enough backend judgment to design a feature's REST contract, schema, and tests and have them hold up: errors, pagination, transactions, indexing, and basic query diagnosis
* Enough frontend judgment to implement a feature in an existing React and TypeScript app and pass review: state, routing, caching, forms, responsive layouts, and the details that make a screen feel finished
* Comfort working inside an existing architecture on both sides. You extend the patterns; you don't replace them
* Production habits on both sides of a feature: integration tests for the API, and care for states, accessibility, and responsiveness in the UI
* Comfort operating what you ship: logging, tracing, and debugging a production issue whether it starts in the client or the service
* Comfortable with AI-assisted / agentic development as day-to-day practice: supervising agents, reviewing output, and knowing when to slow down and craft by hand
* Effective remote collaboration: proactive communication, async documentation, direct feedback Nice to have:
* Fluency with our frontend stack (Vite, TanStack Query/Router, Tailwind) and the shared design system, including Storybook
* Google Cloud familiarity (Cloud Run, Cloud SQL, Pub/Sub, Firebase)
* Identity and access: OIDC/OAuth2, Keycloak, or similar
* Experience with queues, scheduled jobs, webhooks, and third-party APIs
* White-label or multi-tenant product experience, on the API, the UI, or both
* Mobile client concerns: push notifications, offline behavior, long-lived app versions
* Motion and interaction craft in production UIs
* Migrating a domain off a legacy datastore without downtime Why Albertine?
* Join a fast-growing, technology-driven