Lead – Healthcare Product Implementation (Configuration)

Key Responsibilities :

a. GTM Strategy & Product Launches: Develop and execute comprehensive go-to-market plans for new products and features, ensuring alignment across Product, Sales, and Customer Success teams.

b. Messaging & Positioning: Create compelling, research-driven messaging that addresses the regulatory (CMS, HCC, RADV), financial, and operational pressures faced by U.S. healthcare organizations.

c. Sales Enablement: Build a world-class sales enablement engine, providing the Demand Gen and Sales teams with the playbooks, pitch decks, and competitive intelligence needed to win.

d. Content Strategy: Oversee the creation of high-value "hooks," including whitepapers, case studies, and webinars, to fuel outbound demand generation and event ROI.

e. Market & Competitive Intelligence: Conduct deep-dive research into market trends, competitor moves, and U.S. healthcare regulatory shifts to keep the company at the forefront of the industry.

f. Customer Marketing: work with customer success teams to build and drive customer stories, outcome/value frameworks and customer co-marketing programs.

g. Cross-Functional Leadership: Partner with leadership to align targeting and campaign execution, ensuring a consistent and authoritative brand voice across all channels.

Required Qualifications

● Experience: 8–12+ years of experience in product marketing, with a proven track record of leading GTM strategies for B2B SaaS or complex enterprise software.

● Industry Knowledge (mandatory): Deep expertise in the U.S. healthcare sector, particularly within risk adjustment, value-based care, or AI-driven healthcare tech.

● Education: Master’s degree in Business, Marketing, or a related field. ● Communication: Exceptional storytelling and communication skills, with the ability to translate complex AI technicalities into clear business value for C-suite executives.

● Leadership: Demonstrated success in leading high-performing teams and collaborating with executive leadership in a global model.

Preferred Qualifications

● Experience working with AI/ML-based products and a strong understanding of "Agentic AI" applications in healthcare.

● Experience supporting Account-Based Marketing (ABM) initiatives for high-value enterprise accounts.

Technical Skills

● Proficiency in CRM platforms (Salesforce/HubSpot) and Marketing Automation tools (Marketo, Pardot).

● Experience with Sales Intelligence and Research tools (LinkedIn Sales Navigator, Hubspot, SFDC, ZoomInfo).

● Strong command of data analytics to measure campaign impact and pipeline influence. Core Competencies

● Strategic GTM Planning and Execution

● Advanced Messaging and Storytelling

● Cross-functional Team Leadership and Mentorship

● Market Research and Competitive Positioning

Ideal Candidate

1

Strong Lead Business Analyst Profile with team leadership experience and BFSI background

2

Mandatory (Experience 1): Must have 6+ years of experience as a Business Analyst, including team lead or people-management experience with at least recent 2+ years in BFSI background

3

Mandatory (Experience 2): Must have proven ability to lead and mentor analysts and coordinate work across multiple stakeholders

4

Mandatory (Experience 3): Must have owned requirement gathering, analysis, and documentation end-to-end for key initiatives, ensuring quality and consistency of BA deliverables

5

Mandatory (Experience 4): Must have experience translating business needs into functional specifications, user stories, and process flows with senior stakeholders

6

Mandatory (Experience 5): Must have experience defining and driving BA best practices, standards, templates, and process improvements

7

Mandatory (Experience 6): Must have experience overseeing testing, validation, and stakeholder sign-off across workstreams

8

Mandatory (Skill 1): Must have strong requirement-gathering, documentation, and stakeholder-management skills.

9

Mandatory (Skill 2): Must have excellent communication, analytical, and leadership abilities, with a data-informed decision-making approach

10

Mandatory (Domain): Must have a background in the BFSI (Banking, Financial Services & Insurance) sector

11

Mandatory (Shift): Must be willing to support calls during EST hours (this is an EST-based project)

12

Preferred (Tools): Hands-on experience with Unqork or other low-code / no-code platforms

Job Description: Lead - Cloud Engineering (AWS / Azure)

