Senior Full Stack Engineer

EMPLOYMENT TYPE: Full-time

SHIFT: 1:00PM-10:00PM

II. JOB SUMMARY

This is not a follow-the-tickets role. You will be one of the senior engineers on an engagement where architecture decisions are still being made and the codebase is being built from scratch. You are expected to:

• Own the NestJS BFF layer end-to-end — schema design, service architecture, resolver patterns, and endpoint contracts.
• Make confident decisions on the services layer without needing approval for every pattern.
• Bridge the BFF to the Spring Boot business logic service, negotiating API contracts and ensuring clean separation of concerns.
• Drive the React/Next.js frontend from an architecture standpoint — you do not need to be a pixel-perfect designer, but you must enforce the pattern that React contains zero business logic.
• Contribute to and challenge architectural decisions in weekly syncs with the Abstractech solution architect.
• Write code that is clean, typed, documented, and suitable for long-term production use.

III. RESPONSIBILITIES

• Design and own the TypeORM schema for field_registry, base_field_types, screen_metadata, and data_sources tables in PostgreSQL.
• Build and maintain FieldResolverService — walks zones → sections → fields, resolves values from named data sources, and returns fully-hydrated screen payloads.
• Implement the behaviour execution endpoint (POST /field-registry/behaviour/execute): evaluates trigger conditions, fetches from configured data sources, and returns bulk field-populate maps.
• Define and enforce the screen layout JSON schema (zones + sections model) and validate all incoming screen save/update requests against it.
• Expose a clean Swagger/OpenAPI spec — the BFF API is the contract for both the React frontend and the Java service integration.
• Own all BFF seed data: base field types, field registry entries for every screen, data source registrations, and behaviour rules.

• Collaborate with the Java engineer to define REST API contracts for the business logic service (accounts, customers, transactions, exchanges).
• Register and configure Java service endpoints as named data sources in the BFF data_sources table.
• Ensure the BFF never calls the Java service directly from React — all cross-service calls are proxied and enriched through the BFF.
• Design the behaviour fetchPath template syntax ({value} substitutions, query parameter mapping) used by field behaviours to call the Java service.

• Architect and enforce the RENDERER_MAP pattern — a pure lookup from renderer name to component, with no conditional business logic in field components.
• Design ScreenFormContext: shared form state (values, errors, per-field loading) consumed by all input field components.
• Build FieldBehaviourEngine: the client-side trigger runner that calls POST /field-registry/behaviour/execute on blur/change and dispatches bulk setFieldValues to form context.
• Define the zones + sections renderer hierarchy: ScreenRenderer → ZoneRenderer → SectionRenderer → FieldRenderer.
• Establish the shell chrome pattern: ShellLayout, LeftNav, TopBar, RightSidebar are hardcoded permanent components — never driven by screen metadata.
• Review all frontend PRs for business logic leakage into field components.

• Deliver key milestones including BFF extensions, React shell foundation, core input components, and end-to-end demo capabilities.
• Ensure all BFF endpoints are exercisable via Swagger UI before any frontend integration begins.
• Lead the end-to-end integration test: customer_name lookup populates dependent fields; denomination table computes live; stepper reflects resolved step from BFF.
• Write TypeScript strictly — no implicit any, no untyped API responses, DTOs with class-validator decorators on all inputs.
• Proactively identify and address technical debt to ensure production-readiness.
• Participate in demo preparation and walkthrough

• Report to the Abstractech solution architect; coordinate daily with the Java engineer and frontend specialist.
• Raise architectural blockers early to ensure steady progress on delivery goals.
• Document all non-obvious design decisions (especially the two-table field registry pattern, behaviour schema, and zones layout schema) in the repository README and/or architecture decision records.
• Mentor junior frontend developers on the renderer pattern and form context architecture.

• → 5+ years of professional full stack development experience.
• → 3+ years with NestJS or equivalent Node.js server frameworks (Express, Fastify) at production scale — you understand modules, guards, interceptors, and dependency injection at a structural level. Senior Full Stack Engineer — Job DescriptionPage 3

• → Deep TypeScript fluency — strict mode, generics, discriminated unions, utility types. No training required.
• → Strong React experience (hooks, context, custom hooks, component composition). You have built and maintained large React codebases.
• → Experience designing REST API contracts and validating them with OpenAPI/Swagger.
• → Relational database design experience — you can design a normalised schema, write migrations, and reason about query performance.
• → Ability to read and work alongside Java/Spring Boot code — you do not need to be a Java engineer but must be able to review API contracts, DTOs, and data models produced by the Java engineer.
• → Comfort operating in a fast-paced environment: making pragmatic decisions and flagging tech debt without cutting critical corners.
• →Next.js experience — SSR, SSG, App Router, PWA configuration.

• Experience building metadata-driven or configuration-driven UI systems (form builders, CMS renderers, low-code platforms).
• Prior work in fintech, banking, or other regulated industries.
• Familiarity with Keycloak, Auth0, or other OIDC identity providers.
• Experience with dnd-kit or similar drag-and-drop libraries.
• Knowledge of Kafka, Redis, or event-driven architecture (needed for Phase 2).
• Familiarity with WSO2, Kong, or Apigee API gateways.

Take the next step in your career and apply now to join our world-class team!