Stevens is a strategic advisory and technology firm that partners with companies on high-impact transformation and technology initiatives. We work directly with executive and technology leaders to solve complex problems, identify opportunities, and turn strategy into working solutions. We are looking for a highly experienced Enterprise AI Solutions Architect to support enterprise customer engagements on an hourly contract basis. Please read before applying This is a senior enterprise architecture role with a high bar for relevant experience. We are specifically looking for candidates who have worked within major U.S. enterprises, leading technology companies, established consulting firms, systems integrators, or comparable large-scale organizations. Experience consisting primarily of freelance projects, small startups, personal projects, or AI prototypes will not meet the requirements for this role. Candidates must: * Be a U.S. citizen and current U.S. resident. * Have substantial professional experience designing and delivering technology within large enterprise environments. * Have experience working directly with enterprise customers, stakeholders, or technology organizations. * Be able to participate in customer meetings during standard U.S. business hours. * Complete a technical architecture interview as part of our screening process. * Be prepared for Stevens to verify relevant employment history and professional experience before engagement. Please only apply if you meet these requirements. The Role Our engagements often sit at the intersection of business strategy, enterprise architecture, and emerging technology. We help customers identify where AI can create meaningful business value, determine what should actually be built, and provide the technical leadership needed to move from concept to production. This is not a salaried or full-time employment position. Architects work with Stevens on an hourly contract basis as project needs arise. Engagement scope and weekly hours may vary based on active customer projects. This is a senior, highly customer-facing role. You will work directly with customer technology leaders, engineering teams, and Stevens delivery teams to understand complex business problems, shape AI use cases, design solutions, guide proofs of concept, and establish the architecture required to take successful solutions into production. We are specifically looking for someone who understands enterprise application development and architecture, not simply AI models or cloud infrastructure. The model is one component of the system. You should be comfortable reasoning across applications, APIs, data, integrations, identity, security, cloud infrastructure, AI services, and production operations to design complete enterprise solutions. Your work may include * Leading technical discovery and architecture sessions with enterprise customers. * Translating business problems and AI opportunities into practical solution architectures and implementation plans. * Designing enterprise AI applications using LLMs, RAG, agents, tool use, structured and unstructured data, APIs, and modern cloud services. * Integrating AI capabilities into existing enterprise applications, data platforms, SaaS products, and business workflows. * Architecting solutions primarily within AWS, including Amazon Bedrock and SageMaker. * Evaluating models, platforms, frameworks, and architectural approaches against specific business and technical requirements. * Helping customers make build-vs-buy decisions across a rapidly evolving AI technology landscape. * Designing rapid proofs of concept while ensuring successful POCs have a realistic path to production. * Defining architecture across application services, APIs, data, model infrastructure, integrations, identity, observability, and cloud infrastructure. * Accounting for enterprise requirements including security, privacy, governance, scalability, reliability, performance, and cost. * Establishing appropriate approaches to AI evaluation, guardrails, monitoring, and production operations. * Working closely with engineers throughout implementation to ensure architectural decisions translate into high-quality working software. * Reviewing technical approaches, identifying risks, and helping engineering teams navigate architectural tradeoffs. * Presenting architecture recommendations and technical decisions to engineering teams, technology leaders, and senior customer stakeholders. This is not a role where you create an architecture diagram and hand it to someone else. We want architects who stay close to implementation, understand the consequences of their decisions, and can help a team navigate the difficult decisions that emerge as a solution gets built. You will have significant autonomy and ownership. A successful architect at Stevens can walk into an ambiguous problem, quickly understand the customer’s business and technology environment, identify the decisions that actually matter, develop a point of view, and confidently guide both the customer and delivery team toward a solution. Requirements * U.S. citizenship and current U.S. residency are required. * 7+ years of relevant professional experience across software architecture, solutions architecture, application development, engineering, or technical consulting. * Meaningful experience working within or delivering solutions for major U.S. enterprises, leading technology companies, established consulting firms, systems integrators, or comparable large-scale organizations. * Significant experience designing and delivering enterprise applications, platforms, or distributed systems. * Hands-on experience architecting and implementing generative AI applications beyond basic prototypes or isolated model integrations. * Experience taking applications or major technical initiatives from discovery and proof of concept through production. * Strong understanding of modern AI application patterns including RAG, agents, tool use, embeddings, vector search, model orchestration, evaluation, and guardrails. * Strong AWS architecture experience, including practical experience with Amazon Bedrock and SageMaker. * Experience working with commercial AI platforms and models including OpenAI and Anthropic Claude, along with familiarity with open-source models. * Strong understanding of modern application architecture, backend services, APIs, databases, data architecture, distributed systems, and enterprise integration patterns. * Experience integrating new applications and capabilities with existing enterprise systems and data sources. * Familiarity with cloud engineering, DevOps, MLOps, CI/CD, infrastructure as code, and production observability. * Strong understanding of security, identity, privacy, governance, reliability, scalability, and cost considerations in production enterprise systems. * Ability to make pragmatic architectural decisions within complex existing technology environments where replacing everything and starting over is not an option. * Ability to move comfortably between conversations about business requirements and detailed technical architecture. * Experience leading technical discovery, architecture workshops, and customer-facing solution design. * Strong written and verbal communication skills. * Confidence presenting recommendations, defending architectural decisions, and challenging assumptions with senior technology and business stakeholders. * Availability during standard U.S. business hours for customer workshops, architecture sessions, and meetings as needed. Experience at organizations such as major technology companies, cloud providers, Fortune 500 enterprises, nationally recognized consulting firms, or large systems integrators is strongly valued. The company name itself is not the qualification; we care about whether you have actually operated in sophisticated enterprise technology environments and solved problems at meaningful scale. An active U.S. government security clearance is not required but is strongly valued. Additional compensation may be available for individuals who hold and maintain an active U.S. government security clearance. Our Screening Process We maintain a high technical and professional bar because architects in this role represent Stevens directly with enterprise customers. Qualified applicants should expect: 1. Resume and experience review, with particular attention to enterprise architecture and delivery experience. 2. Initial screening conversation focused on your background, customer-facing experience, and recent enterprise work. 3. Architecture interview in which you will be asked to reason through an enterprise technology scenario, make architectural decisions, discuss tradeoffs, and explain how you would take a solution from discovery toward production. 4. Employment and professional experience verification before engagement. Please make sure the employment history and experience described in your Upwork profile, resume, and proposal are accurate and verifiable. Working With Stevens At Stevens, you will have the opportunity to work on sophisticated enterprise AI initiatives across multiple industries, work directly with customer technology leaders and engineering organizations, own meaningful architectural decisions, and stay close enough to implementation to see the solutions you design actually get built. We are building Stevens around the idea that a small, highly capable team can do exceptional work for sophisticated customers without introducing the bureaucracy that often comes with traditional consulting. We value good judgment, technical excellence, clear communication, intellectual curiosity, and pragmatic decision-making. We want people willing to challenge unnecessary complexity, recognize when a simpler solution is better, and say when AI is not the right answer. If your background is in enterprise-scale technology architecture and delivery, and you enjoy solving difficult problems directly with customers, we would like to hear from you.