Role Title: Lead - Cloud Engineering

Experience Level: 10+ Years

Domain Focus: Healthcare AI & Cloud Infrastructure

Location: Remote

Job Overview

We are seeking an experienced Lead - Cloud Engineering with over 10 years of IT experience to lead our cloud strategy, architecture, and infrastructure teams. In this role, you will oversee end-to-end cloud deployment, multi-cloud migration, and scalable architecture designed to support cutting-edge Generative AI applications in the healthcare technology domain.

The ideal candidate brings deep technical expertise in both AWS and Azure, strong hands-on capability in cloud infrastructure, and proven leadership experience driving security, compliance, and team growth.

Key Responsibilities

Cloud Architecture & Migration

• Lead the architecture, design, and execution of cloud migrations, deployments, and modernizations across AWS and Azure environments.
• Drive Infrastructure as Code (IaC) standards using Terraform, CloudFormation, or Bicep to ensure scalable, automated infrastructure provisioning.
• Build high-availability, low-latency architectures optimized for data-intensive Generative AI and Machine Learning workloads.

Security & Healthcare Compliance

• Enforce healthcare security standards including HIPAA, HITRUST, SOC 2, and data governance best practices across all cloud assets.
• Implement Zero-Trust security, Identity Access Management (IAM), data encryption key management, and continuous vulnerability monitoring.

Leadership & Team Management

• Manage, mentor, and scale a high-performing team of DevOps, Cloud, and SRE Engineers.
• Drive Agile workflows, sprint planning, incident response frameworks, and SLA compliance.
• Collaborate closely with Data Engineering, AI/ML, and Software Product teams to align infrastructure with business roadmaps.

Operations & FinOps

• Establish cloud cost optimization strategies (FinOps) to manage computing costs associated with AI models and large-scale data processing.
• Manage monitoring, alerting, and telemetry frameworks (e.g., Prometheus, Datadog, CloudWatch) to ensure 99.99% uptime.

Key Requirements

• Experience: 10+ years of overall IT experience with at least 5+ years in a cloud leadership or lead architect role.
• Cloud Platforms: Advanced hands-on expertise with both AWS (e.g., EC2, S3, EKS, Bedrock, SageMaker) and Azure (e.g., AKS, Azure OpenAI, Blob, Virtual Machines).
• DevOps & IaC: Strong background in Terraform, Docker, Kubernetes, CI/CD pipelines (GitHub Actions, GitLab CI, or Jenkins).
• Domain Knowledge: Prior experience building or managing cloud environments within Healthcare, Life Sciences, or HealthTech is strongly preferred.
• AI/ML Familiarity: Experience supporting cloud infrastructure for machine learning pipelines, LLM deployments, or GPU compute management.
• Certifications (Preferred): AWS Certified Solutions Architect – Professional, Azure Solutions Architect Expert, or Certified Kubernetes Administrator (CKA).

What you'll do

Own a client end to end. Learn their business, find what to automate or rebuild, and lead the work that ships it.

Turn business problems into technical solutions sit in the call, understand the real problem, design the fix, and decide how it gets built.

Stay hands-on. You'll still write code, build integrations, and work with APIs every day.

Build on whatever the client runs Zoho, Salesforce, Azure, similar platforms, and custom apps where needed.

Run delivery: scope it, sequence it, ship it, support it. The timeline is yours.

Review code and designs. Mentor the developers on your projects and unblock them fast.

Be the escalation point when something breaks or an integration misbehaves.

Own client communication on the technical side status, tradeoffs, bad news, early.

Keep the bar high: clear docs, clear updates, clear commit history.

What we're looking for

4–7 years shipping software, with real depth in REST APIs and system integrations.

Experience leading projects or small teams — the person others check with before they build.

Strong with business platforms (Zoho, Salesforce, or similar). Much of the leverage lives there, not in custom code.

You can sit with a non-technical client, understand the problem, and come back with a working solution.

Still enjoy building. This is technical leadership, not coordination.

