Senior Software Engineer

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 and maintain

• Debug issues, improve performance, and support production systems

• Help the team balance delivery speed, technical quality, and customer impact

• Contribute to engineering practices, code reviews, and technical discussions

What We’re Looking For

We’re looking for someone who enjoys product context and wants to be part of shaping what gets built, not only how it gets built.

You probably have:

• Strong experience building production software in a product engineering team

• Experience using AI-assisted engineering tools in real development work

• The judgment to use AI tools without outsourcing your understanding of the system

• Good technical judgment and the ability to make pragmatic trade-offs

• Experience with modern web application development

• A solid understanding of software design, testing, and maintainability

• Comfort working across frontend, backend, or full-stack

• Strong communication skills, especially in async and cross-functional settings

• A bias toward making discussions concrete through prototypes, tests, and working software

• A sense of ownership over outcomes, not just assigned tasks

• The ability to challenge scope constructively and keep work focused

Nice To Have

• Experience with SaaS or B2B software

• Experience with cloud platforms, CI/CD, observability, distributed systems

• Experience building AI-enabled products, agentic workflows, evals, or prompt/tooling systems

• Interest in improving developer experience, technical health, and team practices

What You’ll Join

You’ll join a product engineering team that cares about building useful software, learning quickly, and keeping the systems healthy enough that we can keep moving. We value people who can ask good questions, make things simpler, and help the team find the right trade-off when there is no perfect answer.

This is a good role for someone who wants meaningful product ownership, close collaboration with non-engineering colleagues, and enough technical complexity to make simplification genuinely valuable. We are looking for someone who can move fast, but who also knows that the fastest teams are usually the ones that keep their systems understandable.

Tech stack

Backend: C# / .NET, ASP.NET Core, Entity Framework Core, SQL Server
Frontend: TypeScript, React, HTML/CSS/SCSS
AI: LLM integration & agentic AI (tool-calling, multi-agent)
Cloud/Infra: Azure, Kubernetes, Docker, Terraform
DevOps: Azure DevOps / Pipelines, Git
Testing: xUnit, Playwright