<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Notebook | Tomás Taborda</title><description>Notes by Tomás Taborda on the projects on this site and on building software with AI.</description><link>https://tomastaborda.com/notebook/</link><language>en</language><item><title>AI-assisted development on my own portfolio</title><link>https://tomastaborda.com/notebook/ai-assisted-development-on-my-portfolio/</link><guid isPermaLink="true">https://tomastaborda.com/notebook/ai-assisted-development-on-my-portfolio/</guid><description>How I worked with an AI agent on this site&apos;s design: a brief of checkable outcomes, skills for design and writing, and scripts that measured the result.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I designed the first version of this portfolio by hand. LinkedIn and AI-made portfolios were then getting a lot of exposure, so I overhauled the visuals with AI. The overhaul worked and the content was real, but the design was heavier than it needed to be. Every section opened with the same scaffold: a small uppercase kicker with a section number and a meta suffix, a serif slogan under it, then cards with coloured chips. The “engineering notebook” idea was there five times over: section marks, dimension lines, a taped photo with a tilt, margin notes and red-pen underlines. None of them read as a choice, because all of them were on at once.&lt;/p&gt;
&lt;p&gt;The clean-up came from needing to scale that design back, because simpler is better. I did to it what my thesis argues you should do with AI in any phase of the work: write down what done means, let the agent do the work against it, and check the result with something other than the agent’s own opinion.&lt;/p&gt;
&lt;figure class=&quot;fig&quot; data-astro-cid-khyig4bw&gt;&lt;div class=&quot;fig-media&quot; data-astro-cid-khyig4bw&gt;&lt;img src=&quot;https://tomastaborda.com/_astro/deslop-home-before.B1iykZP6_ZOmVDS.webp&quot; srcset=&quot;https://tomastaborda.com/_astro/deslop-home-before.B1iykZP6_Z1OKD1G.webp 720w, https://tomastaborda.com/_astro/deslop-home-before.B1iykZP6_ZOmVDS.webp 1440w&quot; alt=&quot;The old home hero in dark mode: an uppercase red mono kicker, the name with a red full stop, a long tagline, a status dot, three buttons and a colour-coded graph with a legend.&quot; sizes=&quot;(min-width: 760px) 720px, 100vw&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1440&quot; height=&quot;860&quot;&gt;&lt;/div&gt;&lt;figcaption data-astro-cid-khyig4bw&gt;Before: the home page after the AI overhaul, with the uppercase mono kicker, the red full stop, three button styles, the colour-coded graph with its legend, and the § section label below.&lt;/figcaption&gt;&lt;/figure&gt;
&lt;figure class=&quot;fig&quot; data-astro-cid-khyig4bw&gt;&lt;div class=&quot;fig-media&quot; data-astro-cid-khyig4bw&gt;&lt;img src=&quot;https://tomastaborda.com/_astro/deslop-home-after.DkCJcliV_Z1WcVOD.webp&quot; srcset=&quot;https://tomastaborda.com/_astro/deslop-home-after.DkCJcliV_Z1QEj2I.webp 720w, https://tomastaborda.com/_astro/deslop-home-after.DkCJcliV_Z1WcVOD.webp 1440w&quot; alt=&quot;The new home hero in dark mode: a small grey line above the name, a two-line positioning sentence, a red View work button and a text link, and a grey graph of the path.&quot; sizes=&quot;(min-width: 760px) 720px, 100vw&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1440&quot; height=&quot;860&quot;&gt;&lt;/div&gt;&lt;figcaption data-astro-cid-khyig4bw&gt;After: one sans line above the name, a one-sentence positioning line, two buttons, a monochrome graph and a plain section label.&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2 id=&quot;the-brief&quot;&gt;The brief&lt;/h2&gt;
&lt;p&gt;The starting point was a brief I wrote myself, with ideas from Reddit threads on what makes a generated UI recognisable and with Claude’s help on the wording. It was specific about outcomes and left the method open:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;one serif and one sans, with mono only for code, dates and spec values;&lt;/li&gt;
&lt;li&gt;one type ramp, one radius, one accent colour and two button styles;&lt;/li&gt;
&lt;li&gt;no reveal-on-scroll, shadows, tilts or emoji used as icons;&lt;/li&gt;
&lt;li&gt;plain copy, with a banned list of phrases the overhaul leaned on (“reliable systems”, “with the spec as the anchor”, “drawn to”, “along the way”);&lt;/li&gt;
&lt;li&gt;keep the things that were mine: the hero glow, the dot grid, the wordmark and the dusk photo on the contact page.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It also carried the rules that apply to everything on this site: no phone number or address, and nothing invented. If a fact could not be checked, it became a visible TODO or was left out.&lt;/p&gt;
&lt;h2 id=&quot;the-pipeline&quot;&gt;The pipeline&lt;/h2&gt;
&lt;p&gt;I ran it in Claude Code with three skills installed, and Claude wrote a handful of scripts for the checks.&lt;/p&gt;
&lt;h3 id=&quot;impeccable-before-and-after&quot;&gt;Impeccable, before and after&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/pbakaus/impeccable&quot;&gt;Impeccable&lt;/a&gt; is a design skill with a critique command, an audit command and a rule-based detector for common generated-UI patterns. The critique before any change scored the site 27/40 on Nielsen’s heuristics, with a 1/4 on aesthetic and minimalist design. Its detector found 9 problems on the built pages, including 37 em dashes on the Apex page alone, numbered section markers on every section, a type hierarchy where the small sizes were 12, 14.4 and 15.2 px, and a callout with a coloured side stripe.&lt;/p&gt;
&lt;p&gt;After the pass, the audit scored 19/20. Updating Impeccable from 3.9 to 4.8 near the end was worth it: the new version renders each page at desktop and mobile widths and found problems the first one could not see, such as chart labels around 9 px, chart years at 3.2:1 contrast over the hero glow on mobile, and logo tiles with no padding. All of those are fixed. The one finding left was the cream page background, which I kept at that point.&lt;/p&gt;
&lt;h3 id=&quot;humanizer-for-the-copy&quot;&gt;Humanizer for the copy&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/blader/humanizer&quot;&gt;humanizer&lt;/a&gt; rewrites text that reads as generated: “not X but Y” contrasts, one-line closers, forced lists of three, dashes everywhere, bold labels used as decoration. It ran over every visible string in English and Portuguese. The UI strings and most data files needed nothing by then. The posts and the Apex page data did: it removed several “rather than” contrasts, a closing paragraph that repeated the opening of a post, and closers such as “Confidence is not evidence” that restated the sentence before them. The rule I cared about most was that it keeps facts and adds none. The dissertation abstract and the thesis statement stayed verbatim.&lt;/p&gt;
&lt;h3 id=&quot;frontend-design-as-a-second-opinion&quot;&gt;frontend-design as a second opinion&lt;/h3&gt;
&lt;p&gt;The frontend-design skill lists the traits generated pages cluster around right now. Two of them applied to this site: the warm off-white background with a serif display, and uppercase section labels with &lt;code&gt;·&lt;/code&gt; meta lines. The brief set both, so they stayed at first; a later critique pushed me to drop the uppercase labels and, in the end, the warm background too. Everything else on that list (one-word headline accents, numbered markers, entrance animations on every section, card shadows) is gone.&lt;/p&gt;
&lt;h3 id=&quot;measured-checks&quot;&gt;Measured checks&lt;/h3&gt;
&lt;p&gt;The part I would keep for any project is the verification. Claude wrote small Playwright scripts that measured the built site:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a metrics script that reads the computed style of every visible text element on 7 pages, at 2 widths and in 2 themes, and reports font families, type sizes, radii, uppercase count, accent uses per screen and contrast failures;&lt;/li&gt;
&lt;li&gt;27 function checks: theme toggle, language switch, filters, copy buttons, the mobile menu’s focus trap, no horizontal scroll;&lt;/li&gt;
&lt;li&gt;a link checker over every built page and every external link;&lt;/li&gt;
&lt;li&gt;Lighthouse on 8 pages, mobile and desktop.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The result, measured: 7 type sizes (14, 16, 17, 20, 28, 40 and 56 px), radii of 4 px and a pill, at most 2 accent uses per screen, not counting the wordmark, 0 contrast failures, 0 broken internal links, and Lighthouse performance between 98 and 100 with 100 everywhere else. Before and after screenshots of 6 pages, at 2 widths and in 2 themes, are in the repository next to a report that maps each line of the brief to its evidence.&lt;/p&gt;
&lt;h2 id=&quot;where-my-judgement-still-mattered&quot;&gt;Where my judgement still mattered&lt;/h2&gt;
&lt;p&gt;Some decisions stayed with me.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The brief asked for a short list in the home Experience section. Once I saw it live, it was a boring list next to an Education timeline with logos, so Experience now uses the same timeline.&lt;/li&gt;
&lt;li&gt;The brief kept the hero glow as brand. Later I toned its violet down to a faint corner, because on a dark screen it was the loudest thing on the page.&lt;/li&gt;
&lt;li&gt;The detector flagged the cream background. I kept it for a while because I liked it, knowing it is one of the most common generated defaults, then replaced it with a neutral off-white and re-checked the colour pairs.&lt;/li&gt;
&lt;li&gt;Two steps ran degraded and the report says so: the humanizer install was blocked the first time, so the first copy pass applied its rules by hand, and the before-critique ran in one context where Impeccable asks for two independent assessments.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;a-second-round&quot;&gt;A second round&lt;/h2&gt;
&lt;p&gt;On 5 November I ran the same three skills over the site again. The critique scored 20/32, which can’t be compared with the earlier 27/40: the method differed and two heuristics did not apply. The screenshots above show the end of the first pass, so they no longer match the site in every detail.&lt;/p&gt;
&lt;p&gt;Most of what came out of it was structural or small:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Work moved up the home page, with the Apex diagram, and the Apex page got a section bar and a shorter head.&lt;/li&gt;
&lt;li&gt;Uppercase section labels became sans headings, and the cream background became a neutral off-white.&lt;/li&gt;
&lt;li&gt;The contact form got a request timeout, announced errors and a visible focus state.&lt;/li&gt;
&lt;li&gt;The phase strip, commit graph and heatmap became reachable by keyboard, and standalone links reached a 24 px target.&lt;/li&gt;
&lt;li&gt;The humanizer pass found copy that was correct but thin. The thesis appeared in nearly the same sentence three times on the home page, and the Outfolio card never said what Outfolio is.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Two of the fixes came from me looking at the deployed site. Arrows were still on some links, so I asked for plain text everywhere. The work cards were unbalanced, with empty space on the projects without screenshots, and the Apex card differed between the home and work pages. Now there is one Apex card and the project cards are equal and text-only.&lt;/p&gt;
&lt;p&gt;The larger finding was the Apex ledger, a hand-built page that the first pass had never measured. It had its own violet accent, heading font and theme toggle, 31 uppercase elements and no Portuguese version. The detector reported 55 findings there and 0 on the main pages. My own rescore of the audit, from axe, the detector and the screenshots, came to 15/20 against the earlier 19/20, partly because it now counted that page.&lt;/p&gt;
&lt;p&gt;I had Claude rebuild the ledger inside the site’s design, in both languages, and then ran everything again. Lighthouse found a layout shift of 0.177 on the Portuguese home page on phones, caused by a font arriving late. Preloading it fixed that. The same check showed three font files that every page downloaded and no page used, so those went too, which then widened every paragraph, because the browser had been measuring &lt;code&gt;ch&lt;/code&gt; from one of them. The detector caught that with 22 line-length findings, and the text width went back to what it was.&lt;/p&gt;
&lt;p&gt;The final run: Lighthouse on 11 pages, mobile and desktop, scored 99 to 100 on performance and 100 on everything else. The detector reports 0 findings on the built pages at both widths, axe is clean on 12 pages at 2 widths in 2 themes, and the metrics script reads 7 type sizes and 0 uppercase elements, leaving out chart labels inside SVGs. My rescore of the audit is 19/20. A new critique, run by a separate Claude agent that had not seen the earlier scores or the detector output, gave 24/32. Its main point matches the audit point I held back: serif and crimson on off-white is still a familiar look, and the path tracing, the site’s one original idea, did not reach phones. So I took that up after the critique: the path now runs down the phone hero and along the Experience and Education timelines in crimson, and the pink wash in light mode is almost gone. That gives up the limit of 2 accent uses per screen from the first pass, on purpose.&lt;/p&gt;
&lt;h2 id=&quot;what-i-would-reuse&quot;&gt;What I would reuse&lt;/h2&gt;
&lt;p&gt;Write the brief as a list of checkable outcomes. Give the agent skills that encode taste, so it is not inventing a design language from scratch. Then measure the result with scripts, on every page, and keep the evidence in the repository. The same agent did the overhaul and most of the clean-up; the second time it had a brief and checks to answer to.&lt;/p&gt;</content:encoded><category>ai</category><category>design</category></item><item><title>Defending Apex: hard, mostly good, and fair criticism</title><link>https://tomastaborda.com/notebook/defending-apex/</link><guid isPermaLink="true">https://tomastaborda.com/notebook/defending-apex/</guid><description>Notes from my MSc defence on 23 October 2026: what was hard, what went well, and what the jury was right to push on.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I defended my MSc dissertation, &lt;em&gt;Governed Human-AI Collaboration Across the Software Development Lifecycle&lt;/em&gt;, at Instituto Superior Técnico on 23 October 2026, sixteen days after submitting it. I had twenty minutes to present six months of work: a framework for bounding what AI does at each phase of the lifecycle, and Apex, the working tool that implements it. The dissertation was graded 17/20.&lt;/p&gt;
&lt;p&gt;It was harder than I expected and went well overall, and I agree with most of the criticism I got.&lt;/p&gt;
&lt;h2 id=&quot;why-it-was-hard&quot;&gt;Why it was hard&lt;/h2&gt;
&lt;p&gt;Twenty minutes is not much for a framework with six phases, five quality gates, three governance metrics, a hat model and a reference implementation. Most of the preparation went into deciding what to leave out and walking through the phases one at a time, so the evaluation got less room than it deserved.&lt;/p&gt;
&lt;p&gt;The moment I did not expect came from the jury’s president. I saw the practitioner and expert interviews as one of the stronger parts of the evaluation. The president saw semi-structured conversations, used too casually to count as a rigorous evaluation instrument. That was fair, and the evaluation should have been more rigorous.&lt;/p&gt;
&lt;h2 id=&quot;what-went-well&quot;&gt;What went well&lt;/h2&gt;
&lt;p&gt;The framework held up. Its central idea is that every phase states what AI may contribute, what it must produce, who is accountable and what gate closes it. That came through, and so did the honesty of the results. Apex scored below average on usability (SUS 56.73, grade D) and the thesis says so. I put those numbers on the slides, and I think showing them helped more than it hurt.&lt;/p&gt;
&lt;h2 id=&quot;what-the-jury-pushed-on&quot;&gt;What the jury pushed on&lt;/h2&gt;
&lt;aside class=&quot;callout&quot; data-type=&quot;note&quot; data-astro-cid-q2ml7llr&gt;&lt;p class=&quot;callout-label&quot; data-astro-cid-q2ml7llr&gt;Note&lt;span class=&quot;callout-title&quot; data-astro-cid-q2ml7llr&gt;: The criticism, in short&lt;/span&gt;&lt;/p&gt;&lt;div class=&quot;callout-body&quot; data-astro-cid-q2ml7llr&gt;&lt;p&gt;The method was sound in intent but not fully rigorous in execution.&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;h3 id=&quot;the-dsrm-format&quot;&gt;The DSRM format&lt;/h3&gt;
&lt;p&gt;The dissertation follows Design Science Research Methodology: identify the problem, define objectives, design, demonstrate, evaluate, communicate. The jury’s president questioned how I applied that structure. In places the chapters follow DSRM’s activities more closely than the research needed, so the method shaped the document more than the decisions.&lt;/p&gt;
&lt;h3 id=&quot;an-evaluation-that-was-too-casual&quot;&gt;An evaluation that was too casual&lt;/h3&gt;
&lt;p&gt;Thirteen participants, one unmoderated session each, one seeded project, a sample drawn from my own network, and instruments that measure perception and say nothing about delivered quality. I listed all of these as threats to validity in the dissertation, but listing a limitation does not remove it. The evaluation describes how thirteen people experienced the tool; it does not show that the framework works for teams.&lt;/p&gt;
&lt;h3 id=&quot;consistency-of-roles&quot;&gt;Consistency of roles&lt;/h3&gt;
&lt;p&gt;The framework assigns work to functions it calls &lt;em&gt;hats&lt;/em&gt;. Some roles mentioned elsewhere in the text were missing from the main role table, so the model looked less closed than it is. I fixed this in the final version I submitted after the defence.&lt;/p&gt;
&lt;h2 id=&quot;what-i-would-do-differently&quot;&gt;What I would do differently&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Design the evaluation before the tool. The usability study was planned around a tool that already existed. Deciding first what would prove the framework wrong, and building toward that, would have made the study sharper.&lt;/li&gt;
&lt;li&gt;Get a real team involved early. The partner-organisation demonstration never happened. One team that did not design the framework, using it on their own project, would have told me more than thirteen solo sessions.&lt;/li&gt;
&lt;li&gt;Use the methodology lightly. DSRM is useful for thinking, but it should not dictate the table of contents.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The thesis also came up somewhere I did not expect: &lt;a href=&quot;https://tomastaborda.com/notebook/job-hunting-with-an-ai/&quot;&gt;it was the main topic of my final job interview&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://tomastaborda.com/work/apex/&quot;&gt;case study&lt;/a&gt;, the dissertation PDF and the code at &lt;a href=&quot;https://github.com/thomastabs/apex&quot;&gt;github.com/thomastabs/apex&lt;/a&gt; are public, weaknesses included.&lt;/p&gt;</content:encoded><category>thesis</category></item><item><title>From thesis to OpenSoft: job hunting with an AI in the loop</title><link>https://tomastaborda.com/notebook/job-hunting-with-an-ai/</link><guid isPermaLink="true">https://tomastaborda.com/notebook/job-hunting-with-an-ai/</guid><description>How I used Teamlyzer and Claude to research companies and prepare for OpenSoft&apos;s three-phase interview, and why the job fits my thesis.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I finished my MSc in October 2026 and spent the weeks around it looking for my first full-time engineering role. My dissertation argued that AI is most useful when the process around it is explicit: who decides, what gets checked, and what counts as done. I applied the same rule to my job search. Claude did the research and the drafting. I made the decisions.&lt;/p&gt;
&lt;p&gt;On 16 November 2026 I start as a Software Engineer at OpenSoft.&lt;/p&gt;
&lt;h2 id=&quot;the-problem&quot;&gt;The problem&lt;/h2&gt;
&lt;p&gt;Applying well takes time. A good application needs research on the company, a cover letter that answers the job ad point by point, and preparation for an interview format I usually only half know. When I do that for several companies at once, the quality drops. Letting a model write the letters saves the time and produces generic letters.&lt;/p&gt;
&lt;h2 id=&quot;what-i-tried&quot;&gt;What I tried&lt;/h2&gt;
&lt;h3 id=&quot;teamlyzer-first-for-every-company&quot;&gt;Teamlyzer first, for every company&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://pt.teamlyzer.com&quot;&gt;Teamlyzer&lt;/a&gt; collects reviews of Portuguese tech companies from people who work there and from people who interviewed there. I used it constantly: to decide where to apply at all, to read how a company treats its engineers, and to see what its interviews look like. Before preparing anything, I wanted to know what past candidates had been asked.&lt;/p&gt;
&lt;h3 id=&quot;one-cover-letter-per-role-built-from-the-ad&quot;&gt;One cover letter per role, built from the ad&lt;/h3&gt;
&lt;p&gt;For each application, I pasted the job description and Claude drafted a letter that mapped each requirement to something I have done: the Gescol HR module at Caixa Mágica, teaching in the AI Agents bootcamp, Apex. My rule was that every claim had to point to a real project. If it couldn’t, the claim went. I edited each draft line by line and wrote the opening myself.&lt;/p&gt;
&lt;h3 id=&quot;a-study-plan-built-from-what-candidates-report&quot;&gt;A study plan built from what candidates report&lt;/h3&gt;
&lt;p&gt;For OpenSoft, I asked Claude to turn the 25 interview reviews on Teamlyzer into a study plan built around what those candidates were asked. The reviews described a friendly process, rated 2.1 out of 5 for difficulty, with a technical part covering Java, OOP, SQL and LeetCode-style problems.&lt;/p&gt;
&lt;aside class=&quot;callout&quot; data-type=&quot;decision&quot; data-astro-cid-q2ml7llr&gt;&lt;p class=&quot;callout-label&quot; data-astro-cid-q2ml7llr&gt;Decision&lt;span class=&quot;callout-title&quot; data-astro-cid-q2ml7llr&gt;: Cut what nobody asks&lt;/span&gt;&lt;/p&gt;&lt;div class=&quot;callout-body&quot; data-astro-cid-q2ml7llr&gt;&lt;p&gt;No review mentioned JVM internals, concurrency or JDBC, so those became quick skims, and the time went to live-coding drills and SQL instead.&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;p&gt;The result was a fourteen-day plan, from 7 to 21 October, of about two to three hours a day. Each day mixed Java theory (a 105-question bank), live coding (25 drills, done timed and thinking aloud) and SQL (joins, GROUP BY, normalisation, schema design on paper first). The last days were two mock interviews, both in Portuguese, because I wanted to practise saying the answers out loud.&lt;/p&gt;
&lt;h2 id=&quot;the-interview-phase-by-phase&quot;&gt;The interview, phase by phase&lt;/h2&gt;
&lt;p&gt;The real process matched what Teamlyzer had described.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Background interview: a conversation to get to know me: my academic path, the projects I had worked on, and what I was looking for.&lt;/li&gt;
&lt;li&gt;Technical interview, in two parts:
&lt;ul&gt;
&lt;li&gt;Java: one live-coding problem, plus theory questions on object-oriented programming and the language itself.&lt;/li&gt;
&lt;li&gt;Databases: I designed the schema for a camera system with three tables: the photo, its metadata and its location, and how they relate. Then came theory questions on databases.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Cultural interview, the conversation I enjoyed most. We ended up talking mostly about my thesis (&lt;a href=&quot;https://tomastaborda.com/notebook/defending-apex/&quot;&gt;the defence has its own post&lt;/a&gt;), because OpenSoft had been working on the same problem.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;why-opensoft-fits&quot;&gt;Why OpenSoft fits&lt;/h2&gt;
&lt;p&gt;My dissertation asks how to use AI across the software lifecycle without losing rigour, traceability and quality. OpenSoft deals with that every day. The company is certified under ISO 9001 (quality management) and ISO 27001 (information security), and is appraised at CMMI-DEV v3.0 maturity level 3. In practice, full traceability from requirements to architecture, user stories and code is part of how they deliver software.&lt;/p&gt;
&lt;p&gt;That is the chain Apex tries to keep intact when AI enters it. In our conversations after the interviews, they said the work could feed into their own innovation efforts. I am joining a team that already works the way my thesis argues software should be built, and that wants to find out how AI fits into it.&lt;/p&gt;
&lt;h2 id=&quot;what-i-would-tell-someone-doing-the-same&quot;&gt;What I would tell someone doing the same&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Read what candidates say before you study. Teamlyzer told me more about the interview than any job ad. “Prepare me for a Java interview” gets you a textbook. “Prepare me for this company, based on what its candidates report” gets you a plan.&lt;/li&gt;
&lt;li&gt;Keep your own voice. The drafts were useful because I rewrote them. A recruiter reads many letters a day and can tell which ones were written for them.&lt;/li&gt;
&lt;li&gt;Practise out loud. Most of the gain came from the mock interviews.&lt;/li&gt;
&lt;li&gt;Bring your own work into the room. Most of the final interview was about the thesis.&lt;/li&gt;
&lt;/ul&gt;</content:encoded><category>career</category><category>ai</category></item></channel></rss>