work with me on zoom or other tool to create basic musician website with music player links to youtube video, I can create the hero image and all content. Want to complete in 3 to 7 hours if possible and leave me with the ability to update my site myself going forward

MORE CREATIVE THAN TECHNICAL. (All this is for creative inspriation, what I really need is a basic website with a creative start to the foundation) I'm looking for someone to build the first public face of a long-term creative project—a landing page and simple website that will serve as a signal tower for a community I'm gathering. The site needs to be equal parts aesthetic statement and functional hub, built quickly but with care, and handed off so I can easily update it myself. About the Project This June, I'm attending a concert and handing out business cards with a QR code. That code points to this website. The people scanning it will be a congregation of arcade-dreaming romantics and rock-opera believers who treat dystopian storytelling and neon-faded rebellion as catharsis. The website needs to feel like a continuation of that moment—a door into something real, still taking shape, but unmistakably alive. This is the first domino of a much larger vision. The site will house a blog(main landing page), Community project information (For now just a label, all that needs to be here is a way for me to add info/text easily/at a later date), A D&D campaign world (For now just a label, all that needs to be here is a way for me to add info/text easily/at a later date), An ethical framework (For now just a label, all that needs to be here is a way for me to add info/text easily/at a later date), A share/socials/patreon link (For now just a label, all that needs to be here is a way for me to add info/text easily/at a later date). It should feel like a transmission, not a pitch. What I Need 1. Landing Page A single, striking first impression. Dark background, static or glitch textures. A tagline, a short paragraph of context, an email signup form, and subtle links to deeper sections. The vibe: under construction, but on purpose—like a signal that just went live. 2. Core Tabs / Pages Simple, clean navigation to these sections: Signal – Blog / updates. I'll post regularly about the journey. The Stain – Vision, ethics, philosophy. The City of Trust – My D&D campaign setting. Lore, character profiles, actual play links. The Troupe – Community projects Voices – Introduction to the personas behind the project (Raum, Lai, etc.). Donate / Seed the Signal – A simple, honest donation page explaining what support funds. 3. Functionality Blog posting: I need to be able to write and publish blog posts easily, without touching code, within a week of the site being handed off. Page editing: I need to add or edit text/info on any of the tabs myself, same simple interface. Email signup: A form that collects emails (can use a lightweight service like Buttondown or EmailOctopus embedded). Mobile-first: Most people will first visit on their phones. Fast load times, legible text, easy navigation. Vibe & Aesthetics This is the most important part. The site should feel: Dark, but warm – like a radio broadcast at midnight. Arcade-dreaming, neon-faded – think worn phosphor glow, not sterile neon. Rebellious, but earnest – high stakes, no cynicism. Under construction, intentionally – some sections should feel like a half-built cathedral, not a broken site. Textural – static, glitch, grain, a sense of physical wear. Typographically deliberate – a worn serif for headings, a monospace for details, or a unique display font that feels like a rune-carved signal. I'll want to collaborate on color palette, font choices, and overall feel. I have a strong vision; I'm looking for someone who can translate it into a living page. Technical Needs I will purchase the domain and set up hosting/admin access. You'll work with me to get the site live there. The site should be built on a platform that lets me easily update content: WordPress with a custom theme, a static site with a headless CMS (Netlify CMS, etc.), or Webflow—whatever you recommend as long as it's easy for me to maintain. No heavy page builders that break if I breathe on them. Clean, lightweight code. All pages must be responsive and fast. Timeline Here is the catch, I would like this done by the end of the business day tomorrow, 6/6/2026 How to Apply Just send me a message with your thoughts. This is a paid gig. I'm funding this out of pocket because I believe in what's being built. If the vibe connects, I'd love to work with you on the next phases as the project grows.

I am a memoir writer and published author looking for help improving my existing WordPress writing website so it can function as a simple, effective author landing page. I already have a WordPress webpage for my writing, and I believe it may be possible to revise and improve that page rather than build something from scratch. I need help making it clean, professional, easy to navigate, and focused on my book, my writing, and connecting with readers. The page should ideally include: • A short author bio • A clear description of my memoir • Links to buy the book • A simple email signup/newsletter option • A clean layout that feels appropriate for memoir, recovery, personal story, and creative nonfiction • Possible links to future social media pages I may also need help developing a basic social media presence, but I do not want to take on too much at once. For now, the main goal is to make the WordPress page work well as an author landing page. Social media could become a second step if we work well together. I am looking for someone who has experience with author websites, WordPress, simple design, and preferably writers, books, memoirs, or personal brands. Please include: • Examples of author, book, or writer websites you have worked on • A brief description of how you would approach improving an existing WordPress page • Whether you can help with email signup forms/newsletter setup • Your estimated cost or hourly rate This as a fixed-price starter project

