Senior Frontend Engineer

Job description

Join us in building the ultimate online playground! Poki is on a mission to create the ultimate online playground, bringing easy access to the best games on web to over 100 million monthly players worldwide. These games are created by a dynamic global community of 500+ game developer teams. At the core of our work lies a simple belief: play is how we learn. This value is embodied by our team of 70 unique individuals who each bring something special to the table. What this job is about As a senior Frontend Developer at Poki, you'll shape how players experience our platform. All the way from the first vague problem to what happens after release. That might mean improving discovery on a slow connection, running an experiment, building a tool for our Content team, or fixing a part of the stack everyone has quietly learned to work around. This is a senior role. That means we're looking for judgement, not just throughput. Your Challenge as a senior Frontend Developer Frontend that works on real devices. That means a three-year-old Android phone on unreliable wifi, not just the MacBook that will run anything you throw at it. If it only feels smooth on your machine, it is not done. Clear work from vague problems. You turn "players are leaving on slow connections" into a sensible scope, a first slice and a clear opinion about what can wait. Results you can point at. Decide what success looks like before you build, then use A/B tests and our data to see if you got there. If nothing moves, say so. Sometimes the right result is killing the thing you just built. Ownership in production. You build in enough monitoring to know when your work breaks, then stay with it until it is fixed. Shipping is the start of ownership, not the end. A stronger engineering team. Your reviews teach, your pairing unblocks people and the patterns you leave behind make the next piece of work easier. A stack and a codebase that survive contact with other people. You understand what still earns its place, what is hanging around through habit, and when changing it is worth the cost. What you leave behind, code and reasoning both, still makes sense six months later when the context is gone and somebody else needs to change it. Visible progress in small slices. Something useful in a week beats something theoretically perfect in two months. It also tells you much sooner when the idea was wrong. You…