PickBoard | Remote | Full time The job in one line

- You will be the third engineer at a company building the social network for smarter investing, and you will own product surfaces end to end from your first month.

Why this role exists

- PickBoard makes the best free investing content easy to find, follow, and discuss in one place. Creators and financial publishers claim a profile, connect their sources, and keep the audience they built. Readers get one feed instead of ten tabs.

- Two engineers carry the codebase today. You are the third. That is a fifty percent increase in build capacity, which means two things: the bar is high, and nothing you build will be busywork. Features you ship will be in front of users and publishers within the quarter.

What you will own

- Backend. Features in PHP 8.1 and Laravel 8. Database models, migrations, queries, and the performance of both. Queues for ingestion work that cannot run inline.

- Frontend. Interactive experiences in Vue.js 2 with Vuex and Vue Router. Feeds that stay fast on an old phone and a slow network, because that is what a large share of our users are on.

- APIs. Design and consume REST. Every controller serves two paths: JWT for the mobile app, session for the web SPA. Getting that mirroring right is the single highest leverage habit on this team.

- Integrations. Stripe, AWS S3, Google, Microsoft, Apple, and Alpaca. Webhooks, retries, idempotency, token refresh, and the failure modes nobody sees until money is involved.

- Product surfaces. Authentication, user permissions, subscriptions, payments, portfolios, and publishing.

- Mobile. Support the iOS application through Capacitor, including the things that work on web and break on device.

- Quality. Automated tests with PHPUnit, performance work, troubleshooting, and raising the standard of the code you touch. You will collaborate with product, design, and engineering through Git.

Your first ninety days





- Days 1 to 30. Environment running, app on device. Read the content rules and three feature handoff docs. Ship one flagged fix end to end. Write down the five things that confused you and send them to us. That list is a deliverable, not a courtesy.

- Days 31 to 60. Take one feature from design to flagged merge. Write its handoff doc. Present the tradeoffs you cut and why.

- Days 61 to 90. Pick a metric that matters — creator activation, ingestion reliability, signup completion — move it, and report the number.

What we need from you

- Several years shipping production web applications, with deep hands-on PHP and Laravel. We care about depth and ownership, not the year count on your resume.
- Practical Vue.js and modern JavaScript. Vue 2 specifically is a plus, not a barrier.
- REST API design plus real relational database work: modeling, migrations, indexes, and fixing the query that is quietly costing you 200 round trips.
- Authentication, authorization, and application security in production, not in theory.
- Third-party API and payment platform integration. You have debugged a webhook that fired twice and know why that matters.
- Comfort working independently inside an existing codebase, with Git and collaborative review.
- Clear written technical English. Most decisions here live in writing, in handoff docs a stranger has to be able to run cold.

Nice to have, not required

- Capacitor or hybrid mobile. Introducing tests to a codebase that does not have a working suite yet. Brokerage or market data APIs such as Alpaca. Platform APIs like YouTube, X, or Meta. Planning a Laravel major version upgrade without freezing a roadmap. Spanish.

What is hard about this job

We would rather tell you now than in week three.

- Compliance is not overhead here. Content rules from platform terms, publisher agreements, and App Store review constrain what we are allowed to build. Breaking one is a company level incident.

📌 Senior Software Engineer (México)
🏢 PickBoard.com
📍 México