Senior Fractional SaaS / Full-Stack Engineer for Production CRM Platform I am looking for an experienced Senior Full-Stack SaaS Engineer / Platform Engineer to provide independent technical oversight, production troubleshooting, architecture review, automated testing, and long-term engineering support for an existing construction-industry CRM platform called ForgeOne CRM. This is not a project to build a new application from scratch. ForgeOne is already a substantial working SaaS application with multiple modules, user roles, business workflows, customer/job management functionality, integrations, mobile and desktop interfaces, and an expanding feature set. The platform has been developed rapidly with significant use of modern AI-assisted development tools. That has allowed us to move very quickly, but the application is now reaching the point where I want an experienced senior engineer involved to help transition the development process from rapid feature-building into a more mature production environment with stronger automated testing, monitoring, release controls, architecture oversight, and regression prevention. I am the founder/business owner, not a traditional software engineer. I need someone who can understand the technical side deeply while also communicating clearly with me in normal business language. This will initially be a fractional/part-time position, approximately 5–10 hours per week depending on what is happening. If the relationship is successful and ForgeOne continues growing, this could potentially develop into a much larger role or eventually a full-time technical leadership/engineering position. What I Need My biggest priority is production reliability. As ForgeOne has grown, there are now enough interconnected features that making a change in one area can potentially create an unexpected issue somewhere else. I do not want to rely solely on the founder, employees, customers, or subcontractors manually discovering regressions after a release. I want to develop a proper engineering safety net around the platform. The person I hire should be capable of looking at the entire application as a system rather than only working on individual frontend tickets. You should be comfortable investigating problems across: * Frontend * Backend * APIs * Database * Authentication * User permissions * Multi-tenant data separation * Third-party integrations * Browser/mobile behavior * Deployment * Logging * Monitoring * Automated testing * Production infrastructure * Security Initial Assignment — Production Readiness / Architecture Audit The first thing I want is an independent technical review of the existing ForgeOne platform. I want someone experienced to examine how the system is currently structured before making major recommendations or changes. The review should include areas such as: * Overall SaaS architecture * Code organization and maintainability * Frontend/backend interaction * Database design * Multi-tenant architecture * Company/tenant data isolation * Authentication * Authorization and role-based permissions * API design * Third-party API integrations * Error handling * Logging * Production monitoring * Security * Secrets/environment configuration * Deployment process * Database migrations * Backup/recovery considerations * Performance * Scalability * Mobile responsiveness * Automated testing coverage * Release/change-management process * Technical debt that creates actual business risk I would like findings categorized approximately as: Critical — immediate production, security, data, or operational risk. High — should be corrected before significant customer growth. Medium — important improvements that should be placed on the engineering roadmap. Low — optimization, cleanup, or longer-term technical improvements. I also want the engineer to identify what is currently working well. I am not looking for someone who automatically recommends rebuilding everything because they prefer another framework or architecture. If part of the existing application works correctly, is secure, scalable enough for our requirements, and can be maintained, I want that taken into consideration. Changes should be driven by actual technical or business reasons. Automated Regression Testing A major project I want implemented is a comprehensive automated testing system that acts like real ForgeOne users. The goal is to automatically test critical workflows after changes instead of waiting for a human user to discover that something stopped working. I am interested in browser-based end-to-end testing using Playwright or an equivalent framework. Examples of workflows that should eventually be automatically tested include: * User login * New-user invitations * Invitation acceptance * Authentication * User permissions * Company/tenant separation * Dashboard loading * Navigation * Creating jobs * Opening existing jobs * Editing job information * Estimates * Saving information and returning to it * File uploads * Photo uploads * Multiple-file uploads * Customer workflows * Employee workflows * Subcontractor workflows * Notifications * Status/workflow changes * Mobile navigation * Desktop navigation * Responsive layouts * Major CRM modules * Third-party integration screens * Error states * Permission restrictions I want a structured test environment/test company using controlled test data rather than automated testing that performs destructive actions against real customer information. External integrations that could create real financial or operational transactions must be handled appropriately through sandbox environments, mocks, test accounts, or other safeguards. Production Monitoring I also want much stronger visibility into what is happening when something fails. I am interested in implementing or improving tools such as: * Sentry or equivalent application monitoring * Frontend error reporting * Backend error reporting * API failure tracking * Performance monitoring * Browser console error capture * Failed network request capture * Deployment/version tracking * Useful diagnostic logs * Screenshots or traces from failed automated tests When an automated test fails, I want enough information available that an engineer can quickly determine what happened rather than spending hours trying to reproduce an unknown problem. AI Reliability / Diagnostic Agent Another area I am interested in developing is an internal AI Reliability Agent. The AI should NOT have unrestricted authority to modify production code, production databases, or customer information. The primary purpose would be: * Monitoring * Testing * Diagnosing * Comparing failures with recent changes * Organizing logs * Identifying possible causes * Generating incident summaries * Helping prioritize issues * Suggesting possible fixes * Assisting engineers with investigation For example, if an automated browser test fails while opening a job, the ideal system could collect information such as: * Which test failed * Expected behavior * Actual behavior * Screenshot * Browser console errors * Network/API failures * Relevant application logs * Deployment/version * Recently modified files * Potential source of regression The AI could then help analyze that information and provide an engineer with a useful starting point. I want AI helping engineering, not AI operating production without appropriate controls. Experience with the OpenAI API, AI agents, LLM integrations, developer tooling, or AI-assisted diagnostics is valuable, but strong traditional software engineering experience is more important to me than someone whose primary background is prompt engineering. Release Process I want help developing a safer release process. The eventual goal is something similar to: Development/change → automated tests → code/technical review → staging/testing → approval → production deployment → production smoke tests → monitoring Critical workflows should be tested before a release is considered successful. I also want guidance on sensible rollback procedures when a production change creates a regression. Third-Party Integrations ForgeOne includes and is developing multiple third-party integrations. The engineer should be comfortable reviewing and troubleshooting: * REST APIs * OAuth/authentication flows * Webhooks * API credentials * Rate limits * Error handling * Retries * Sandbox versus production environments * Integration security * Data synchronization * Failure recovery Some integrations involve construction-industry suppliers and other outside service providers, so protecting credentials and preventing unintended external transactions is extremely important. Additional details regarding integrations and architecture can be provided to qualified candidates after appropriate confidentiality protections are in place. Security / Multi-Tenant SaaS Experience Multi-tenant security is extremely important. ForgeOne supports multiple independent companies using the same SaaS platform. I need someone who understands that authentication alone is not sufficient. The architecture must ensure that one customer/company cannot access another company’s: * Jobs * Customers * Employees * Financial information * Files * Photos * Communications * Credentials * Integration information * Other tenant-specific data Experience reviewing authorization, RBAC, tenant isolation, database access controls, API authorization, and SaaS security is highly desirable. Who I Am Looking For I am looking for a senior engineer who has actually supported real production SaaS applications. Ideal experience includes several of the following: * Senior full-stack development * SaaS application architecture * Multi-tenant applications * Modern JavaScript/TypeScript development * Modern frontend frameworks * Backend development * SQL/relational databases * API development * REST APIs * Authentication * Authorization * RBAC * Third-party integrations * Git/GitHub * CI/CD * GitHub Actions or equivalent * Playwright * Cypress or other automated E2E testing * Production monitoring * Sentry or equivalent * Cloud deployment * SaaS security * Performance troubleshooting * Production incident investigation * AI-assisted development * OpenAI/LLM integrations * AI agent development Experience with CRM, ERP, field-service, construction-management, project-management, fintech, insurance, or other workflow-heavy SaaS platforms is a strong plus. The exact technology stack and repository architecture can be discussed with shortlisted candidates rather than making assumptions in this posting. What I Am NOT Looking For I am not looking primarily for: * Desktop IT support * Help desk support * Network administration * Basic website development * WordPress development * Landing-page development * Someone learning SaaS development for the first time * A prompt engineer with limited traditional software engineering experience * An agency sending a salesperson while an unknown developer actually performs the work * Someone who immediately wants to rebuild the entire application before understanding it I want to communicate directly with the engineer who will actually be reviewing and working on ForgeOne. Working Style I move quickly and appreciate clear communication. I do not need technical terminology used simply for the sake of sounding technical. When there is a problem, I want an engineer capable of explaining: 1. What is wrong. 2. Why it matters. 3. What caused it or what likely caused it. 4. What options we have. 5. What they recommend. 6. What could potentially be affected by the change. 7. How we test the fix. 8. How we prevent the same problem from happening again. I value engineers who understand that the objective is not merely to make a bug disappear. The objective is to make the product more reliable after every fix. Engagement This will begin as an hourly fractional engagement. Expected initial involvement is approximately 5–10 hours per week, although hours may increase or decrease depending on the project phase. The first major deliverable will be the technical/production-readiness assessment. If that goes well, I would like the relationship to continue into: * Production stabilization * Automated regression testing * Monitoring * Release-process improvements * Architecture oversight * Security improvements * Integration review * Difficult production debugging * AI Reliability Agent development * Ongoing engineering consultation For the right person, this could become a significant long-term role as ForgeOne grows and could potentially transition into a full-time position in the future. When Applying Please do not send a generic copy-and-paste proposal. Please answer the following: 1. Describe a production SaaS application you personally worked on and what your responsibility was. 2. Have you taken over or audited an application that was developed rapidly and needed stabilization? What did you find and what did you do? 3. Describe your experience with multi-tenant SaaS applications and tenant data isolation. 4. What experience do you have with authentication, authorization, and RBAC? 5. What automated end-to-end testing tools have you used? 6. Specifically, what experience do you have with Playwright, Cypress, or similar browser automation? 7. What production monitoring/error-tracking systems have you implemented? 8. What is your experience troubleshooting difficult production regressions? 9. Have you worked with applications developed using AI-assisted coding tools? 10. Have you built AI agents or LLM-powered engineering/operations tools? If yes, briefly explain what they did. 11. If you discovered that an existing part of ForgeOne was designed differently than you personally would have designed it, how would you determine whether to leave it alone, improve it, or replace it? 12. Are you comfortable beginning with a paid technical audit before assuming broader responsibility? Please begin your proposal with “ForgeOne Review” so I know you read the posting. I am looking for an experienced engineer who can become a trusted independent technical resource for ForgeOne—not simply someone to complete isolated coding tickets.