Book Editor and Amazon KDP Formatter Needed for Executive AI Business Book I am seeking an experienced nonfiction book editor and formatter to prepare a completed manuscript for publication through Amazon Kindle Direct Publishing (KDP) in both paperback and Kindle/eBook formats. The manuscript is a completed, ten-chapter executive-level business book focused on artificial intelligence, organizational transformation, and leadership. It includes original frameworks, figures, diagrams, and citations throughout. The complete manuscript will be shared only after an NDA is signed by the selected freelancer. Scope of Work The selected freelancer will be responsible for: Copyediting and proofreading for grammar, punctuation, consistency, clarity, and readability Identifying awkward wording, unnecessary repetition, inconsistencies, and formatting issues; humanize content edited by AI-generated tools Preserving the author's voice and executive-level tone rather than substantially rewriting the manuscript Reviewing headings, subheadings, chapter structure, figure references, captions, citations, fact check, and other book elements for consistency Professionally formatting the manuscript for Amazon KDP & Ingram paperback Preparing and formatting the manuscript for Kindle/eBook publication Properly incorporating figures, diagrams, tables, callout boxes, and other visual elements Ensuring visual elements remain legible and professional in the paperback edition Preparing publication-ready files that meet current Amazon KDP & Ingram requirements Create Table of Contents, Dedication, Foreward, Introduction, Acknowledgements, About the Author, Appendices, Copyright/Disclaimer, Glossary AI Literacy, Glossary of Acronyms, Endnotes, References pages Conducting a final quality-control review before delivery AI Knowledge Is Important The ideal freelancer should be AI proficient and comfortable editing material involving artificial intelligence, emerging technologies, organizational transformation, governance, and executive leadership. You do not need to be an AI engineer, but you should understand AI concepts and terminology well enough to preserve technical meaning, recognize potential inconsistencies, and avoid introducing inaccuracies during the editing process. Experience editing business, technology, leadership, or AI books is strongly preferred. Ideal Qualifications Professional nonfiction or business book editing Amazon KDP paperback and Kindle/eBook formatting Complex manuscripts containing figures, diagrams, tables, citations, and references Microsoft Word and professional book-production tools AI, emerging technology, digital transformation, or technology leadership content Deliverables Edited manuscript with tracked changes or equivalent editorial markup Clean final approved manuscript Publication-ready paperback interior file for Amazon KDP Kindle/eBook-ready file All source files used to create the final formatted book Final quality-control review for KDP publication requirements Confidentiality The selected freelancer will be required to sign a non-disclosure agreement before receiving the manuscript. All materials, including the manuscript, figures, frameworks, and concepts, are original intellectual property and may not be shared, reproduced, or used for portfolio or promotional purposes without prior written authorization. When Applying Please begin your proposal with "AI Business Book" so I know you have read the complete project description. Then provide: Examples of nonfiction books you have edited and formatted for Amazon KDP and Kindle Your experience with business, technology, or AI-related content Your approach to handling figures, diagrams, and visual elements Software you use for paperback and eBook production Whether editing, paperback formatting, Kindle formatting, and KDP quality assurance are all included in your proposed fee Your estimated turnaround time I am looking for an experienced publishing professional who can serve as the final editorial and production partner for this book.

