Yes the title is how many decimal places I remember Pi to…
This week landed clean, practical changes you can actually ship: Python 3.14 went GA, Ruff and FastAPI both moved, and Pydantic shipped 3.14 support. If you maintain infra, this is a good window to bump, test and lock. If you’re interviewing, it’s also a good week to tighten prep because loops are getting stricter across the board.
Python 3.14.0 is out as the new stable. If you own images or packaging, start running your test matrix now and note that many libs have already lined up 3.14 support. Release post and highlights are live.
Tooling kept pace. Ruff 0.14.0 dropped on the 7th and updates defaults for Python 3.14. If your pre-commit still targets the 0.13 line, bump so everyone formats and lints against the same rules.
Frameworks moved too. FastAPI 0.119.0 landed on Saturday; if you maintain a service template, plan a weekday upgrade and skim the notes about the fastapi[standard] install including the FastAPI Cloud CLI so fastapi deploy is available by default.
Packaging: uv cut three tags this week (0.9.0, 0.9.1, 0.9.2). If you are trialing uv in CI, pin one of the 0.9.x tags and record “time to green” before and after. The release stream is active enough that you should lock versions between deploys.
Ecosystem support notes worth banking: pandas 2.3.3 is 3.14-compatible, which removes one of the last blockers for teams planning a minor bump this quarter. Pydantic 2.12.0 shipped on release day with initial 3.14 support. If any of your services still rely on Pydantic V1, note that V1 is not compatible with 3.14 so you will want a clear migration plan.
Security remains noisy. Phishing against PyPI maintainers has continued from late September, with warnings to avoid look-alike domains and enable phishing-resistant 2FA. If your org publishes to PyPI, rotate any tokens used from CI in the last month and audit recent install events for suspicious names.
Now the human part. Interviews are tougher right now. I’m seeing tighter CV screens, higher writing standards, stricter technical bars and closer behavioural reads. That lines up with what larger surveys show: talent teams are leaning harder into skills-based evaluation and structured loops, and many companies are adding or tightening assessments to raise quality of hire.
There is some evidence this is the right direction. Structured interviews and work samples are consistently among the best predictors of on-the-job performance, which is exactly why more teams are standardising questions, using short take-homes, and scoring against rubrics. In other words, the bar isn’t just higher; it’s clearer.
If you’re a candidate, here’s the plan for this week:
Tighten your CV to one page (two if you are senior with relevant scope). Make the top third do the work: role, stack, impact, scale. Then link to code or talks if you have them. This is what survives first pass.
Prepare like it’s an exam. Do three timed LeetCode mediums that match your target roles, write a clean second pass with tests, and be ready to talk trade-offs.
Expect structured questions and behaviour checks. Practice concise answers that show ownership, debugging under pressure, and delivery.
All of this is baked into the Interview Prep hub: targeted LeetCode sets, a technical Q&A, and a short guide that maps the whole loop. Start here: https://snakesignals.com/#interview-prepCandidates are failing on over usage of AI during take home tasks and not being able to explain what has been written in follow ups - AI is fine but you need to know what and how it’s working.
If the website has helped already or might help in the future, share it with someone who builds or hires in Python. New readers can join at snakesignals.com.
Hiring? Contact:
Josh Smith
LinkedIn: https://www.linkedin.com/in/python-recruitment/
Email: [email protected]
Phone: 01727 225 552