*** DO NOT APPLY IF YOU CAN NOT DO AT LEAST 95% OF THE JOB DESCRIPTION*** We're looking for a battle-tested engineer with deep, self-earned coding fundamentals who also knows how to leverage AI as a force multiplier. This is not a role for developers who have grown dependent on AI to write code they couldn't write themselves. You should be able to navigate a large, complex brownfield codebase on your own — and when you do bring AI into the work, your engineering foundation is what makes the difference between AI generating noise and AI generating production-ready solutions. This role is deliberately vertical. You'll write product code, and you'll own the AWS environment it runs on. Those aren't two jobs handed to one person to save a headcount — they're one job, because the interesting failures happen at the seam between them. ## About the Role You'll work across a TypeScript codebase with a Next.js frontend and AWS-backed services supporting consumer mobile applications at meaningful scale. AI tools are a deliberate part of the workflow: prompting for implementation plans, critically evaluating those plans against our architecture and business requirements, reviewing generated code for correctness and quality, and shipping with confidence. When AI hits the limits of a complex legacy system — and it will — you'll be the one who knows how to guide it through. On the platform side, you'll own infrastructure defined in code, the network boundaries around our data services, our cloud security posture, and the vulnerability backlog. The systems you'll inherit include an event-driven ingestion pipeline (managed queues and a key-value store behind an API gateway), a columnar analytics warehouse feeding BI dashboards, object storage with a query layer over it, a document database, and webhook integrations with third-party attribution and app-store billing systems. That's real scope, and we're stating it plainly so you can decide whether you want it. If you'd rather not touch infrastructure, this isn't the role. If you've been looking for a job where you own the whole vertical instead of filing tickets across a boundary, it is. ## What You'll Do ### Product engineering - Own the full lifecycle of AI-assisted development: generating plans, stress-testing them against real architectural constraints, and validating that generated code is production-worthy - Write correct concurrent code: reason clearly about async/await, the event loop, promise scheduling and cancellation, and the difference between concurrency and parallelism — and keep blocking work off the request path so a slow upstream API never stalls the thread serving users - Make and defend architectural decisions: know where layered, clean, and hexagonal (ports-and-adapters) designs each earn their complexity, enforce separation of concerns, and keep AI-generated solutions inside the boundaries the codebase already established rather than letting them drift toward whatever pattern the model saw most often in training - Practice test-driven development in earnest — write the failing test first, make it pass, then refactor — and use TDD as the mechanism that keeps AI-generated code honest rather than a box to check afterward - Drive tests past the happy path: use AI to enumerate boundary values, error branches, race conditions, malformed input, and failure modes of dependencies, then verify the generated tests actually assert behavior instead of restating the implementation back at itself - Contain the blast radius of AI-assisted work: small reviewable diffs, plans before code, incremental commits, contract and regression coverage on anything touching shared surfaces, and a bias toward changes you can reason about end to end - Build and maintain the backend services behind our mobile applications, including event ingestion, third-party webhook consumers, and the integrations that feed reporting ### Platform and infrastructure - Define and change infrastructure as code: extend and review Terraform modules, manage state, read a plan critically before applying it, and recover when state and reality disagree - Own cloud networking: private and public subnets, security group and NACL design, and the access patterns for data services that sit inside the network — with a clear view of when putting compute in a VPC is the right call and when it just buys cold starts and NAT charges - Design read and write paths for scale, cost, and exposure: when something is hammering an object store or an API, diagnose whether it's legitimate traffic or an unsecured origin being scanned, and reach for the fix that matches — edge caching, cache-control and conditional requests, presigned URLs with sane TTLs, request collapsing, batching and backpressure on one side; blocking public access, origin access control, bucket policy and IAM scoping, WAF rate limiting, and keeping repository metadata and build artifacts out of served paths on the other - Treat a surprising cloud bill as a security signal, not just a cost problem — know which request outcomes you're billed for, what shows up in access and audit logs, and when the right response is rotating credentials rather than adding a cache - Own and tune cloud security posture management (AWS Security Hub, GuardDuty, Config, or equivalents): configure the standards, suppress the noise so real signal survives, and drive findings to closed - Apply and enforce security best practices aligned with NIST controls, including access control, audit logging, system integrity, and secure configuration management — using automated config checks to continuously verify those controls rather than attesting to them in a document nobody re-reads - Manage IAM as a design problem: least-privilege roles, scoped policies, credential rotation, and no long-lived keys where a role will do - Own CI/CD: pipelines that gate on tests, coverage, and security scans, with deploys that are reproducible and reversible ### Vulnerability management - Remediate CVEs, don't just report them. Take findings from discovery through to a shipped fix, including the unglamorous part where the patched version is a major bump and you absorb the breaking changes across the application - Triage with judgment: knowing whether a finding is reachable in code paths we actually execute or buried in a transitive dependency that never runs is what keeps you from breaking production over a theoretical risk. But the deliverable is a closed finding, not an assessment - Maintain dependency hygiene across a large Node/TypeScript tree, where the vulnerability surface is mostly transitive and the fixes are mostly version bumps with consequences - Remediate infrastructure and configuration findings, not just application dependencies — misconfigured storage, over-permissive policies, unencrypted resources, missing logging ### Operations - Serve as a rapid-response resource for user-facing issues — diagnosing, prototyping, and deploying fixes fast when production is on the line - Leave the environment legible to someone else: documented infrastructure, runbooks for the things that page you, and reproducible deploys. Sole ownership only works if it isn't sole knowledge ## What We're Looking For - 5+ years of proven TypeScript development experience, with work you can walk us through line by line and explain the reasoning behind — you know the language, not just the prompts - Deep proficiency in React and Next.js - Fluency in the JavaScript concurrency model, and enough exposure to how other ecosystems solve the same problem (C# tasks, Python asyncio, Kotlin coroutines, Rust futures, Go goroutines) to explain what async/await actually buys you and where it doesn't help - Demonstrated experience with TDD and a clear point of view on what it's good for and where it isn't worth it - The ability to reason about architectural tradeoffs out loud — not just name patterns, but say what each one costs and when you'd skip it - Strong working knowledge of AWS across compute, managed queues, key-value and relational stores, object storage, CDN, WAF, and IAM — including request-pattern and caching design under load and hardening of publicly reachable origins - Hands-on Terraform experience: writing and reviewing modules, managing state, and recovering from drift. Other IaC backgrounds (CDK, CloudFormation, Pulumi) transfer if the depth is there - Practical cloud networking: VPCs, subnet architecture, security groups, NACLs, and private connectivity to managed data services - Experience running a cloud security posture tool in anger — configuring standards, tuning findings, mapping automated checks to a control framework, and closing items rather than accumulating them - A demonstrated CVE remediation history: specific vulnerabilities you personally fixed, in both application dependencies and infrastructure configuration, including at least one where the fix required meaningful refactoring - Working fluency with SCA tooling (AWS Security Hub, Prowler, Dependabot, Snyk, npm audit, or similar) and a defensible process for prioritizing what gets fixed - The ability to critically read and evaluate AI-generated code — catching architectural drift, security gaps, and subtle logic errors that AI won't flag itself - A specific, experience-backed account of where AI coding tools fail: missing system-wide context, no real model of your codebase's complexity or layering, confidently wrong abstractions, tests that validate the bug, and volume that outpaces review capacity — plus the practices you use to keep that in check - Familiarity with AWS Security Hub, CIS Benchmarks, NIST or comparable security frameworks and the ability to translate controls into practical engineering decisions - Comfort using AI tools (Claude, Copilot, etc.) as a development partner, with the technical depth to steer them effectively in unfamiliar or complex codebases - Strong debugging instincts and the ability to move fast under pressure without cutting corners on security or quality - CI/CD pipeline ownership experience, including gating deploys on tests, coverage, and security scans ## Nice to Have Experience with mobile platforms (iOS/Android). Familiarity with FedRAMP, SOC 2, or other compliance frameworks that map to NIST. Experience with data warehousing or BI tooling. Container or serverless packaging experience. A CS degree or equivalent depth in fundamentals — data structures, concurrency, systems — however you came by it.

