Job Opportunities API

ABOUT LABRYNTH Labrynth accelerates progress by streamlining regulatory complexity. We build AI-powered platforms that navigate complex regulations, generate audit-level documentation, and provide certainty, not shortcuts. Our technology serves clients across heavily regulated industries including energy, compliance, and government regulations. We operate as a forward-deployed engineering organization: small, high-velocity teams embedded directly with clients to rapidly discover needs and ship production-quality solutions. ABOUT THE ROLE We're building the next product in this line: an invite-only B2C platform for personal and team accounts, developed as a greenfield product alongside the current application in the patent/IP space. We're looking for a Front End Engineer to own the client-facing B2C experience end to end: invited-account onboarding, account and membership UX, a guided exploration experience built over our workspace/exploration/idea/draft model, and durable-operation progress UI — all built entirely against our generated BFF client, and all built to hold up in live prospect and partner demos. This is a contract engagement (Agency / Statement of Work), with an initial term of 60–90 days and the option to extend. You'll report to the Patent Project engineering lead and coordinate closely with Backend, DevOps/Platform, Security, our Product designer, and QA. A note on the architecture: identity runs through Amazon Cognito (customer pool: email/password + Google federation, PKCE), with customer sessions as opaque, HttpOnly/Secure cookies issued by our BFF. The TypeScript BFF is the sole authorization, capability, entitlement, and domain-mutation boundary — the frontend is a presentation and interaction layer that consumes generated OpenAPI clients only, even for server-rendered calls. The frontend holds no database, Neo4j, S3, Stripe-secret, queue, model-provider, or worker credentials. Private customer data lives in PostgreSQL and S3; Neo4j holds only the shared public patent corpus. During closed beta, payment is disabled by configuration, and entitlements resolve through a capability matrix. WHAT YOU'LL DO Immediate deliverables (first 2–4 weeks) - Wire up the BFF client: consume the checked OpenAPI contract via generated clients, and establish stable success/error envelopes, request IDs, idempotency-key and If-Match plumbing, and loading/empty/error/permission state scaffolding. - Build invited sign-in and account context: Cognito sign-in (email/password + Google, PKCE) wired to opaque BFF sessions and protected routes, with explicit account-context switching on staging. - Stand up the guided-exploration entry point: exploration create/run UI wired to the agent and the public corpus, showing the operation lifecycle via resumable SSE on staging. - Conduct a UX & code audit: review for correctness, performance, and consistency; produce a prioritized fix list and a design-system alignment plan. 60–90 day scope - Invited-account onboarding: invitation acceptance (personal signup / team membership), first workspace creation, first source upload with visible quarantine states (upload_pending → quarantined → processing → available|rejected|processing_failed), and ToS/legal-disclosure acceptance. - Account & membership UX: personal/team accounts, owner/member capabilities via capability policy v1, membership states, and guarded personal↔team conversion flows, with the active account always explicit and never inferred. - Guided exploration experience: the primary entry point over the workspace/exploration/idea/draft model, surfacing exploration lineage (derived_from / incorporates / branches_from / supersedes) and the operation lifecycle (accepted → dispatched → executing → succeeded|failed|cancelled|expired); raw model chain-of-thought is never shown. - Durable-operation progress: fetch-based resumable SSE (auth via header, cookie, or storage; reconnect replays from