Self-driven. You'll often be the senior-most engineer on the account.

Why you'll love this role

Full ownership from first call to delivery — you run projects, not a ticket queue.

Direct access to clients and leadership. Your decisions ship the same week.

Constant variety: new systems, new problems, new builds.

A step into technical leadership without giving up the hands-on work.

About the Role

We are looking for an experienced Business Analyst Lead to lead requirements gathering and business analysis activities for a Visitor Management System (VMS) project.

The VMS is a digital platform designed to register, track, and manage non-employee visitors entering business premises. The solution aims to replace manual/paper-based visitor processes with a secure, standardised, and automated visitor check-in and management workflow.

Key Responsibilities

* Lead end-to-end requirements gathering and business analysis activities.

* Engage with stakeholders to understand business needs, processes, and system requirements.

* Conduct stakeholder interviews, workshops, and requirement discussions.

* Analyse and document business, functional, and non-functional requirements.

* Translate business requirements into clear specifications for the software development team.

* Identify process gaps and recommend improvements aligned with the VMS objectives.

* Prepare BRDs, functional requirements, user stories, process flows, and other BA documentation as required.

* Work closely with UI/UX, development, testing, and project teams throughout the implementation lifecycle.

* Support requirement validation, UAT, issue resolution, and stakeholder sign-off.

* Ensure requirements remain aligned with project scope, timelines, and business objectives.

Required Skills & Experience

* 7+ years of experience working on software projects.

* Strong experience in business analysis and requirements management.

* Experience leading requirements gathering activities for software/digital solutions.

* Strong stakeholder management and communication skills.

* Ability to work effectively with technical and non-technical stakeholders.

* Experience working in Agile/software development environments is preferred.

* Fluent in Arabic and English.

* Strong analytical, documentation, presentation, and problem-solving skills.

Run delivery for 15–25 backend, frontend, and AI engineers building construction- tech and CAD drawing-automation software — with structural engineers on one side of you and the codebase on the other. Must have Hands-on familiarity with AutoCAD, Revit or experience at a product company in the CAD / AutoCAD / BIM / PLM / EDA /simulation space

Role overview-

We are hiring one Technical Product Manager to own delivery across our engineering teams in Bengaluru. You will run 15–25 engineers across backend, frontend, and AI workstreams, and you will be the person who turns requirements originating with our structural and detailing engineers into scoped, sequenced, shipped software.

This is a technical role. You will not be handed a groomed backlog and asked to move cards across it. You will sit in the design discussion and have a view on how and when — you will push back on an approach that will not scale, ask why a trade-off was made, and know the

difference between a two-day change and a two-sprint one. You are not expected to write production code. You are expected to read it, understand the system, and never be the least- informed person in a technical conversation you are chairing

What you’ll own- Delivery ownership

• Own the end-to-end delivery plan for every active workstream — scope, sequence,dependencies, capacity, and dates that actually hold.
• Break large, ambiguous product intent into engineering-sized increments with explicit acceptance criteria, agreed with the people who will build them.
• Run the operating cadence: planning, standups, refinement, demos, and retrospectives that change something the following week.
• Maintain one honest view of status — on track, at risk, slipped, and why — visible to the founders and to the team at the same time.
• Manage cross-team dependencies between backend, frontend, AI, and drawing-automation workstreams so no team idles waiting on another.
• Surface risk early, quantify it, and arrive with options — never an escalation without a proposal.
• Protect the team from thrash: absorb changing priorities, re-plan properly, and say no or not now when a plan cannot take more.
• Drive releases to genuinely done — QA, UAT with domain experts, documentation, and post- release verification included.
• Own and improve the delivery metrics that matter: cycle time, predictability of committed scope, defect escape rate, and rework.
• Run the release calendar across two products so neither becomes the permanent second priority.

The floor & the team.

Our requirements do not come from a product spec written in a vacuum. They come from structural and detailing engineers sitting on the floor with decades of practice behind them. Converting that into software is the defining skill of this job.