I’m running a real estate investment platform called ToInvested.com. The project is about 90% finished, and most of the code was built with Claude together with another engineer. Now I need a senior engineer to step in, review the full product carefully, test every major workflow, and help verify that everything is working correctly before it goes live. This is not just a “write more code” role. I need someone who can look at the platform like a real product, find hidden bugs, catch weak logic, test edge cases, review the AI-generated code, and tell me honestly what is ready and what still needs fixing. Because this is a real estate investment platform, accuracy and trust matter a lot. Users may rely on property data, investment logic, calculations, and AI-driven insights, so even small issues can create a serious problem later. The ideal person has strong full-stack experience, understands AI-assisted development, and has a good testing mindset. Real estate tech experience would be a big plus, especially with property platforms, investment tools, marketplaces, mortgage systems, or financial workflows. My main goal is simple: I want someone to break the project before real users do. If you’re the kind of engineer who can take a nearly finished product, test it deeply, clean up weak areas, and help make it production-ready, I’d be happy to talk.

Senior Full-Stack Flutter Developer (AI Platform) We're looking for a Senior Full-Stack Flutter Developer to lead development of a production-grade AI-powered web and mobile application. This is a long-term opportunity for an experienced engineer who can own architecture, development, and deployment. Responsibilities Build Flutter applications for Web, iOS, and Android Design scalable backend services and REST/GraphQL APIs Develop data import, ETL, cleanup, and normalization pipelines Integrate AI/LLMs (OpenAI, Claude, or similar) into production workflows Build analytics dashboards and AI-driven insights Architect PostgreSQL databases and cloud infrastructure (AWS/GCP/Azure) Optimize performance, security, and scalability Deploy and maintain production applications Requirements 7+ years of software development experience Expert in Flutter (Web & Mobile) Strong backend experience (Node.js, Python, Go, or similar) PostgreSQL and API design expertise Experience building ETL/data pipelines Production experience integrating AI/LLMs (OpenAI, Anthropic Claude, etc.) Hands-on experience with Claude Code and Claude Design for AI-assisted development workflows Experience using modern AI coding tools (Claude Code, Cursor, GitHub Copilot, Windsurf, etc.) Cloud deployment experience (GCP, AWS, Azure) Position is available immediately Must be available to work between 8 am - 5:00 pm + M-F

