Solution Architect

Who We Are

PALO IT is a global innovation consultancy and Agile software development company dedicated to helping organizations embrace tech as a force for good. We work with clients to rapidly launch products and services, create new business models, and prepare leadership and culture for the

future. We are a community of innovators, designers and technologists across 11 offices and five continents (France, Hong Kong, Singapore, Thailand, Australia, Mexico and Colombia).

We're committed to helping businesses transform to better our world. We're proud to be a World Economic Forum (WEF) New Champion, and a B Corp-certified company in Singapore and Hong Kong, currently working towards certification across all other locations.

Our Impact in PALO IT

Using our B Corp certification and WEF status as our north star, we’re eager to adapt to change, learn from our experiences and move to meet our planet’s urgent needs. With 2025 as our horizon, we are taking action to meet the following objectives:

• Become a climate net-zero company
• Attain 50% of revenue from projects with a positive impact
• Train 100% of our workforce on impact
• Achieve B Corp certification among all 11 of our offices across the globe
• Attain 90% happy employees at PALO IT

Our clients are amongst the world's most successful companies. We innovate with both established Fortune 1000s, SMEs and start-ups who aim to make an impact, become global leaders and address the world's most complex challenges.

What does your job look like?

The role of the Solutions Architect will be responsible for designing and implementing solutions in the projects based on the reference architectures and the best practices of their platform (Java).

Support the team in the analysis of the solution to identify quality attributes (non-functional requirements) and identify the business context.

Support the DevOps engineer in the configuration and definition of components (pipelines and repositories).

Main Responsabilities

• This profile, even if they don't program day by day, must have solid fundamentals of microservices, distributed systems, and software engineering.
  The Solutions Architect is responsible for identifying the new functionalities of the client's systems and being able to determine which system/component is responsible for implementing said functionality, in addition to having the following responsibilities.
  • Client & Governance team
    • Provide visibility into integrations and relationships between different systems
    • Support in choosing the best technology to solve a specific concern, for example, using mongodb instead of postgreSQL based on a use case.
    • Document Solution Architectures
    • Support in the PI Planning to give visibility to the teams in relation to the functionality to be implemented by Squad
    • Support in the design of the platform infrastructure considering the components of AZURE
  • Squad development
    • Provide visibility into the responsibility of the software components that each Squad builds and their integration and relationship with other systems.
    • Validate with the development team the design of your components to ensure interoperability between systems
    • Support the development Squad in the design of components by giving recommendations and good practices based on Cloud Native, for example, if it is AZURE with the WAF (Well Architecture Framework)
  • Commercial
    • Support in the development of technological solution proposals
    • Support in determining the time and scope of commercial proposals
  • Architecture
    • Documentation and modeling of some architecture views
    • Quick understanding of the business to be able to communicate to product owners and software architects, reaching a low level for engineering teams
      The skills that should be considered that this profile must meet are the following.

What you need to succeed on this rol

• Documentation and modeling of architectures using 4+1 or viewpoints & perspectives
• Knowledge in project management with PMP framework
• Knowledge in agility (not just scrum)
• UML modeling language, such as sequence diagrams and classes
• BMPN Modeling Language (optional)
• Archimate modeling language (optional)

Architectural Styles and Design Patterns

Architectural style microservices, you need to understand some of these design patterns

CQRS

• SAGA
• API design using OpenAPI Swagger
• Knowledge of using an API Manager
• Exposure of microservices through any of the following mechanisms
  • Rest

GRPC: GraphQL

Cloud / AZURE

• Managed Services
  • RDS (Aurora)

SQS, SNS

• Kinesis (Nice to Have)
• Elastic Cache (Redis)
• Security

KMS

• Secrets Manager
• Cluster (Must):
  • EKS[K8s]
  • Docker
• GitOps (ArgoCD): Nice to Have
• Service Mesh (Linkerd): Nice to Have
• Infrastructure as a Code (Nice to have): Terraform
• Linux: Must
• GCP - Nice To Have

Observability: Monitoring and Observability Concepts, you should not have a deep knowledge, but you should know what it consists of, because they are components that are used in all solutions.

• Datadog

ELK : Dynatrace - Grafana

DevOps (Automation), you don't have to have a deep knowledge, but you do know what it consists of, because they are components that are used in all solutions, CI/CD concepts CI Engine (must, knowledge in 1 of these tools)

• Github actions
• GitLab CI/CD
• Bitbucket pipelines
• Jenkins

CD Engine (1 of these tools, nice to have)

• ArgoCD
• Spinaker
• Jenkins X

Git (must) : Branch Strategy

MR/PR

• Security (Nice to Have): Veracode or some other
• Quality Code (Nice to have): Sonar

Programming languages (even if you don't code, you need to be clear about the concepts)

Java 11+ (must)

En Palo IT, we are a team of Values

• local partner
• Nice
• Enthusiastic
• Outgoing
• Leader

What We Offer

• Stimulating working environments
• Unique career path
• International mobility
• Internal R&D projects
• Knowledge sharing
• Personalized training
• Entrepreneurship & intrapreneurship

For more on our team culture and benefits, check out our careers page.