I am working through a design agency on an application for their end client. I think the agency will need you to contract with them directly, but I will manage the project for them. I have scoped out the project already, and our plan is to internally perform a design phase with the client to produce a prototype with Lovable. There may be minor changes to scope after that design phase. The purpose of the app is to create bespoke wedding gown concept images for potential customers of an online wedding dress store. I have provided the details below and attached as a PDF 1. Customer opens an AI dress/gown design experience from a link in their separate e-commerce site. - This can be presented in its own page, we don't want a chat window to be present on any other page - This will be a chat-based interface built into the content area of the page, instead of a popup - The design must be elegant, and match the theme of the e-commerce site - The top navbar and footer don't need to be exactly recreated in this subdomain site, but should look similar enough to create a seamless experience - There will be no integration with the e-commerce site, we need to keep these web apps completely separate 2. The customer must sign up for an account and purchase one credit to begin the AI session - We will need to set up the subdomain site with its own payment processing system and login system - The payment integrations are Stripe to facilitate credit card and Apple pay, and a basic Paypal integration 3. The customers should be able to use a magic link to sign into their accounts, instead of having to remember a password - The account should automatically remember the browser to reduce friction for future access to the app 4. When an AI session begins, we will ask the customer a series of questions programmatically to prime the AI agent so that it can deliver better results - The questions will need to use conditional logic, such that the first question which determines one of 3 main conditional tracks: What type of gown are you looking for? Wedding Gown, Evening Gown, Cocktail Dress - If Wedding Gown is selected, the AI should suggest for the customer to take go to a bridal store and pictures of themselves in different dresses they like and upload the pictures, and describe what they do and don’t like about each dress. It can ask this in the freeform chat, since it may make the most sense to let them fill out the entire questionnaire to stay engaged, and we should reduce the costs of development for the questionnaire by omitting any unnecessary UI that the freeform chat can provide. - It may be best to always just prompt for them to upload the inspirational image at the beginning of the freeform chat so we can omit unnecessary programmatic UI, but in the case of the Wedding Gown it will specifically ask the customer to peform the above task. - We may have other specific questions to add to the questionnaire depending on what conditional track the customer chooses, though only the 3 main branches of conditional logic based on dress type will be required. - Examples of general questions it will need to ask are as follows: -- silhouette -- neckline -- sleeves -- fabric -- embellishments -- color -- train -- length -- closure -- lining -- structure -- inspiration -- event type -- I didn’t get the exact list of questions yet from my client that we should ask in the initial questionnaire. Let me know if you will need this information to accurately provide a price for the development of this application 5. We should not display a concept image after the programmatic questionnaire, the customer will be taken directly into the freeform chat from the questionnaire. - The AI agent may start with an overview of the selected choices from the questionnaire, then can generate concept images at its discretion. 6. The AI should guide the customer through a freeform conversation - The conversation should begin with the AI asking the customer to subjectively describe their dream dress 7. The AI should also make a suggestion near the beginning of the conversation for the customer to upload at least one inspirational photo, but photo upload is optional - If the customer uploads an initial inspiration image, the AI agent should not attempt to figure out body type, measurements, or any other information that we can gather programmatically. - It should treat the inspirational image the same way it would treat any image the customer uploads during the freeform chat, to reduce the cost of development as much as possible. 8. Customer can proceed with a freeform conversation description - The customer should have the option to type in a chat and to upload images - The purpose of the conversation is for the customer to describe the desired dress or gown in an open-ended way 9. AI generates one or more concept images based on the conversation, as soon as it can once it has enough information - The AI model we select should be very good at generating these types of images, this is probably the most important quality the AI model needs to have - The concept images should have the same quality as the final image 10. It is acceptable to generate the gown on a mannequin or a real human model, however the dress must be photorealistic, not a sketch or cartoonish rendering. 11. The concept images that the AI generates and the final image should portray the body type and skin color which the customer specifies - It is very important for us to render the image of the garment on the correct body type - ex. Hourglass, pear-shaped, thin, plus sized, etc. -- Specific body measurements do not need to be factored into the rendering of the body type, it just generally needs to be able to render the garment on different body types. - It is also very important for us to render the garment on a human model or mannequin which has the same or similar skin color as the customer inquiring -- This is important for the customer to judge the garment color and fabric type that will look best on them -- This is also important to make the app inclusive for people of all racial backgrounds who might use the app -- It may be best not to display the face, or if human models are used, to use pictures of models with different racial backgrounds, to avoid bizarre mismatches between facial characteristics and skin tone - The AI agent should ideally prioritize pictures of garments from our client’s website to use as inspiration when it generates renderings in the freeform conversation, along with the customer’s description of what they want. However this is not a hard requirement, so it could be eliminated from the requirements if it greatly increases devlopment effort. - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to build the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application. 12. AI asks whether the generated concept is generally what the customer wants - Customer can revise the concept conversationally 13. AI can regenerate or refine images after customer feedback 14. The tone of the conversation the AI has with the customer is important. - We will want it to speak like a friendly expert seamstress. - This requirement will be somewhat subjective and so we will need to budget time for our client to request revisions to this tone based on their review of the system. 16. We ideally want the agent (both chat and image generation) to have deep expertise about fabrics and these types of garments in general, so it can guide the user through prompts, and render the chosen fabrics correctly - I think freeform chat will be necessary for the customer to explain which fabrics should be used where on the garment, instead of gathering this informaton in the programmatic questionnaire - The customer will likely revise the fabric selections after they see the initial renderings of the garment - We would like to avoid the costs of training an AI for this, so ideally we should use commercially available AI models which have been trained for this purpose, instead of having to train our own model. Prompting the AI with this information might be a cost-effective way to teach it this expertise 17. There will be certain restrictions on what types of colors or fabrics can be used in the dress designs - So, the agent should know these restrictions when it has the freeform conversation with the customer. - For example, the store owner will not be able to produce dresses with neon colors, tie dye colors, etc. - Our client will articulate a list of restrictions for us before we begin the project. 18. AI should never display links to other websites, or suggest for the customer to navigate to other websites 19. This AI might not need to be trained specifically for this industry, but we should at least use prompting to direct it to gather this kind of information, and to give it some background about what each of these things mean, so it can describe them to the customer. We basically need to make it as knowledgable as possble while keeping costs low. 20. The AI system the system should remember their active conversation - Since the customer will be required to have an account to use the AI system we can use that to automatically save the AI conversation - The saved conversation should preserve all the information that the customer input since the beginning of the AI session - A customer can only have one active AI session at a time - The customer cannot resume an AI session that has been completed - We don't need to provide a way for the customer to see the details of completed AI sessions 21. AI should have a fallback/human-help option if the customer gets stuck or the AI fails. - The fallback should collect enough information for an admin to follow up manually, so it should present a form in order to ensure that all the necessary information gets collected - A message should be displayed above the form, or somewhere on the page, to inform the customer that the entire conversation will be sent along with the form submission, so they know that they do not have to type all the details of the AI conversation - The app must present a button outside of the chat prompts after 3 - 5 chat messages have been sent, so the customer knows they have the option to terminate the AI conversation and manually ask for help. - That button would display the form - We don't want to display the button before any conversation has happened because we don't want customers to skip the chat altogether. -- One of the business goals of this app is to allow custom inquiries without overwhelming the support staff - Site admins must have the ability to adjust how many messages the button will display after, so they can control this threshold after they observe the results of real conversations - After the button initially displays, it should remain present in the view so the customer can easily access it at any point in the conversation 22. The freeform chat must be limited to something like 50 to 75 messages, in order to avoid excessive charges from the 3rd party AI services - This threshold should be adjustable from an admin portal - If this threshold is reached during the conversation, then we should force the customer to use the fallback form from requirement #21 to submit their inquiry 23. Customer can submit the completed design inquiry when satisfied. - During the submission process, the chat must ask for the following information, and present the following pre-written messages. This doesn't actually need to be executed by the AI model, but it can just be programmatically presented to the customer: - Ask for customer contact info, including name, email, and phone number. - Ask for requested event/date, while making clear the date is not guaranteed. - Ask for seamstress-relevant measurements, including bust, waist, hips, hollow-to-hem, shoulder width, bust point, underbust, waist-to-floor, arm length, bicep, wrist, back width, torso length, height, shoe height, and preferred fit. -- I still have to refine this list with the client, I am not sure if it needs to ask for all these things, or if there are some different things that I haven't listed here which it needs to ask for -- When it asks for this information it should display links under each measurement type to articles which describe how to produce each of the measurements. We can hardcode these links or allow the admin to specify each, they don't need to be generated by AI. - Prewritten disclaimer text should display. 24. The final submission should notify a list of email addresses set by a site admin. 25. The final submission will completely consume the credit used to purchase this AI session - The AI conversation cannot be resumed after the final submission - Another credit must be purchased to start a new AI conversation - New AI conversations will not have any memory of the previous conversations, any new AI conversations will start from a clean slate 26. Admins must have the ability to manually reset a credit, or assign a credit for free and cancel a current session, so the customer can start a new AI conversation. - This doesn't need to be very user friendly for the admin. If a session is reset this way, no knowledge of the previous conversation needs to be preserved. 27. Admins should be able to review partial, or completed conversations within a list in the admin portal - Each line item should display a status indicator to show if the conversation has been submitted yet, if an admin has began the review process, or if the item has been handled: Ex. In Progress, Submitted, In Review, Awaiting Payment, Handling, Ready To Ship, Closed - Admin should be able to see the answers to the programmatic questionnaire - Admin should be able to review the full conversation history - Admin should be able to review all uploaded photos/files - Admin should be able to review all AI-generated images, and the final one should be clear to them - Admin should be able to see the collected technical design details and measurements 28. Pricing of the garment remains manual and is handled by after review, the AI should not give any quote or present any pricing even if asked by the customer. 29. If the customer asks for pricing, the AI should display a prewritten script like this: "Pricing will be determined by the store owner after this conversation has been reviewed." 30. Invoices and payment will be handled manually through native WooCommerce custom order/invoice functionality which is already present in the e-commerce site, the AI system doesn't need to handle this at all. I mentioned this above on the requirements, but I want to reiterate since it is important and a hard requirement for how the development milestones must be structured: - The requirement for the quality of the images that are generated will be somewhat subjective and so we will need to budget time for our client to request revisions to this based on their review of the system. - We need to do the image generation part upfront to ensure the quality is acceptable before we spend time on other parts of the application As an optional add-on to the scope of this project, can you give a separate estimate to enhance the AI such that it understands which kinds of modifications will increase or decrease the cost of producing the gown, so it can guide the customer in case they are asking for very expensive things. - It shouldn’t give any specific price numbers, but should give the customer guidance if additions or alterations will significantly increase or decrease the cost of production. - This will be to prevent the customer from being surprised when the store owner manually follows up with them with the price of the garment they designed. This client did agree to adhere to a strict schedule to provide feedback after each round of development, given that we complete each round of development on the schedule we agreed to. - However, this client has deviated from agreed schedules multiple times in the past on other projects I did with them, so you should factor that into your timeline and cost estimations - We cannot increase the development cost mid-way through the project, however we can adjust the development timeline if the client deviates from the schedule In your proposal, please also include a quote or estimate for the cost of hosting and ongoing maintenance after the app has launched - Our client can pay for the hosting directly - We will need at least ongoing updates to patch security vulnerabilities and ensure uptime of the app and all its features which will be defined by the scope of this project - We don't need a 100% 24/7 uptime SLA, but basically just keeping everything up to date so it stays stable, and we'd need someone to respond to outages within 24 hours - Outage response can consist of simple rollbacks, if necessary, as long as all the chat session info is at least provided to the client as a CSV or similar, along with all graphic assets from any conversations, so they don't lose any data from an outage - I would set the expectation with my client that we would treat any future support or enhancement requests to be additionally charged for on an as-needed basis

