Posting record
Open 12+ days
- Grvt's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Grvt, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
What You’ll Do
- Design, implement, test, and operate production systems in a complex trading environment.
- Own the correctness, reliability, and operability of the features you build.
- Actively surface and resolve ambiguity in requirements, product logic, and system behavior.
- Write clear, maintainable code with a strong bias toward simplicity and correctness.
- Participate in incident response and follow through with durable fixes and improvements.
- Collaborate closely with peers through code reviews, design discussions, and shared problem-solving.
What We’re Looking For
- Strong engineering fundamentals and sound judgment in complex systems.
- A demonstrated bias toward correctness, reliability, and production ownership.
- Comfort reasoning about non-trivial business logic, stateful systems, and edge cases.
- Consistent self-directed productivity in ambiguous or loosely scoped work.
- Clear, collaborative communication and a strong team-oriented mindset.
Nice to Have
- Experience with trading systems, exchanges, or other high-stakes domains.
- Production experience with Go (Golang) or performance-sensitive backend systems.
- Prior ownership of services in production, including on-call or incident response.
This Role Is Not a Fit If
- You prefer narrowly scoped tasks with fully specified requirements.
- You avoid production ownership or incident responsibility.
- You optimize primarily for speed or novelty over correctness and clarity.
- You are uncomfortable working in systems with significant complexity and real-world consequences.
Something wrong with this posting?