We are looking for a full-stack developer to design and build the MVP for Midnight Riviera, a new platform focused on nightlife events and recording studio discovery and booking. This should be a coded, functional MVP, not just a landing page or mockup. The goal is to launch a clean, premium platform that can begin accepting recording studios and processing bookings while also promoting Midnight Riviera events. PROJECT SCOPE Homepage Premium, modern nightlife/music-focused design Mobile responsive Sections for upcoming events and featured recording studios Clear navigation between Events and Studios Recording Studio Marketplace Browse recording studios Individual studio profile pages Photos, description, location/area, amenities, equipment, pricing, and availability information Basic search/filter functionality Studio Onboarding Recording studios can apply to join Midnight Riviera Studio submits business/profile information, photos, pricing, etc. Admin can approve or reject studios Approved studio profiles can be published to the marketplace Booking System Customer selects a studio Customer chooses or requests a date/time Studio can accept or reject the booking request Customer can pay through Midnight Riviera Booking status and confirmation are recorded automatically Customer and studio receive appropriate booking notifications Payments Stripe integration Preferably Stripe Connect architecture so Midnight Riviera can collect a platform commission and studios can receive payouts Payment and booking records stored in the platform Basic refund/cancellation capability Events Upcoming events page Individual event pages Event images, descriptions, dates, locations, pricing, etc. Ticket purchase button For the MVP, ticketing can integrate with an external ticketing provider rather than building a custom QR/ticketing system Basic Admin Admin should be able to: Add/edit/remove events Review studio applications Approve/reject studios Manage studio listings View bookings View basic payment/booking information TECHNOLOGY We are open to recommendations, but a stack such as Next.js/React, Supabase, Stripe, and Vercel would be appropriate. IMPORTANT We want a real coded application with a clean codebase that can be expanded after the MVP. The developer must provide full ownership and handoff of: Source code GitHub repository Database Deployment Stripe integration All project credentials/accounts Documentation needed for another developer to continue development This MVP does NOT need: Custom event QR/ticketing infrastructure Advanced messaging Advanced analytics AI features Native mobile apps Complex recommendation algorithms Large-scale enterprise functionality The focus is a simple, polished and reliable first version. BUDGET Fixed-price budget: approximately $3,000. We are looking for someone who understands how to keep an MVP lean and can recommend practical solutions rather than overengineering the first version. TARGET TIMELINE Approximately 4 to 6 weeks. WHEN APPLYING Please include: Examples of marketplaces, booking platforms or similar applications you have built Your recommended technology stack Whether you have experience with Stripe Connect Your estimated timeline Confirmation that all source code and project assets will be fully transferred at completion A brief explanation of how you would approach the recording studio booking and payment flow