• Partner with structural and detailing engineers to turn drawing standards, project practice, and domain expectation into unambiguous, implementable requirements
• Run requirement sessions whose output is a written spec — sample data, expected output,edge cases, and explicit non-goals — not a shared verbal understanding.
• Arbitrate the constant gap between “how it has always been done on site” and “what can be deterministically automated.”
• Set up validation loops so domain experts review generated output early and repeatedly, rather than at the end of a sprint.
• Maintain a decision log for domain rules so the same question is not re-litigated three sprints later by different people.
• Manage internal stakeholder expectations and, where relevant, commitments made to customers.
• Spot when a “small clarification” is actually a scope change, and handle it as one.
• Make sure engineers get access to the domain expert directly — your job is to structure that contact, not to become a relay in the middle of it.

Challenges you’ll solve.

We prefer to be candid. These are the problems that make this role genuinely difficult — and genuinely interesting.

Domain knowledge that arrives as tribal knowledge

Our structural and detailing engineers know what a correct drawing looks like, but much of that knowledge is tacit. Your job is to extract it into deterministic, testable rules before an engineer starts building. Getting this wrong is the single most expensive failure mode we have

— it produces work that looks finished and is not.

Three disciplines, one release

Backend (AWS serverless), frontend (Angular / React), and AI engineers ship into the same

product. They have different failure modes, different testing regimes, and different natural cadences. Sequencing them so nobody idles and nothing integrates late is the core scheduling problem here.

Correctness is not negotiable

This is construction software. A wrong drawing, a wrong quantity, a wrong permission, or a wrong payroll figure has consequences outside the screen. “Ship it and iterate” has limits here, and you will need judgement about exactly where those limits sit for each workstream.

AI workstreams do not estimate like CRUD

Drawing generation and extraction work is research-shaped: some weeks produce a breakthrough, some produce a negative result. You will plan around that uncertainty honestly— with timeboxes, decision points, and fallbacks — instead of pretending an unknown is a two-

week ticket.

Live customers, finite engineers

Companies run their operations on this platform daily. Production incidents, customer escalations, and enterprise integrations (Asite, Autodesk Construction Cloud) compete with roadmap work for exactly the same people. You will make that trade-off explicitly, every week,

and be able to defend it.

Two products, one organisation

The operations platform and the drawing-automation platform have different customers, different rhythms, and partly shared people. Keeping both moving — without either becoming the perpetual second priority — is a standing constraint on every plan you make.

Founder-adjacent, fast-changing priorities

Direction can change on new customer information, and sometimes it should. You are the shock absorber: re-plan quickly, communicate the change clearly and once, and make sure the team experiences it as a decision rather than as chaos.

Qualifications.

• 6–7 years minimum in software delivery, including at least 4 years directly managing engineering teams as a project, delivery, or engineering program manager.
• Proven experience running teams of 10+ engineers across more than one discipline —backend, frontend, mobile, data, or AI.
• Fluency in modern delivery practice — Agile / Scrum or Kanban applied with judgement rather than ceremony — plus genuine facility with Jira or Linear, Git workflows, CI/CD, and release management.

Strongly preferred

• Experience at a product company in the CAD / AutoCAD / BIM / PLM / EDA /simulation space — Autodesk, Bentley, Dassault, Siemens, PTC, Trimble, Hexagon, Ansys or similar.
• Exposure to AEC, construction tech, manufacturing, or industrial software where domain correctness matters more than interface polish.
• Experience managing teams that included AI / ML engineers alongside conventional product engineers.
• Hands-on familiarity with AutoCAD, Revit, Civil 3D, Tekla, or DXF / drawing-export workflows.

The bar, the process, the offer.

The manager we’re looking for

Technical enough to be trusted

Engineers respect the questions you ask, not just the dates you set.

Owns outcomes, not activity

Measures the job by what shipped and worked, not by how busy the board looked.

Direct and specific

Says the uncomfortable thing early, in plain language, to the person who needs to hear it.

Reduces chaos

