neoSign in
neoSign in
Senior Backend Engineer, Payments Reliability / Evidence review

Alex Morgan

Backend engineer, 7 years in payments and logistics · reviewed 8 Oct · example, fictional

View Alex’s profile

Alex's projects show direct work on two of the role's core problems: duplicate payouts and queue lag at peak load. Three requirements are supported with quotes. Postgres scale and mentoring aren't covered by any project yet. Alex's stated view on on-call differs from the role's one-week-in-six rotation.

6 requirementsEvidence supports · 3Still unclear · 2Discuss a difference · 1
Requirement (from brief)StatusReasonFrom Alex’s projects

Designing idempotent APIs for money movement

Evidence supports

Built idempotency keys for a payout service; duplicates stopped.

“I designed client-supplied idempotency keys, wrote the migration for two years of payout records and rolled it out behind a flag. Duplicates went to zero the next quarter.”

Self-reportedPayout retries at Fernway · Open project

Debugging distributed queues in production

Evidence supports

Found and fixed a hot-partition lag during peak load.

“I traced it to one hot partition keyed on warehouse ID and re-keyed by route. Lag stayed under two minutes for the rest of the season.”

Self-reportedRoutewise dispatch queue

Postgres performance on very large tables

Still unclear

Projects mention Postgres but not table sizes or tuning.

No project covers this.

Ask: What's the largest Postgres table you've tuned, and what changed?

Writing incident reviews that change practice

Evidence supports

Wrote a review whose actions became team defaults.

“Two of its five actions became team defaults, including no deploys on settlement days.”

Self-reportedMarch settlement outage review · Open project

Mentoring mid-level engineers

Still unclear

No project describes mentoring.

No project covers this.

Ask: Tell me about someone you helped grow. What changed for them?

Owning on-call for a payments service

Discuss a difference

Alex prefers to avoid on-call; the role includes one week in six.

“I'd rather not carry a pager as a main duty again.”

Self-reportedPreferences

Practical fit

Alex is in Montréal, inside the role's time zones. The role is hybrid, two days a week in Toronto; Alex asked for fully remote. Alex didn't state a pay range; the role offers CAD 175–195k base plus equity.

Questions for the conversation

4
  1. 1. On-call here is one week in six. What would make that workable for you?
  2. 2. What's the largest Postgres table you've tuned, and what changed?
  3. 3. Tell me about someone you helped grow. What changed for them?
  4. 4. Two office days in Toronto: is that possible from Montréal?