I am building KIBA, an AI personal assistant and accountability platform. We already have a working messaging-based V1, and I am preparing to build a much larger V2 native iOS/Android application. I am NOT looking for someone to immediately replace my current developer or build the entire app. I want to hire a highly experienced senior mobile/AI engineer, software architect, or fractional CTO to act as an independent technical advisor. You will review our complete product specification, current architecture, existing features, future roadmap, and development quotes. You will then join a 60–90 minute call with my current developer, ask technical questions about how he plans to build everything, challenge the architecture where necessary, review his estimates/pricing, and help me determine whether he has the technical ability to successfully build the complete KIBA product. KIBA V2 will be a native AI application combining a general-purpose personal AI assistant with a deep accountability system. Features include AI chat, Claude/OpenAI integration, long-term user memory, proactive AI messaging, goals, commitments, Today/tasks, Execution Score, proof/photo verification, AI Spaces for fitness/business/money/school, workout and meal tracking, live web search, challenges, social accountability, GPS/geofencing verification, Apple HealthKit/Google Health Connect, Screen Time/app restrictions where supported, push notifications, Stripe payments, Money Mode/consequences, Plaid/banking data, and external API/business integrations. We are also building part of the web frontend/dashboard using Base44, so I specifically need someone who understands the difference between inexpensive frontend/UI work and legitimate backend/infrastructure engineering. I want to know when features should use existing APIs/SDKs or reusable infrastructure instead of being developed and priced as completely separate systems. A major goal of this review is making sure our architecture is reusable. For example, the web dashboard, native application, AI conversations, Today/tasks, Execution Score, proof system and AI Spaces should share backend infrastructure wherever appropriate. I do not want to pay to build something now and then rebuild the same system when we move into the full native V2 app. After reviewing everything and participating in the call, I want a private written assessment covering: * Current developer’s technical ability * Whether you believe he can realistically build the complete KIBA V2 * Quality and scalability of his proposed architecture * Major technical risks * Whether his feature pricing and timelines are reasonable * Features that appear overpriced or unnecessarily separated * Features that should share reusable infrastructure * Areas where existing APIs/SDKs/services could reduce cost * Whether current work will genuinely transfer into the native V2 application * What you would architect differently * Recommendation: move forward / move forward but restructure & renegotiate / replace developer I am not looking for someone who will automatically agree with me or automatically criticize my current developer. I want an unbiased senior technical opinion. REQUIRED EXPERIENCE You should have strong production experience with several of the following: * React Native * iOS / Swift * Android / Kotlin * Mobile application architecture * Node.js / TypeScript and/or Python backends * REST APIs / Webhooks * PostgreSQL / Supabase / Firebase * Claude API and/or OpenAI API * AI agents / tool calling * AI memory / RAG / vector databases * Apple HealthKit * Google Health Connect * GPS / geofencing / background location * Apple Screen Time APIs (FamilyControls / DeviceActivity / ManagedSettings) * Android device/usage controls * Stripe * Plaid * Push notifications * Authentication/security * Real-time synchronization * Photo uploads / AI vision * SaaS architecture * App Store / Google Play production launches * Third-party API integrations Experience with Base44, RevenueCat, Twilio/messaging infrastructure, Shopify, Meta APIs, Whop APIs or similar platforms is a bonus. BEFORE I HIRE YOU Please start your proposal with “KIBA REVIEW” and answer these questions: 1. What production iOS/Android applications have you personally built or architected? Please provide App Store/Play Store links. 2. Have you built production AI applications using Claude/OpenAI with memory and tool/API calling? 3. Have you personally worked with HealthKit/Health Connect? 4. Have you worked with Apple’s Screen Time APIs? 5. Have you implemented GPS/geofencing/background location? 6. Have you integrated Stripe and/or Plaid? 7. Have you designed a backend shared between web and native mobile applications? 8. Are you comfortable questioning another developer on a live technical call? 9. Are you comfortable reviewing development estimates and identifying where reusable architecture could reduce development costs? 10. What do you believe are the three technically hardest parts of building KIBA based on the description above? This will initially be a paid technical audit/consultation, approximately 2–5 hours, with the possibility of an ongoing technical-advisor relationship if it is a good fit.