Title: Backend Developer — AI Data Pipeline, Vector DB & Real-Time Push API Post: We are building an automated backend system that continuously crawls public web sources, processes and indexes content using AI, and delivers updates via webhooks. Looking for someone who has built this type of system before and can move fast. NDA required before project details are shared. What you’ll build: • Web crawler network —. • AI processing pipeline — cleans, deduplicates, chunks, and embeds ingested content into a vector database using an LLM embedding model. Quality scoring and incremental updates required. • Push API — monitors for significant content changes and delivers updates via webhook endpoints automatically. Includes configurable push schedules per subscriber, REST query endpoint, API key authentication, and token usage tracking per key. Tech stack (flexible — use what you know best): • Python (FastAPI) or Node.js • Any vector DB — Pinecone, ChromaDB, Supabase • Any LLM API — Anthropic or OpenAI • Any scheduler — n8n, APScheduler, cron • Redis for queue management • Railway, Render, or AWS for deployment Requirements: • NDA signed before kickoff — non-negotiable • Must have built RAG pipelines or vector DB systems in production — not tutorials • Must have experience with web crawlers and scheduled job pipelines • Must have experience with webhook delivery systems • GitHub or portfolio showing relevant deployed work required • 95%+ Job Success Score preferred • Individual contractors only — no agencies To apply include: • Example of a similar system you’ve built — web crawler, RAG pipeline, or push notification API • Your preferred stack for this type of build • Brief technical approach in 3–5 sentences • Hourly rate and availability to start Budget: $50–$80/hr Timeline: 3 weeks — focused sprint with daily check-ins

