Software Engineer - Frame work | Offshore - HYD

JDSoftware Engineer — ADI Portal Platform
\n Alter Domus Intelligence · hybrid · 2 open roles
\n About the role
\n The ADI Intelligence team is building the next-generation client portal for Alter Domus — a
\n single-spa micro-frontend platform that brings fund managers, investors, accountants, and
\n administrators into one unified experience, backed by real-time data.
\n We're growing the platform team by two engineers. You'll own features end-to-end: from
\n writing the user story acceptance criteria to shipping to production via our CI/CD pipeline. The
\n work spans frontend (React micro-frontends, design system, dashboard widgets), platform
\n infrastructure (CloudFront, WAF, Terraform), and authorization (OpenFGA fine-grained
\n permissions model).
\n You won't be a cog in a large machine. The platform team is small, the backlog is concrete, and
\n the impact is immediate — every story you ship goes directly into the hands of Alter Domus
\n clients and employees.
\n What you'll work on
\n • Build and polish the Home dashboard MFE — pending approvals, portfolio metrics
\n widgets, quick actions, and the extensibility API that lets squad MFEs register their own
\n widgets.
\n • Complete the Admin console — user management, group permissions, fund access
\n control, and the OpenFGA role assignment UI wired to our authz service.
\n • Harden the shell: profile settings drawer, DomiAI assistant button, notification priority,
\n and email delivery.
\n • Design and implement the OpenFGA authorization model — personas, entity hierarchy,
\n FGA DSL, test suite, real-time tuple sync.
\n • Build and maintain the CI/CD promotion pipeline (dev → qa → sim → prod) on GitHub
\n Actions.
\n • Integrate Heap analytics, Sentry error tracking, and MFE loading/error boundaries.
\n • Collaborate with the Photon component library team to keep ADI on the latest releases.
\n Tech stack
\n • Frontend: React 18, TypeScript, Vite, Tailwind v4
\n • MFE Framework: single-spa, import maps
\n • Auth: Auth0, OpenFGA
\n • APIs: GraphQL, REST
\n • Infra: AWS, Terraform
\n • CI/CD: Github Actions, pnpm
\n • Observability : Grafana, Sentry, Heap
\n What we're looking for
\n Must have:
\n • 3+ years shipping production React + TypeScript applications.
\n • Strong grasp of browser fundamentals — module loading, HTTP caching, authentication
\n flows, CSS cascade.
\n • Experience with CI/CD pipelines and deploying to cloud infrastructure (AWS or
\n equivalent).
\n • Comfort reading and writing Terraform (or a strong desire to learn it fast).
\n • You write code that your teammates enjoy reviewing — clear, well-named, no surprises.
\n Nice to have:
\n • Micro-frontend experience (single-spa, Module Federation, or import maps).
\n • Familiarity with fine-grained authorization systems (OpenFGA, Oso, Casbin, or Zanzibarinspired models).
\n • Previous work in financial services or regulated environments.
\n • Contributed to a shared component library or design system.
\n We don't care about:
\n • Degree requirements.
\n • Whether you know our exact stack — we care that you learn fast and ask good
\n questions.
\n What good looks like
\n You read a user story, ask one clarifying question if needed, and ship it. You push back when
\n acceptance criteria are vague. You break large stories into reviewable PRs. You leave the
\n codebase better than you found it — but you don't over-engineer.
\n You're comfortable working in a polyglot environment (TypeScript frontend, occasional
\n Python/Node for tooling, HCL for infra) and you don't wait to be unblocked — you investigate,
\n form a hypothesis, test it, and move.