Job Opportunities API

About us: Founded in Copenhagen, Denmark, in 2014, Templafy’s success is built by our 60+ employee nationalities found at offices around the world. We believe that when people feel valued, heard, and empowered, they perform at their best—creating a win for all. Our unique product and dedication to innovation and excellence have raised over $200 million in funding from top investors like Insight Venture Partners, Seed Capital, Dawn Capital, Damgaard Company and Golub Capital. About the role and company: I'm using AI to write the job posting, and I asked Codex to use the Slack connector to collect some "cultural proof points" about what it's like working at Templafy. This is what it came up with: Templafy engineering culture comes across as pragmatic, product-close, technically opinionated, and unusually open about trade-offs. · Engineers are expected to think like product builders , not just implementers. Threads often connect technical work to customer demos, pilots, product quality, adoption, and user feedback · Pragmatism is a real value. There’s repeated language around simple/explicit code, logical PR chunks, avoiding feature creep, solving the 80% case first, building MVPs, and getting something testable into users’ hands quickly · Quality matters, but in a practical way. Tests, E2E coverage, evals, pipeline health, flaky tests, feature-flag cleanup, and technical health all show up as shared concerns · Engineers are candid and trusted to challenge scope. I saw people questioning whether work should be bugs vs feature requests, whether backlog items are clutter, when to pause work, and when a “quick fix” is acceptable · Cross-functional collaboration is very present. PMs, design, solutions, support, security, platform, and product engineering are all in the same threads negotiating quality bars, customer urgency, UX, risk, and ownership · AI/tooling curiosity is strong, but not naive. The AI guild and engineering channels show people experimenting with code review agents, AGENTS.md , evals, Codex/Claude workflows, guardrails, and agentic SDLC, while also worrying about learning, friction, false positives, security, and long-term maintainability · There’s a bias toward async feedback and shared learning. Moving sprint review-style updates into short videos and Slack feedback is a good culture signal: fewer meetings, more continuous visibility · Ownership is distributed. People jump in to unblock, sanity-check, investigate, create PRs, clean up flags, or hand over work when someone is away. The tone is informal but accountable Small caution: I would avoid selling the culture as “perfectly polished.” The honest version is stronger: Templafy looks like a place where engineers have real agency, real product context, and real technical messes to improve. The rest of this job posting is probably more like what you'd expect. What You’ll Do In Product Engineering, you will help build and improve product experiences used by Templafy customers. You will work with product managers, designers, and other engineers to understand customer problems, shape solutions, and deliver features from idea through production. You will: Build, improve, and maintain customer-facing product features Collaborate with Product and Design to turn ambiguous problems into usable solutions Use AI-assisted development tools thoughtfully as part of your everyday engineering workflow Make technical decisions within your area and contribute to broader architecture discussions Write reliable, maintainable code that fits existing patterns and systems Use tests and fast feedback loops to support confident delivery Build early versions of ideas to evaluate real behavior instead of debating hypotheticals Help simplify product paths, remove complexity, and make features easier to test