Lost login PW to pages on my website that are updated daily

We are seeking a motivated and skilled Front-End Developer to join our apparel technology team. In this exciting role, you will play a key role in building and enhancing the next generation of operational tools that will be utilized across various departments within our organization. Your primary focus will be on creating intuitive web applications and interactive dashboards that deliver real-time insights into crucial aspects of our operations, including production performance, inventory movement, sales trends, and overall operational efficiency. As a Front-End Developer, you will collaborate closely with a diverse group of professionals, including data analysts, operations managers, product stakeholders, and back-end engineers. Your collaborative efforts will be essential in transforming complex business data into clear, concise, and actionable user experiences. You will be responsible for designing and implementing user interfaces that not only convey critical information effectively but also enhance user engagement and accessibility. This position is particularly well-suited for developers who are passionate about creating data-rich applications and who excel at building user-friendly interfaces. You will be challenged to solve complex problems related to information presentation and workflow optimization, all while employing best practices in front-end development. Additionally, you will have the opportunity to stay updated on emerging technologies and trends, allowing you to improve and innovate the applications you develop. Your contributions will have a significant impact on the organization, empowering teams to make informed decisions, improving workflow visibility, and ultimately increasing productivity in multiple areas of the business. This is a unique opportunity for a talented developer looking to make a meaningful difference in an innovative and fast-paced environment. The required skills and requirements for this position are listed below: - Strong proficiency in React, JavaScript, TypeScript, HTML5, and CSS3. - Experience developing data-driven web applications or dashboard interfaces. - Understanding of frontend architecture and reusable component design. - Experience consuming APIs and handling dynamic data within applications. - Familiarity with state management solutions such as Redux, Zustand, or similar tools. - Strong debugging and troubleshooting skills. - Experience working with Git and collaborative development environments. - Ability to communicate effectively with both technical and non-technical stakeholders. - Strong attention to detail and commitment to user experience quality.

