Solution Architect

Solution Architect

Full-time, permanent | Remote-first — United States, Canada, Argentina, or India | Reports to the Chief Technology Officer

🎯 Role Overview

A Solution Architect at EVOCS turns ambiguous business problems into concrete, buildable designs — fast. You sit with a stakeholder or a struggling project team, understand how the business actually operates, ask the questions that surface every edge case (what happens when this branch fires? what does the state machine look like?), and produce a solution the delivery team can build from immediately: the workflow, the components, the integration points, and why each technology was chosen.

This is a hands-on architecture role, not a talk-only one. You validate your own designs by prototyping the critical path yourself, and every solution you design, you could build. Your designs must work for non-technical users — the right answer is the simple one, and sometimes it is a process change rather than a technical build.

We are an AI-native firm: we build our own tooling, automate our own operations, and hold our client work to the same standard.

🧩 What You Will Do

Roughly half of your time is client-facing pre-sales and escalation work; the other half is designing solutions for delivery teams and EVOCS's internal operations.

• Pre-sales solutioning. Produce solution designs, architecture diagrams, and technical approach narratives for RFP responses and client proposals — strong enough that senior leadership only needs to review, not rewrite.
• Escalation design. Parachute into escalated projects, identify what is actually wrong, and hand the team a concrete solution design within hours — components, integration route, sequence — so they know exactly what to build over the following weeks.
• Decomposition. Take high-level business problems and break them into requirements, workflows, states, branches, and edge cases, accounting for the exceptions in advance rather than discovering them in UAT.
• Technology selection. Choose the right platform, data store, and integration pattern for each problem — and defend the choice in front of both engineers and executives.
• Design validation. Prototype the risky or novel part of a design yourself to prove it works before delivery commits to it.
• Internal architecture. Design the workflows, automations, and integrations that run EVOCS's own back office, working alongside our Forward Deployed Engineers who build them out.

🧠 What You Will Bring

• A track record of solutioning across enterprise systems: workflows, integrations, APIs, and data flows across HR, finance, ITSM, or similar platforms.
• Elite decomposition and requirements skills — the instincts of a high-caliber technical business analyst, applied at architecture level.
• Data literacy: data modeling and transformation, and grounded opinions on relational vs. document vs. event-log storage for a given problem.
• Cloud fluency (Azure and/or AWS) and integration depth: API gateways, middleware, event routing, and authentication patterns.
• Enough engineering ability to prototype: you can personally build a proof of concept for anything you design.
• AI-native working style: you use modern AI tooling to compress design, documentation, and data work from weeks into hours.
• Communication range: you can whiteboard with a CFO in the morning and spec an API contract with an engineer in the afternoon.
• 8+ years across solution architecture, integration architecture, or senior engineering roles.

🚫 What This Role Is Not

• Not a talk-only architect. If you cannot build a working proof of what you design, this is not the right role.
• Not a project manager or delivery owner. Delivery managers own client relationships, escalation politics, resourcing, and margin.
• Not a slide-deck factory. Your artifacts exist so something gets built, not so a meeting gets held.

🛠️ Show Us What You Build

Architecture is easy to claim and hard to verify, so we weight evidence over titles. Portfolios beat certifications here.

• A system you designed end to end: what the problem was, what you chose, and what you would change now.
• A prototype or proof of concept you built yourself to de-risk a design before a team committed to it.
• An integration or data model you are proud of — or one that went wrong and taught you something.
• A GitHub profile, an architecture writeup, a talk, or a design doc you are free to share.

Send links or short descriptions. One design you can walk through in depth beats a list of platforms you have touched.

⭐ What Will Make You Stand Out

• Professional services or consulting experience, where architecture is scoped, billable, and defended in front of a client.
• Depth in one or more enterprise platforms: ITSM, HR, or finance and ERP systems.
• A pre-sales and RFP record you can describe: what you wrote, what you won, and why.
• Event-driven architecture, message brokers, and idempotency patterns at real scale.
• Architect-level Azure or AWS certification — useful, though never a substitute for what you have built.
• Experience designing for distributed delivery teams across multiple time zones.
• Working Spanish, given our Argentina delivery hub.

🤝 How We Will Work Together

You report to the Chief Technology Officer. Your designs go to senior leadership for review, not rewriting, and to delivery teams as something they can start building from on day one.

Delivery managers own the client relationship, escalation politics, resourcing, and margin. You own the design and its technical defensibility. That line is deliberate, and it holds.

You will work alongside our Forward Deployed Engineers, who build out much of what you design — for clients and for EVOCS's own back office.

Expect to move between pre-sales, a live escalation, and internal architecture in the same week. If you want to sit inside one platform doing one thing, this is the wrong role.

#LI-Remote