Work directly with our CEO and CTO to build technology that helps people find addiction treatment and recovery support. Start Your Recovery is a public health resource that has helped connect more than 3 million people to care. We work with clinicians, public health experts, nonprofits, and treatment providers to make it easier for people and families to navigate addiction treatment. We’re looking for a Technical Product Manager to help us build what comes next. This is a hands-on role for someone early in their career who wants to learn quickly, take on meaningful responsibility, and work closely with experienced leaders. You’ll work side-by-side with our CEO and CTO to understand important problems, take a first crack at solving them, rapidly prototype solutions using AI and modern tools, and then work with our developers to turn the best ideas into durable products and systems. What you’ll do - You’ll sit at the intersection of product, engineering, data, operations, AI, and addiction treatment. - Own problems from idea to launch. Understand the problem, develop an initial solution, define requirements and workflows, and drive the project through execution. - Prototype before you spec. Use AI, low-code tools, scripts, and whatever else helps you quickly build and test potential solutions before handing successful approaches to engineering to harden and scale. - Be AI-native. Continually experiment with new AI tools and capabilities, and look for ways they can help us build products faster, automate work, improve our data, and solve problems that previously required significant engineering effort. - Help shape the roadmap. Evaluate opportunities, clarify scope, make tradeoffs, and help us decide what we should—and shouldn’t—build. - Develop deep domain knowledge. Learn how addiction treatment works—from levels of care and insurance to facility operations and how people search for help—and translate that understanding into better products and systems. - Work closely with engineering. Develop enough technical depth to reason about systems, data, integrations, and implementation tradeoffs, then partner with developers to turn prototypes into reliable production solutions. - Use data to solve problems. Investigate issues, test assumptions, measure performance, and identify opportunities for improvement. - Improve how we operate. Find processes that can be made better through software, automation, AI, or better tooling. - Create clarity. Turn ambiguous problems into clear decisions and executable plans. - Ship. We value learning by building and getting useful solutions into the world over perfect process or documentation. What we’re looking for We’re intentionally open to someone relatively early in their career. We care more about trajectory than tenure. You’ll likely thrive here if you: - Have 1–4 years of experience in product, engineering, analytics, technical project management, consulting, operations, or another analytical role - Are highly analytical and technically curious - Are AI-native—when faced with a problem, your instinct is to explore, experiment, and see how far you can get toward a working solution yourself - Enjoy prototyping and are comfortable learning new tools on the fly - Have a strong “let’s figure it out” mindset rather than assuming every technical problem needs to start with an engineering ticket - Want more responsibility than you might get at a larger organization - Take ownership rather than waiting to be told what to do - Can turn an ambiguous objective into a clear path forward - Communicate well with both technical and non-technical teammates - Are organized without being overly process-oriented - Are comfortable making decisions with imperfect information - Are genuinely interested in addiction treatment and behavioral healthcare, and excited to turn domain knowledge into technical solutions You do not need to have already held the title “Technical Product Manager.” We’re looking for someone smart, ambitious, curious, and capable of growing quickly. Why Start Your Recovery Work on something that matters We’ve already helped connect 3M+ people to care. Your work will directly influence how we help the next several million. Grow quickly You’ll work directly with our CEO and CTO and take on problems that might sit with much more senior employees at a larger company. You’ll get significant autonomy, frequent feedback, and increasing responsibility as you demonstrate good judgment and execution. Build in a new way AI is changing what a small, capable team can build. We want you to be one of the people experimenting at that frontier—using AI to move from problem to prototype quickly, learning what works, and partnering with our developers to turn promising solutions into robust products and systems. Learn across disciplines Our work spans software, AI, data, search, healthcare, consumer behavior, and business strategy. You’ll have the opportunity to develop both strong technical product skills and deep expertise in addiction treatment—so you can understand problems well enough to see solutions others miss. The person we’re hoping to find Maybe you’ve spent a few years in product, engineering, analytics, consulting, or operations and feel ready for more. You want to learn faster. Own bigger problems. Build things yourself. Work closely with people you can learn from. And do work that has a tangible impact. When you encounter a problem, your first instinct isn’t simply to write a ticket. It’s to understand it, experiment, use the tools available to you, and see whether you can get something working. You learn quickly. You use AI naturally. You create clarity. You take ownership. And when someone hands you an important, messy problem, you figure out how to solve it.

Job description We are developing a browser-based virtual jewelry try-on application that allows users to see realistic 3D rings on their fingers using a phone or computer camera. We already have a working 3D implementation built with MediaPipe, Three.js and React. The application can track the hand, position a 3D ring on the finger, handle basic occlusion and render jewelry in real time. However, we want to significantly improve the accuracy and realism of the current implementation, particularly: Ring centering and positioning on the finger Accurate orientation as the hand/finger rotates Correct fit and depth Stability and reduction of jitter Side-angle accuracy Occlusion Performance across different hand positions Consistency between front and rear mobile cameras We are looking for a highly experienced computer vision / AR engineer to review our existing implementation, identify the primary limitations, and determine what algorithmic improvements could bring the tracking quality substantially closer to leading commercial virtual jewelry try-on solutions. This is not a project starting from scratch. You will be reviewing and improving an existing application and working alongside our current developer. For the initial phase, we would like a technical assessment of the current approach followed by implementation/testing of the highest-impact improvements. If the initial work produces promising results, this can develop into a larger ongoing project. Strong experience in some of the following is important Computer vision MediaPipe / hand landmark tracking Hand pose estimation 3D geometry and coordinate systems AR object placement Pose estimation and transformation Temporal filtering / tracking stabilization Depth estimation Three.js / WebGL Real-time mobile/browser computer vision Occlusion / segmentation Experience with virtual try-on, AR commerce, hand tracking, rings/watches/jewelry, or similar camera-based object placement would be especially valuable. When applying, please answer: What experience do you have with hand tracking, pose estimation, AR or virtual try-on? Have you worked with MediaPipe hand landmarks? If so, please describe the project. Have you previously improved stability/accuracy beyond the raw output of an existing tracking framework such as MediaPipe? Based on the description above, what areas would you investigate first to improve ring positioning, orientation and stability? Please provide examples of relevant computer vision/AR work. We are specifically looking for someone with deep technical experience, rather than a general web or 3D developer. *****Because this project involves access to proprietary source code, selected developer must be currently residing and performing work in the United States. Please confirm this in your proposal.