We are building a browser-based virtual trading card pack opening experience inspired by the excitement and animation style of the Pokémon TCG Pocket app. https://www.youtube.com/watch?v=GKNsrJY4D3U Users will purchase virtual packs, open them through an engaging animated experience, receive cards based on configurable rarity odds, and optionally request shipment of physical cards. We are looking for a developer or small team capable of delivering the entire project from start to finish. Core Requirements Frontend Experience The pack opening experience should feel exciting, polished, and mobile-friendly. Features include: * Mobile and desktop responsive * Pack carousel where users can scroll through multiple pack choices * All packs may visually appear similar initially * User selects a pack before opening * Animated pack opening sequence * Smooth reveal animations * Sound effects support * Epic and Legendary card reveal effects * Fast loading experience * Modern UI and UX We want an experience comparable to modern digital card-opening games. Pack Logic Users purchase a pack and receive cards based on predefined rarity percentages. Example structure: * Common * Uncommon * Rare * Vintage * Epic * Legendary Admin must be able to control: * Hit rates * Card pools * Available inventory * Pack configurations *Inventory Management System* A backend inventory system is required. Example: Common Pool: Horsey x500 Nidoran x300 Staryu x250 Legendary Pool: Mewtwo x5 Charizard x3 Lugia x2 Admin should be able to: * Add cards * Remove cards * Edit quantities * Upload card images * Enable or disable cards * View inventory remaining When a card is awarded, inventory should decrease automatically. Pack Configuration System Admin should be able to create new packs. Examples: ShadowMind Pack Retro Pack Vintage Pack Holiday Pack Each pack should have: * Custom artwork * Custom odds * Custom card pools * Active/inactive status User Accounts Users should be able to: * Create account * Login * View collection * View opening history * View owned cards * Request shipment of cards Collection System : Vault Users should have a digital collection page showing: * Cards owned * Quantity owned * Rarity * Card images * Opening history Physical Fulfillment System After opening packs, users should have the ability to request shipment of physical cards. Requirements: * Shipping address collection * Shipment request system * Admin fulfillment dashboard * Mark orders shipped * View shipment history Admin Dashboard Admin dashboard should include: * Inventory management * Pack management * User management * Shipment management * Order history * Analytics Payments Integrate Stripe / apple pay Users should be able to: * Purchase packs * View order history * Receive purchase confirmation Technology Preference Preferred: * Next.js * React * PostgreSQL * Stripe Open to recommendations if a better stack is proposed. Deliverables * Fully functioning production-ready web application * Source code * Admin dashboard * Database setup * Mobile responsive design * Deployment assistance * Basic documentation Proposal Requirements Please include: 1. Fixed price for the complete project 2. Estimated timeline 3. Similar projects completed 4. Recommended technology stack 5. Examples of gaming, collectible, loot-box, card-opening, or marketplace projects Important Please provide one total fixed-price bid for the complete project. We are looking for a long-term development partner but want a complete build quote for Version 1 of the platform. This is a real project that will move quickly for the right developer.