We have built a functional demo/prototype of a Leave of Absence Case Management Portal in Replit and are looking for an experienced SaaS developer to help us productionize and deploy it on AWS. The platform is designed for employers to manage employee leave requests, documentation, approvals, and case workflows. Current prototype includes: • Employee leave intake portal • Manager and HR dashboards • File upload capabilities • Leave status tracking • Intermittent leave reporting • Extensions and renewals • Employee data feed integration (HRIS file feeds) • Role-based workflows We need someone to: • Review the current Replit codebase and deployment files • Assess architecture for scalability and security • Rebuild/refactor where necessary for production readiness • Deploy to AWS (best architecture recommendations welcomed) • Set up authentication and user roles • Secure document storage • Configure database structure • Build audit trail/logging • Implement API integrations for HRIS file imports • Establish CI/CD pipeline • Advise on SaaS multi-tenant architecture for future clients Ideal experience: • SaaS application architecture • AWS (Lambda, RDS, S3, Cognito, API Gateway, ECS, or similar) • HIPAA/SOC2 compliant architecture preferred • Secure file handling/document storage • Workflow/case management systems • HR tech or leave management experience is a plus Please include examples of similar SaaS platforms you have built and explain your approach to taking a prototype to production.

We are seeking an experienced Full-Stack/AI Developer to create an automated capture-to-proposal pipeline. The platform will integrate opportunity tracking with automated RFP parsing, compliance matrix creation, and draft proposal generation. The ideal candidate will have a strong background in both full-stack development and AI technologies.

