Golang Jobs

I run frequent drops on the official Bundesliga online store and I want to eliminate the manual steps at checkout. The goal is simple: a script or small application that reliably autofills my saved billing and shipping details and then submits the final purchase in the fastest, most human-like way possible. Scope of work • Navigate from cart to payment on the Bundesliga shop. • Inject my preset name, address, phone and email into every required form field. • Handle any hidden or dynamically loaded elements so the script never stalls. • Trigger the “Place Order” (or equivalent) button and confirm the order number or success page. • Run headless or with a lightweight UI where I can update profiles as needed. Tech flexibility I did not lock t...

I run frequent drops on the official Bundesliga online store and I want to eliminate the manual steps at checkout. The goal is simple: a script or small application that reliably autofills my saved billing and shipping details and then submits the final purchase in the fastest, most human-like way possible. Scope of work • Navigate from cart to payment on the Bundesliga shop. • Inject my preset name, address, phone and email into every required form field. • Handle any hidden or dynamically loaded elements so the script never stalls. • Trigger the “Place Order” (or equivalent) button and confirm the order number or success page. • Run headless or with a lightweight UI where I can update profiles as needed. Tech flexibility I did not lock t...

My simple chat app is built with a React frontend and Golang backend and served by Nginx on an Ubuntu EC2 instance (public IP). When the browser tries to POST to API/* I receive the error: “Access to fetch at 'http://localhost:8080/register' from origin 'http://public-ip' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space `loopback`.” I need the CORS policy tightened to allow requests only from specific public IPs (not a blanket *). Whether the change belongs in the Go server, the Nginx reverse-proxy rules, or both. Need more support to end the final deployment into ec2 and aws rds connection.

My simple chat app is built with a React frontend served by Nginx on an Ubuntu EC2 instance (public IP ‑ 3.235.226.188) and a Golang API listening on port 8080. When the browser tries to POST to /register I receive the error: “Access to fetch at 'http://localhost:8080/register' from origin 'http://3.235.226.188' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space `loopback`.” I need the CORS policy tightened to allow requests only from specific public IPs (not a blanket *). Whether the change belongs in the Go server, the Nginx reverse-proxy rules, or both, I’m open to the cleanest approach as long as: • The React app running at http://3.235.226.188 can successfully hit t...

I need a developer who can design, build, and container-deploy a new API that will live in a hybrid landscape—part of it running in the cloud, the rest on-prem. The codebase will revolve around Node.js, Go, and TypeScript, packaged for Kubernetes so that services can be moved or scaled between the two environments without friction. Core capabilities the API must ship with: • User authentication (JWT or OAuth2, your call as long as it is secure and test-covered) • Data processing that can handle both real-time and batch workloads • External integrations, mainly REST and a handful of webhook-driven services The workflow I have in mind is straightforward: containerize the service, write Helm (or similar) charts for deployment, set up CI/CD that pushes to both cluste...

I’m building a full-featured interpreting platform that lets our clients choose how they connect with language professionals—video, phone, or on-site—simply by speaking a request or using more traditional inputs. Scope • Three interpreting modes: virtual remote interpreting, over-the-phone interpreting, and onsite interpreter scheduling, all managed from the same interface. • Three interaction styles: voice commands for hands-free operation, plus keyboard/mouse and touchscreen for desktop and mobile users. • Role-based access: distinct dashboards for clients, interpreters, administrators, and an additional scheduler/project-manager role with permission controls. Core requirements 1. Integrate best-fit APIs for video conferencing, VoIP, and rea...