We're a fast-moving company with a strong in-house backend team looking to add a dedicated frontend developer on a retainer basis. This is not a one-off gig, we need someone available, responsive, and able to execute quickly when projects move. We're expanding our dev capacity and want to bring on someone who is hands-on, communicative, and fully present on every project they take on. Direct collaboration with our internal team is essential, we move fast and need someone who moves with us. WHAT YOU'LL BE DOING: Working directly alongside our in-house backend developers, design team, and marketing team to build and maintain web interfaces, implement designs, and ship features quickly. You'll own the frontend layer completely. WHAT WE NEED YOU TO KNOW COLD: - Tailwind CSS — this is non-negotiable, it's our primary styling approach - React and TypeScript — you should be writing this daily - Laravel — familiarity required, it's a core part of our backend stack - Astro — familiarity expected, you'll encounter it in our stack - Clean, responsive UI implementation with an eye for detail WHAT WE'RE LOOKING FOR: - Someone who writes their own code and takes full ownership of their work - Strong availability during US business hours - Fast turnaround without cutting corners - Clear, proactive communication throughout every project TO APPLY, PLEASE INCLUDE: - Your portfolio or GitHub link - 2–3 examples of projects built with Tailwind + React - A short note on your availability and how you handle tight deadlines

We are a growing software agency looking for a client-facing technical team member to handle discovery calls, technical interviews, and early project discussions with prospective and existing clients. This is not primarily a hands-on development role. We need someone with a solid development background who can communicate comfortably with clients, understand what they are trying to build, and ask practical technical and business questions before work begins. You will help clarify project requirements, identify missing information, discuss possible technical approaches, and prepare clear notes for our development team. You may also stay involved during delivery when client questions or technical clarification are needed. We are looking for someone with mid-level development experience. Full-stack CMS, ecommerce, and mobile development backgrounds are especially relevant. You do not need to be actively coding, but you should understand how software projects are planned, built, tested, and delivered. What we are looking for Professional experience as a software developer Mid-level understanding of full-stack, CMS, ecommerce, or mobile development Confidence handling client discovery calls and technical interviews Ability to turn client conversations into clear project requirements Good judgment when identifying missing requirements, scope concerns, and technical risks Clear spoken and written English Reliable availability during Eastern Time business hours Comfort using AI tools as part of daily work This role is a good fit for a developer who enjoys client communication and wants to move toward project discovery, requirements gathering, and technical coordination. When applying, please send a short video of around two minutes using Loom or a similar tool, briefly covering Your development background The types of software projects you understand best Any experience handling client calls or technical discussions Please include the video link with your application.