Leaves every process, plan, and handoff simpler than they found it.

Holds opinions loosely

Strong views on how to run delivery, updated when the evidence changes.

Raises the standard around them

The team becomes more predictable and more capable because you are in it.

What You’ll Do:

In the Platform (30–40% of your time)

• Review cloud and data architectures to identify gaps and risks.
• Lead technical triage on P1 incidents — be comfortable on bridge calls and know the right questions to ask.
• Stay hands-on with automation, scripting, and platform operations; you're not above writing the runbook yourself.
• Conduct FinOps reviews including cost anomaly analysis, licence audits, and resource right-sizing, bringing a technical and commercial lens.
• Stress-test transition readiness and define the gates before services move into BAU.

Running the Service (60% of your time)

• Own SLA performance and the RAID log across multiple client engagements.
• Lead sprint retrospectives and daily stand-ups with a strong understanding of Agile ways of working.
• Create executive service review packs that are crisp, data-driven, and actionable.
• Manage the Run / Change / Project boundary and protect BAU capacity from scope creep.
• Mentor and performance-manage a team of engineers, with a strong understanding of technical quality and delivery.
• Navigate commercial structures including fixed retainers, capacity tokens, and NTE caps.

With Clients

• Build trusted relationships with CXO and VP-level stakeholders through technical credibility.
• De-escalate challenging situations with empathy, clarity, and precision.
• Run effective Executive Business Reviews (EBRs) that build client confidence and demonstrate tangible value.

What We’re Looking For

You came up through the technical side — cloud engineering, data engineering, platform, or DevOps — and over time started solving problems beyond purely technical challenges. You now want a role that explicitly combines technical depth, service delivery, operations, and client leadership.

Specifically:

• 8+ years of experience working in cloud and data environments, with meaningful experience in managed services or operational delivery.
• Hands-on expertise in at least one major platform: Azure, AWS, GCP, Snowflake, or Databricks.
• Ability to read infrastructure and diagnose issues at the code/configuration level, not just through dashboards.
• Experience managing complex client relationships, including difficult or escalated conversations.
• Practical working knowledge of ITIL (Incident, Problem, Change) and Agile methodologies.
• Commercial exposure to SOW management, scope negotiation, and capacity planning.
• Strong operational judgment developed through handling critical incidents and making decisions with incomplete information.
• Strong communication, stakeholder management, and team leadership skills.

You don't need to have had "Service Delivery Manager" in your previous title. If your background is in senior data, cloud, platform, or DevOps engineering and you've also handled operations, governance, service delivery, and client-facing responsibilities, we'd like to hear from you.

What You’ll Get

• Opportunity to work across industries, clients, and technologies.
• Exposure to global businesses and complex technology environments.
• Access to technical IP, frameworks, playbooks, and accelerators.
• Exposure to a broad ecosystem of technologies.
• Mentorship and support from experienced senior consultants and technical leaders.
• Strong learning and development support, including certifications, training, hackathons, and mentoring.
• Transparent career progression and structured performance reviews.
• Opportunities to strengthen public speaking, consulting, and leadership skills.
• Comprehensive health insurance.
• Recognition, rewards, and long-term incentives.
• A collaborative environment with regular team and social activities.

Interview Process

The interview process consists of four stages:

1. Technical Online Screening – Baseline assessment of problem-solving and technical capabilities.
2. Introductory & Cultural Assessment – Discussion around experience, career goals, and alignment.
3. Technical Assessment – Detailed evaluation of technical competency by the technical panel.
4. Final Round – Final assessment covering technical depth, leadership, and overall fit.

About NonStop io Technologies

NonStop io Technologies is a value-driven company with a strong focus on process-oriented software engineering. We specialize in Product Development and have a decade's worth of experience in building web and mobile applications across various domains. NonStop io Technologies follows core principles that guide its operations and believes in staying invested in a product's vision for the long term. We are a small but proud group of individuals who believe in the 'givers gain' philosophy and strive to provide value in order to seek value. We are committed to and specialize in building cutting-edge technology products and serving as trusted technology partners for startups and enterprises. We pride ourselves on fostering innovation, learning, and community engagement. Join us to work on impactful projects in a collaborative and vibrant environment.

