> Markdown version of [/jobs/ext/598469-founding-go-developer-ai-saas-platform](https://www.wearedevelopers.com/jobs/ext/598469-founding-go-developer-ai-saas-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Founding Go Developer - AI SaaS Platform - **Company:** EUROPEAN SERVICE CENTER INC. - **Location:** Roswell, GA, United States - **Salary:** $85,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Business Logic, Optical Character Recognition (OCR), Audit Trail, Automation of Tests, Software as a Service, Code Review, Relational Databases, Database Storage Structures, Programming Tools, Github, Python (Programming Language), PostgreSQL, Screenshots, ReactJS, Large Language Models, Backend, Build Tools, Front End Software Development, Golang - **Published:** June 22, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=1cba1bded722af0d ## About the Role Do you have experience in Workflow management (operations management method)? ## Description We are building a closed-loop operating system for automotive repair businesses. The platform will connect: * Shop management. * Estimates. * Repair orders. * Invoices. * Customer and vehicle history. * Accounts payable. * Credit card transactions. * Bank transactions. * Document reconciliation. * Accounting workflows. * Payroll logic. * Technician pay. * Owner dashboards. AI-assisted workflow automation., * Python for AI, OCR, document processing, and automation where appropriate. * React for frontend interfaces. * PostgreSQL for relational data. * APIs for banking, credit card, payroll, accounting, and shop workflows. * AI coding agents and LLM-based development tools. * OCR and document matching. Audit trails and approval workflows. You do not need to know everything on day one. You do need to learn quickly and care about building systems the right way. Go experience is strongly preferred, but a strong backend developer who can become productive in Go quickly may also be a fit. What You Will Actually Do: * You will work directly with ownership and technical leadership. * There are no layers of management. * There are no committees. * There are no endless meetings. * You will help turn real business workflows into working software. You will: * Build backend services in Go. * Design database structures and business logic. * Build APIs and system workflows. * Use AI tools to accelerate development. * Review, test, and improve AI-generated code. * Build systems for repair orders, invoices, bills, transactions, approvals, and reconciliation. * Design audit trails so important decisions can be traced later. * Create and maintain project markdown files, architecture notes, and implementation plans. * Decide where automation is safe and where human approval is required. * Help build interfaces that make complex operations understandable. * Own problems from concept to production. * Some days you will write code. * Some days you will review code. * Some days you will map a workflow on a whiteboard. * Some days you will document architecture so future AI tools and developers understand the system. * Some days you will realize the original idea was wrong and help design a better one. That is normal here. The Personality That Fits Here: * The right person may be quiet. * The right person may prefer working deeply instead of talking constantly. * The right person may enjoy solving complex problems alone before discussing the answer. * That is completely fine. We value people who: * Notice details others miss. * Think in systems. * Like understanding how things really work. * Prefer clear and direct communication. * Can focus for long periods. * Are comfortable working independently. * Care more about accuracy than appearances. * Are willing to question assumptions. * Do not need constant meetings to feel productive. * Like building tools that other people depend on. Are persistent when a problem is difficult. We are not looking for corporate polish. We are looking for judgment, ownership, and the ability to build. Who May Be a Strong Fit. You may be a strong fit if: * You are self-taught or learned by building real things. * You have built applications, tools, systems, automations, apps, or platforms on your own. * You can point directly to GitHub or working examples of what you have built. * You enjoy backend systems and business logic. * You like using AI tools, but you do not blindly trust them. * You use documentation, notes, markdown files, or architecture files to organize your thinking. * You can explain why you made a technical decision. * You are comfortable saying "this does not make sense" when something is wrong. * You care about edge cases. * You like clean data models. * You think audit trails and permissions matter. * You would rather solve a real problem than chase trends. You want meaningful responsibility early. We are less interested in credentials than proof that you can think and build. Who Will Probably Not Enjoy This Role: This is probably not the right role if: * You need a large team around you. * You need every task fully defined before starting. * You only want to work from tickets. * You prefer meetings over building. * You want a highly structured corporate environment. * You are uncomfortable making technical decisions. * You think AI-generated code should be trusted without review. * You think AI-generated code is always worthless. * You dislike documenting your work. * You are mainly looking for remote work. * You are applying to hundreds of jobs with the same generic response. You cannot show examples of applications, systems, or tools you have built. * Location: * This is a strictly in-office position. * No remote. * No hybrid. * We need someone close to the business, the workflows, the CTO, and the real problems we are solving. * If you are not able to work in office, this role is not a fit., * Your GitHub profile or links to applications, tools, APIs, automations, or systems you have built. * A short explanation of the most important thing you personally built or owned. * What problem it solved. * Why you approached it the way you did. * What technical decisions you made. * What tradeoffs you accepted. * What broke, failed, or became harder than expected. * What you would do differently today. * Your experience with Go/Golang. * What AI coding tools you use. * How you verify AI-generated code before trusting it. * How you use markdown, documentation, architecture files, or technical notes to organize a project. * One example of a time you disagreed with the original product or technical direction and what you did about it. Include anything that proves you can build: * GitHub repositories. * Live demos. * Screenshots. * Documentation. * Architecture diagrams. * Personal projects. * Internal tools. * Automation scripts. Workflows you designed. If you built something useful that other people never fully understood or appreciated, start there. We are not looking for the best interviewer. We are looking for the right builder. About European Service Center ## Related Videos - [Agentic AI in Go](https://www.wearedevelopers.com/videos/100274-agentic-ai-in-go) - [Go with the Flow: Stop the Leaks Before Your Memory's a Waterfall!](https://www.wearedevelopers.com/videos/100073-go-with-the-flow-stop-the-leaks-before-your-memory-s-a-waterfall) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Innovating Developer Tools with AI: Insights from GitHub Next](https://www.wearedevelopers.com/videos/1268-innovating-developer-tools-with-ai-insights-from-github-next) - [MLOps and AI Driven Development](https://www.wearedevelopers.com/videos/347-mlops-and-ai-driven-development) - [How One Developer Built the Back Office for 10 Million Companies](https://www.wearedevelopers.com/videos/100082-how-one-developer-built-the-back-office-for-10-million-companies) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [Find a Developer Job: 12 Best Job Sites For Developers](https://www.wearedevelopers.com/magazine/165-find-a-developer-job-12-best-job-sites-for-developers) - [Where To Find Software Engineering Jobs](https://www.wearedevelopers.com/magazine/396-where-to-find-software-engineering-jobs)