Work at Postproxy
We build infrastructure for social publishing at scale, written by engineers who've done it before. We care about correctness, performance, and solutions that hold up under load.
Ownership & impact
Build features end-to-end. What you ship goes straight to users, and you see the results yourself.
Remote & async
Work from anywhere within ±3 hours of Berlin (CET). Writing is the default, meetings happen when they're worth it.
Move fast
Small team, short feedback loops. No approval chains, no quarterly planning cycles. Ship, learn, repeat.
Straight talk
Flat team. We say what needs to be said. Feedback is direct, decisions are documented, context is shared.
Open Roles
We're building PostProxy, a SaaS API platform for social media publishing. We aim to provide the best API for social posting out there.
For this we need an engineer who knows how the things work, understands database internals, understands asynchronous processing and queues and has solid experience proving this.
The stack
- Go + Rails. We use the tools that fit the purpose. If you think some weird combo will bring considerable value so be it.
- You (AI ;)) need to write some browser JS sometimes. Sorry.
- Postgres is our the only and beloved database.
- Docker. We do containers in production but nothing crazy.
- All those small but important things like error tracking, etc.
- We DO use AI but we DO NOT vibecode. You own the code and its performance.
What you'll work on
- Build features end-to-end, from data model to UI.
- Work with high-throughput job queues and media processing: video, images, multi-platform publishing with different format requirements per network.
- Maintain and extend third-party API integrations that have a habit of changing behavior silently. It's not like you watch in the logs non stop looking for abnormalities. It's more like you build tools to detect them and be able to act promptly.
- Contribute to architectural decisions. Your input lands in real deployments.
Who you are
- First of all, you care about your users. API-first services are not tolerant to even small outages.
- High-load is a concrete toolbox for you: proper indexes, queues, selective denormalization, caching where it's justified and so on.
- You worked on 3rd party integrations with many-many requests before.
- You push back on duplication and "temporary" solutions that end up living forever.
- You explain your decisions because you value code review.
What we offer
- Fully remote, async. We do calls maybe 2 calls per week.
- Small team. Your decisions ship to production and go straight to users.
- A live product with real customers and revenue.
- Direct communication. If something is off, we say so.
Interested? Tell us about a project you're proud of and what your specific contribution was.