Brief Description

As a Business Systems Analyst working at NonStop io, you will analyse and define system requirements to support the software products in the clinical genetics domain area. We are seeking a skilled and motivated Business Analyst with expertise in the healthcare domain. The ideal candidate will have a strong technical background, excellent analytical skills, and the ability to bridge the gap between business requirements and technical solutions. You will play a pivotal role in driving impactful healthcare projects by analyzing, documenting, and improving processes.

Essential Functions

• Collaborate with stakeholders to gather and analyze business requirements in the healthcare domain
• Develop clear and detailed business requirement documents (BRDs), functional specifications, and workflows
• Conduct gap analysis and recommend solutions to enhance healthcare systems and processes
• Work closely with development teams to translate business needs into technical solutions
• Ensure compliance with healthcare regulations and standards (e.g., HIPAA, HL7)
• Create and execute test plans to validate system functionality and performance
• Assist in the implementation and adoption of new healthcare software and tools
• Provide training and support to users for new systems or processes
• Continuously monitor and evaluate project outcomes to identify opportunities for improvement

Key Skills and Qualifications:

• Bachelor’s degree in Computer Engineering or a related field
• 3+ years of experience as a Business Analyst in the healthcare domain
• Strong understanding of healthcare systems, processes, and regulatory requirements
• Proficient in tools like MS Office, JIRA, Confluence, or other project management software
• Familiarity with data analysis tools and healthcare standards like HL7, ICD, or FHIR
• Excellent communication and interpersonal skills to interact with stakeholders at all levels
• Strong problem-solving and analytical skills with attention to detail
• Ability to manage multiple tasks and work in a fast-paced environment
• Knowledge of Agile methodologies

Preferred Qualifications:

• Certification in Business Analysis (e.g., CBAP, CCBA or any other relevant certification)
• Experience with Electronic Health Records (EHR) or Hospital Management Systems (HMS)

What We Offer:

• Competitive salary and benefits
• A collaborative and innovative work environment
• Opportunities for professional growth and development

15+ years of IT Delivery and Technology Services experience.

15+ years managing large offshore delivery organizations.

Proven leadership of portfolios exceeding 200+ resources.

Financial Services or Banking experience is a MUST

Extensive technical experience in Data Engineering, Data Platforms, Data Brics.

Cloud Data Transformation Programs, Data Warehousing, Azure Data Platform and compliance experience

Lead Product Engineer - Pod Captain 

A Little Bit About the Role

There is a version of this role that attracts the wrong person: a senior engineer who wants a title upgrade and a slightly bigger scope. That person will struggle here. The Lead PE is not a promotion for being a great individual engineer. It is a fundamentally different job.

Your success at this level is measured entirely by what your Island delivers — not by the quality of your own code. You will still write code, often the hardest and most risk-laden on the project: auth systems, payment integrations, data migrations, the things nobody else should touch. But that is a fraction of the role. The majority is managing delivery, owning the client relationship on the technical side, unblocking engineers before problems compound, and making scope calls under pressure with incomplete information.

You are also the technical and commercial bridge between your Island and the client. You own every piece of technical communication that goes to them — what is being built, what risks exist, what the honest timeline is. When a client pushes for something technically unsound, you push back directly and professionally, always with an alternative. When something breaks in production, you own the post-mortem process and the client receives it within 24 hours. You protect your team from unfiltered client pressure; you translate it into clear, actionable direction instead.

On top of delivery and client management, you are the AI operating standard for your Island. Every engineer on your pod uses Cursor and Claude within the rules you define. You set those rules before the first line of code is written, govern how they evolve, and you are accountable when AI-generated code ships without being understood.

If you are energised by all of that — by the accountability, by owning outcomes rather than tasks, by the combination of technical depth and people management — this role will suit you well. If you want to spend most of your time in code, this is not the right level.

