Abdul Basit Banbhan

Personal update: I've joined Flinn.ai as an AI Engineer. Joining the Clinical Product Group to build Cursor for MedTech compliance.

@gklambauer Me leaving the uni and even more cool things are coming to JKU. FOMO is kicking in. :D

Open PhD and PostDoc positions!

Pretty cool stuff!

curious what goes into training an agentic coding model? join @srush_nlp, ML researcher at Cursor, for a walkthrough on how we built Composer 2 We'll cover: - continued pre-training + large-scale reinforcement learning - CursorBench for evaluating real-world coding tasks Join us at luma.com/b62tuosv?utm_s…

Yesterday, I was posting about Thinking Machines. Today, I woke up and saw this. Interesting timing.

Interesting times ahead...

Vienna>>>>Your City

How to make your engineering job application stand out (from the perspective of someone looking at hundreds of resumes): 1. Your resume should be one page. If you really need more space, link to a website. You don't need 10+ bullets for each job. 2. You will immediately stand out >90% of applications if you link a personal website that has some intentionality behind it. 3. If you are going to link your X, you might want to clean up your posts? Seems obvious but... people post some wild stuff. 4. You should link your GitHub. Please avoid doing a profile README that looks like a MySpace profile with the badges and images. I'm trying to look at code and your ability to build interesting ideas. 5. You should try to customize your application to the company. If you're applying to a startup, the courses you took in college probably don't matter as much. Maybe more if you're trying to make it through the ATS screening for FAANG. 6. I'm seeing a surprising number of resumes which don't talk about AI or agents at all. Software engineering is changing and it's a pretty fair assumption that you will be expected to learn or understand coding with AI for your job. That should be reflected on your resume and projects (and I'm not just saying this because I'm at Cursor). 7. Take your LinkedIn seriously. Most devs are here hanging out on X but surprisingly still most people will send around your LinkedIn internally. 8. Find ways to show your unique strengths/tastes/interests. It's nice to see people are smart, well-rounded, and thoughtful. Maybe this is a collection of books you enjoyed and why. Or some writing you've done. Or films you liked. At the end of the day, people want to work with other people they like and respect. If nothing else, it will be a good conversation starter ("oh I love [book] as well!"). 9. Do not use AI to write your cover letter or resume text. It's incredibly obvious, especially if you are applying to an AI company. You can still use it to ideate on ideas or phrases, but write it by hand (don't fall victim to the overused in-the-distribution-AI-phrases). See: /humanizer skill. 10. No photos on resumes. Save those for whatever you link out to. 11. Quality over quantity. 3 really good, thoughtful, detailed, interesting projects versus a wall of 27 AI-slop ones. Remember that hiring managers / recruiters are getting hundreds or thousands of applications for a role. They're not going to spend 20 minutes on every single application. You need to cut the cruft and get to the point. I hope this helps you stand out!

euromaxxing.

Pretty cool work!

Introducing /orchestrate, a skill that recursively spawns agents to tackle your most ambitious tasks with the Cursor SDK. We’ve used it to: - Autoresearch our internal skills, cutting token use by 20% while improving evals - Cut cold start times on our internal backend by 80%

We are hosting our next Cursor Meetup Vienna #3 luma.com/cursormeetup Looking forward to meeting you all!

I thought AGI was around the corner.. programbench.com

Nice event yesterday with @andreasklinger! Thanks to @tu_wien Robotics Club for organizing this great event.

this is cursor team kit: a plugin for some skills we use to build cursor at cursor skills for verifying changes, driving local tools, and shipping reviewable PRs cursor.com/marketplace/cu…

@benln We are just getting started!

Cursor community is everywhere. Coming to a city near you soon: cursor.com/community

cursor sdk launched yesterday! people are already putting cursor agents in places they already work: gmail, chrome, ci, terminal, docs github issues here are 11 projects built in the first day ↓

@benedictk__ Same here in Austria.

Please give me AI customer service. If you ever been to Germany you will know. Not bashing.

We’re introducing the Cursor SDK so you can build agents with the same runtime, harness, and models that power Cursor. Run agents from CI/CD pipelines, create automations for end-to-end workflows, or embed agents directly inside your products.