Careers
Help build the open-source platform for AI search
We have no open positions at the moment, and we'd rather say so than run an empty job board. You can still work on AutoSEO today: the whole codebase is on GitHub, and contributions of every size are welcome.
Open positions
No open positions right now
Until then, the best way to work with us is through the code. Everything happens in public on GitHub: issues, discussions, pull requests and releases.
Contribute
Where help is most welcome
Look for issues labeled good first issue or help wanted, or pick one of these areas.
AI engines
Add new answer engines, improve how citations and shopping cards are parsed and make providers more robust. Engines are defined in
src/lib/engines.ts.Integrations
CMS publishing, analytics, CRM and project-management connectors. Some are still in beta or marked “coming soon”, such as Fastly and AWS CloudFront.
Translations
The app interface is English today, with the onboarding wizard in English and German. Help bring more of the app and this website into other languages.
Documentation
Self-hosting guides for more platforms, API and MCP examples, troubleshooting. The docs live in the repository next to the code.
Agent skills and plugins
AutoSEO ships agent skills and plugins for Claude Code, Codex and Cursor. New skills and better instructions are welcome.
Bug reports and testing
A precise bug report with steps to reproduce is a contribution, too. Use the issue templates on GitHub.
Getting started
Your first contribution in four steps
- 1
Pick an issue
Start with a good first issue. For bigger ideas, open a thread in Discussions first so we can agree on the approach.
- 2
Set up locally
Node 24, pnpm and Docker for PostgreSQL. Run
pnpm install,pnpm db:pushandpnpm dev; the details are in CONTRIBUTING.md. - 3
Follow the conventions
Read
docs/ARCHITECTURE.md. Runpnpm typecheck,pnpm lintandpnpm testbefore you open a pull request — CI runs exactly these. - 4
Open a pull request
Use Conventional Commits and keep changes focused. Review and discussion happen in the open.
Speculative applications
Want to work on AutoSEO professionally?
If you believe you can make a real difference — in engineering, GEO research or working with agencies — write to us anyway. Tell us what you would work on first and link to things you have built. Contributions to AutoSEO say more than any CV.
- Send it to info@codext.de with the subject “Application”
- A short note and links are enough; no cover letter template needed
- We can't promise a position while no role is open
Why contribute
What you get out of it
Work in public
Every contribution is visible and credited in the commit history — a portfolio that speaks for itself.
A young field
Generative engine optimization is being defined right now. Engines, crawlers and answer formats change quickly, so there is real ground to break.
A modern stack
Next.js 16, React 19, Tailwind v4, PostgreSQL 17 and Drizzle, plus a local agent that runs Claude Code and Codex.
Questions about working on AutoSEO
Are you hiring?
Not at the moment. There are no open positions for AutoSEO at Codext GmbH right now. When that changes, the role will be listed on this page.
Can I apply speculatively?
Yes. Email info@codext.de with the subject “Application”, a short note on what you would work on first and links to your work. We can't promise a position while no role is open.
Do I need to be an experienced developer to contribute?
No. Issues labeled good first issue are scoped for newcomers, and documentation, translations and precise bug reports are valuable contributions that need no deep knowledge of the codebase.
Are contributions paid?
No. AutoSEO is an open-source project under the MIT license, and contributions are voluntary. If you would like to work on AutoSEO professionally, send a speculative application.
Under which license are contributions published?
AutoSEO has no contributor license agreement. Contributions are published under the project's MIT license, like the rest of the code, and you are credited in the commit history.
Where do I ask questions before I start?
In GitHub Discussions. For larger changes, open a discussion or an issue first, so we can agree on the approach before you invest a lot of time.
Start with one issue
The fastest way to work with us is a pull request.