Toolbox Gamez is looking for an experienced full-stack developer to provide ongoing support for our existing SaaS and mobile application. Our app is currently live on the Apple App Store and Google Play Store. The source code is maintained in our company-controlled GitHub account, the application is hosted in AWS, and the database is managed through MongoDB Atlas. We need a developer who can become familiar with the existing codebase, help keep the application stable, troubleshoot issues as they arise, and make minor improvements to the product over time. Responsibilities may include: • Reviewing and understanding the existing codebase • Troubleshooting and resolving application issues • Supporting the backend, admin panel, manager portal, and mobile app • Maintaining AWS and MongoDB connections • Assisting with mobile app updates and app-store releases • Fixing bugs and improving performance • Making minor feature and usability improvements • Supporting backups, deployments, and basic security improvements • Documenting important technical changes and processes We are not looking for a full rebuild. Our goal is to find a dependable developer who can support the current application and help us continue improving it as the business grows. The ideal candidate has experience taking over an application built by another development team and is comfortable working independently within an existing production environment. Please include: • A brief description of similar applications you have supported • Your experience with AWS, MongoDB, GitHub, APIs, and mobile apps • Whether you work independently or through an agency or know of group to tackle larger improvements • An example of a minor feature or improvement you have added to an existing product

PLEASE NOTE: ALL DIRECT CALLS AND EMAILS WILL BE BLOCKED, AND SENDERS WILL BE DISMISSED FROM CONSIDERATION, EVEN ON UPWORK. WE WILL NOT WORK WITH ANYONE WHO CONTACTS US OUTSIDE OF UPWORK. ZERO EXCEPTIONS. We are seeking a full-stack developer for both the ongoing maintenance of current products as well as the development of new products. We are a sports media company that creates applications that help fans be more effective when it comes to attending live sporting events. EXISTING PRODUCT DEVELOPMENT: Our first product launched two months ago: calendar.thestadiuminsiders.com, a custom calendar which incorporates team sports calendars (NFL, NBA, NHL, MLB, etc.) plus concerts/special events into a single view for each city. This required the integration of calendars from multiple sources in multiple formats, consolidated into a single view. Lots of moving pieces. The calendar has been developed, successfully launched, and is very stable. But there is ongoing maintenance to do, as well as continued enhancements to make. Our calendar was built in React, Next.js, and Firebase (this was not an AI developed product: it was built the old fashioned way). It also incorporates ICS feed parsing, which is critical. You need to understand these elements, as well as complex data architectures and data management. (Our advice: please don't approach your proposal by telling us about all of the pitfalls and traps waiting for us. We've had great developers and product managers working extremely hard to build a great product, and we haven't overlooked the complexities and nuances. We need someone to take a really well-built product and build on top of it, not tell us how they're going to save it from assured collapse. We're happy to hear that you understand some of those traps and nuances and complexities. Just please don't assume we haven't thought of them. Better to focus on why your experience is a good fit, rather than explaining coding to us). NEW PRODUCT DEVELOPMENT: Separate from the above product, we have a pipeline of products that are on deck that are being developed via vibe coding (specifically in Lovable), but we need a developer who can push them the last 10 yards before launch. Porting these projects from Lovable into Claude is completely fine (we know Claude is the stronger dev platform), but our front-end team is working in Lovable because it is an easier interface. But I expect we will move the projects over to Claude once we have the right person in place to assist with that. General Requirements: --NextJS --React --Firebase Functions and Firestore --NoSQL design --ICS calendar formats --CSV uploading --Vercel --Vibe coding (specifically taking products built with Lovable and making them production-ready) An understanding of sports is helpful, as it makes it easier to understand the relationship between teams, venues, leagues, and cities. You don't need in-depth specific understanding of stats or players or such, but an understanding of sports leagues will make it easier to understand the tasks at hand. In terms of approach, we will first want to make a bunch of quick fixes/improvements to the calendar app, followed by two more substantive upgrades. After that we will turn our attention to new products. Thanks -- we appreciate your interest, and we look forward to finding someone great. This is a fun product and an interesting company, especially for someone who likes sports.

Need Re-architect a static interactive web tool so its content lives behind login on a server, not in the browser. Next.js + Supabase. US-Only. No Subcontracting.