AI Governance Expectation

You set the AI standard for your entire Island. If an engineer on your pod is shipping AI-generated code they do not understand, or underusing AI tools entirely, both are your problem to fix — not theirs alone.

At Lead level, AI governance means:

• Authoring the .cursorrules file before the first PR is opened. This defines how every engineer on the team writes code, uses Cursor, and structures prompts. You update it as the team learns, and you submit it to the Fountane Mainland at the close of every engagement.
• Evaluating new AI tools before they reach client code. You are the gate. A tool that looks useful in a demo can create untraceable technical debt in production. You decide what enters the workflow.
• Governing prompt discipline across the team: scoped prompts, codebase context hygiene, no AI-generated code that the author cannot explain line by line.
• Using Claude for architecture reasoning, sprint planning, risk documentation, and client-facing technical communication — not just Cursor for code generation. AI works at every layer of the Lead role, not just the coding layer.
• Staying ahead of the Golden Stack. You should know what Cursor and Claude can and cannot do at the codebase level better than anyone on your Island. When the Mainland updates the standard toolchain, you integrate the change into your Island’s workflow first.

Key Responsibilities

Technical Architecture & Standards Ownership

Design the full-stack architecture for every engagement before the first sprint starts: service boundaries, API contracts, database schema, state management strategy across web and mobile surfaces, and the security baseline. Author the .cursorrules file that governs how the entire Island writes code and uses AI. Own the highest-risk code personally — auth systems, payment integrations, live data migrations — these are not delegated regardless of workload. Enforce Mainland security standards across the entire codebase: input validation, correct auth scoping, safe data handling. If a security issue reaches production that was visible in a PR, that is a failure you own.

CE Prototype Gatekeeping

Review every Concept Engineer prototype before any engineer touches it. This is not a courtesy review — you have veto authority. If the scope is technically unrealistic for the sprint, the architecture is unbuildable as specified, or the prototype makes promises the codebase cannot keep, the sprint does not start until those are resolved. The time to surface a structural problem is before it is built, not after it is demoed. Produce a written checklist verdict for every prototype review — approved, approved with conditions, or blocked with reasons.

Client Technical Communication & Scope Ownership

Own all technical communication with the client directly. This means: what is being built each sprint, what risks exist and what is being done about them, honest timelines when estimates change, and clear explanations of technical decisions in plain language. Push back on risky or scope-expanding requests professionally and always with an alternative — “we cannot do X because Y; here is what achieves the same outcome.” Manage scope creep actively: every request that expands the engagement goes through you, gets assessed for impact, and is either absorbed, priced, or declined with a rationale. Renewal conversations are yours to lead in coordination with the CE.

Island Integration Audit

When a prospective client wants fractional augmentation — one or two roles rather than a full Island — you conduct the Island Integration Audit. This means evaluating their existing engineering team against Fountane Mainland SOPs: coding standards, AI tool usage, deployment practices, and documentation quality. If they pass, fractional deployment proceeds. If they do not, you produce a written audit report that either recommends full Island deployment or a Mainland upskilling programme. You are protecting your team’s velocity — a fractional deployment into a dysfunctional team destroys it.

Delivery & Velocity Management

Review the work cycle board every morning. Flag anything stuck, stale, or at risk before it becomes a client problem — not after. Communicate risks to the CE proactively with options, not just problems. Track every engineer’s billing hours: a shortfall spotted on Wednesday is a Thursday conversation, not a Friday surprise. If an engineer is consistently under-billing, that is either a workload problem, a capability problem, or a motivation problem — each has a different resolution and you are responsible for diagnosing which one it is.

Production Incident Ownership

When something breaks in production, you own the resolution process end to end: take technical lead, make the call on rollback vs. hotfix, communicate status to the client directly if the incident affects them, and own the post-mortem. The client receives the post-mortem within 24 hours of resolution — this is a hard commitment, not a target. The post-mortem covers: what happened, why it happened, what was done to fix it, and what structural change prevents recurrence. You produce it; it is not delegated to the engineer who caused the issue.

