💻 Hiring: Graduate PMS Engineer - Elwood Technologies 📍 London | 💼 Full-time | 🧑‍💻 Golang, Postgres, Cloud | 💰 £50k | 🕐 2 hours ago - June 14, 2026 Elwood Technologies has built a digital asset trading infrastructure for institutional investors. The company provides an end-to-end, modular solution for execution, risk and portfolio management workflows. The company is seeking a recent graduate to join its engineering team and help develop the industry-leading Portfolio Management System while collaborating with product and quant teams. Excellent opportunity to launch a FinTech career. 📋 Responsibilities include: - Support iteration and refinement of PMS utilizing Golang. - Collaborate with Quant, Product and Engineering Teams on trading solutions and technical architectures. - Meet deadlines in a fast-moving release cycle. - Participate in architecture, implementation and QA of new capabilities. - Monitor live environments and handle troubleshooting. - Translate product strategy into technical implementation. - Use AI tools like Claude to enhance code quality. 🔑 Requirements: - Recent graduate with degree in CS, Engineering, Math or related technical field. - Foundational knowledge of Golang/C# or similar strongly typed languages (Java/C ). - Familiarity with Postgres and cloud tech (GCP/K8s, AWS). - Internship experience in financial markets is a plus. - Strong interest in digital assets and institutional markets. - Passion for software engineering and quality delivery. - Collaborative with excellent communication skills. 💡 Perks & Benefits: - Competitive salary & packages. - Full medical/dental coverage. - Generous vacation holidays. - Enhanced parental leave. - Stocked kitchen, gym discounts, EAP, study leave. 📩 To apply: Submit resume and cover letter via the Greenhouse portal. Applications reviewed on a rolling basis. 🔗 Original post: job-boards.greenhouse.io/elw… ⚠️ DYOR! I don’t verify every job. If someone asks to run files (even from GitHub) or ask for payment 🚩 likely a scam. ❗️ I'm not hiring myself! I just sharing fresh web3/crypto/blockchain roles DAILY for all levels! 💡 For Interns & juniors → t.me/crypto_vazima_english 💼 Mid/senior jobs → t.me/web3_jobs_crypto_vazima #Web3 #Crypto #Blockchain #FinTech #Hiring #Jobs #Engineering #Golang #London #Graduate #PMS #DigitalAssets #PortfolioManagement

Which database are you using for your product? - Supabase - Postgres - Firebase - MongoDB

Postgres gets a lot of love, but this result beautifully sums up why MySQL and InnoDB are still awesome.

I benchmarked Postgres vs Kafka as a job queue transport in Rust. Kafka had 77% lower per-job overhead and 40% higher throughput under real workload. Here's the full breakdown

google tanstack drizzlw linear (i think) zod posthog vercel sentry lodash better auth react postgres

Columnar performance inside familiar Postgres operational workflows is exactly the kind of upgrade path teams want for time-series workloads. github.com/xataio/deltax

The tech stack of 80% startups: - Frontend: React (because everyone uses React) - Backend: Whatever the CTO knew from his last job - Database: Postgres (or Mongo if someone watched a YT tutorial) - Auth: Copied from a blog post - Payments: Stripe (obv)

Indian tech firms want large profit margins. They pay peanuts to their employees who are happy with React.js & postGres working in shitty places like Hyderbad & traveling in Vande Bharat trains. With EMI paid tin can cars & pseudo SUVs.

Patron Launcher does not use: Github Actions, Vercel, Firebase, Supabase, Railway Its plain postgres docker on a VPS with bunch of python script for CI/CD. Only issue you need write or design that scripts. It takes a lot of time but teaches a lot.

This is the loop: Don't stop until you build a database better than Postgres

supabase gives a solo dev superpowers postgres auth storage edge functions row level security realtime generous free tier a backend team for $0 until you scale

Hiring : Software Engineer 📍Fully remote Employer: Sticker Mule Location: Worldwide (Remote) Salary:$150,000-$250,000/year Tech Stack: Go, TypeScript, React, GraphQL, Postgres, GCP Interested?????

3. The SQL Drafter I'm working in [database, e.g. Postgres, BigQuery]. Here are my tables and key columns: [paste]. Write the SQL to answer: [plain-language question]. Comment each step so I can follow the logic, and flag any join that could silently double-count rows. If there's a simpler or faster way to get the same answer, show that too.

Builders 👇 Which database are you using for your product right now? 🐘 Postgres ⚡ Supabase 🔥 Firebase 🍃 MongoDB And if you could start over today, would you choose the same one? 👀

i think you can do insane stuff with just deepseek hdbscan and postgres at this point

There is only a answer, Postgres

PostgreSQL, no contest.For a startup you want something reliable, scalable, and future-proof. Postgres gives you ACID compliance, great performance, JSON support, full-text search, and it scales well.

You mean if i login to my render dashboard i should not be able to see my deployed postgres credentials ?

Postgres

Every startup tech stack in 2026: Frontend: React. Because Airbnb used React. Airbnb has 10 million users. You have 12. Makes sense. Backend: Node.js. Because a Netflix engineering blog said it handles millions of requests. Your mom is your only user. She's not impressed. Database: Postgres. Unless someone watched a MongoDB tutorial at 2am. Then MongoDB. Then a painful migration back to Postgres. Then a Medium article about why Postgres was always the answer. Auth: Copied from a dev[.]to article written by someone with 3 followers. Never fully read. Currently holding your entire user data. Sleep well. Payments: Stripe. Only thing that works. Only thing you didn't build. Coincidence? No. Security: Copied the same blog post everyone copies. Added SSL certificate. Called it "enterprise grade security." Went to sleep. Documentation: The founder mentions it every Monday. Has been mentioning it since 2025. Tests: Users find the bugs. Engineers fix them at 2am. Same test suite used since launch. Called production. The entire stack was copied from a TechCrunch article about what Uber used in 2015. Uber had 3000 engineers. You have 3. But the blog said it was "production ready." So here we are.