The short version We are an AWS partner and are constantly applying for partner funding programs to benefit our customers adoption of AWS. This process includes qualifying customers for AWS AI funding programs, file the paperwork that unlocks them, and then deliver the AI engagements those programs pay for. Right now one person carries both the filing and the delivery coordination. We are hiring the person who takes that over. The job is two halves, roughly 50/50: 1. Funding operations — moving applications through AWS Partner Central: ACE opportunities, APFP fund requests, claims, and the artifact packages that go with them. 2. Delivery program management — keeping the engineers who fulfill those engagements on scope, on schedule, and inside the program’s deadlines. You’ll get to work closely with our director and internal AI systems getting exposure to the full lifecycle from idea to funding. You will have important responsibilities from day 1, being the final touchpoint for the style, verification, and filing - so your work has a massive impact on your team and the company as a whole. -------------- Half one — AWS funding and opportunity operations You own the pipeline of applications end to end. • Qualification screening. Run each new customer or use case against program eligibility gates before scoping conversations happen — partner-path stage, opportunity stage, customer type, segment, and program-specific screens. Name the gate a prospect fails and cite the source guide. Escalate exception paths to our AWS Partner Development Manager rather than improvising policy. • ACE opportunity management. Create and maintain opportunities in AWS Partner Central: type, stage progression, campaign tagging, solution records, parent-opportunity linkage for follow-on vehicles, and close-out obligations at Launched. • Fund request filing. Work the APFP wizard for AI Assessment, Proof of Concept, MAP AI Modernization, GenAI Production Ready, and related vehicles — program templates, activity naming, dates, linked opportunity, invoice entity, milestones, and required document tags. • Artifact finalization. Take draft SOWs, year-one usage calculations, pricing-calculator estimates, assessment reports, and executive readouts to submission quality: formatting, house style, internal consistency, and a clean upload package. • The consistency pass. Before anything is submitted, confirm that every number agrees across every artifact — opportunity value, fund-request value, usage calculation, and the AWS Pricing Calculator estimate. Mismatch between artifacts is the single most common rejection cause in these programs, and catching it is your job. • Claims and clocks. Track planned start and end dates, submission lead times, claim windows, fund-request expirations, and the annual budget cutoff. Route customer sign-off envelopes the day delivery completes. File claims and invoices on time, every time. • Reviewer correspondence. Handle returned fund requests: read reviewer comments, assemble the evidence or attestations they asked for, and resubmit through the correct path. • System of record discipline. Keep deal briefs, status notes, and program trackers current. When a decision gets made in a call, it lands in writing the same day. Half two — delivery program management Once funding is approved, the engagement has to actually ship — inside a fixed window, against countable deliverables. • Run the delivery calendar for concurrent engagements: assessments, proofs of concept, modernization workloads, production-readiness projects, and experience-based acceleration events. • Translate scope into work. Turn a signed SOW into an engineering-facing plan with real milestones, then hold the line on what is and is not in scope for that vehicle. • Manage the developers day to day. Standups, unblocking, dependency tracking, environment and access requests, and honest status. You are not writing the code; you are making sure the people writing it have what they need and know what “done” means. • Protect the deliverable-to-artifact chain. Every engagement produces documents that AWS and the customer will read — reports, readouts, architecture diagrams, delivery packets, sign-offs. You make sure they get produced on schedule and match what was filed. • Customer-facing coordination. Schedule discovery calls and readouts, chase the inputs we need from customer stakeholders, send recaps, and keep expectations accurate. You will be the steady voice the customer hears between milestones. • Backward-plan from the deadlines. Claim windows and the budget-year wall are not negotiable. Delivery dates get set so the claim is safe, and you are the one who says so early when a date is slipping. What you need Core AWS knowledge — non-negotiable. You do not need to be an engineer, but you need to hold a technical conversation without translation. Concretely: you know what an AWS account and organization structure is, you can read a pricing calculator estimate and a usage projection and tell whether they make sense, and you are comfortable with the vocabulary of the AI services our projects are built on. Foundational or Associate-level AWS certification is a strong plus; Partner Central and ACE experience is a stronger one. Exceptional organization. This role lives or dies on tracking. Multiple customers, multiple programs, each with its own dates, caps, document requirements, and sequencing rules. If you are the person who keeps a real system and never loses a deadline, you will be very good at this. If you rely on remembering things, you will not. Excellent written and verbal communication. You will write to AWS reviewers, to customer executives, and to engineers, and those are three different registers. Clear, plain, precise, no padding. You will also be the person who has to say “this date does not work” out loud, early, to someone who does not want to hear it. Precision under written rules. Comfort working inside published program rules and internal filing standards — following them exactly, quoting them when they are ambiguous, and recording the interpretation instead of inventing policy. Judgment about what not to send. These packages go to AWS and to customers. Confidentiality about customer material, care with claims, and a habit of a second pass before anything leaves the building.   Nice to have • Prior work inside AWS Partner Central, ACE, or APFP (or an equivalent hyperscaler partner program) • Experience managing software or data engineering delivery teams • Background in consulting or professional services operations • Familiarity with generative AI project patterns — retrieval, agents, evaluation, inference cost modeling • Comfort using AI tooling as part of your own workflow; we do, heavily • Technical writing or proposal-operations experience How we work • Small team, high trust, no layers. You will work directly with the founder and with our Director of AI and Software Engineering. • We are building process, not folklore. Every rule we follow is written down, and part of your job is making the written version better than the version in someone’s head. • We use AI tooling throughout the practice — drafting, research, consistency checking. You will inherit that setup, not fight it. • Deadlines are external and firm. In exchange, the work is unusually clear: you always know what “on track” means. What success looks like • First 30 days — you know the programs, the filing standards, and the live pipeline. You can screen a new prospect for eligibility and say which gate it passes or fails. • First 90 days — you are filing opportunities and fund requests independently, with review rather than supervision, and you own the delivery calendar for active engagements. • First 180 days — nothing slips a claim window on your watch. You are catching consistency problems before anyone else sees them, and the process documentation is measurably better than you found it. Logistics Employment structure is open — full-time, contract-to-hire, or a fractional arrangement for the right person. Tell us what you are looking for and we will have an honest conversation about it. Compensation depends on structure and experience. To apply Send a résumé and cover letter covering three things: 1. Your AWS background — what you have actually worked on, and any certifications. 2. A time you managed something with a hard external deadline and a lot of moving parts. What was your system? 3. A time you caught a mistake in a document before it went out. How did you catch it? No cover-letter theater. Three straight answers is what we are reading for.