Automation & Infrastructure Boundary Arbitration

The Automation Engineer owns the test gates within the CI/CD pipeline. The Infrastructure Engineer owns the pipeline configuration itself. When these overlap and conflict — which they will — you arbitrate. The resolution must be documented in the Island’s .cursorrules and SOP onboarding document so the boundary does not need to be relitigated every sprint. This is not optional housekeeping; an unresolved boundary between these two roles is one of the most common sources of deployment failures on Islands.

Full Stack Ownership — Web & Mobile

You review and own work across the entire application layer: React / Next.js web frontends, React Native or Flutter mobile apps, Node.js / Python backends, and database schema. You cannot delegate a review of mobile code because you do not know mobile, or backend code because your background is frontend. If there is a gap in your full-stack depth, that is something to resolve before taking this role, not on the job.

People Management & Mentoring

Hold bi-weekly 1:1s with every engineer on the Island — focused on growth, blockers, and career direction, not status updates. Status belongs on the board; 1:1s are for the person. Address performance gaps early, directly, and specifically: a pattern spotted in week two is a conversation in week two, not month three. Protect the team from unfiltered client anxiety — absorb it, process it, and give the team clear direction instead of noise. If an engineer is struggling, that is your problem to solve before it becomes the client’s problem to notice.

Network Contribution

At the close of every engagement, submit to the Fountane Mainland: the .cursorrules file, all prompt templates used, a short retrospective on what worked and what did not, and any reusable patterns or scripts developed during the engagement. This is a Lead-level obligation, not a nice-to-have. The network’s collective capability grows through what Leads bring back from the field. An engagement that ends without a Mainland submission has left the network no smarter than it was before.

Qualifications

• 8+ years of software engineering experience, with at least two years in a role where you were accountable for delivery outcomes — not just your own code. You should be able to describe an engagement where something went wrong on your watch, what you did about it, and what you would do differently. If your experience is entirely individual-contributor, this role will be a difficult fit.
• Genuinely full stack across web and mobile: React / Next.js, React Native or Flutter, Node.js or Python, and database architecture including schema design and migrations. You review and own work across all of these surfaces — not just the ones you are most comfortable in.
• Hands-on, daily Cursor and Claude usage with the ability to set and enforce standards for how a team uses them — not just personal proficiency. You should be able to describe the .cursorrules file you would write for a standard SMB engagement and explain the decisions behind it.
• Proven ability to communicate technical risk and decisions directly to non-technical clients — not through a PM, directly, in plain language. You should be able to describe a client pushback you navigated and how you handled it.
• Experience managing scope on a real engagement: a client who wanted more than was in the contract, and how you resolved it without damaging the relationship or the team’s velocity.
• Has conducted security-aware architecture design: auth systems, input validation, safe data handling. You should be able to describe a security decision you made and why.
• Has led or coordinated a small engineering team — run 1:1s, addressed performance gaps, made scope calls under pressure. Management experience at a staffing agency or outsourcing firm counts if the accountability was real.
• Comfortable having direct, specific performance conversations early — not after the situation has compounded. You should be able to describe a time you addressed a performance issue at the first sign rather than waiting.
• Bachelor’s or Master’s in Computer Science or a related field, or equivalent experience.

About Fountane

Fountane is a technology ventures lab - one part product studio, one part startup engine. We build high-quality software and AI products for clients ranging from fast-moving startups to large enterprises, and we co-build and invest in new companies when we see the right opportunity.

Founded in 2017 and headquartered in Minneapolis, we have grown to 60+ people across four continents and were recognised as one of America’s fastest-growing companies, ranking No. 699 on the Inc. 5000 with 595% three-year growth.

We are serious about craft, direct about expectations, and operate at the frontier of AI-assisted engineering. Lead PEs here carry real authority and real accountability — over delivery, over people, and over client outcomes. If that combination is what you are looking for, this is the place.