The Technical Architect will serve as the technical point of reference, with the objective of transforming business goals into robust, evolvable, secure, and operable architectures.
Responsibilities
Define the end-to-end technical architecture of the project, including components, integrations, data flows, dependencies, and boundaries of responsibility.
Make and document architectural decisions using ADRs, evaluating alternatives, trade-offs, evolution costs, risks, and operational consequences.
Translate functional and non-functional requirements into implementable designs, technical acceptance criteria, and an evolution roadmap.
Design scalable and resilient distributed solutions, considering consistency, concurrency, idempotency, fault tolerance, and disaster recovery.
Participate in the development of critical components and conduct code reviews focused on design, maintainability, security, and operational behavior.
Requirements
Nice to have: financial platforms
Nice to have: corporate banking
Nice to have: trading
Nice to have: high-criticality transactional systems
Lead end-to-end technical architecture design, establish criteria, support implementation, ensure quality, performance, resilience, and security for critical enterprise platforms.
Responsibilities
Define end-to-end technical architecture
Make and document architectural decisions using ADRs
Translate functional and non-functional requirements into designs
Design scalable and resilient distributed solutions
Participate in development of critical components and conduct code reviews
The Technical Architect will serve as the technical point of reference, with the objective of transforming business goals into robust, evolvable, secure, and operable architectures. They will lead end-to-end technical architecture design, establish technical and non-functional criteria, support the team during implementation, and ensure that deliverables meet the quality, performance, resilience, and security levels required by a critical enterprise platform.
Responsibilities
Define the end-to-end technical architecture of the project, including components, integrations, data flows, dependencies, and boundaries of responsibility.
Make and document architectural decisions using ADRs, evaluating alternatives, trade-offs, evolution costs, risks, and operational consequences.
Translate functional and non-functional requirements into implementable designs, technical acceptance criteria, and an evolution roadmap.
Design scalable and resilient distributed solutions, considering consistency, concurrency, idempotency, fault tolerance, and disaster recovery.
Participate in the development of critical components and conduct code reviews focused on design, maintainability, security, and operational behavior.
The Technical Architect will serve as the technical point of reference, with the objective of transforming business goals into robust, evolvable, secure, and operable architectures.
Responsibilities
Define the end-to-end technical architecture of the project, including components, integrations, data flows, dependencies, and boundaries of responsibility.
Make and document architectural decisions using ADRs, evaluating alternatives, trade-offs, evolution costs, risks, and operational consequences.
Translate functional and non-functional requirements into implementable designs, technical acceptance criteria, and an evolution roadmap.
Design scalable and resilient distributed solutions, considering consistency, concurrency, idempotency, fault tolerance, and disaster recovery.
Participate in the development of critical components and conduct code reviews focused on design, maintainability, security, and operational behavior.
The Staff II Software Engineer is a senior individual contributor who provides technical leadership across a platform or domain and drives complex, cross-team engineering initiatives from problem framing through production outcomes.
Responsibilities
Set technical direction for a platform or domain, connecting business outcomes to architecture, platform evolution, and a practical multi-quarter roadmap.
Own and shape the technical backlog for the area: identify systemic risks and opportunities, prioritize foundational work, and make progress visible through measurable outcomes.
Lead ambiguous, high-impact initiatives spanning multiple teams; clarify the problem, surface dependencies and risks, align stakeholders, and guide delivery through production adoption.
Design and review architectures for distributed, event-driven, cloud-based systems, documenting key decisions, trade-offs, migration paths, and operational considerations.
Make sound build, buy, and partner recommendations; evaluate technologies, libraries, vendors, and AI-enabled capabilities against business value, total cost, security, privacy, and operational fit.
Requirements
Bachelor’s degree in Computer Science or a related field