AI is becoming extraordinarily capable. The defining question is whether that capability strengthens the people using it. Exponentials is building personalized discovery around human intention: what someone wants to find, understand, accomplish, or become. We are seeking an exceptional technical co-founder who wants to turn that vision into a trusted product and help build the company behind it. Study https://exponentialsdiscovery.com/, explore the live demo, and read our essays on human–AI co-evolution. If the mission resonates and the engineering challenges excite you, we should talk. **The opportunity** Most digital discovery begins with a platform’s objectives. Exponentials begins with the person. Users express their needs; AI explores relevant possibilities, explains why results fit, and learns through feedback while preserving the user’s authority to choose. Our ambition is an evolving personal World Model connecting interests, goals, preferences, and constraints across ecommerce, healthcare, education, and media. Someone’s life crosses these boundaries. Useful intelligence should understand those connections without silently assuming permission or deciding what matters for them. We believe this architecture can address a central source of the AI backlash: people questioning whose interests increasingly powerful systems actually serve. Trust, agency, and useful outcomes are product requirements with commercial consequences. A live proof of concept exists. The opportunity now is to establish what works, challenge what does not, and build the foundations for a differentiated, scalable business. Exponentials is receiving strong interest from several of the world’s leading investors, adding momentum to this early founding opportunity. **What you will own** You will work directly with the founder on technical strategy, product decisions, architecture, execution, and the engineering team. You must enjoy writing code, investigating failures, making difficult tradeoffs, and translating an ambitious thesis into products people repeatedly choose. Build the discovery pipeline: natural-language intent understanding, retrieval from reliable sources, entity resolution, constraint-aware ranking, and evidence-backed explanations. Results must connect users to real, relevant destinations, with uncertainty clearly identified. Develop the World Model: distinguish stated preferences from inference, scope constraints appropriately, update context as goals change, and give people meaningful ways to inspect, correct, withhold, export, or delete their information. Make cross-domain personalization useful and accountable. A budget for shoes should not automatically become a healthcare constraint. A recommendation should explain its evidence and assumptions. User feedback should visibly improve subsequent discovery. Create the evaluation and operating discipline: repeatable tests, source provenance, observability, security, access controls, latency and cost measurement, failure recovery, and controlled deployments. Measure successful discovery and user understanding alongside engagement. Use AI agents to accelerate engineering, research, verification, and operations. Determine where Grok, other models, APIs, and conventional software genuinely help. Build explicit approval boundaries for consequential actions and maintain evidence that humans can inspect. Help recruit outstanding builders, establish engineering standards, and explain the technology clearly to prospective partners and investors. **Who should apply** You have personally shipped substantial software and can show what you owned, how it performed, and what failed. Strong experience in applied AI, search, recommendations, data systems, or personalization matters more than fashionable terminology. You can architect across frontend, backend, data, and infrastructure; evaluate model behavior critically; and balance speed with reliability. You understand that a persuasive generated answer is not the same as a verified result. You bring entrepreneurial judgment, intellectual honesty, product taste, and the confidence to challenge the founder constructively. You can narrow an expansive vision into an excellent first experience while designing for what comes next. **The working relationship** This posting seeks a potential long-term technical co-founder through an initial freelance collaboration. We will discuss a bounded paid diagnostic, mutual expectations, availability, compensation, and any potential equity arrangement before committing. Cofounder fit must be established through working together. **How to respond** Share two relevant systems you personally built, with links or a brief demonstration and your specific contribution. After exploring Exponentials, identify its strongest technical opportunity, its most consequential unproven assumption, and one concrete improvement to the demo. Propose your first 30 days: the experience you would prioritize, what you would measure, and what you would deliberately defer. Include your availability, proposed diagnostic scope and fee, and what you need from a founder to do exceptional work. Help build AI that expands what people can discover—and what they can do with their lives.

