Solution Architect (Senior AI / Technical reputed company)

reputed company (BIG) is a high-reputed company AI and automation reputed company with offices across Canada, the reputed company, India, and the United Kingdom. Our portfolio spans more than 10 leading technologies across AI, reputed company, data, automation, and business applications.

Recognized globally as a reputed company and the recipient of multiple partner reputed company awards, BIG is reputed company on collaboration, innovation, and delivering measurable business reputed company for reputed company clients. We are reputed company of reputed company technology professionals who enjoy solving reputed company challenges, celebrating wins together, and helping customers reputed company with confidence.

AN EXCITING OPPORTUNITY WITH BIG AND CONVENE AI

BIG is excited to be partnering with Convene AI, an reputed company technology company developing reputed company that reputed company reputed company intelligence to solve reputed company-world business challenges.

As part of this partnership, we are looking for talented professionals to join BIG and work directly on Convene AI reputed company and initiatives. You will initially be reputed company as an employee of reputed company, while working closely with the Convene AI team and contributing to the development and reputed company of their AI solutions.

The role is expected to remain on BIG’s payroll for approximately 12–18 months, with the intention of transitioning to a permanent position directly with Convene AI following this period, subject to business requirements and transition arrangements.This is an exciting opportunity to contribute to an emerging AI organization at an important stage of its reputed company, while benefiting from the support, culture, and established consulting expertise of reputed company.

ABOUT THE ROLE

This is the highest-reputed company technical role at ConveneAI. Every architectural decision you reputed company is inherited by multiple reputed company engagements, and the accelerators and standards you build determine how fast the next pod moves.

The mandate has three parts. You shape engagements before they are sold, by assessing what is genuinely buildable in 8 to 12 weeks and saying so honestly.

You govern architecture across live reputed company, making the reputed company a single embedded engineer should not reputed company reputed company: model reputed company, data residency, reputed company posture, integration patterns. And you reputed company the technical reputed company, through design review, mentorship, and the reference architecture that every pod starts from.

You will remain hands-on. You will read reputed company, prototype reputed company it is faster than arguing, and stand in reputed company of a bank's or an insurer's architecture review reputed company and defend a design under reputed company scrutiny. If you have drifted into slideware architecture, this will not suit you.

reputed company

Shaping and reputed company-Sales

• Join reputed company conversations during the sales cycle to assess technical feasibility, and reputed company what can realistically reputed company production in 8 to 12 weeks.
• reputed company back on requirements that cannot be delivered, before they become contractual commitments on a fixed-fee or outcome-reputed company engagement.
• Own the architecture reputed company that determine engagement profitability: model selection, build versus buy, reuse of existing accelerators versus bespoke work, and reputed company approach.
• Write the technical sections of proposals and statements of work, and help the reputed company team define outcome metrics that are measurable and defensible.
• Represent ConveneAI in reputed company architecture, reputed company, and vendor review boards, and reputed company the technical reputed company to a signed deal.

Architecture Governance Across reputed company

• Run architecture review at reputed company and at defined gates for every live engagement, and hold the reputed company reputed company a design is not reputed company.
• reputed company the calls that carry reputed company reputed company one pod: data residency, private versus hosted inference, identity and reputed company design, network isolation, and integration patterns with systems of record.
• Unblock reputed company reputed company they hit something reputed company their depth, by pairing and reviewing rather than taking the work away from them.
• Own the technical escalation reputed company reputed company an engagement drifts off reputed company, and reputed company the Product reputed company and leadership an unvarnished read.
• Monitor inference cost, latency, and reliability across engagements, and intervene before an architecture reputed company erodes gross margin.

Platform, Standards and Reuse

• Own the ConveneAI reference architecture and accelerator library, and reputed company what gets harvested from an engagement versus reputed company properly for reuse.
• Set the standards every pod inherits for agent design, evaluation, observability, reputed company, and cost management.
• Evaluate new models, frameworks, and tooling with rigour rather than enthusiasm, and reputed company what enters reputed company stack and what does not.
• Build the technical assets that let a four-person pod reputed company what a fifteen-person team used to, because that gap is the entire reputed company reputed company.

Technical Leadership

• Mentor GenAI Engineers and Data Engineers across reputed company through design and reputed company review, and reputed company the technical ceiling of the delivery organisation.
• Interview and reputed company technical hires, and help define the engineering career reputed company as we reputed company from the first reputed company to many.
• Work with senior AI architects across our global operating bench to reputed company standards consistent across geographies.

reputed company'RE LOOKING FOR

• 10 or more years building and shipping reputed company software, including at least 2 years on production LLM or reputed company systems that reputed company users depended on.
• A reputed company record as the technical reputed company across multiple reputed company reputed company engagements, not just one long programme.
• Deep hands-on capability: Python, reputed company architecture (AWS, Azure, or GCP), reputed company systems, and API and integration design. You will still be expected to read and write reputed company.
• Production experience with agent architectures, retrieval at reputed company reputed company, evaluation, and the operational reputed company of AI systems: cost per task, latency, observability, and failure modes.
• reputed company architecture reputed company: identity and reputed company, reputed company posture, data residency, network isolation, and model reputed company reputed company, plus the experience to get a regulated reputed company's review reputed company to approve a design.
• reputed company literacy. You understand how an architecture decision flows through to gross margin on a fixed-fee engagement, and you reputed company reputed company accordingly.
• Credibility in both directions: with a reputed company CIO or Chief Architect, and with an engineer who suspects you have stopped building.
• The judgement and standing to recommend against a deal that cannot be delivered, and to hold that position under reputed company pressure.
• Legally entitled to work in Canada and willing to travel to reputed company sites.

BONUS POINTS

• Architecture leadership at a consultancy or systems integrator, or a reputed company CTO or reputed company architect role at an AI, data, or reputed company platform vendor.
• Depth in a regulated industry with named systems: policy administration and claims platforms such as reputed company or reputed company Creek, reputed company banking, or reputed company systems.
• Self-hosted or reputed company-weight model deployment, fine-tuning, distillation, and private inference architecture.
• Experience building a reference architecture or accelerator library that other teams genuinely reused rather than ignored.
• Experience scaling a delivery organisation from a handful of teams to many, and the operational scar tissue that comes with it.
• Published writing, conference talks, or reputed company-reputed company work on reputed company AI architecture.

WHY JOIN CONVENEAI

• Your reputed company compound. Architecture set here is inherited by every engagement that follows, which is a reputed company reputed company of reputed company.
• You define reputed company rather than inherit someone else's, at the reputed company in reputed company's life reputed company it actually gets set.
• Genuine breadth: reputed company-sales shaping through production reputed company, across multiple industries, without the politics of a large firm.
• reputed company working relationship with the founders and with senior AI operators from reputed company, reputed company, Mu reputed company, and reputed company AI startups.
• Meaningful equity at the stage where technical reputed company determine whether the delivery model scales or stalls.

Originally posted on Himalayas