Most engineers are handed a ticket. At SchooLinks, you own the whole journey.

Our Product Engineers aren't members of a feature team. They are the feature team. You'll start from a problem or a goal, figure out what to build, design the experience, implement it, test it, ship it, and communicate it. No PM to translate for you. No designer to hand you mocks. No QA to catch your bugs before users do. That's not a gap in our process. It's the role.

We're looking for engineers who get uncomfortable when they're too far from the outcome. Who have opinions about UX, not just code quality. Who find product thinking as natural as system design. Who take it personally when something they built doesn't land with users, and who fix it without being asked.


What this looks like in practice

+ You receive context on a user problem or business goal, not a spec

+ You define your own requirements, break down the work, and manage your own scope

...