Part-Time Business Development Coordinator | Engineering Consulting | Long-Term Opportunity Overview We are a boutique engineering consulting firm that helps OEMs and technology companies develop connected products, embedded systems, IoT devices, cloud-connected platforms, and AI-enabled solutions. We're looking for a proactive Business Development Coordinator to build and manage our outbound business development process. This is **not** a high-volume call center role and **not** a commission-only sales position. Your responsibility is to consistently create qualified opportunities by identifying the right decision-makers, building relationships, executing thoughtful outreach, and ensuring nothing falls through the cracks. The founder will lead all technical discussions, proposals, and client engagements. Your role is to get us in the room with the right people. Responsibilities * Research target companies that fit our ideal customer profile. * Identify engineering leaders, CTOs, product managers, and technical decision-makers. * Conduct professional outbound phone calls to identify the correct contacts and request introductions where appropriate. * Send personalized follow-up emails. * Execute LinkedIn outreach when appropriate. * Build relationships with recruiters, industry contacts, and referral sources. * Schedule discovery meetings. * Maintain and update our CRM. * Manage follow-up sequences so every opportunity receives timely follow-up. * Prepare a concise weekly pipeline report including: * Companies contacted * Conversations held * Meetings scheduled * Active opportunities * Recommended next actions Ideal Candidate You are: * Professional and confident on the phone. * An excellent written communicator. * Organized and process-oriented. * Persistent without being pushy. * Comfortable speaking with executives. * Self-directed and dependable. Preferred Background Experience in one or more of the following is highly desirable: * Engineering consulting * Technical recruiting * Industrial automation * Manufacturing * B2B technology sales * Electronics * Embedded systems * IoT * Engineering services An engineering degree is **not required**, but an interest in technology is a plus. Success Metrics Success will **not** be measured by call volume. Instead, we'll evaluate: * Qualified engineering introductions * Meetings booked with decision-makers * Active opportunities created * Consistent follow-up * CRM quality * Overall pipeline growth Hours * 10–20 hours per week * Fully remote * Flexible schedule * Long-term opportunity Compensation * Competitive hourly rate (please include your desired hourly rate) * Performance bonuses based on qualified meetings and business opportunities generated ## Application Instructions Please include the following in your proposal: 1. A brief summary of your business development experience. 2. The industries you've worked in. 3. A short example of how you successfully reached a difficult-to-contact decision-maker. 4. A 1–2 minute voice recording introducing yourself. 5. Your availability (hours per week and time zone). 6. Begin your proposal with the word **Engineer** so I know you've read the full posting. Candidates with experience building relationships with engineering, manufacturing, or industrial organizations are especially encouraged to apply.

