Solution Architect

Solution Architect (Java)

Hybrid in Maryland, Heights MO

High-visibility initiative: Ordering Convergence, expanding into mobile services.

Strategic shift to a larger offshore delivery model.

Modernization of the Agent OS Ordering Platform (upgrade to Golden Eagle) to address tech debt and security vulnerabilities.

Must Haves:

• Senior developer level or greater experience in object-oriented programming (Java)
• Experience architecting large solutions that affect multiple systems.
• Designing RESTful web services
• Firm understanding and show practical application of REST design principles.
• Proficient in designing large and complex web APIs and documenting them via Swagger / OpenAPI specs.
• Experience with BPMN/workflow diagrams.
• Experience documenting basic infrastructure designs (servers, firewalls, load balancers, etc.)
• Good communication skills

Nice to Haves:

• Experience with Camunda and/or Pega
• Experience creating APIs that process aspects of Orders.
• Experience in the Communications / Telco industry.

Team Dynamics:

• 5 Architects on the team.
• Interfacing with business stakeholders across all domains
• Business Requirement Document given from business lines to implement policies / new features through JAD sessions. Determine if the request is supportable.
• Once intake is done, OBO Solution Architect will establish high level design (existing Service versus new Service needed)
• Once design is Approved, SA would ensure smooth hand-off to Engineering team.

Notes:

• Given Business Requirements Document (BRD), SA should document E2E design specifications. This org is 100% responsible for only RESTful Services. Many are highly complex Services.
• Need to be able to support and maintain documentation that goes with all features. Document in Chalk and cleanly represent data flow diagrams, data maps, system flows, etc. Chalk skills are preferred.
• They want this person to be able to engage in research, understand downstream applications, make suggestions / alternatives as they really think about the Problem Statement. They don’t want to see code in design but rather clear, detailed design.
• SA will shadow other SAs and learn the org from a high level. The org does a lot of component sharing. Needs to know when another team’s code base / design can be used in Ordering rather than always recreate. Reading through Chalk and working with existing SAs.
• Fail Open Architecture is used since continuous operation is critical.
• Sample Domain Names: Online bi-flow. Any online submission, Credit Eligibility, Orders, Self-Install, Restarts, etc.
• Focus on establishing resiliency through interactions with Ops, Engineering, and other technology stakeholders. i.e. SA may work with Ops to determine which Splunk alerts are appropriate.
• 5-6 Ordering channels. 20-25 consumers of OBO’s Services across Charter’s technology org.
• Expanding OBO into ordering into not just Cable but Mobile phone provider services. Ordering Convergence is the big priority for 2025.
• SA will join meetings with business stakeholders, contribute to JAD Session, and be the solution-minded expert to support business requirements.
• Org has 2 Rule Engines. Camunda (on Charter’s and Pega (cloud based) Customer Decision (CD) Edge.
• Org designs and supports Services for Credit rules and Fraud rules.
• Currently shifting more to Cloud / configured infrastructure to ensure quicker time to market.
• Likely career progression of a qualified candidate could be Software Engineering (possibly Technical BA) that has spent time in a custom development environment and shifted focus to high level design specifications.
• SAs with Ordering and/or Communications (Cable/Fiber Services) is a Plus.
• Politely but assertively negotiate designs for desired features. Regular meetings include VPs, Directors (business and technical side), and Product Owners across the org. Excellent communication and presentation skills are a must.
• Key Tools: Jira / Chalk

Concrete Deliverables:

1. Determination of which products impacted.
2. Ensure E2E design which will be consumable across the enterprise as a Service
3. Handoff / discussion to socialize the design with the responsible teams.
4. As outputs:

• Reasonable confidence that downstream capabilities exist and will support the design (RESTful Services); or call outs for those that don't and reasonable confidence that they could be built
• Proposed design (RESTful Services) can be built in a supportable, maintainable, scalable
• Work with Technical teams – different architects, etc. to gain understanding of technical feasibility.
• Think in the abstract at the beginning, comfortable giving an estimate based on how the app will be impacted + level of effort needed.

• As engagement: Research current downstream capabilities, makes suggestions/offers alternatives that may meet the spirit of the "requirements" (the problem statement) that do align to downstream capabilities.

• Engages in the design process, offers potential solutions/influences the design to assure supportable/maintainable/scalable software.

• Shared Responsibilities:

• Minimize unicorn solutions, encourage re-use, require justification for inventing new patterns, strategies, duplicating functionality and/or concepts/patterns.
• Considers the problem presented and collaborates to propose the best solution balancing technical soundness and usability.
• Aware of best practices of designing RESTful APIs

Required Skills: Java Dev Skills

Basic Qualification :

Additional Skills :

Background Check : Yes

Drug Screen : Yes

Notes :Selling points for candidate :Project Verification Info: The information provided below is for Apex Systems AV use only and is not to be distributed publicly, or to any third party. Any distribution of the below information will result in corrective action from Apex Systems Vendor Management.