I am preparing an existing education focused SaaS application for a controlled beta followed by a public launch to individual speech language pathologists. I am looking for a senior full stack developer with strong application security experience to help ensure the application is secure, stable, and appropriately configured for ongoing real world use. The application is functional and nearing completion. This is not a ground up build. I need an experienced developer to review the existing codebase, identify security vulnerabilities or structural concerns, provide a prioritized remediation plan, complete mutually agreed upon fixes, and retest the application. The goal is not a temporary beta level solution; the completed work should support both the controlled beta and the subsequent public release. The application was developed using AI assisted coding tools and has not yet undergone a comprehensive review by a senior software engineer. For that reason, I am looking for someone who can independently evaluate the code and architecture rather than assume that the current implementation follows production level security and engineering practices. Current technology stack: • Next.js • Supabase database and authentication • Vercel • GitHub • Stripe or subscription billing components, if applicable to the current implementation The application will eventually handle confidential student-related information, so data privacy, secure user separation, and access controls are especially important. There is currently no real student data in the application. Initial review should include: • Authentication and session management • Supabase Row Level Security policies • Separation of data between individual user accounts • Database permissions and access controls • API routes and server-side authorization • Storage permissions • Exposure of keys, secrets, or sensitive information • Input validation and common web vulnerabilities • Dependency and configuration risks • Logging, monitoring, backups, and recovery considerations • Vercel and Supabase deployment configuration • Subscription and payment security, if currently implemented • General code quality, stability, and performance concerns Requested deliverables: 1. Review of the existing application and configuration 2. Written findings categorized as critical, high, medium, or low priority 3. Recommended remediation plan with estimated time and cost 4. Completion of mutually agreed-upon critical and high-priority fixes 5. Final retest confirming that the completed fixes are working 6. Recommendations for safely preparing the application for controlled beta, public launch, and ongoing maintenance. Please note that I am not asking a developer to certify the application as automatically FERPA- or HIPAA-compliant. I am looking for a technically sound security review and documented remediation work that can support a separate legal and privacy review. The ideal developer: • Has substantial experience with Next.js and Supabase • Has implemented and audited Supabase RLS policies • Understands multi tenant SaaS data isolation • Has experience securing applications that handle sensitive information • Can explain findings clearly to a nontechnical founder • Is comfortable working within an existing GitHub repository using branches and pull requests • May be available for future bug fixes, maintenance, and feature updates Please include: • Relevant Next.js and Supabase projects • Examples of security or code audits you have completed • Your proposed approach to this review • Your estimated timeline • Whether you can provide a fixed estimate or capped number of hours after an initial review • Your availability for occasional ongoing support This is a self funded, early stage product, so I am looking for a phased and cost conscious approach. The engagement should begin with the initial review and prioritized findings. Any remediation work must be estimated and approved before it begins, with clear hour caps or fixed milestones whenever possible.

We are looking for a deeply experienced Homecare Homebase (HCHB) integration expert to help us architect and build a third-party solution that extends HCHB's scheduling capabilities. This is not a general healthcare integration role. We are specifically looking for someone who has personally built applications or integrations on top of HCHB before, using a combination of HCHB APIs, data interfaces, and RPA/desktop automation. What You'll Help Us Build Our goal is to build a third-party scheduling and workflow layer on top of HCHB that can replicate and ultimately extend capabilities available through HCHB Smart Scheduling. You will work with our engineering and product teams to determine the best architecture for: * Reading the HCHB data required for intelligent scheduling and optimization * Writing scheduling decisions and updates back into HCHB * Understanding which workflows can be supported through official HCHB APIs and interfaces * Designing reliable RPA approaches where APIs are unavailable or insufficient * Handling authentication, sessions, permissions, concurrency, error recovery, and other HCHB-specific constraints * Building an architecture capable of operating reliably across large, multi-location home health and hospice organizations * Identifying ways a third-party platform can go beyond * Smart Scheduling through automation and AI We are particularly interested in understanding the practical boundaries of what can and cannot be accomplished outside of HCHB's native applications. Who We're Looking For * You should have demonstrated, hands-on experience building third-party technology that integrates deeply with Homecare Homebase. Required: * Significant experience working directly with Homecare Homebase * Hands-on experience with HCHB APIs and/or integration interfaces * Experience building RPA or UI automation against HCHB, including Citrix-based environments where applicable * Strong understanding of HCHB scheduling workflows, data structures, and operational concepts * Experience extracting data from HCHB and writing information or actions back into HCHB * Ability to advise engineers on architecture, technical limitations, reliability, and implementation tradeoffs * Experience taking an HCHB integration into a real production environment Strongly preferred: * Experience specifically with HCHB Smart Scheduling Experience building scheduling, routing, workforce optimization, or visit-management applications on top of HCHB * Experience supporting large home health or hospice organizations * Familiarity with HCHB's various API, database, interface, reporting, and integration options * Experience combining APIs with RPA when HCHB does not expose the required functionality programmatically Demonstrated Experience Is Critical We are **not** looking for someone whose experience is limited to administering or implementing HCHB. Candidates should be able to show us technology they have previously built that interacts with HCHB. As part of the evaluation process, we will ask candidates to: * Walk us through at least one third-party application or integration they personally helped build against HCHB. * Explain which HCHB interfaces/APIs were used and where RPA or other techniques were required. * Demonstrate the application operating against an HCHB sandbox, test, or other appropriately authorized environment, where permitted. * Explain the major technical limitations they encountered and how they worked around them. * Discuss how they would architect an external scheduling platform capable of matching and extending Smart Scheduling. Existing authorized sandbox or development access to HCHB that can be used to demonstrate prior work is highly desirable. Engagement We are open to an individual consultant, independent engineer, or highly specialized integration architect. The initial engagement will focus on technical discovery and architecture, with the opportunity to expand into hands-on development and implementation. If you have spent years figuring out how to make HCHB work with systems outside of HCHB, we want to talk to you.